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 technically all that is necessary. The history of the aacp Content Type was to allow the stream to show in the SHOUTcast Directory, but since Icecast streams cannot show in the SHOUTcast Directory anyway, this doesn't matter, and a content type of aac should be used. This way there is one Content Type for either AAC or aacPlus streams, and the decoder takes it from there. -greg. At 20:12 2006-05-30, Ross Levis wrote:>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" <ross@stationplaylist.com> >To: <icecast@xiph.org> >Sent: Wednesday, May 31, 2006 2:25 PM >Subject: [Icecast] Winamp v5.22 / oddcast / aac+ > > >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 encode AAC+ >and send it to an Icecast server. This is working and playing in Winamp >v5.22. So it appears to be an Oddcast encoding issue. > >You may need to do some analysis Oddsock to see if you can duplicate the >Shoutcast DSP output byte for byte to get around this blocking they seem >to be doing. > >Nullsoft must think they are big enough now to enforce their ideals on >their customers. In the meantime, I'm considering removing Winamp from >my list of compatible players on my website. They can use Windows Media >Player, XMPlay, Foobar2000, etc. > >Regards, >Ross. > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast__________________________________________________________________________ Greg J. Ogonowski VP Product Development ORBAN / CRL, Inc. 1525 Alvarado St. San Leandro, CA 94577 USA TEL +1 510 351-3500 FAX +1 510 351-0500 greg@orban.com http://www.orban.com
Perhaps you are right Greg, but when I was testing earlier, I tried a /stream.mp1 mountpoint, and this also played fine in Winamp 5.22. It just seems biased on the .aac extension in the URL. And surely AAC+ encoded audio files would also have a .aac file extension, so it doesn't make any sense to me. Regards, Ross. ----- Original Message ----- From: "Greg J. Ogonowski" <greg@orban.com> To: "Ross Levis" <ross@stationplaylist.com>; <icecast@xiph.org> Sent: Wednesday, May 31, 2006 5:39 PM Subject: Re: [Icecast] Winamp v5.22 / oddcast / aac+ 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 technically all that is necessary. The history of the aacp Content Type was to allow the stream to show in the SHOUTcast Directory, but since Icecast streams cannot show in the SHOUTcast Directory anyway, this doesn't matter, and a content type of aac should be used. This way there is one Content Type for either AAC or aacPlus streams, and the decoder takes it from there. -greg.
Just got a message from Nullsoft and they think it is a side effect of this fix in 5.22... * Fixed: [in_mp3] Winamp crashes when trying to play any wrongly named .aac file. Regards, Ross. ----- Original Message ----- From: "Greg J. Ogonowski" <greg@orban.com> To: "Ross Levis" <ross@stationplaylist.com>; <icecast@xiph.org> Sent: Wednesday, May 31, 2006 5:39 PM Subject: Re: [Icecast] Winamp v5.22 / oddcast / aac+ 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 technically all that is necessary. The history of the aacp Content Type was to allow the stream to show in the SHOUTcast Directory, but since Icecast streams cannot show in the SHOUTcast Directory anyway, this doesn't matter, and a content type of aac should be used. This way there is one Content Type for either AAC or aacPlus streams, and the decoder takes it from there. -greg.
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 / aac+ 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 technically all that is necessary. The history of the aacp Content Type was to allow the stream to show in the SHOUTcast Directory, but since Icecast streams cannot show in the SHOUTcast Directory anyway, this doesn't matter, and a content type of aac should be used. This way there is one Content Type for either AAC or aacPlus streams, and the decoder takes it from there. -greg. At 20:12 2006-05-30, Ross Levis wrote:>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" <ross@stationplaylist.com> >To: <icecast@xiph.org> >Sent: Wednesday, May 31, 2006 2:25 PM >Subject: [Icecast] Winamp v5.22 / oddcast / aac+ > > >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 encode AAC+ >and send it to an Icecast server. This is working and playing in >Winamp v5.22. So it appears to be an Oddcast encoding issue. > >You may need to do some analysis Oddsock to see if you can duplicate >the Shoutcast DSP output byte for byte to get around this blocking they >seem to be doing. > >Nullsoft must think they are big enough now to enforce their ideals on >their customers. In the meantime, I'm considering removing Winamp from >my list of compatible players on my website. They can use Windows >Media Player, XMPlay, Foobar2000, etc. > >Regards, >Ross. > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast__________________________________________________________________________ Greg J. Ogonowski VP Product Development ORBAN / CRL, Inc. 1525 Alvarado St. San Leandro, CA 94577 USA TEL +1 510 351-3500 FAX +1 510 351-0500 greg@orban.com http://www.orban.com _______________________________________________ Icecast mailing list Icecast@xiph.org http://lists.xiph.org/mailman/listinfo/icecast
Other than the software that is resident on the mobile phones at the time of purchase, I don't know of anything else yet. We might be planning a CE Player, since that area is definitely untapped, but I'm not sure yet. -greg. At 22:56 2006-05-30, Alexander Dal Farra wrote:>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 / aac+ > >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 technically all that is necessary. The history of the aacp >Content Type was to allow the stream to show in the SHOUTcast Directory, but >since Icecast streams cannot show in the SHOUTcast Directory anyway, this >doesn't matter, and a content type of aac should be used. This way there is >one Content Type for either AAC or aacPlus streams, and the decoder takes it >from there. > >-greg. > > > >At 20:12 2006-05-30, Ross Levis wrote: > >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" <ross@stationplaylist.com> > >To: <icecast@xiph.org> > >Sent: Wednesday, May 31, 2006 2:25 PM > >Subject: [Icecast] Winamp v5.22 / oddcast / aac+ > > > > > >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 encode AAC+ > >and send it to an Icecast server. This is working and playing in > >Winamp v5.22. So it appears to be an Oddcast encoding issue. > > > >You may need to do some analysis Oddsock to see if you can duplicate > >the Shoutcast DSP output byte for byte to get around this blocking they > >seem to be doing. > > > >Nullsoft must think they are big enough now to enforce their ideals on > >their customers. In the meantime, I'm considering removing Winamp from > >my list of compatible players on my website. They can use Windows > >Media Player, XMPlay, Foobar2000, etc. > > > >Regards, > >Ross. > > > >_______________________________________________ > >Icecast mailing list > >Icecast@xiph.org > >http://lists.xiph.org/mailman/listinfo/icecast > > > >_______________________________________________ > >Icecast mailing list > >Icecast@xiph.org > >http://lists.xiph.org/mailman/listinfo/icecast > > >__________________________________________________________________________ >Greg J. Ogonowski >VP Product Development >ORBAN / CRL, Inc. >1525 Alvarado St. >San Leandro, CA 94577 USA >TEL +1 510 351-3500 >FAX +1 510 351-0500 >greg@orban.com >http://www.orban.com > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast > >_______________________________________________ >Icecast mailing list >Icecast@xiph.org >http://lists.xiph.org/mailman/listinfo/icecast__________________________________________________________________________ Greg J. Ogonowski VP Product Development ORBAN / CRL, Inc. 1525 Alvarado St. San Leandro, CA 94577 USA TEL +1 510 351-3500 FAX +1 510 351-0500 greg@orban.com http://www.orban.com