e the files I am testing with are not corrupted.
>
>
>
> -vikram singh
>
>
>
> *From:* live-devel [mailto:live-devel-boun...@ns.live555.com] *On Behalf
> Of *Vikram Singh
> *Sent:* Friday, June 20, 2014 7:58 PM
> *To:* 'LIVE555 Streaming Media - development &am
: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
Vikram Singh
Sent: Friday, June 20, 2014 7:58 PM
To: 'LIVE555 Streaming Media - development & use'
Subject: Re: [Live-devel] Starting Frames are corrupted
Hi ross,
Please ignore my previous mail. I was s
causing this problem.
-vikram
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
Ross Finlayson
Sent: Wednesday, June 18, 2014 11:13 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Starting Frames are corrupted
I am having -- unsi
PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Starting Frames are corrupted
I am having -- unsigned OutPacketBuffer::maxSize = 90; in
mediaSink.cpp
If I decrease the maxSize then the frames I get are truncated.
OK, there are two separate buffer sizes
I am lucky with most encoders, I deal with about 23 brands.
At least 6 major brands I communicate with and we have a healthy
relationship in which we get changes in their FW on request. Inded
sometimes it seems we are debugging their firmware for them. It rolls both
ways. (A lot of them use live555
> A related technical question. Can we split a large Iframe nal frame into
> slices after the fact? Sometimes the encoder is a closed piece of
> hardware/firmware. Is it possible to split it into slices at a macroblock
> boundary?
I suppose it might be technically possible, but it would require
> In any case, 90 bytes is an *insanely large* NAL unit (I-frame) size!! A
> NAL unit this large will get fragmented into *60* RTP packets
Correction: 600 packets!
> and *all* of these RTP packets must be received by the receiving application,
> otherwise the entire frame will be unrendera
> I am having -- unsigned OutPacketBuffer::maxSize = 90; in mediaSink.cpp
> If I decrease the maxSize then the frames I get are truncated.
OK, there are two separate buffer sizes that you need to concern yourself with.
"OutPacketBuffer::maxSize" is the buffer size that is used - by your ser
axSize.
>
>
>
> Thanks
>
> Vikram Singh
>
>
>
> *From:* live-devel [mailto:live-devel-boun...@ns.live555.com] *On Behalf
> Of *Ross Finlayson
> *Sent:* Wednesday, June 18, 2014 7:03 PM
> *To:* LIVE555 Streaming Media - development & use
> *Subject:* Re: [Live-de
-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
Ross Finlayson
Sent: Wednesday, June 18, 2014 7:03 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Starting Frames are corrupted
I am testing the testH264VideoStreamer.cpp provided in the testprog
use
Subject: Re: [Live-devel] Starting Frames are corrupted
I have implemented RTSP Streaming using Live555 Library.
Have you used the "LIVE555 Streaming Media" code to implement a RTSP server,
a RTSP client (i.e., media player), or both?
If you have implemented only a RTSP server,
> I am testing the testH264VideoStreamer.cpp provided in the testprogs of
> live555 library folder.
> This file will stream a h264 file.
> My h264 file is not corrupted.
> I am viewing the stream using vlc player.
(Sorry, I sent my previous email before I read your last email, in which you
explai
> I have implemented RTSP Streaming using Live555 Library.
Have you used the "LIVE555 Streaming Media" code to implement a RTSP server, a
RTSP client (i.e., media player), or both?
If you have implemented only a RTSP server, then what are you using as your
RTSP client (i.e., media player)?
Ro
, June 18, 2014 4:28 PM
To: live-de...@ns.live555.com; vik...@vizexperts.com
Subject: Re: [Live-devel] Starting Frames are corrupted
What codec are you using? For example, in the case of H.264 you should only
start decoding the stream on the client once you've received an IDR frame.
In other
What codec are you using? For example, in the case of H.264 you should only
start decoding the stream on the client once you've received an IDR frame.
In other cases, artifacts typically occur due to packet loss.
>>> "Vikram Singh" 06/18/14 7:02 AM >>>
Hi,
I have implemented RTSP Streaming us
Hi,
I have implemented RTSP Streaming using Live555 Library.
Initially when the streaming starts, the frames are corrupted.
But later this clears up and I have smooth rendering of the stream.
Has anyone faces such an issue.
Initially : https://docs.google.com/file/d/0B9yXmUZbfI7_Q0xsR
16 matches
Mail list logo
