On Thu, Dec 22, 2011 at 6:12 AM, Jeff Shanab wrote:
> Above the live 555 libs I have my own frame class. It is a simple RAII
> data class with payload, a bit of byte alignment, and some metadata like
> size and type. I use a reference counted pointer to this. This allows my
> multiple subscribers
Thanks...
You are right It is not a good idea to ignore RTCP corrections...
I have no problem with viewing...I just push incoming streams [ since
they are from real time ip camera ] to decoder than viewer, I can see
the video
Since my rtsp source is in real time i do not insert any time-stamp or
> I want to create a rtsp server that supports multiple live video source
> playing using threads. I have created my custom live source, sink and
> session object and modified MediaSubsession::initiate to handle it. I created
> multiple rtspclients using threads to use my own session. The pr
Hi,
I want to create a rtsp server that supports multiple live video source
playing using threads. I have created my custom live source, sink and
session object and modified MediaSubsession::initiate to handle it. I
created multiple rtspclients using threads to use my own session. The
probl
> (My goal here is to have a H.264 file that I know that - if processed with
> our "testH264VideoToTransportStream" demo application, after I've modified
> our Transport Stream multiplexing code based on your changes - will produce a
> Transport Stream file that works with HTTP Live Streaming.)
