[Live-devel] seg fault in framed source

2009-01-04 Thread Mat Laibowitz
I am trying to add optional unicast support to my stream server which currently runs great using multicast. I have implemented a custom DeviceFrameSource class extending FramedSource to control my MPEG4 encoder hardware. This is working great using multicast. To get it to run using unicast I based

Re: [Live-devel] rtsp client and server in the same app

2008-10-26 Thread Mat Laibowitz
The problem is the MPEG hardware. I can only have one open connection to MPEG hardware for both encoding and decoding. I don't need the client to talk to its local server. I need the client to talk to a server on a remote device. So if I have two devices one serves rtsp://ip1:8554/video and connect

Re: [Live-devel] rtsp client and server in the same app

2008-10-26 Thread Mat Laibowitz
, > > Amit Yedidia > > Elbit System Ltd. > > Email: [EMAIL PROTECTED] > > Tel: 972-4-8318905 > > -- > > > > -- > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED]

Re: [Live-devel] rtsp client and server in the same app

2008-10-26 Thread Mat Laibowitz
uot; << env->getResultMsg() << "\n"; } else { *env << clientProtocolName << " \"OPTIONS\" request returned: " << optionsResponse << "\n"; } delete[] optionsResponse; } On Sun, Oct 26, 2008 at

[Live-devel] rtsp client and server in the same app

2008-10-26 Thread Mat Laibowitz
So I have made it pretty far referencing the complete source code and the test programs. But I am a bit stuck on one issue. I have built a RTSP server with a custom FrameSource that talks to my hardware for encoding. This works great, it uses the background read handling and can be received by open