similar to: admin.cgi metadata updates for AAC+ streams

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 /

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".

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

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"

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

Hi all. I believe there is an opportunity to have thousands of Shoutcast servers replaced with Icecast. What will do this is if Icecast can send a MPEG-4 AAC+ header as the first data a player receives when connecting to an audio/aacp stream. The reason for this is the AAC+ support added to Adobe Flash player last December. I could hear a loud sigh of relief each around the world when this was

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

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...

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+

I would just like to confirm that this is suppose to work with Ogg Vorbis streams. I'm using 2.2-kh5 at a hosting company. http://servername.com:9876/admin.cgi?pass=mypassword&mode=updinfo&song=a_song_title I'm sure I have the correct servername, port and password, but it's not working. I can do other admin tasks. When I brought this up a few months ago I'm sure

> you can already do all this outside of icecast (my DoSomething winamp > plugin was specifically written for things like that), so I'm not entirely > sure I see the benefit in sending the data to icecast. Well, it could be used to provide cheaper hosting by subsidizing the bandwidth costs with CD sales, all controlled by the host and not the broadcaster. This would require an

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

Thanks for your reply Karl > It may be that you are just using the wrong url for updating metadata, > http://servername.com:9876/admin/metadata?mount=/stream.ogg&mode=updinfo&song=a_song_title That will be the problem. But how do I specify the userid and password in the URL? Regards, Ross.

I heard that Icecast 2.2 now supports metadata updating via http for vorbis streams. We are adding http metadata support into our broadcasting software for the next release. Can someone point me to a link for the syntax, or is it identical to the Shoutcast syntax? http://www.host.com:port/admin.cgi?pass=Password&mode=updinfo&song=Artist_Title&url=http://someurl.com Has there been

I only have mp3s and it doesn't make sense to me to change all of them to ogg. My MDA(windows mobile phone) plays mp3s with no problem. It uses them as ringtones. Its more widely used in my circles. Why would I and everyone else want to switch to ogg? What is the benefit? Why the shun on mp3? And I can stream at 64 and 32 which is great for those streams that will get a lot of

If you have access to a Windows box, Winamp v5.1 can rip CD's to AAC+. I can't imagine why you would want to do that normally, but it would be useful for comparisons. Ross. ----- Original Message ----- From: "Karl Heyes" <karl@xiph.org> To: "Ross Levis" <ross@stationplaylist.com> Cc: "icecast" <icecast@xiph.org> Sent: Thursday, September

I can understand wanting to boost the adoption of Xiph codecs, but I think restricting the directory to vorbis streams only will not help this endeavour. I can imagine it will just piss a lot of people, including myself, and give Xiph a bad name. I get very few listeners of my AAC+ stream now since this occured. The restriction is not an insentive to switch to Ogg Vorbis at all. The incentive

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

I wrote: > Is there any chance of adding support for something like this... > mount=/stream.ogg&user=username&pass=password&mode=... Actually, this may not be necessary afterall. I'm adding this function into a Windows application I'm writing and the HTTP component I'm using appears to support a separate username & password property for authentication, so I

Karl Heyes wrote: > It uses http auth, so you can use > http://user:pass@servername.com:9876/....... Ah, well that's no good then. Windows doesn't support http auth in a URL anymore, and I'm wanting send this from a Windows application. Is there any chance of adding support for something like this... mount=/stream.ogg&user=username&pass=password&mode=...