[Live-devel] add a delay in between the RTSP SETUP message and corresponding RTP SETUP message

2014-02-06 Thread Dave Wilder
Hello, When using openRTSP to set up an RTSP connection, is it possible to add a delay in between the RTSP SETUP message and the corresponding RTP SETUP message i.e. send the RTSP SETUP message, delay "N" seconds and then send the RTP SETUP message? Thank you, Dave

Re: [Live-devel] regarding test app MPEG2TransportStreamIndexer

2014-02-06 Thread Ross Finlayson
> I am using test app MPEG2TransportStreamIndexer. > In file MPEG2IndexFromTransportStream.cpp,when it got error "Unexpectedly > large PES header size" its close all handles and goes down. John, Thanks for the note. Please put your Transport Stream file (the one that produces this error) on a

Re: [Live-devel] Stream WAV audio over RTP

2014-02-06 Thread Ross Finlayson
> I am writing an application which I would like to stream 8 and 16 bit pcm > audio from wav files over rtp to a receiver elsewhere on my network. The > control mechanism for this however will eventually be snmp (with SAP messages > for the reciever configuration) rather than rtcp so I would li

Re: [Live-devel] Boolean Groupsock::deleteIfNoMembers;

2014-02-06 Thread Ross Finlayson
> I'm wondering why there is a "Boolean Groupsock::deleteIfNoMembers;" when it > is never used... It's not used elsewhere within the "LIVE555 Streaming Media" software, but it is used by other Live Networks code (for UDP multicast tunneling). (In any case, this is a moot point, because the "grou

[Live-devel] Boolean Groupsock::deleteIfNoMembers;

2014-02-06 Thread Thomas Göllner
Hi all, I'm wondering why there is a "Boolean Groupsock::deleteIfNoMembers;" when it is never used... I think for operations on limited hardware it is a good idea to delete the groupsock when it is no longer needed instead of keeping it alive in case it would be used in future. Thanks, Thomas Göl

Re: [Live-devel] Play response setting in Live555 Server

2014-02-06 Thread Nambirajan
Hi Ross, Please find below the details of player request and the corresponding Server response of the player in FFW and REW condition. We are using the latest version of the code. Normal Play: RTSPClientConnection[0x11fbc40]::handleRequestBytes() read 138 new bytes:PLAY rtsp://192.168.1