On 25/06/13 11:36, marcin at saepia.net wrote:> Ralph, > > so why the same Xiph.Org Foundation ever introduced AAC support in Icecast? >icecast has never had AAC support in. Don't confuse the ability to pass through content unmodified with parsing formats for timing, decoding or encoding. The latter is the issue with AAC. Without encoding or timing support then you could ask why use libshout at all? libshout does not have a maintainer so if you wish to step up and tackle these issues then feel free to do so. karl.
"AAC is added as a supported streaming format Not too many source clients support streaming in this format, but we support it." Source: www.icecast.org, chapter Icecast Release 2.2.0. Even if it is very limited support compared to MP3 or Vorbis, it is still better than nothing. The reason to use libshout instead of raw sockets is DRY. Moreover, adding such functionality to libshout can easily lead to embedding it in GStreamer's shout2send which is much easier process than introducing whole new element into GStreamer. I can initially declare will to take care of libshout and adding AAC support but I will confirm this in July. Marcin 2013/6/25 Karl Heyes <karl at xiph.org>> On 25/06/13 11:36, marcin at saepia.net wrote: > > Ralph, > > > > so why the same Xiph.Org Foundation ever introduced AAC support in > Icecast? > > > > icecast has never had AAC support in. Don't confuse the ability to pass > through content unmodified with parsing formats for timing, decoding or > encoding. The latter is the issue with AAC. Without encoding or timing > support then you could ask why use libshout at all? > > libshout does not have a maintainer so if you wish to step up and tackle > these issues then feel free to do so. > > karl. > > _______________________________________________ > Icecast-dev mailing list > Icecast-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast-dev/attachments/20130625/df9c8d62/attachment.htm
On 25 June 2013 12:16, marcin at saepia.net <marcin at saepia.net> wrote:> "AAC is added as a supported streaming format > > Not too many source clients support streaming in this format, but we support > it." > > Source: www.icecast.org, chapter Icecast Release 2.2.0.~/src/icecast-trunk/src$ grep -i aac * fserve.c: else if(!strcmp(ext, "aac")) fserve.c: type = strdup ("audio/aac"); Yeah, that's all there is. The 'support' was apparently essentially 'check if it does actually work' in pass through mode also with AAC, not only with MP3. We're not going to remove, pass through support, among other things not to break backwards compatibility. I'll soon send some more detailed thoughts on the whole situation. Cheers Thomas