Joseph Barrows wrote:
thanks IOhannes,
i'm trying to avoid needing to build it myself, 've been using pd/gem for a few years, started with the planet ccrma system, after having broken my linux system several times and having to re-install i decided to try ubuntu and stick with a policy of install stable version (when will pd hit version 1.0?)
i don't think that there are any plans to move to 1.0 ever. (but of course i really don't know; i am not making the version numbers)
use ffmpeg : no (forced)
hmm, maybe i should compile it myself then
probably not. ffmpeg support in Gem is not something i would consider stable. (the API is changing so fast...)
"mpeg" and "mpeg-3" are just able to decode mpeg-file, which you don't seem to care about right now.
onl;y because i need the number of frames, and pixmovie always seems to return "0" for mpeg files (i have build a video player that fades between clips, and so it needs to know when a clip is about to end)
i see, does it help if you create a table-of-contents first? iirc, there is a tool mpeg3toc which will create TOC from an mpeg-file which can then be fed into [pix_film] to allow frame accurate accessing of mpeg-files (and probably the exact number of frames in the file).
otoh, it seems that this has stopped working some time ago...
probably you should just check.
the funnier parts are quicktime and aviplay; these APIs both support a number of codecs depending on how they were compiled and/or which codecs they find on your harddisk.
even funnier is that my linux machine now plays more in PD than it does in VLC, something has gone wrong again ...
hmm, i would rather say that this is cool. watchout, one day Pd/Gem will be the most universal movie-player ever.
gem still causes PD to completely die when given a video file it doesn't like.
which is not fine. i suspect that it is libmpeg1 (if it is really used; check out which APIs are really supported when creating the first [pix_film]) - this library is highly unstable; it's only in the code in case libmpeg3 is missing and you still want to decode mpeg-files.
mfgads IOhannes
use ffmpeg : no (forced)
hmm, maybe i should compile it myself then
probably not. ffmpeg support in Gem is not something i would consider stable. (the API is changing so fast...)
i'll leave it out - stability is even more important than reading wide range of video formats (i can transcode video, having PD vanish in the middle of a performance is very bad form - happened 4 times last night) my system reports the standard pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libaviplay support
though i think i do want ffmpeg (i think someone mentioned it would enable support for .flv files)
i see, does it help if you create a table-of-contents first?
iirc, there is a tool mpeg3toc which will create TOC from an mpeg-file which can then be fed into [pix_film] to allow frame accurate accessing of mpeg-files (and probably the exact number of frames in the file).
otoh, it seems that this has stopped working some time ago...
probably you should just check.
i seem to remember using the TOC when i first started using gem, but yes, it did stop working and i havent checked for some time.
gem still causes PD to
completely die when given a video file it doesn't like.
which is not fine. i suspect that it is libmpeg1 (if it is really used; check out which APIs are really supported when creating the first [pix_film]) - this library is highly unstable; it's only in the code in case libmpeg3 is missing and you still want to decode mpeg-files.
thanks, i'll try removing mpeg (guess i'll have to compile my own, oh well, since i'm going to do that any ideas how i would go about making Gem use opengl 1.5 instead of 2 (which i think it does now), i want to use it with chromium, which insists on opengl 1.5
the crashing is more random than i thought (sometimes happens with video files that worked a few minutes earlier) (some of the crashes were due to one of my subpatches, that i removed last night, but i think that was the part causing the GUI lockups - it was giving a lot of "stack overflow" messages)
On Apr 18, 2008, at 11:48 PM, Joseph Barrows wrote:
use ffmpeg : no (forced)
hmm, maybe i should compile it myself then
probably not. ffmpeg support in Gem is not something i would consider stable. (the API is changing so fast...)
i'll leave it out - stability is even more important than reading
wide range of video formats (i can transcode video, having PD
vanish in the middle of a performance is very bad form - happened 4
times last night) my system reports the standard pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libaviplay supportthough i think i do want ffmpeg (i think someone mentioned it would
enable support for .flv files)
What might be more useful would be a nice document about how to
transcode files using VLC, and which formats work best for Gem. Most
codecs take a lot of CPU power to decode, so for realtime video work,
it's best to use low CPU codecs, like MJPEG.
.hc
see, does it help if you create a table-of-contents first? iirc, there is a tool mpeg3toc which will create TOC from an mpeg-file which can then be fed into [pix_film] to allow frame accurate
accessing of mpeg-files (and probably the exact number of frames in the file).otoh, it seems that this has stopped working some time ago...
probably you should just check.
i seem to remember using the TOC when i first started using gem,
but yes, it did stop working and i havent checked for some time.gem still causes PD to completely die when given a video file it doesn't like.
which is not fine. i suspect that it is libmpeg1 (if it is really used; check out which APIs are really supported when creating the first [pix_film]) - this library is highly unstable; it's only in the code in case libmpeg3 is missing and you still want to decode mpeg-files.
thanks, i'll try removing mpeg (guess i'll have to compile my own,
oh well, since i'm going to do that any ideas how i would go about
making Gem use opengl 1.5 instead of 2 (which i think it does now),
i want to use it with chromium, which insists on opengl 1.5the crashing is more random than i thought (sometimes happens with
video files that worked a few minutes earlier) (some of the crashes were due to one of my subpatches, that i
removed last night, but i think that was the part causing the GUI
lockups - it was giving a lot of "stack overflow" messages)
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
"[T]he greatest purveyor of violence in the world today [is] my own
government." - Martin Luther King, Jr.