> And I'm sure that there are many of us who could spend an hour or two > figuring it out - I have done it in the past, although the method was > really messy and slow.
Figuring out the details isn't really the problem if i just get a hint what to do. Do i really need to iterate over all pixels and send them manually to the server? This would be really bad, because 640*480*24bit = 900kB for one pic! And I can't use any compression here, right? Isn't there a better way? Like maybe it is possible to choose the exact frame to send to the server by publishing just for 1/30th of a second when setting fps to 30. And maybe i can implement an interface on the serverside to intercept this very frame and save it to a JPG. Can anyone with enough insight in the inner workings of red5 shed some light on whether something along these lines would be possible? regards Claudius _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
