<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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US><div class=WordSection1><p class=MsoNormal>Hi Fred. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Appreciate your response. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Maybe in my explanation I have some red and green apples, but I can <o:p></o:p></p><p class=MsoNormal>agree that my understanding is as you explained it. <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The point is that if I can successfully stream mp4 with H.264 and AAC </p><p class=MsoNormal>encoding without any issues to icecast, I can then use ffmpeg to </p><p class=MsoNormal>turn it into HLS which then solves my iOS support issue. The CPU </p><p class=MsoNormal>cost of repackaging MP4 into HLS architecture should be minimal</p><p class=MsoNormal>because at the core it’s all H.264. No transcoding! Low CPU objective </p><p class=MsoNormal>achieved!</p><p class=MsoNormal>Additional bonus is that I already use Apach2 with icecast and </p><p class=MsoNormal>integrating the whole lot into my existing infrastructure is easy.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>My question remains<o:p></o:p></b></p><p class=MsoNormal>If webm/ogv is supported but mp4 not, what are the technical differences </p><p class=MsoNormal>in how icecast handles the one and not the other? What does icecast </p><p class=MsoNormal>manage/do for supported formats as opposed to unsupported ones?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Kind regards<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Wed, 2019-05-01 at 19:56 +0200, Sytze Visser wrote:</p><p class=MsoNormal>> I read somewhere that MP4 is not supported on icecast, which is a</p><p class=MsoNormal>> pity. I have invested a lot in an icecast based audio solution and</p><p class=MsoNormal>> want expand it with video. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It all depends on what one means by 'MP4' (which is more a marketing</p><p class=MsoNormal>term than a technical one). AAC+ (aka 'high efficiency' AAC) works very</p><p class=MsoNormal>well on IceCast, albeit that only covers the audio side on the</p><p class=MsoNormal>equation.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> So my question is now: </p><p class=MsoNormal>> MP4 (H.264) is a close relative of HLS (can also be H.264) which</p><p class=MsoNormal>> brings me very close to a solution.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You're mixing apples and oranges here (pun accidental). H.264 is a</p><p class=MsoNormal>content encoding, like MPEG Layer III (so-called 'MP3') or OggVorbis.</p><p class=MsoNormal>HLS OTOH is a streaming architecture, and as such is largely orthogonal</p><p class=MsoNormal>to the content encoding used. It works by segmenting the media stream</p><p class=MsoNormal>into discrete files and then distributing them via HTTP(S). The big</p><p class=MsoNormal>advantage of this approach is that standard 'garden variety' web</p><p class=MsoNormal>servers (think Apache) can be used to serve the streams, which makes it</p><p class=MsoNormal>play particularly well with CDNs, at the cost of significantly greater</p><p class=MsoNormal>complexity in the encoder and player components. No specialized</p><p class=MsoNormal>'streaming server' (such as Icecast) is required in the HLS ecosystem</p><p class=MsoNormal>at all.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>|---------------------------------------------------------------------|</p><p class=MsoNormal>| Frederick F. Gleason, Jr. | Chief Developer |</p><p class=MsoNormal>| | Paravel Systems |</p><p class=MsoNormal>|---------------------------------------------------------------------|</p><p class=MsoNormal>| An expert is a person who avoids the small errors while he sweeps |</p><p class=MsoNormal>| on to the grand fallacy. |</p><p class=MsoNormal>| |</p><p class=MsoNormal>| -- Benjamin Stolberg |</p><p class=MsoNormal>|---------------------------------------------------------------------|</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>Icecast mailing list</p><p class=MsoNormal>Icecast@xiph.org</p><p class=MsoNormal>http://lists.xiph.org/mailman/listinfo/icecast</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>