Ogg Vorbis optimized for speed

Topic: Ogg Vorbis optimized for speed (Read 258973 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Ogg Vorbis optimized for speed

Reply #175 – 2006-02-10 00:43:40

I'd like someone experienced to make a static linux build too, as I failed every time trying to do one

Ogg Vorbis optimized for speed

Reply #176 – 2006-02-10 11:19:17

Quote

Quote
dbpoweramp error messages..

Code: [Select]
Encoding standard input to
         "D:\~dmcout.ogg"
at quality 3.00
Internal error: attempt to read unsupported bitdepth 16


Done encoding file "D:\~dmcout.ogg"

        File length:  0m 00.0s
        Elapsed time: 0m 00.0s
        Rate:         0.0000
        Average bitrate: 1.$ kb/s
^^ without any extra options, just ' - --output=D:\~dmcout.ogg'

after I removed this from the options file....
--raw --raw-chan=[Channels] --raw-bits=[BitsPerSample] --raw-rate=[SamplesPerSec]
I got this error
ERROR: Input file "(stdin)" is not a supported format

I also tried using [WriteWaveRIFF], but gave me the same error as above (and other junk), and it made my computer 'beep' at me

even though piping works fine with it in foobar2000, it is obvious to me that something is wrong
[{POST_SNAPBACK}][/a]
I also test it with a .pcm file saved from CoolEdit Pro and same error occured.
[a href="index.php?act=findpost&pid=362957"][{POST_SNAPBACK}][/a]

From [a href="http://64.233.179.104/translate_c?hl=en&sl=ja&u=http://pc7.2ch.net/test/read.cgi/software/1136822006/266&prev=/search%3Fq%3Dhttp://pc7.2ch.net/test/read.cgi/software/1136822006/%26hl%3Den%26hs%3DEOq%26lr%3D%26client%3Dfirefox%26rls%3Dorg.mozilla:en-US:unofficial%26sa%3DG]Author's reply[/url], it is a bug with oggenc 2.8.

Ogg Vorbis optimized for speed

Reply #177 – 2006-02-10 14:08:38

If you are looking for a (more or less) perfect frontend for transcoding your FLAC´s, Monkey´s audo- or WAVPack-files to OGG-vorbis, including perfect transfer of the TAG´s from the original and replaygaining (automatically after the encoding process), just stick with this frontend:

Universal-Front -All-In-One- (7-zip-packed, 3,29 MB)
(Note: All necessary codecs are already included.)

Ogg Vorbis optimized for speed

Reply #178 – 2006-03-01 15:02:44

Lancer 20060301 is out.
http://homepage3.nifty.com/blacksword/
Now SSE and SSE2 optimizations!

Ogg Vorbis optimized for speed

Reply #179 – 2006-03-01 15:24:59

Translated by excite.co.jp
--
2006/03/01 Lancer 20060301

The optimization option when compiling is reexamined.
Oggenc is renewed to Ver.2.81.
Because the function of the management of the project of Visual Studo is unstable, the development environment is completely shifted to the command line.
The optimization code for SSE2 is implemented.
The optimization code that uses an in-line assembler for bark_noise_hybridmp and seed_curve is implemented.
The SSE optimization of mdct_forward is changed.
Double-Step Bresenham algorithm is implemented on render_line and render_line0.
AMD CodeAnalyst is introduced into the code analysis.

[EDIT]fine tuning translation.[/EDIT]

Ogg Vorbis optimized for speed

Reply #180 – 2006-03-01 15:36:40

Test on Pentium M 715 (2MB L2 Cache, 1.5GHz, 400MHz FSB)

Code: [Select]

c:\Temp\test>oggenc_aotuv_451.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
         "test.ogg"
at quality 3,00
        [ 99,6%] [ 0m00s remaining] /

Done encoding file "test.ogg"

        File length:  2m 46,0s
        Elapsed time: 0m 20,0s
        Rate:         8,3069
        Average bitrate: 105,0 kb/s


c:\Temp\test>oggenc2_lancer_20060131.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
         "test.ogg"
at quality 3,00
        [ 99,6%] [ 0m00s remaining] /

Done encoding file "test.ogg"

        File length:  2m 46,0s
        Elapsed time: 0m 07,9s
        Rate:         21,1372
        Average bitrate: 105,0 kb/s


c:\Temp\test>oggenc2_lancer_20060209_sse2test.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
         "test.ogg"
at quality 3,00
        [ 99,6%] [ 0m00s remaining] /

Done encoding file "test.ogg"

        File length:  2m 46,0s
        Elapsed time: 0m 07,8s
        Rate:         21,3080
        Average bitrate: 105,0 kb/s

c:\Temp\test>oggenc2_lancer_20060301_p3.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
         "test.ogg"
at quality 3,00
        [ 99,6%] [ 0m00s remaining] /

Done encoding file "test.ogg"

        File length:  2m 46,0s
        Elapsed time: 0m 07,9s
        Rate:         21,0970
        Average bitrate: 105,0 kb/s


c:\Temp\test>oggenc2_lancer_20060301_p4.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
         "test.ogg"
at quality 3,00
        [ 99,6%] [ 0m00s remaining] /

Done encoding file "test.ogg"

        File length:  2m 46,0s
        Elapsed time: 0m 07,6s
        Rate:         21,8345
        Average bitrate: 105,0 kb/s


c:\Temp\test>

Ogg Vorbis optimized for speed

Reply #181 – 2006-03-02 10:24:33

May I post bugreport here? Thanks!

Can't build new lancer code by gcc into linux. Error is

Code: [Select]

../../lib/psy.c: In function 'seed_curve':
../../lib/psy.c:745: error: 'post05' undeclared (first use in this function)
../../lib/psy.c:745: error: (Each undeclared identifier is reported only once
../../lib/psy.c:745: error: for each function it appears in.)
../../lib/psy.c:768: error: 'post06' undeclared (first use in this function)

I think it's because of define at line 635:

Code: [Select]

#if     defined(_MSC_VER)
                int post07       = ((post1-i)&(~1));
                int post06       = (post07&(~3));   
                int post05       = (post06&(~7));

and using post05, post06 & post07 into #else block.
Well, I've move these declarations before "#if defined(_MSC_VER)" and can compile code.

But with gcc 4.0.2 I get

Code: [Select]

% oggenc test.wav -o /dev/null
Opening with wav module: WAV file reader
Encoding "test.wav" to 
         "/dev/null" 
at quality 3,00
Mode initialisation failed: invalid parameters for quality

With gcc 3.4.5 I get error at compile time again, but more mysterious

Code: [Select]

../../lib/floor1.c: In function `floor1_encode':
../../lib/floor1.c:2333: internal compiler error: in trunc_int_for_mode, at explow.c:54
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-3.4/README.Bugs>.

O'key... At last I'm trying with gcc 3.3.6 and compile code fine like with gcc 4.0.2. And oggenc works! But bitrate not as with generic aoTuV 4.51. For aoTuV it's 115.3 kb/s but for Lancer it's 111,8 kb/s. And difference between tracks in Audacity up to 0.2 of amplitude range.

Is this code untested for any compiler other MS Visual C ? Is it planned to support GCC? (optimization up to x2-x3 is very good thing!)

Ogg Vorbis optimized for speed

Reply #182 – 2006-03-02 14:11:29

Lancer 20060302 is released!

Because there's a problem with decoding function of SSE2 edition of Lancer 20060301, Lancer 20060302 was released.

The straight line drawing algorithm of the fixed point of "Extremely Fast Line Algorithm" was improved and implemented.
It quickens because it became easy to optimize SIMD though it is a
little.

Ogg Vorbis optimized for speed

Reply #183 – 2006-03-02 16:05:36

Quote

Lancer 20060302 is released!

It doesn't seem to be working...

In foobar (0.8.3), I get the following error:

Code: [Select]

INFO (foo_clienc) : CLI encoder: C:\Program Files\Codec\Vorbis\Lancer 2.81 2006 03-02\oggenc.exe
INFO (foo_clienc) : Destination file: file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
INFO (foo_clienc) : Source file: file://F:\Albums\Bad Company\Bad Company (AF Gold)\05 Bad Company.wv
INFO (foo_clienc) : 44100Hz 24bps 2ch
INFO (foo_clienc) : Encoding took 62 milliseconds, speed 1.68x
ERROR (foo_input_std) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_speex) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_input_std) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_speex) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
INFO (CORE) : attempting to edit file info : file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
WARNING (CORE) : file info update failure on : file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_diskwriter) : Conversion failed.

...and from the command line:

Code: [Select]

Encoding standard input to "C:\Documents and Settings\372\Desktop\05 Bad Company.ogg" at quality 6.00

can't write .WAV data, disk probably full!

** ERRORS:
General errors: 1
Press any key to continue...

I'm using oggenc281_p4_lancer20060302 on a P4 3.2GHz system with 1G of RAM.
The old oggenc28_p4_lancer20060131 works fine.

I notice in the foobar error report it says:

Code: [Select]

INFO (foo_clienc) : 44100Hz 24bps 2ch

...but the file is 16bps, not 24.

Any suggestions?

Thanks!

~esa

Ogg Vorbis optimized for speed

Reply #184 – 2006-03-02 16:24:14

@esa372

Set "Maximum bitdepth" to 16bits, works here with fb2k 0.9RC

Cheers,

Tim

Ogg Vorbis optimized for speed

Reply #185 – 2006-03-02 16:27:10

Quote

Set "Maximum bitdepth" to 16bits, works here with fb2k 0.9RC
[a href="index.php?act=findpost&pid=368571"][{POST_SNAPBACK}][/a]

I was wrong, on a second file, foobar reports:
"Error writing to file (Encoder has terminated prematurely with code -1073741819; please re-check parameters)"

Ogg Vorbis optimized for speed

Reply #186 – 2006-03-02 16:41:41

Quote

Lancer 20060302 is released!

It doesn't seem to be working...

In foobar (0.8.3), I get the following error:

Code: [Select]

INFO (foo_clienc) : CLI encoder: C:\Program Files\Codec\Vorbis\Lancer 2.81 2006 03-02\oggenc.exe
INFO (foo_clienc) : Destination file: file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
INFO (foo_clienc) : Source file: file://F:\Albums\Bad Company\Bad Company (AF Gold)\05 Bad Company.wv
INFO (foo_clienc) : 44100Hz 24bps 2ch
INFO (foo_clienc) : Encoding took 62 milliseconds, speed 1.68x
ERROR (foo_input_std) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_speex) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_input_std) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_speex) : Ogg stream is corrupted : C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
INFO (CORE) : attempting to edit file info : file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
WARNING (CORE) : file info update failure on : file://C:\Documents and Settings\372\Desktop\05 Bad Company.ogg
ERROR (foo_diskwriter) : Conversion failed.

...and from the command line:

Code: [Select]

Encoding standard input to "C:\Documents and Settings\372\Desktop\05 Bad Company.ogg" at quality 6.00

can't write .WAV data, disk probably full!

** ERRORS:
General errors: 1
Press any key to continue...

I'm using oggenc281_p4_lancer20060302 on a P4 3.2GHz system with 1G of RAM.
The old oggenc28_p4_lancer20060131 works fine.

I notice in the foobar error report it says:

Code: [Select]

INFO (foo_clienc) : 44100Hz 24bps 2ch

...but the file is 16bps, not 24.

Any suggestions?

Thanks!

~esa
[a href="index.php?act=findpost&pid=368569"][{POST_SNAPBACK}][/a]

What's your CPU?
There's report that Athlon64 3000+ doesn't work with this build but P4 2.6G works.

EDIT: Typo.

Ogg Vorbis optimized for speed

Reply #187 – 2006-03-02 16:56:54

Quote

Quote
Set "Maximum bitdepth" to 16bits, works here with fb2k 0.9RC
I was wrong, on a second file, foobar reports:
"Error writing to file (Encoder has terminated prematurely with code -1073741819; please re-check parameters)"

Too bad... thanks anyway.

Quote

What's your CPU?

Intel P4 3.2GHz

Ogg Vorbis optimized for speed

Reply #188 – 2006-03-02 17:09:00

The good news is that today's P3 build works here (P4 2,66). I just encoded 4 cd's to be sure (Yesterday's P4 build worked too, today's P4 build gives me strange errors... ).

Cheers,

Tim

Ogg Vorbis optimized for speed

Reply #189 – 2006-03-03 00:28:58

Mr 637 said that there's some problems with straight line drawing algorithm and the compiler. A bug fix version will release in next Monday.

Ogg Vorbis optimized for speed

Reply #190 – 2006-03-03 01:50:42

Quote

Mr 637 said that there's some problems with straight line drawing algorithm and the compiler. A bug fix version will release in next Monday.

Good to know - thanks!

Ogg Vorbis optimized for speed

Reply #191 – 2006-03-03 03:12:56

cool... this one (march 2, 2006 for those reading this a long time from now) works with piping in dbpoweramp... but it's slower than the november 05 release

edit: actually, the new one is faster... silly me must have been running too many other programs at the time of my initial test nov. lancer went 20x in dbpoweramp, and the new one at 24x

Ogg Vorbis optimized for speed

Reply #192 – 2006-03-03 11:13:02

Quote

Quote
Mr 637 said that there's some problems with straight line drawing algorithm and the compiler. A bug fix version will release in next Monday.
Good to know - thanks!

[a href="index.php?act=findpost&pid=368672"][{POST_SNAPBACK}][/a]

Mr. 637 is always come as a surprise!
Lancer 20060303 is released!
--
Mr 637 said in 2ch board,
"After all, it is a lapse of judgment of the priority of the operator. It is shameful. "

Ogg Vorbis optimized for speed

Reply #193 – 2006-03-03 11:49:00

The bug with variable declaration in psy.c has gone but resulted bitrate differ from generated by generic aoTuV 4.51 (compiled by gcc 3.3.6 with -march=athlon-xp, run on AthlonXP+ 2200 under Ubuntu 5.10).

Ogg Vorbis optimized for speed

Reply #194 – 2006-03-03 15:47:06

Quote

Mr. 637 is always come as a surprise!
Lancer 20060303 is released!

Excellent - thank you!

It's working fine on my system now.

Test @ -q6:
Bad Company (2006 AudioFidelity remaster)

aoTuV b4.51 P4 - 2:15 encode time
Lancer 20060303 P4 - 1:27 encode time

Identical bitrates and file sizes.

Ogg Vorbis optimized for speed

Reply #195 – 2006-03-04 11:54:24

Athlon64 X2 3800+ E3 (512 L2 Cache, 2x2000, 200Mhz FSB)
oggenc281_p4_lancer20060303
D:\test>oggenc2.exe test.wav
Opening with wav module: WAV file reader
Encoding "test.wav" to
"test.ogg"
at quality 3,00
[100,0%] [ 0m00s remaining] |

Done encoding file "test.ogg"

File length: 73m 11,0s
Elapsed time: 2m 15,9s
Rate: 32,3169
Average bitrate: 114,6 kb/s

so, what about dual core ?

Ogg Vorbis optimized for speed

Reply #196 – 2006-03-04 23:20:42

Launching two encodes in parallel, not setting the affinity by hand like so:

Code: [Select]

C:\temp>type code.bat
@echo off
start codeone 1
start codeone 2

C:\temp>type codeone.bat
@echo off
oggenc2 -q 5 %1.wav
pause

Results in:

Code: [Select]

Done encoding file "1.ogg"

        File length:  4m 16,0s
        Elapsed time: 0m 07,9s
        Rate:         32,4412
        Average bitrate: 171,7 kb/s

Done encoding file "2.ogg"

        File length:  4m 16,0s
        Elapsed time: 0m 08,0s
        Rate:         32,0600
        Average bitrate: 171,7 kb/s

They start and complete in almost exactly the same time, so the effective rate is about 64x real-time!

(The source file(s) are "Reflect the storm" off the new In Flames album, which I made disk-cache hot by checksumming them prior to starting the script. The CPU is an AMD X2 3800+ at 2.0GHz (the default) with cool'n'quiet enabled)

Ogg Vorbis optimized for speed

Reply #197 – 2006-03-05 09:35:06

You can test this easily with foobar2000 0.9 Release Candidate: it will automagically encode in parallel on multiprocessor machines.

Ogg Vorbis optimized for speed

Reply #198 – 2006-03-05 11:16:31

but if i have a really big file? 700 mbs of audio - one track or so...
[span style='font-size:8pt;line-height:100%']i remember it was a nice app out there - gogo2, now it speeds up at 250x on my pc and i think that is tyni int counter limination
the homepage was also on homepage1.nifty.com/herumi
so i would like to ogg will be faster, btw multicore lame 3.97 beta 2 gives me only 45x, so possible 64x speed of ogg on x64 platform will be amazing think, isnt`it?[/span]

update:
I wrote to the author about multi-core and got this:

Quote

Hello,

The MultiThreading function is certainly cool. But I do not have
dual-core machine. I have Athlon-XP 1700+ and Pentium4M only.

It should be detailed to the algorithm of vorbis to do the work
and requires more memory in process.
Therefore, it is not easy. However, if a new machine is obtained,
I will challenge it.

Ogg Vorbis optimized for speed

Reply #199 – 2006-03-10 17:14:55

Lancer 20060310 is released.

Notice