Re: Re: [bitpim-cvs-checkins] bitpim midifile.py,NONE,1.1 fileinfo.py,1.11,1.12

>>Ok. I'll remove the check since it was only there due to my bad code.
> 
> I would keep it since having gone through this excercise, I don't trust 
> those mp3 files available out there any more :-)

Yes, but bad files could be off by more than one byte in either direction.
The code was failing on mp3 produced by ffmpeg which was a critical
problem.

I would much rather not be lenient in what we accept, and then when
failures happen analyse why it is happening and address it then.
Your fixed code hasn't had any issues on any mp3 files I have thrown
at it.

>>I would recommend just doing a seperate dialog using the ranged >slider.
> 
> Should we add this capability (possibly via the context menu) to all 
> audio formats that can be trimmed?

Sure.  I think it is fairly low priority since people can always 
re-import the originals and do the chopping then.  And for midi files,
the only people who have originals are musicians and the like and
they already have way better tools for clipping them.  QCP clipping
probably would be the most useful.

If you are looking for another challenge, see if you can figure out
the motion jpeg format and what on earth ffmpeg produces for it.
(They don't seem to add up.)

The goal is to display videos in the wallpaper pane at about one
frame per second.  My idea was to convert the video to mjpeg
and then extract the frame for the start of each second as a
jpeg.  Finally the wallpaper pane would display the next frame
as each second ticks by.  This is all to give a preview of the
video content, not to actually play it.  To play and edit etc
the user will need an appropriate media player.

Roger


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt