<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">AFAIK, there’s no built in mechanism for adaptive streaming.
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There are some things you can do, but may not be flexible enough. For instance, if you have a low-res-h264 and high-res-h264 version of a video, in the server code, you could switch which file you are reading from, seek to the same point
in the media and start outputting those samples. You will need to make sure you send out the SPS and PPS NALs that belong to the new stream first though. Things get a little more complicated/impossible with codecs that don’t support this, and of course audio.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Again, AFAIK, your best bet may be a higher level application strategy of detecting packet loss and immediately dropping to a lower bitrate url in the background until enough of your client play-through buffer is ready. This won’t be seamless,
but I don’t think real-time protocols and adaptive streaming mesh well. You may be better off using something that is made for this, like HLS, DASH or smooth-streaming. Those methods of streaming are tuned to download chunks of media (ex 2seconds worth),
and if it cannot download them faster than real-time, it will start downloading the smaller bitrate chunks of media. The way the chunks are written are specially designed to be seamless (specially in the context of audio).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Jer<o:p></o:p></p>
</div>
</body>
</html>