Thanks of answers.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Wednesday, January 30, 2013 3:05 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Parsing frames received by testRTSPClient
S
> Since, I just want to receive stream and send to decoder, do you think using
> testRTSPClient over OpenRTSP would be an advantage or there should be no
> difference if either one is used from CPU cycles perspective? I’m about to
> profile both on my system.
Both applications use about the sam
?
Regards,
Yogesh.
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: Tuesday, January 29, 2013 3:22 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Parsing frames received by testRTSPClient
I wa
> I want two know if testRTSPClient allows me to specify codec type and if it
> can give me single encoded frame every time afterGettingFrame() is invoked?
Yes. Look at the "DummySink" class that the "testRTSPClient" demo application
uses. Note, in particular, the (non-static) "DummySink::afte
Hi,
I want two know if testRTSPClient allows me to specify codec type and if it can
give me single encoded frame every time afterGettingFrame() is invoked? If not,
what would be my options to have support for H264 frame parsing in received bit
stream? I want to identify frame boundary in the en
