hi, i am having trouble with GEM, it only reads .MOV and only some of those (has to be motion jpeg, but still not all of them open) apparently GEM video support is defined at compile time, so i was wondering what libraries are used in the sourceforge build environment.
i'm currently using pd extended 41.4 built early april but I was having the same problem with the previous stable release (39.xx)
running Ubuntu 7.10 constantly updated (which may be part of the problem, when i first installed ubuntu and PD GEM could read a wider variety of video, so i was carefull NOT to use the auto update feature, untill accidently clicking it when tired one night, since then only a few mjpeg .mov's will load)
thanks, joseph\
Joseph Barrows wrote:
hi, i am having trouble with GEM, it only reads .MOV and only some of those (has to be motion jpeg, but still not all of them open) apparently GEM video support is defined at compile time, so i was wondering what libraries are used in the sourceforge build environment.
none, as Gem (and Pd) do not use the sourceforge build farm, but hans has set up his own.
anyhow, are you trying to build Gem yourself or are you just using pre-packed binaries (e.g. Pd-extended); it's not clear to me though your email suggests the latter.
anyhow, Gem uses several APIs to decode video; which APIs it can read is defined at compile time as you have corretly guessed.
which APIs are actually found at compile time can be seen in the output of Gem's configure (which is part of the build-logs to be found on the autobuid website where you downloaded the Pd-extended package)
the build-logs for gutsy on 2008-04-16 show: video-support use mpeg : yes use mpeg-3 : yes use QuickTime : yes use aviplay : yes use ffmpeg : no (forced)
so there are 4 APIs used; you should also see something similar when you first instantiate a [pix_film] or [pix_movie] object. (e.g. on my machine it says: pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libaviplay support pix_film:: FFMPEG support which tells me that i use other APIs than the autobuild versions (e.g. i have ffmpeg support))
"mpeg" and "mpeg-3" are just able to decode mpeg-file, which you don't seem to care about right now. 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. (i think libquicktime have changed their policy to just include built-in codecs; whereas aviplay uses external codecs)
so the key thing to do to get more movies to load is to either update these libraries or install (or update) packages that provide codecs.
on debian, one beloved package used to be "avifile-win32-plugin" from debian-multimedia-org, which would provide a number of non-free (potentially copyright and/or patent protected) codecs as w32-dlls.
i don't know whether there is this package for ubuntu (or whether you can "just use" the debian-multimedia packages)
due to the potentially illegal nature of some codec packages available in the net, these packages vanish from time to time.
fmgasd IOhannes
On Thu, 2008-04-17 at 09:33 +0200, IOhannes m zmoelnig wrote:
Joseph Barrows wrote:
hi, i am having trouble with GEM, it only reads .MOV and only some of those (has to be motion jpeg, but still not all of them open) apparently GEM video support is defined at compile time, so i was wondering what libraries are used in the sourceforge build environment.
"mpeg" and "mpeg-3" are just able to decode mpeg-file, which you don't seem to care about right now. 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. (i think libquicktime have changed their policy to just include built-in codecs; whereas aviplay uses external codecs)
so the key thing to do to get more movies to load is to either update these libraries or install (or update) packages that provide codecs.
on debian, one beloved package used to be "avifile-win32-plugin" from debian-multimedia-org, which would provide a number of non-free (potentially copyright and/or patent protected) codecs as w32-dlls.
i don't know whether there is this package for ubuntu (or whether you can "just use" the debian-multimedia packages)
due to the potentially illegal nature of some codec packages available in the net, these packages vanish from time to time.
There is a Media Ubuntu repository that has the restricted copyright codecs: Medibuntu
Le Thu, 17 Apr 2008 09:33:39 +0200, IOhannes m zmoelnig zmoelnig@iem.at a écrit :
Thnaks IOhannes for this very clear explanation. I just translated this post into French and added it to the mediawiki, it's worth it.
http://wiki.puredata.info/fr/Quel_codec_utiliser_pour_lire_de_la_vid%C3%A9o%...
english here : http://wiki.puredata.info/en/Gem_codecs
it's been added to the How-to category : http://wiki.puredata.info/en/Category:How-to
I've also linked to http://puredata.info/dev/APIDoku
++ O.
Joseph Barrows wrote:
hi, i am having trouble with GEM, it only reads .MOV and only some of those (has to be motion jpeg, but still not all of them open) apparently GEM video support is defined at compile time, so i was wondering what libraries are used in the sourceforge build environment.
none, as Gem (and Pd) do not use the sourceforge build farm, but hans has set up his own.
anyhow, are you trying to build Gem yourself or are you just using pre-packed binaries (e.g. Pd-extended); it's not clear to me though your email suggests the latter.
anyhow, Gem uses several APIs to decode video; which APIs it can read is defined at compile time as you have corretly guessed.
which APIs are actually found at compile time can be seen in the output of Gem's configure (which is part of the build-logs to be found on the autobuid website where you downloaded the Pd-extended package)
the build-logs for gutsy on 2008-04-16 show: video-support use mpeg : yes use mpeg-3 : yes use QuickTime : yes use aviplay : yes use ffmpeg : no (forced)
so there are 4 APIs used; you should also see something similar when you first instantiate a [pix_film] or [pix_movie] object. (e.g. on my machine it says: pix_film:: quicktime support pix_film:: libmpeg3 support pix_film:: libaviplay support pix_film:: FFMPEG support which tells me that i use other APIs than the autobuild versions (e.g. i have ffmpeg support))
"mpeg" and "mpeg-3" are just able to decode mpeg-file, which you don't seem to care about right now. 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. (i think libquicktime have changed their policy to just include built-in codecs; whereas aviplay uses external codecs)
so the key thing to do to get more movies to load is to either update these libraries or install (or update) packages that provide codecs.
on debian, one beloved package used to be "avifile-win32-plugin" from debian-multimedia-org, which would provide a number of non-free (potentially copyright and/or patent protected) codecs as w32-dlls.
i don't know whether there is this package for ubuntu (or whether you can "just use" the debian-multimedia packages)
due to the potentially illegal nature of some codec packages available in the net, these packages vanish from time to time.
-
danomatika -
IOhannes m zmoelnig -
Joseph Barrows -
Olivier Heinry