hi.

bbogart@ryerson.ca wrote:

Good catch Johannes!

so i was right then ? you were so insistent, that i really wasn't that sure anymore, that nobody has done the seperator-numbering already ;-) having had a look at the code, i was quite relieved (there is a lot of work to be done, before concentrating on such things)

Now I just need an effective way to do this for 10+ chains, all in abstractions...

I agree that trigger is the most important (and of course I use it a lot) but I do still think its confusing in the context of a gem-chain, but thats just the way to do it.

yes, i'm sorry to say so (no, i am not sorry ;-) but you are right) the problem with gem-chains is, that they didn't really appear to be message-lists until the cvs-version. in fact, all the message-handling was done in a separate DAG, and that was really confusing. however, nowadays, gem-chains are really just messages between gem-objects, and thus all the cool things can be done, like demux'ing gemchains, gateing parts of gemchains (with [spigot]) and using the trigger thing, you could also change the execution-order of sublists in real-time.

I've not been in the Gem CVS yet, what is the status of pix_video using DV (firewire) input under linux?

well, good time to ask. i have just (1 week ago) committed a test-version of [pix_video] supporting video over ieee1394 to the CVS. i need alpha-testers for now ;-)

the basic thing is, that you need to send a [driver 1( message to the [pix_video] object to use dv4linux instead of video4linux (which would be [driver 0() and you will need the dv1394-driver installed. you can only capture to full resolution (720x576 for PAL), but you can use grey, yuv or rgba colour-space. texturing these images is quite slow under linux (as chris has pointed out, only mac offers a cool way to do *lots* of textures.)

mfg.a.sr IOhannes