<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><br></div><div dir="ltr"><blockquote type="cite">Am 27.12.2020 um 14:15 schrieb Sergio M. Ammirata, Ph.D. <sergio@ammirata.net>:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>Hello,</div><div><br></div><div>Both native and librist modules share the rist:// namespace with librist having higher priority. I did not delete the old ones because I do not know if the librist library will compile for all the architectures VLC is compiled for. If it does, we can remove the old ones and having simple profile is better than not having rist support at all on those.</div></div></blockquote><div><br></div><div>Having both seems like it would be quite a support nightmare and maintenance burden.</div><br><blockquote type="cite"><div dir="ltr"><div>The config options do not match 100% either. Here is the analysis on the config options:</div><div>1) The config for the buffer size is called "latency" on native rist and "buffer" in the librist module.</div><div>2) There are a few config options present in native rist that do not exist on the librist module (packet-size, maximum-jitter, nack-type, disable-nacks, mcast-blind-nacks).</div><div>3) There are a number of new config options present in librist module that do not exist in native rist. These are expected as the new settings/options are related to encryption, selecting profile levels, multiplexing, multipath, congestion control and timing mode.</div><div><br></div><div>Should I fix (1) before 3.0.12 goes out and add (2) to the librist modules options in 4.0?</div></div></blockquote><div><br></div><div>3.0.12 was already tagged, so it is too late I think.</div><br><blockquote type="cite"><div dir="ltr"><div>Regards,</div><div><br></div><div>Sergio</div><div><br></div><div>-----Original Message-----</div><div><b>From</b>: Jean-Baptiste Kempf <<a href="mailto:Jean-Baptiste%20Kempf%20%3cjb@videolan.org%3e">jb@videolan.org</a>></div><div><b>To</b>: "Sergio Ammirata, Ph.D." <<a href="mailto:%22Sergio%20Ammirata,%20Ph.D.%22%20%3csergio@ammirata.net%3e">sergio@ammirata.net</a>>, vlc-devel <<a href="mailto:vlc-devel%20%3cvlc-devel@videolan.org%3e">vlc-devel@videolan.org</a>></div><div><b>Subject</b>: Re: [vlc-devel] PATCH: librist based access and access_output modules</div><div><b>Date</b>: Sat, 26 Dec 2020 16:44:46 +0100</div><div><br></div><!-- text/html --><title></title><div>Hello,<br></div><div><br></div><div>Where is the deletion of the old modules?<br></div><div>Do the config options match?<br></div><div><br></div><div>Best,<br></div><div><br></div><div>On Sat, 26 Dec 2020, at 03:05, Sergio M. Ammirata, Ph.D. wrote:<br></div><blockquote type="cite" id="qt" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>Here are the librist based access and access_output<br></div><div>modules.<br></div><div><br></div><div>They have been rebased against latest master.<br></div><div><br></div><div>Thanks,<br></div><div><br></div><div>Sergio Ammirata<br></div><div><br></div><div><br></div><div>_______________________________________________<br></div><div>vlc-devel mailing list<br></div><div>To unsubscribe or modify your subscription options:<br></div><div><a href="https://mailman.videolan.org/listinfo/vlc-devel">https://mailman.videolan.org/listinfo/vlc-devel</a><br></div><div><br></div><div><b>Attachments:</b><br></div><ul><li>0001-Add-libRIST-based-access-and-access_output-modules.patch<br></li></ul></blockquote><div><br></div><div id="sig60240713"><div class="signature">--<br></div><div class="signature">Jean-Baptiste Kempf - President<br></div><div class="signature">+33 672 704 734<br></div><div class="signature"> <br></div><div class="signature"><br></div></div><div><br></div>
<span>_______________________________________________</span><br><span>vlc-devel mailing list</span><br><span>To unsubscribe or modify your subscription options:</span><br><span>https://mailman.videolan.org/listinfo/vlc-devel</span></div></blockquote></body></html>