similar to: Updates to the "Dare To Compare" pages ?

--- boink <boink@tetter.xs4all.nl> wrote: > The ogg stream is running at around 30 kbps/11 kHz in stereo. The > WMA > stream (provided by yacast.fr) is running at 16 kbps/22 kHz in > mono. Is stereo vs. mono, and 22khz vs. 11khz even a fair comparison? 22khz vs. 11khz: 22khz, by definition, gives the 22khz stream much more frequency range and *opportunity* to sound clearer.

hello, I like your point here .. it's difficult to make such a comparision, since yacast.fr choosed to stream like that. Why did they choose to stream like that? That's beyond me, since Radio France has a budjet of millions. The point of this comparision was to show why is Radio France doing and paying for something like this? Me, with cheap computers which were had no more value (well,

hello all! After having read http://www.xiph.org/ogg/vorbis/listen.html and listened to the examples on that very educational page, I decided to augment the info. This example is more simple, it involves the comparision between two streams of the same radio station, FranceInter (a station of Radio France in Paris). The ogg stream is running at around 30 kbps/11 kHz in stereo. The WMA stream

On 8/31/05, Michael Hale <giftculture@gmail.com> wrote: > Hello everyone, > > I sent the last email prematurely - I had a few more questions. I > don't wish to start a holy war here, but are there certain OSs / > Distros that are preferred for running very busy icecast servers? > We're a Solaris shop currently, but don't mind using linux or BSD if > that

Hello all I have been encoding to OGG as a default for well over a year, but I recently thought I ought to test how it sounds compared to other codecs. I got the Windows Media 9 encoder and I was quite surprised at how bad a job OGG did at quality 0 with a simple piano clip, and how well WMA9 was - I've always considered WMA as being a bit naff, but WMA9 has forced me to re-access this view

On Aug 31, 2005, at 4:19 PM, Michael Smith wrote: > > Our primary aim is to have excellent support for free formats > (primarily, this means the xiph codecs - we'd be happy to help out > with any other freely usable formats, though). As a concession to > existing icecast users, we have basic mp3 support (basically we just > pass it through untouched), and this mechanism works

Hello everyone, I sent the last email prematurely - I had a few more questions. I don't wish to start a holy war here, but are there certain OSs / Distros that are preferred for running very busy icecast servers? We're a Solaris shop currently, but don't mind using linux or BSD if that would make things easier. I see there is a Fedora Core RPM on the icecast page - does that

I must say this is a very confusing issue. I generate AAC+ on an open source system which downloaded some code during installation from the 3GPP source. It appears the encoding software is being freely distributed, and hardware which decodes the stream pays a licence fee at point of manufacture. We have such hardware. In a number of locations. One brand has AAC+ only, not AAC. I note VLC

I'm streaming to 2 mountpoints, one a Vorbis stream and the other an AAC+ stream. Both mountpoints are specifically set up in the Icecast2 configuration with max listeners etc. I'm updating the metadata via http/admin.cgi calls. This is updating the song title information for the Vorbis stream but not the AAC+ stream. Both mountpoints seem to be set up the same. Any ideas? Thanks,

I am not a lawyer, information in this email is no legal advice! On 17 May 2017, at 2:09, Greg Ogonowski wrote: > 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. That only applies to the source code. You still need to license

For archiving from source media (CD usually) to flac? I typically use EAC either from Windows or Wine as it allows for the most configuration. Off the top of my head I think Sound Juicer will do it for *nix, though there are probably others that work just as well. Chris Dave wrote: > Hi, > Thanks. As is usually the case circumstances kind of put this > project on a few days hold,

Yeah, ezstream is a source client just like ices0, but the manner in which they go about processing files or playlists may differ. I don't know too much about ices0 but in the configuration for ezstream you can either specify a single file to stream or you can point it to an m3u playlist and it will play though that, I'm not sure this is compatible with how you currently queue media.

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

Taking the 128 mp3 and re-encoding to flac won't fix any quality issues you may have as they will retain the same 'flaws'. In the end you'll end up with the same quality as you would have seen going from 128 mp3 to q3 ogg. One nice thing about ezstream is that you can specify decoders for multiple formats so if going and ripping all your media again is too daunting a task you

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

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

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 /

Hi, I'll attach my ezstream.xml file to illustrate how ezstream can be "programmed" to do various on-the-fly re-encodings. The basic idea is to treat each <encdec> section as a pair of cmd-line tools: implying a *ix pipe connects the output of the <decode> cmd to the input of the <encode> cmd. The stdout of the <encode> cmd is fed back to ezstream for

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

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"