Dave Phillips wrote:
IOhannes m zmoelnig wrote:
you mean, using the "pix_rgba" object (which might be (pre-alpha) crashy)) it slows down ?
Yes, the frame rate is cut by what appears to be about half, quite an obvious slow-down.
if you are referring to the example-patch "film.pd", the frame-rate drops not because of the pix_rgba object, but because of the pix_convolve. if pix_rgba is turned off, pix_convolve will get RGB-data but knows not what to do with it. therefore there is now (time-consuming) convolution (and you see masses of errors on the shell) when switching pix_rgba on, the pix_convolve will now start to convolve the (converted) RGBA-images. Since the default convolution-kernel is something like 0 0 0 0 1 0 0 0 0 , the image still looks "normal" (even though the (redundant) convolution is done !!)
i didn't notice any slowdown, due to the pix_rgba itself
most of the decoders only return RGB instead of RGBA, but all of them are able to decode to RGB. however, this depends on the used codec, so it might be up to you to use a codec that supports RGBA or use pix_rgba to make a "manual" conversion.
Do you mean it's possible to convert the format via Pd ? That would be sweet, but I suspect you mean something else (?).
it is done via the pix_rgba object
try loading the file after turning on the rendering
It doesn't seem to make a difference. I can load the MOV and MPG videos just fine, but I get no video display. The rendering seems to be working correctly (it bangs at the end of the numbered frames), there's just no video display. I've attached a simplified patch, perhaps you can see where I'm doing something wrong. I'll gladly send the example movies too if you want to try them.
as i hinted in a previous mail, this might be due to the image-size. if your image-dimensions are not powers of 2, you will have to pix_texture2 instead of pix_texture
...pix_film and pix_movie use the very same procedure-calls (eg: for opening files). the only difference between these two is, that pix_movie immediately loads the frame as a texture onto the gfx-card, whereas pix_film does not. however, the "brownish look" of your window comes from using the wrong colour-space (i guess: RGB instead of RGBA...) i'll check this.
Cool, just let me know when you need some testing done.
here we go: ftp://iem.kug.ac.at/pd/Externals/GEM/LINUX/gem-linux-0.87_test2.tgz
fixed: pix_film fixed: pix_fx (parent class for fx, like pix_rgba) fixed: model/glm thanks to guenter not really fixed, but more likely to work: configure not fixed: pix_movie colour-space problems (i do not encounter this problem here)
mfg.c.asdr IOhannes
ftp://iem.kug.ac.at/pd/Externals/GEM/LINUX/gem-linux-0.87_test2.tgz
configure works now though it still doesn't find libdv.h i can create pix_dv but gem gives an error message when i try to start rendering: define DV(IEEE1394) for your OS.
pix_movie and pix_film both work (though slow and with reduced colors) but i was not able to load any other format than mpeg's made with "motion". mov's did not load due to unsupported codecs, but maybe thats because these clips were made on another OS with RLE and SVQ1 codec (are these video codecs available for linux, preferably as a debian package?). i also tried it with an avi captured in linux with "kino" - no success.
pix_model works great on linux now. the smoothness feature is really usefull!
pix_sig2pix~ was very funny to play with but i don't know if i used it the right way. i just put it in the render-tree just before pix_texture. is there something similar to the quality message in pix_texture? pix_pix2sig~ always put out a high whistle on the RGB outs even though i heavily maniplulated the mpeg with colorGRB.
i encountered some crashes when working with gem; several segfaults and few "socket receive error: connection reset by peer(104)" but maybe thats a bug on the user-side...
anyway, it's great
regards, ulrich
...the teapot works too ;)
Ulrich Kehrer wrote:
pix_movie and pix_film both work (though slow and with reduced colors) but i was not able to load any other format than mpeg's made with "motion". mov's did not load due to unsupported codecs, but maybe thats because these clips were made on another OS with RLE and SVQ1 codec (are these video codecs available for linux, preferably as a debian package?).
JPEG MOVs seem to work fine but I've had no luck with other MOVs, will try some more this evening. MPEGs are also uneven: some are acceptable, others appear to load and run but produce no display. I'll start keeping closer track of the working formats.
Ulrich, do you have any suggestions for finding some of the MPEGs that work for you ?
i also tried it with an avi captured in linux with "kino" - no success.
I think there's no Linux support for AVI in this release...
pix_model works great on linux now. the smoothness feature is really usefull!
It is pretty cool, but where can I obtain more obj files to play with ?
pix_sig2pix~ was very funny to play with but i don't know if i used it the right way. i just put it in the render-tree just before pix_texture. is there something similar to the quality message in pix_texture? pix_pix2sig~ always put out a high whistle on the RGB outs even though i heavily maniplulated the mpeg with colorGRB.
This sounds like fun, do you have an example patch ?
i encountered some crashes when working with gem; several segfaults and few "socket receive error: connection reset by peer(104)" but maybe thats a bug on the user-side...
I'm getting a lot of those too. For the record, I'm running Linux kernel 2.4.5 patched for low-latency, ALSA driver package 0.9.0beta10, XFree86 4.1, and a Voodoo3 AGP card in an 800 MHz machine.
I've also received a number of these messages:
X Error of failed request: BadValue (integer parameter out of range
for operation) Major opcode of failed request: 128 (XFree86-DRI) Minor opcode of failed request: 13 () Value in failed request: 0x2400004 Serial number of failed request: 36 Current serial number in output stream: 36 [dlphilp@localhost dlphilp]$ pd_gui: pd process exited
but IOannes already knows about them.
anyway, it's great
Indeed. I'm looking forward to using this stuff for a piece, but I've got lots to learn first...
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://sound.condorow.net
On Tue, 5 Mar 2002, Dave Phillips wrote:
Ulrich, do you have any suggestions for finding some of the MPEGs that work for you ?
i've used mpeg's i made with motion and the ucbmpeg encoder, both available as debian packages or here: http://motion.technolust.cx/ http://bmrc.berkeley.edu/frame/research/mpeg/index.html
This sounds like fun, do you have an example patch ?
http://www.softpink.com/gem/misc_oscs.pd http://www.softpink.com/gem/sig2pix.pd the first one is just an abstraction you need. i think there's a zexy object in it.
some obj-models can be found here, but there are lots of other places: http://avalon.viewpoint.com/
today i've loaded quicktimes with photo jpeg and motion jpeg-a compression. motion jpeg-b is unsupported.
so far, ulrich
ah thanks Ulrich for doing a little documentation patch
Ulrich Kehrer wrote:
On Tue, 5 Mar 2002, Dave Phillips wrote:
This sounds like fun, do you have an example patch ?
http://www.softpink.com/gem/misc_oscs.pd http://www.softpink.com/gem/sig2pix.pd the first one is just an abstraction you need. i think there's a zexy object in it.
great.
so the main thing about both the pix_sig2pix~ and pix_pix2sig~ is, that they are working on a signal-block base. this is: when using normal blcok-sizes (default: 64), you can only get/set 64 pixels of your image-data. so if you create a "pix_sig2pix~ 64 64" you can only control the very first row with your signals. you will have to add a "block~ 4096" somewhere in your patch. this will slow-down the frame-rate of the "sig-video" (let's call it like this) to ~10 fps (the rendering frame-rate of Gem will be unaffected). so you would like to use "block~ 4096 2" to get reasonably values. you can change the dimensions of the image-data with the dimen-message (as is shown in Ulrich's example)
unfortunately the dimensions default to 256x256 (which is very unreasonabely for the use within pd). i think i will change this (to 8*8 for example). anyhow, you will always want to set your initial values.
similar things apply to pix_pix2sig~. if you try to convert "large" images (like 256x256) with pd's default blocksize, you will only get the first 64 pixels. this might be the case, why some of you encountered the very high tone not changing: it was just listening to a non-representative part of the image
some obj-models can be found here, but there are lots of other places: http://avalon.viewpoint.com/
yo, the web is full of wave-front models. but since few modellers are natively able to write .obj-files (yes, i know by now: there are plenty of filters/plugins/converters to read/write .obj-models with commen modellers) i am looking for a free (or more free) alternative.
mfg-.c.asdr IOhannes
hi,
i was able to build gem but on load it gives me:
/home/erich/software/pd34p2/gem-0.87_2/Gem.pd_linux: /usr/lib/libquicktime.so: undefined symbol: raw1394_errcode_to_errno software/pd34p2/gem-0.87_2/Gem: can't load library
libquicktime.so is the one from heroine libdv.h is also in place (even if configure is not able to find it)
any idea what i can do ?
cheers
erich
On Tue, 5 Mar 2002, Ulrich Kehrer wrote:
ftp://iem.kug.ac.at/pd/Externals/GEM/LINUX/gem-linux-0.87_test2.tgz
configure works now though it still doesn't find libdv.h i can create pix_dv but gem gives an error message when i try to start rendering: define DV(IEEE1394) for your OS.
pix_movie and pix_film both work (though slow and with reduced colors) but i was not able to load any other format than mpeg's made with "motion". mov's did not load due to unsupported codecs, but maybe thats because these clips were made on another OS with RLE and SVQ1 codec (are these video codecs available for linux, preferably as a debian package?). i also tried it with an avi captured in linux with "kino" - no success.
pix_model works great on linux now. the smoothness feature is really usefull!
pix_sig2pix~ was very funny to play with but i don't know if i used it the right way. i just put it in the render-tree just before pix_texture. is there something similar to the quality message in pix_texture? pix_pix2sig~ always put out a high whistle on the RGB outs even though i heavily maniplulated the mpeg with colorGRB.
i encountered some crashes when working with gem; several segfaults and few "socket receive error: connection reset by peer(104)" but maybe thats a bug on the user-side...
anyway, it's great
regards, ulrich
...the teapot works too ;)
On Wednesday 06 March 2002 22:33, rat@telecoma.net wrote:
hi,
i was able to build gem but on load it gives me:
/home/erich/software/pd34p2/gem-0.87_2/Gem.pd_linux: /usr/lib/libquicktime.so: undefined symbol: raw1394_errcode_to_errno software/pd34p2/gem-0.87_2/Gem: can't load library
libquicktime.so is the one from heroine libdv.h is also in place (even if configure is not able to find it)
any idea what i can do ?
Use an older version, like this one: http://prdownloads.sourceforge.net/heroines/quicktime.090901.tar.bz2
hi again, thx 4 help hmmm so i changed to the older one, and i get another error:
/home/erich/software/pd34p2/gem-0.87_2/Gem.pd_linux: /usr/lib/libquicktime.so: undefined symbol: mmx_ok software/pd34p2/gem-0.87_2/Gem: can't load library
any idea ?
cheers
erich
On Wed, 6 Mar 2002, mik wrote:
On Wednesday 06 March 2002 22:33, rat@telecoma.net wrote:
hi,
i was able to build gem but on load it gives me:
/home/erich/software/pd34p2/gem-0.87_2/Gem.pd_linux: /usr/lib/libquicktime.so: undefined symbol: raw1394_errcode_to_errno software/pd34p2/gem-0.87_2/Gem: can't load library
libquicktime.so is the one from heroine libdv.h is also in place (even if configure is not able to find it)
any idea what i can do ?
Use an older version, like this one: http://prdownloads.sourceforge.net/heroines/quicktime.090901.tar.bz2
On Thursday 07 March 2002 00:02, rat@telecoma.net wrote:
hi again, thx 4 help hmmm so i changed to the older one, and i get another error:
/home/erich/software/pd34p2/gem-0.87_2/Gem.pd_linux: /usr/lib/libquicktime.so: undefined symbol: mmx_ok software/pd34p2/gem-0.87_2/Gem: can't load library
any idea ?
cheers
erich
You have to run configure before compiling.
Use an older version, like this one: http://prdownloads.sourceforge.net/heroines/quicktime.090901.tar.bz2
so i got gem 0.87_2 to compile fine and i made and installed the libquicktime listed above, but i still get the following error when gem loads:
/usr/lib/libquicktime.so: undefined symbol: g_log
any ideas or suggestions???
cgc
chris clepper wrote:
Use an older version, like this one:
http://prdownloads.sourceforge.net/heroines/quicktime.090901.tar.bz2
so i got gem 0.87_2 to compile fine and i made and installed the
do you mean test1 or test2 (which both expand to gem-0.87_2/) with test2 you *should* be able to compile with the normal debian(???) package libquicktime4linux-dev
libquicktime listed above, but i still get the following error when gem loads:
/usr/lib/libquicktime.so: undefined symbol: g_log
you need the glib-library. is it detected by the configure-script ? just check, whether there are things like "-lglib" in the LIBS=(...) line of the Gnu/Makefile
mfg.cds.ar IOhannes
chris clepper wrote:
so i got gem 0.87_2 to compile fine and i made and installed the libquicktime listed above, but i still get the following error when gem loads:
/usr/lib/libquicktime.so: undefined symbol: g_log
any ideas or suggestions???
Sorry to make you run around collecting versions of libquicktime, but the version that's been working for me is the one at Guenter's site:
ftp://xdv.org/pub/gige/gem/
Best regards,
== Dave Phillips
The Book Of Linux Music & Sound at http://www.nostarch.com/lms.htm
The Linux Soundapps Site at http://sound.condorow.net
On Friday 08 March 2002 21:27, Dave Phillips wrote:
chris clepper wrote:
so i got gem 0.87_2 to compile fine and i made and installed the libquicktime listed above, but i still get the following error when gem loads:
/usr/lib/libquicktime.so: undefined symbol: g_log
any ideas or suggestions???
Sorry to make you run around collecting versions of libquicktime, but the version that's been working for me is the one at Guenter's site:
mine works too, for me at least. chris, did you recompile gem after you installed the new quicktime. if not, you'd better.
mik