PDA

View Full Version : Impact of change to SOX for ogg users



Gerald B. Cox
2005-04-01, 15:50
I've notice Slimserver has changed from oggdec to sox. From what I can gather
this was done to fix an outstanding issue, which I have not experienced. I'm
not really familiar with sox but I ran across this statement in the
documentation:

"SoX can decode all types of Ogg Vorbis files, but can only encode at 128 kbps.
Decoding is somewhat CPU intensive and encoding is very CPU intensive."

Does anyone know what the performance/quality implications are for ogg users as
a result of this change? Are all the files we playback going to be of a 128
kbps quaility even if we originally encoded at higher levels? What is the
performance hit of all this?

Thanks!

vidurapparao
2005-04-01, 15:54
Gerald B. Cox wrote:

>I've notice Slimserver has changed from oggdec to sox. From what I can gather
>this was done to fix an outstanding issue, which I have not experienced. I'm
>not really familiar with sox but I ran across this statement in the
>documentation:
>
>"SoX can decode all types of Ogg Vorbis files, but can only encode at 128 kbps.
>Decoding is somewhat CPU intensive and encoding is very CPU intensive."
>
>Does anyone know what the performance/quality implications are for ogg users as
>a result of this change? Are all the files we playback going to be of a 128
>kbps quaility even if we originally encoded at higher levels? What is the
>performance hit of all this?
>
>

We only use sox for decoding, not for encoding, so you shouldn't see a
quality change. I've not noticed a substantial performance change on my
Windows 1GHz laptop - both oggdec and sox use the same decoding library,
so I suspect that they are equivalent. There's an additional resampling
cost for audio that's under 44.1KHz, but that's balanced out by actually
being able to listen to it at regular speed. :-)

--Vidur