The "about" box reports vorbis Post Release 1.0.1 CVS with OggDrop Megamix. Didn't know if that's OK.

  Why the song using oggdropXPd is not the same size as the one using Oggenc2.3 P4 or oggenc-megamix.exe.
I see the song's size with Foobar.

Quote

  Why the song using oggdropXPd is not the same size as the one using Oggenc2.3 P4 or oggenc-megamix.exe.
I see the song's size with Foobar.

I believe 'oggenc-megamix' is a MSVC compile, so I would expect a difference with a different math lib. However, I can't quite see, ATM, why there is a difference with the other two. On a 5.5MB encode at '-q 5', there is a difference of 93 bytes. Entirely inconsequential, but I'd like to establish why!! 

I mean:Is MegaMix better than aoTuVb2 at q4?

oggenc2.exe megamix crashes everytime when a filename that does not exist is given instead of displaying an "error:file does not exist" or whatever. No big deal though, I just thought you'd know.

Both the P3 and P4 compiles behave correctly here.

Quote

Quote

  Why the song using oggdropXPd is not the same size as the one using Oggenc2.3 P4 or oggenc-megamix.exe.
I see the song's size with Foobar.

I believe 'oggenc-megamix' is a MSVC compile, so I would expect a difference with a different math lib. However, I can't quite see, ATM, why there is a difference with the other two. On a 5.5MB encode at '-q 5', there is a difference of 93 bytes. Entirely inconsequential, but I'd like to establish why!! 

Yeah, it's an MSVC compile (with default settings). 

One thing to note is that, since the codebase is essentially aoTuV beta 2, then using bitrate management is not advisable.

--- vorbis-megamix/examples/encoder_example.c.orig      2004-04-21 22:59:10.000000000 +0200
+++ vorbis-megamix/examples/encoder_example.c   2004-07-04 17:55:18.105580606 +0200
@@ -75,7 +75,7 @@ signed char readbuffer[READ*4+44]; /* ou
        puts("usage: encoder_example -q4 filename.wav");
        exit(1);
   }
-  if( !strnicmp(argv[1], "-q", 2) ){
+  if( !strncasecmp(argv[1], "-q", 2) ){
        if( strlen(argv[1]) > 2 ){
                qnum = atof(argv[1]+2);
        }
@@ -114,9 +114,9 @@ signed char readbuffer[READ*4+44]; /* ou
      verify that it matches 16bit/stereo/44.1kHz.  This is just an
      example, after all. */

-  DWORD footer = 0; //+
-  DWORD sa_rate = 44100; //+
-  WORD channel; //+
+  unsigned long footer = 0; //+
+  unsigned long sa_rate = 44100; //+
+  unsigned short channel; //+
   struct stat sbuf; //+
   stat(argv[qx], &sbuf); //+

I'm having trouble compiling megamix (http://www.rarewares.org/quantumknot/vorbis-megamix-src.zip) on Linux.

The code uses some WIN32ism's, this patch is needed to solve this:

Code: [Select]

--- vorbis-megamix/examples/encoder_example.c.orig      2004-04-21 22:59:10.000000000 +0200
+++ vorbis-megamix/examples/encoder_example.c   2004-07-04 17:55:18.105580606 +0200
@@ -75,7 +75,7 @@ signed char readbuffer[READ*4+44]; /* ou
        puts("usage: encoder_example -q4 filename.wav");
        exit(1);
   }
-  if( !strnicmp(argv[1], "-q", 2) ){
+  if( !strncasecmp(argv[1], "-q", 2) ){
        if( strlen(argv[1]) > 2 ){
                qnum = atof(argv[1]+2);
        }
@@ -114,9 +114,9 @@ signed char readbuffer[READ*4+44]; /* ou
      verify that it matches 16bit/stereo/44.1kHz.  This is just an
      example, after all. */

-  DWORD footer = 0; //+
-  DWORD sa_rate = 44100; //+
-  WORD channel; //+
+  unsigned long footer = 0; //+
+  unsigned long sa_rate = 44100; //+
+  unsigned short channel; //+
   struct stat sbuf; //+
   stat(argv[qx], &sbuf); //+

Furthermore I'm having trouble running the configure script, it just spits out:
: bad interpreter: No such file or directory

I can solve this problem by running autoconf, but then the configure script errors with
configure: error: cannot run /bin/sh ./config.sub

Quote

The "about" box reports vorbis Post Release 1.0.1 CVS with OggDrop Megamix. Didn't know if that's OK.

I've uploaded new compiles. No code changes, just the "About" box title corrected. 

I'm sorry if this is off-topic, but neither your MSVC compile nor John's ICL compile accepts wild card (like *.wav). They spit out an error message 'ERROR: Cannot open input file "*.wav": No such file or directory
'.

Aoyumi's compile of his AoTuV b2 on the other hand accepts wild card with no problem, and I love it   Is that a matter of compile options or the compiler difference?

Oh, of course, I had not thought about this. It's working now after a bit of dos2unix :-) Thank you. It would be a good idea that the authors would provide a working tarball for Linux together with the windows binaries.

Quote

I'm sorry if this is off-topic, but neither your MSVC compile nor John's ICL compile accepts wild card (like *.wav). They spit out an error message 'ERROR: Cannot open input file "*.wav": No such file or directory
'.

Aoyumi's compile of his AoTuV b2 on the other hand accepts wild card with no problem, and I love it   Is that a matter of compile options or the compiler difference?

Yes, MSVC compiles don't support wildcards.  The reason aoyumi's compile works is because he used mingw32, where wildcards are known to work with the oggenc's.  I can do a mingw32 compile but John33 can probably doing it quicker than me.

Yes, MSVC compiles don't support wildcards.

Yes, MSVC compiles don't support wildcards.  The reason aoyumi's compile works is because he used mingw32, where wildcards are known to work with the oggenc's.  I can do a mingw32 compile but John33 can probably doing it quicker than me.

Might this additional code improve performances with micro-attacks samples? What do you think? Difference between megamix and GT3b2 are surprising.

For exemple: vorbis is adding something comparable to a "noise curtain" on the creaking.wav sample, and the length of this curtain is much shorter with GT3b2 than with aoTuV/megamix:
http://www.foobar2000.net/divers/tests/200...gamix_aoTuV.gif
[a href="index.php?act=findpost&pid=225718"][{POST_SNAPBACK}][/a]