<div dir="ltr">Okay, that makes more sense, it was the partition boundary splitting which I was referring to and not the blocks, please excuse my misuse of terms.<div><br></div><div>I assume the codec on the receiving end would be able to handle the missing partitions using the error concealment method already built into the codec, and the client therefore would not have to adapt to the new behavior other than to enable error concealment.</div>
<div><br></div><div>However if there exists no information of the partition boundaries, it makes sense that it is not possible to implement.</div><div>Thank you for taking the time to answer</div><div>Kind regards</div><div>
Morten S. Laursen</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-02-19 12:48 GMT+01:00 Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class=""><blockquote type="cite"><div dir="ltr"><div>Yes I was referring to the packing of VP8 payloads as done in the referenced draft. If that is already implemented and used automatically the problem must lie elsewhere as I am using the VP8VideoRTPSink class as you are referring to. </div>
<div>As I understand the payload packing it should split the frames on image block boundaries and therefore a failed packet should only result in that block failing.</div></div></blockquote><div><br></div></div>No, not in our implementation. If a frame is fragmented over multiple RTP packets, then the loss of *any* of these packets will cause the whole frame to be discarded by the receiver.</div>
<div><br></div><div>The VP8 RTP payload format specification does, however, allow for VP8 frames to be split on 'partition' boundaries when packed into RTP packets, in such a way that a receiver *could*, conceivably, receive just some partitions of a VP8 frame if packets are lost. We don't implement this, however (because we don't parse VP8 frames at all, and therefore can't know where 'partitions' start and end within frames). (In any case, this would be useful only if your decoder were able to handle incomplete frames (consisting of some, but not all, 'partitions').)</div>
<div class=""><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:Helvetica;word-spacing:0px">Ross Finlayson<br>
Live Networks, Inc.<br><a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></span></span>
</div>
<br></div></div><br>_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br></blockquote></div><br></div>