I just loaded the pix_film example from Guenter's CVS version. Upon loading the alea.mpg file from the distro pix_film reports -1 frames, and scrubbing the frames simply advances the frame by one each time the number changes (in either direction) The mov works fine.
Ben
Ben Bogart - FMPM/F1999 wrote:
I just loaded the pix_film example from Guenter's CVS version. Upon loading the alea.mpg file from the distro pix_film reports -1 frames, and scrubbing the frames simply advances the frame by one each time the number changes (in either direction) The mov works fine.
this is not really a bug, but looks like compiled with libmpeg1 rather than libmpeg3 this means, that movie-files are interpreted as streams, which have no known length, and thus are set to 1
mfg.dsa.cas IOhannes
Thanks Johannes,
If only everything was that easy a fix! ;)
I had to link include/mpeg3 -> include/libmpeg3
Thanks Ben
On Wed, 10 Jul 2002, IOhannes zmoelnig wrote:
Ben Bogart - FMPM/F1999 wrote:
I just loaded the pix_film example from Guenter's CVS version. Upon loading the alea.mpg file from the distro pix_film reports -1 frames, and scrubbing the frames simply advances the frame by one each time the number changes (in either direction) The mov works fine.
this is not really a bug, but looks like compiled with libmpeg1 rather than libmpeg3 this means, that movie-files are interpreted as streams, which have no known length, and thus are set to 1
mfg.dsa.cas IOhannes
On Wed, 10 Jul 2002, IOhannes zmoelnig wrote:
this is not really a bug, but looks like compiled with libmpeg1 rather than libmpeg3 this means, that movie-files are interpreted as streams, which have no known length, and thus are set to 1
I found the libmpeg1 somehow very buggy, and furthermore it just does an "exit" when it fails to load a file, which leads to surpises somehow.
libmpeg3 is not very accessible, so I vote to support the following libraries:
http://libmpeg2.sourceforge.net/ http://avifile.sourceforge.net/
For the beginning we could include the two versions in the GemLibs tarball.
Guenter
? wrote:
I found the libmpeg1 somehow very buggy, and furthermore it just does an "exit" when it fails to load a file, which leads to surpises somehow.
libmpeg3 is not very accessible, so I vote to support the following libraries:
http://libmpeg2.sourceforge.net/ http://avifile.sourceforge.net/
i have used libmpeg3 because it was more stable and had more features than libmpeg1. I didn't know about libmpeg2 and it's features.
however, since i knew that libmpeg3 wasn't that available i thought it would be best to configure it out, which one to take
of course, avifile has to be included...
For the beginning we could include the two versions in the GemLibs tarball.
i have always thought of the GemLibs to provide libraries that are not packaged (with debian as the reference distribution) but seeing, that libmpeg2 is cross-platform (at least linux/windoze) (and not very big) this is a very strong reason to add it to the GemLibs
mfg.ds.dar IOhannes
I just loaded the pix_film example from Guenter's CVS version. Upon loading the alea.mpg file from the distro pix_film reports -1 frames, and scrubbing the frames simply advances the frame by one each time the number changes (in either direction) The mov works fine.
Ben
B. Bogart
hey ben,
...assuming that you are talking about the OS X version, this is known, and has to do with the way that quicktime loads .mpg's, in addition to the way that pix_film plays movies...basically, quicktime can't tell how many frames there are in advance in an mpg, and I haven't found a way around this that I like...so, with os X, we're kinda stuck with formats that quicktime knows about...
btw, did you get my email last nite? something seems to be screwy with eudora all of a sudden...but I had written about a new idea on how to copile your external with project builder...
l8r, jamie