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
Yeah, but one is a server and one is a client, so it should work
that way I think.
Depending on your operating system, this might still not be possible.
I suggest not doing what you are trying to do (run the client and the
server that it's communicating with in the same application). It's
we
*On Behalf Of *Mat Laibowitz
> *Sent:* Sunday, October 26, 2008 11:53 AM
> *To:* [EMAIL PROTECTED]; [EMAIL PROTECTED]
> *Subject:* Re: [Live-devel] rtsp client and server in the same app
>
> A little more info. It is not the SDP request that fails, it is the OPTIONS
> request that
:[EMAIL PROTECTED] On Behalf Of Mat Laibowitz
Sent: Sunday, October 26, 2008 11:53 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Live-devel] rtsp client and server in the same app
A little more info. It is not the SDP request that fails, it
A little more info. It is not the SDP request that fails, it is the OPTIONS
request that returns NULL.
I added a check fro null after the getOptionsRequest as shown below. And it
returns NULL when called in the same program as starting a RTSP server.
So the actual error message is the same, but it
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
