One more thing. Because your input device (H.264 encoder) is (I presume)
delivering discrete NAL units (one at a time), rather than an unstructured byte
stream, be sure to use a "H264VideoStreamDiscreteFramer", not a
"H264VideoStreamFramer".
Ross Finlayson
Live Networks, Inc.
http://www.live55
> As a side note: I'm having trouble understanding what happens when
> DeviceSource triggers it's event trigger..
>
> The trigger calls deliverFrame(), The first line of deliverFrame() is:
>
> if (!isCurrentlyAwaitingData()) return;
>
> and unless I'm mistaken, this is always going to return un
Thanks Ross,
I have made some changes to my architecture and it is working ok now,
although I spent quite a while trying to figure out why the RTPSink
wasn't starting which turned out to be because i forgot to wrap my
source in a Framer when I made the changes; should I have expected to
see e
> When I create a new ByteSteamFileSource/H264VideoStreamFramer inside the
> 'createNewStreamSource' method ala H264FileServerMediaSubsession it works as
> expected.
You should continue to do this.
> From this I take it that each call to 'createNewStreamSource' should return a
> pointer to a
I am implementing an RTSP server to stream live H264 video via either
multicast or unicast RTP.
My multicast solution is working fine but the unicast stream is giving
me trouble.
I've read the FAQ and based on this I created a test program like so:
1) Created an OnDemandServerMediaSubsessio
