> >> FYI, I've now installed a new version (2011.12.02) of the "LIVE555
> >> Streaming Media" code that avoids this problem (for H.264 parsing). You
> >> should no longer need to modify the "BANK_SIZE" constant.
>
> I guess I should download the patch and look at the new code but could you
>
Hi Ross,
>> FYI, I've now installed a new version (2011.12.02) of the "LIVE555
Streaming Media" code that avoids this problem (for H.264 parsing). You
should no longer need to modify the "BANK_SIZE" constant.
I guess I should download the patch and look at the new code but could you
just e
FYI, I've now installed a new version (2011.12.02) of the "LIVE555 Streaming
Media" code that avoids this problem (for H.264 parsing). You should no longer
need to modify the "BANK_SIZE" constant.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
__
>Date: Tue, 29 Nov 2011 16:58:09 -0800
>From: Ross Finlayson
>To: LIVE555 Streaming Media - development & use
>
>Subject: Re: [Live-devel] StreamParser internal error (14+ 4 > 15)
>Message-ID: <0b428036-277d-430b-8664-feb4b992e...@live555.com>
>
Hi Ross,
>> Surely the answer is to test the frame-size from the encoder before
>> passing it into Live555
>Unfortunately not, because we don't know the frame size in advance; we can
figure it out only by parsing/copying the >data, looking for the next 'start
code'. And it's this that's ove
e
Subject: Re: [Live-devel] StreamParser internal error (14+ 4 >
Surely the answer is to test the frame-size from the encoder before passing it
into Live555
Unfortunately not, because we don't know the frame size in advance; we can
figure it out only by parsing/copying the data, loo
> Surely the answer is to test the frame-size from the encoder before passing
> it into Live555
Unfortunately not, because we don't know the frame size in advance; we can
figure it out only by parsing/copying the data, looking for the next 'start
code'. And it's this that's overflowing our str
Hi Ross,
Further to your answer on this, we have an image size of 2144x1944 pixels
and have already increased the BANK_SIZE beyond 30 to 45. However
there is no guarantee that any number is sufficient. Surely the answer is to
test the frame-size from the encoder before passing it into Live
The problem here is the extremely large H.264 frame (about 280,000 bytes in
size) that you have in this video. This was too big for our stream parsing
code to handle.
You can fix this by changing the constant BANK_SIZE in
"liveMedia/StreamParser.cpp" from 15 to 30. (I'll also make thi
Hello,
I'm using live as an RSTP server and it worked great with the test videos
that come with the package, I also succeed to work with some other sample
video.
The version I'm using is 0.72 2011.10.27
I tried to stream the attached sample (
http://dl.dropbox.com/u/12151823/2mp.264) video that ha
10 matches
Mail list logo
