similar to: dir.xiph.org only listing Ogg streams

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, On Sun, Jun 18, 2006 at 11:06:25AM -0700, Ralph Giles wrote: > Everyone, > > I have modified the yp cgi script on dir.xiph.org to reject non-ogg > streams. As the site has grown in popularity, it hasn't scaled well, > and maintaining the database was eating most of the resources on the > server. We did some minor tuning

I decided recently to change my stream from Ogg to AAC+ because I have a limited upload bandwidth and I wish to provide the best sound quality at low bitrates. If Ogg was as good ias AAC+ then I would definately use it. I'm apposed to this decision and I think it is a very bad idea. It is only the xiph directory where my potential listeners come from. I will have to switch to using

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

Hi There, 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 streams from one station in the different formats.

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

Michael Smith wrote: >On Wednesday 05 May 2004 08:15, cloper wrote: > > >>List, >>Time and time again I am sure you get this question. I am trying to >>setup a radiostation, and here is what I am looking for: >> >>1. Ability for people to "call in" with say, winamp+oddcast or simplecast. >>2. Ability to change password for the caller at any

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

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

First: I am not a lawyer, this is no legal advice! On 16 May 2017, at 0:25, Robert Jeffares wrote: > Jack, > > I am using AAC+ encoded by Darkice and distributed on Icecast2 on a > Ubuntu server. I had to install a number of open source libraries and > compile darkice from source. No licence. This sounds like it would violate the license, given that the FAQ on

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

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

It's really pretty simple. You can download the code and build it all you want... ...for yourself. It cannot be distributed, sold, or used commercially in any way. That's all. /g. -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Robert Jeffares Sent: Tuesday, 16 May, 2017 17:03 To: icecast at xiph.org Subject: Re: [Icecast] Frauenhofer signing

Greg, Yes, I have noticed that new codec.. AACPlus. Its really impressive in it's abilities, and it's sound quality. I tried to open it up with Windows Media Player and my Flash Player.. didn't seem to like it very much. While It's really kewl as a codec, and it has great support with a couple players, and limited support for the rest, I'll stick with the mainstream for now,

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

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 (=

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

> hmmm.. very interesting.. any info on how they've done the licensing ? No idea how the licensing works. If it's free for the streamer then that may destroy Vorbis's inroads into streaming. 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 anything is being worked on presently.

Good afternoon, On Sat, 2019-05-04 at 10:19 -0400, Fred Gleason wrote: > On Fri, 2019-05-03 at 12:24 -0400, Fred Gleason wrote: > > > Don't use PUT at all. Instead, open a TCP socket connection to the > port > > that the server is running on, write all of your headers to that > > (terminating each one with a CR/LF), send a naked CR/LF to tell > Icecast >

Hello, I’ve a question. I have a station now with Shoutcast and shoutcast transcoder for 2 bitrates. 192kbps mp3 and 64 kbps aac+. I want to transfer these to Icecast. I’ve an working icecast server but i need an auto dj that can encode 2 bitrates, 192kbps mp3 and 64kbps aac. I had a working setup, but my nonstop machine is not on the icecast server but externally. Now in shoutcast transcoder i