Skip to main content
Topic: Ogg Vorbis optimized for speed (Read 217376 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Ogg Vorbis optimized for speed

Reply #325
I think very few people care about audio encoder speed in the era of fast multicore processors. 
Hi
Currently I'm using...
Quote
$ oggenc -v
OggEnc v2.83 (Lancer [Nov 14 2009](SSE) based on aoTuV b5)

With a single-core machine.
Is there anything faster out there - for LINUX?
Bump
Has this thread died, or is it a very very difficult question?

Re: Ogg Vorbis optimized for speed

Reply #326
I think dutch109 answered that question anyway with a link to faster builds for single core machines. 
I think very few people care about audio encoder speed in the era of fast multicore processors. 
Hi
Currently I'm using...
Quote
$ oggenc -v
OggEnc v2.83 (Lancer [Nov 14 2009](SSE) based on aoTuV b5)

With a single-core machine.
Is there anything faster out there - for LINUX?
Bump
Has this thread died, or is it a very very difficult question?

Did you see dutch109's post above? It has a link to newer, more optimized builds than you are running.

Re: Ogg Vorbis optimized for speed

Reply #327
Did you see dutch109's post above? It has a link to newer, more optimized builds than you are running.
I don't see a link to optimized linux builds, it is a thread about patches.

Re: Ogg Vorbis optimized for speed

Reply #328
https://www.freac.org/en
Is 24-bit/192kHz good enough for your lo-fi vinyl, or do you need 32/384?

Re: Ogg Vorbis optimized for speed

Reply #329
It has a link to newer, more optimized builds than you are running.
Unfortunately, it only uses the name of the Lancer, but it works much slower than the original Lancer. Quality is almost the same, all Vorbis encoders provide almost the same quality. libvorbis doesn't use patches from the latest aoTuV versions, just because improvements are barely perceptible, if they are perceptible at all. I don't think that authors of the libvorbis would ignore aoTuV patches if improvements were indisputable.

Re: Ogg Vorbis optimized for speed

Reply #330
What is the difference in speed between the current and original builds?

Re: Ogg Vorbis optimized for speed

Reply #331
libvorbis doesn't use patches from the latest aoTuV versions, just because improvements are barely perceptible, if they are perceptible at all. I don't think that authors of the libvorbis would ignore aoTuV patches if improvements were indisputable.
They might also ignore AoTuv changes because they disagree with the result it produces, see the changelog from libvorbis 1.3.2:
Quote
...
 * vorbisenc: Back out an [old] AoTuV HF weighting that was
   first enabled in 1.3.0; there are a few samples where I
   really don't like the effect it causes.
...
https://github.com/xiph/vorbis/blob/master/CHANGES#L36

 
SimplePortal 1.0.0 RC1 © 2008-2019