similar to: add AAC+ file header to new streams

I believe that Oddsock is using a Content Type of aacp. Using a .aac extension with this Content Type may present a conflict. This might actually be by design. I will do some further testing with Winamp and report here tomorrow. I will also double-check with the developer of Winamp for complete clarification. FYI, Orban Opticodec-PC allows the use of either Content Type of aac or aacp. aac is

I'm not sure if this is an icecast issue or oddcast issue or both, but the latest Winamp (v5.22) is not now playing AAC+ streams encoded with Oddcast. Winamp v5.21 and earlier versions work fine. This may be some attempt by Winamp developers to force people to use Shoutcast, or to prevent oddcast from using their enc_aacplus.dll. Right, just took some time to set up the Shoutcast DSP to

hate to burst the "collective sigh of relief" bubble, but Flash's HTTP-based streaming within their player is horribly broken. First off, in order to get it to even *stream*, you need to fake the content-length in the initial response header. Seemingly innocent at first, what this, in fact, does is cause the player to download that much data, regardless of "playstate".

On Tue, May 07, 2019 at 01:59:05PM +0200, Michel van Dop wrote: > [2019-05-07 13:33:29] WARN format/format_get_type Unsupported or legacy > stream type: "audio/aacp". Falling back to generic minimal handler for best > effort. Is one source AAC-LC (standard AAC) and the other HE-AAC v2 (AAC+)? There are three variants of AAC: AAC-LC HE-AAC (= AAC-LC with SBR) HE-AAC v2 (=

Something else, Greg. Are you aware of any 3G / 2.5G (EDGE) clients for mobile phones that support AAC+ streaming? Be it java or symbian based. Thanks Alex -----Original Message----- From: icecast-bounces@xiph.org [mailto:icecast-bounces@xiph.org] On Behalf Of Greg J. Ogonowski Sent: Mittwoch, 31. Mai 2006 07:40 To: Ross Levis; icecast@xiph.org Subject: Re: [Icecast] Winamp v5.22 / oddcast /

Pockect pc phones can use beta player that will play aac+ streams. http://tcpmp.corecodec.org/about For symbian there is this: http://opensource.nokia.com/projects/s60internetradio/index.html that will stream aac+ Im a pocket pc person so don't ask me about symbian stuff. ;-) Regards. For your free copy of the new Ultralon Group Catalogue goto

Hello. I have same problem, and I think that it's because AAC+ uses VBR and when it's changes, is not the same bitrate, because varies... El jue., 9 may. 2019 a las 21:29, Michel van Dop (<mvandop at xs4all.nl>) escribió: > Hi Paul, > > Thank you for the information. I already try a player to discover the > stream type of both streams if the are the same. > But i can

On Mon, 19 Jun 2006, Dennis Heerema wrote: > The nice thing of dir.xiph.org [http://dir.xiph.org/] was the fact that it > supported more or less all formats, this way we were able to send out > different formats, where the listener was able to choose his appriciated > format from and listen to it, also the way it all got listed made it very > easy for a listener to see all te

Here is a patch for icecast 2.3.2 that adds support for listening to mp3 and aac+ streams on the iphone. A quick background on the technical aspects of the patch and why it is needed : With the advent of 3g on the iphone, lots of people have been jumping on the bandwagon of providing internet radio streams that work on the iPhone. The biggest problem is that (without having to install an

I'm am currently using autuvb4 at q-2 mono 44100. This produces roughly 28 to 34kb/s. It's ok but I've heard AACPlus at 32kb/s stereo and it's definately better, unfortunately. Regards, Ross. >> I'm hoping that Monty and others can improve Vorbis to start >> competing >> with AAC+ at low bitrates. Monty said he had some ideas but I wonder >> if

Anyone wanting their AAC/HE-AAC/aacPlus stream(s) listed on Tuner2, please send request(s) with relevant information to me directly. This is free and does not require an Orban Opticodec-PC Encoder. This will also help lighten the load for Xiph. -greg. ORBAN. At 01:45 2006-06-19, Michael Smith wrote: >On 6/19/06, paranoid <paranoid@dds.nl> wrote: > >>To me, that would not be

Hi Rob The stream format has nothing to do with your audio files. I probably have 70% MP3's and 30% Ogg Vorbis files, and 1 or 2 WAV files for jingles on my hard drive. I only encode new CD's to Ogg Vorbis. But my station is streaming in AAC+ format, and I have also streamed in Ogg Vorbis format simultaneously. There is no way I would bother streaming in MP3 format. It's 15+

Hello- You guys have done an excellent job with the Icecast2 server. I probably don't need to tell you that, but I did anyway. We are Coding Technologies licensees and have recently developed a streaming audio encoder supporting AAC/HE-AAC/aacPlus using RTSP/RTP, SHOUTcast HTTP/ICY, and Icecast2 HTTP/ICY, Orban Opticodec-PC. More information here:

Can anyone tell me why this AAC+ Icecast stream will not play. http://s2.stationplaylist.com:7014/listen.aac.m3u The Icecast Server web page looks fine with a 64k stream. We host a small number of streams and other 64k AAC+ streams are working fine but this one won't play in any player. Thanks, Ross. -------------- next part -------------- An HTML attachment was scrubbed...

The open source fdk-aac encoder, available there: https://github.com/mstorsjo/fdk-aac offers pretty good quality. As for libshout, I do not think that it is currently posible to send AAC data using it. First, libshout doesn't have support to buffer and control timing of data sent. And even is you use the un-timed API (shout_send_raw), the library cannot set the proper mime type, due to a

On 17 May 2010, at 22:42, Romain Beauxis <toots at rastageeks.org> wrote: > Le lundi 17 mai 2010 23:36:53, Jamie Bullock a ?crit : >> On 17 May 2010, at 21:07, Geoff Shang wrote: >>> On Mon, 17 May 2010, Jamie Bullock wrote: >>> >>> >>>> I'm write an icecast source client and I'd like to support >>>> streaming of

Hello, I've got a FreeBSD 6 machine running icecast2 and ices0streaming four different streams of mp3's. Now i have a need to stream the same content as either aac+ or ogg vorbis whichever would be easiest to set up and give the best quality. I want these new streams to handle both broadband and dialup users without sacrificing quality. My problem is i really really do not want to

OK, I've organized this. It's not possible to average 32kb/s stereo with Vorbis using VBR. Quality -2 stereo proeduces roughly 32 to 38kb/s which is too high for many modems. I would have to use ABR, but last I tried that, it utilized too much CPU for my 950Mhz PC, and oddcast doesn't appear to support that option anymore. I've tried AACPlus 32kb/s mono and there is very

Ok, it's not as bad as I thought. With some investigation and discussion with a "Major Dude" in the Winamp forums, it appears to be a bug in Winamp v5.22 with streams that end with the mountpoint extension .aac. I changed the mountpoint to end with .aacp and now it works fine. Regards, Ross. ----- Original Message ----- From: "Ross Levis"

Hi Paul, Thanks for the quick response! We use the same type of encoder (Sam Cast) both live for both mountpoints on 96 Kb Joint Stereo. it is difficult to see if it is exactly the same. Is there a player that show exactly this? I will check this. We have use the limit-rate in our config. Thats work better for go to play the last fallback-mount file (i test this). See here our part of the