[Live-devel] compiling each modules individually in VS2008

2010-03-08 Thread Harish N
Regards, Harish NPD team From: Harish N Sent: Tuesday, March 09, 2010 10:42 AM To: 'live-devel@lists.live555.com' Subject: Hello all... I am working on LIVE555,on RTSPClient and RTSPserver..I need little help in compiling OpenRTSP using visual Studio 2008..i tried compiling but there fe

[Live-devel] playMediaSession H264

2010-03-08 Thread Miguel Angel Arcos
Hi developers, I'm having some problems with an specific IP source of H264. The problem is on the response of PlayMediaSession. I send this: OPTIONS, DESCRIBE, SETUP and PLAY. when I send PLAY I receive BAD REQUEST from the Server. In all the other cases I receive OK. I don't understand where i

Re: [Live-devel] Where to register the file extension name in Live555

2010-03-08 Thread Ross Finlayson
Hi We are trying to enhance the live 555 code to stream MP4 . We have developed the parser for it. Please tell us, where to register the extension name .MP4 (the file which registers the extensions). For the "LIVE555 Media Server" application, you would add a new branch to the "if" statement

Re: [Live-devel] openRTSP

2010-03-08 Thread Andro Debevere
I already did this for myself and I wrote it in a previous post: http://lists.live555.com/pipermail/live-devel/2010-February/011827.html This does solve the issue, and I only get in trouble now while testing if I start and stop the application too many times in a short time (due to a socket limit

Re: [Live-devel] openRTSP

2010-03-08 Thread Ross Finlayson
>OK, the problem is that the *client* port numbers are the same for both streams. I don't know why the server does this, but in any case it's not something that we currently support in our code (to do so would require that we demultiplex based on SSRC, which is something that we don't do). Ju

Re: [Live-devel] openRTSP

2010-03-08 Thread Andro Debevere
>OK, the problem is that the *client* port numbers are the same for both >streams. I don't know why the server does this, but in any case it's >not something that we currently support in our code (to do so would >require that we demultiplex based on SSRC, which is something that we >don't do).