jit.broadcast rtsp issues
i am using a system where two laptops are networked via a router.
computer 1 is using the eyesight to take in the live video feed (jit.qt.grab) and broadcast it (jit.broadcast) to computer 2, receiving it through the rtsp in a web browser where it opens up the feed in quicktime. computer 2 is using the same process, taking in live video feed and broadcasting it to computer 1.
after the computers are idle (have not received a new frame) for a short amount of time, Max will still be grabbing the video but the computer will stop sending the feed. it is not the router, as often enough it is only in one direction that the feed will stop. (computer 1 will be receiving, but not sending)
is there an automatic timeout on the rtsp if not in use for a time?
could this be an issue with quicktime or the web browser being used to open it?
I turned off the sleep mode options on the computers and installed caffiene to keep the computers awake. this still did not solve the problem.
any suggestions?
Thanks!
Sorry if I jump in but I'm having trouble with the jit.broadcast object, where can I find some detailed documentation about it? Max help isn't very informative. In my lan I can stream video although only among some computers. On one computer for instance the jit.qt.movie object responds with a "network error 400" fed with a "read rtsp://192.168.1.2:8554/jitStream" message, while on the same machine VLC plays ok with the same address.
I also tried to stream out across the internet: opened port 8554 in both TCP & UDP (just to be sure... which one jit.broadcast does use anyway?!!). Fed the remote computer with the "read rtsp://x.x.x.x:8554/jitStream" and again get a "Network error 400", while VLC log messages state that the connection is established but no packets are arriving.
Anyone with some clues about the whole thing? I'm on a very short deadline and need to stream a webcam and recive it in max across the internet with a decent (10fps) framerate and a decent resolution (QCIF or CIF).
Thanks to anyone,
F
(If i don't find a solution quickly i'll just have to binarize the image, write a .js to run-lenght compress it, and send it with jit.net.send)