That all sounds clear now, thank you!
--
Joshua Kordani
LSA Autonomy
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
>> Nonetheless, small NAL units are still a good idea, because they reduce the
>> effect of network packet loss. It's always a good idea, for example, to
>> break large 'I-frame' NAL units into multiple slices; they just don't need
>> to be as small as a standard MTU (1500 bytes), because our s
Ross,
Thank you for your detailed response! I have responded inline.
On 10/8/13 3:11 PM, Ross Finlayson wrote:
You don't have to do that. The LIVE555 code automatically takes care
of fragmenting large NAL units into appropriate-sized RTP packets.
Nonetheless, small NAL units are still a goo
> I wish to use live555 to deliver in memory nals created with x264. In my
> application, I spawn off the live555 event loop into a separate thread from
> the one responsible for doing the encoding. I am configuring my encoder to
> output nals that will fit inside the standard mtu.
You don't
Greetings all,
I wish to use live555 to deliver in memory nals created with x264. In my
application, I spawn off the live555 event loop into a separate thread
from the one responsible for doing the encoding. I am configuring my
encoder to output nals that will fit inside the standard mtu.
I
