2. I have a second question about live555 stability in long run
tests. We plan to use live555 (the client side) to receive and
record streams from cameras with built-in RTSP servers. I am not
aware of any other RTSP/RTP implementation that we could use, I
think there are not many of them out th
Hi Ross, 1. Thanks for your reply. Just for anybody who wants to
receive the correct mpeg4 configuration header, the solution is
simple. One must replace
No, it's even easier: Replace your current version of the code with
the latest version (2010.01.07), which fixes the bug.
--
Ross Finlayso
whatever on
the client side? Thanks for any comment.
Best regards
Alex
>-
>Od: Ross Finlayson
>Přijato: 7.1.2010 7:49:55
>Předmět: Re: [Live-devel] parseGeneralConfigStr
>
>>why does the parseGeneralConfigStr function
why does the parseGeneralConfigStr function (used for parsing the
MPEG4 configuration header) return one more byte than I would expect?
Thanks - you've identified a bug in the code. That extra byte should
not be there (this code was mistakenly copied from
"parseStreamMuxConfigStr()", which *d
Dear all,
why does the parseGeneralConfigStr function (used for parsing the MPEG4
configuration header) return one more byte than I would expect?
Having a configuration string C the resulting byte array should have
strlen(C)/2 bytes. Of course, if strlen(C) is odd (which should normally not be
t
