marco wrote:

Hi, I would be very excited to pix_dv to work.

Unfortunately, there are some problems compiling... (I am using a highly modified Redhat 7.1 machine)

Since there is no ./configure script for makeauxlibs, I had to edit the Makefile for glm so that it would find glut.h in /usr/X11R6/include. (Perhaps a configure for makeauxlibs would be a good idea, as many people probably don't have those libs, I couldn't find glm quickly using google (and the top-level configure was blocking on that). Then I saw you had included it!)

Ja, I think compiling Gem could be easier, but it looks like the sources are prepared for cross-platform use. Still, reading the README.build notes make it clear what needs done. IMO, the AuxLibs stuff needs a 'make install' too.

Which version of libdv should I use? I did not find this in the Docs.

IOannes might be asleep now (he spent yesterday helping me compile Gem, I think I wore him out ;) so I'll repeat what he advised me. Yes, you want the Heroine Warrior libquicktime stuff; IOannes also suggested using libmpeg3 instead of libmpeg, and there are some code bugs that he may have fixed now in the sources. Also, the configure script needs a little more attention. But remember, this version is an alpha release.

I've tested his examples for pix_film and pix_movie: pix_film worked great, but I had problems with pix_movie that I'll investigate today.

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

marco wrote:

I did not mean my mail to be a criticism. Yes the README.build is very clear.

Perhaps I am not knowledgeable enough to be an alpha version user, but I have been so dying to get a film or movie object working under linux that I wanted to jump on this opportunity. And let Iohannes know there is the desire for this work.

well, since there obviously was such demand for movie/film-objects under linux and people wanted to have dv-support i decided to release this (pre-)alpha version of the stuff, and lo! here we are.

If I can be of any help getting these objects working easily for as many users as possible. Please let me help.

Perhaps this is my lack of knowledge but I still can't get this version to compile with the heroine warrior libs... It blocks on the libdv stuff. I tried compiling just pix_film, or pix_movie but this is a bit over my head :( . I'll have to read more on how to compile an external for pd.

well, seems funny, but the same goes for me! i wrote the code at home using libquicktime4linux-dev 1.3-4 (that's debian's version number; and i hope i am remembering it right). there certainly is the libdv-stuff included, as it is documented in /usr/share/doc/libquicktime4linux-dev/firewire.html so i was quite sure, that it would be no problem anywhere. since many of you brave alpha-testers mailed me, that the source was kind of uncompilable, i tried to compile it myself on my machine here at iem. guess what: thousands of compile problems sorry for not testing it before putting it on the web (but hey: it's alpha) especially the quicktime/libdv-support seems to be gone with 1.3-5 (debian) so i will have to have a look at the "normal" libdv. in the meantime i would suggest to just not use the pix_dvLinux.cpp code (it should be enough to "#if 0" at the beginning and #endif# at the very end of the pix_dvLinux.cpp-file. remove the pix_dvLinux_setup() lines in the GemSetup.cpp;

don't forget to apply the patch on the pix_filmLinux.cpp in line200

-- row[0]=mframe ++ while(i--)rows[i]=m_frame+m_xsize*m_csize*i;

mfg.cd.sdatr

I'll be watching this thread with great excitement.

Marco

hi ! thanks for keeping bug-reporting

2) When I switch the input to RGBA things slow down quite a bit. I'm

running an 800 MHz Duron with a Voodoo3 AGP card, I realize it's outdated, but should I expect such a significant slowdown ? 3) Is it possible to convert an RGB movie to RGBA via a format converter ? Is there such a thing for Linux ?

you mean, using the "pix_rgba" object (which might be (pre-alpha) crashy)) it slows down ? 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.

4) Performance seems "brittle", i.e., sometimes certain MPEGs will

load and play nice, at other times the same files will load but not play.

try loading the file after turning on the rendering

5) Often when I destroy the GL rendering window Pd will close with

this output:

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: 0x2e00004 Serial number of failed request: 36 Current serial number in output stream: 36 [dlphilp@localhost dlphilp]$ pd_gui: pd process exited

Is this a known bug ?

No, maybe it has something to do with your GraphicsCard ? (but i guess this behaviour started with the new gem and did not happen before...)

6) pix_movie doesn't seem to work at all. Pd crashes when I try

lading an MPEG, and the MOV files that work with pix_film don't display with pix_movie. I get a flickering brownish window during the rendering, but no video. Also, if I try changing the named file in the pix_movie object Pd will often crash.

this is very(!) strange, since 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.

mfg.cas.f IOhannes