[Live-devel] H264 working in openRTSP but not testRTSPClient

Shervin Emami shervin at dibaustralia.com.au
Tue Dec 22 19:03:40 PST 2015


Thanks for the info. From reading your linked threads, it seems I should
contact the camera manufacturer (hiQview) and tell them they should modify
their cameras to send smaller NAL units. I'm often seeing some 150KB NAL
units, so I had set my buffer to 300KB just for safety. Assuming the
hardware manufacturer doesn't give me an overnight firmware update to fix
it (highly unlikely!), for now I'll stick with 300KB buffer and try to get
testRTSP working as well as openRTSP does. I did notice that openRTSP calls:
    subsession->rtpSource()->setPacketReorderingThresholdTime();
And also
    setReceiveBufferTo()
Whereas testRTSPClient doesn't call those.

So perhaps that's what I need. Let me know if you can think of anything
else that might cause a difference, but if not I'll try the 2 functions
above and let you know how it goes.


Cheers,
Shervin Emami.
Senior Embedded Vision Engineer,
DIB Australia.
1/41 Botanical Drive,
Labrador, QLD 4215
Australia
+61 431 845 843
http://dibaustralia.com.au/


On 23 December 2015 at 13:25, Ross Finlayson <finlayson at live555.com> wrote:

> > When I run "openRTSP -b 300000 rtsp://192.168.2.101" on the H.264
> stream of my IP camera it works perfectly, but when I tried modifying
> testRTSPClient to do the equivalent (ie: saving NAL packets to a H264 raw
> bitstream file), it works perfectly sometimes but occasionally the video
> looks broken.
>
> (Argh, this is not going well.  Resending again.)
>
> ...From what I can tell (from your description of your modification to
> “testRTSPClient”), there should be *no* difference between the behavior of
> “openRTSP” and your modified “testRTSPClient”, in this case.  I suspect
> that you’ve been running your modified “testRTSPClient” more often than
> “openRTSP”, and that if you ran “openRTSP” more often, you’d see the issue
> there as well.
>
> Does your H.264 video stream really have NAL units that are close to
> 300000 bytes in size?? If so, then that’s the problem.  NAL units this
> large are *much* to large to be streamed over RTP.  They should instead be
> encoded as a sequence of smaller ‘slice’ NAL units.
>
> Please read
>
> http://lists.live555.com/pipermail/live-devel/2015-November/019773.html
> and the links therein.
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20151223/f880c1ef/attachment.html>


More information about the live-devel mailing list