Hydrogenaudio Forums

Lossy Audio Compression => Ogg Vorbis => Ogg Vorbis - General => Topic started by: forart.eu on 2010-03-26 09:07:18

Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: forart.eu on 2010-03-26 09:07:18
Quote
libao 1.0.0 released
libVorbis 1.3.1 released
vorbis-tools 1.4.0 released


Xiph.Org announces the release of libao-1.0.0, libvorbis-1.3.1 and vorbis-tools-1.4.0. This is a coordinated update of the audio libraries and tools to deploy improved surround-sound support across the libraries and toolchain.

libao improvements
  • AO returned to active development
  • Added surround channel mapping API and capability
  • Updated all drivers on modern installs
  • New config file options
  • Driver options may be specified in config file
  • Support for MacOSX updated to 10.5 and later
  • Build in WMM driver rather than using dlopen()
  • Added Roar Audio driver
  • Added OpenBSD SNDIO driver
  • Workaround for ESD non-4096 byte write bug
  • Workaround aRts server crash bug
  • Workaround for VIA82xx click/crackle bugs under ALSA
  • Remove dead/unused drivers (solaris, alasa05, mmsound)
  • Numerous patches from multiple downstreams


libvorbis improvements
libVorbis 1.3.0 was briefly available as an unreleased staging snapshot. This official release bumps the version number to 1.3.1 to avoid any possible confusion.
  • Optimized/coupled surround support for 5.1 encoding at 44.1/48kHz
  • Added encoder control call to disable channel coupling
  • Corrected an overflow bug in very low-bitrate encoding on 32 bit machines that caused inflated bitrates
  • Numerous API hardening, leak and build fixes
  • Correct bug in 22kHz compand setup that could cause a crash
  • Correct bug in 16kHz codebooks that could cause unstable pure tones at high bitrates


vorbis-tools improvements
vorbis-tools 1.4.0 is the first official release of vorbis-tools since 1.2.x. 1.3.x was never offered as an official snapshot, though various versions were widely deployed as patch-sets by distributions.
  • Implement corrected channel mappings for all input and playback file types
  • Correct an possible infinite loop in WAV input reading code when header is corrupt
  • Implement "disable_coupling" option for oggenc
  • Fix Ctrl-C lockup bug in ogg123
  • ogg123 directory playback in sorted order
  • Add WAVEFORMATEXTENSIBLE support
  • More translations
  • Add '-' as stdin/out filename in vcut
  • Add -lnetwork check for socket in configure
  • Remove 'extra' F parameter from ogg123 remote output
  • Numerous code and build fixes


Downloads

The libao 1.0.0 release is available from http://downloads.xiph.org/releases/ao/ (http://downloads.xiph.org/releases/ao/)

The libvorbis 1.3.1 and vorbis-tools 1.4.0 releases are available from http://downloads.xiph.org/releases/vorbis/ (http://downloads.xiph.org/releases/vorbis/)

Happy hacking!

Monty
Xiph.Org
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-26 09:10:53
libogg 1.2.0 is also part of this release.

I'll produce a set of new compiles through the day and post back here when they're available.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: forart.eu on 2010-03-26 09:42:15
Yep, was a yesterday release...

john33, time for x64 builds too ?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-26 11:46:08
Yep, was a yesterday release...

john33, time for x64 builds too ?

Very probably!
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: HotshotGG on 2010-03-26 16:17:33
Sweet I wonder if the Ubuntu team has made a x86_64 debian compile for Linux yet! I will update my dependencies.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-26 17:46:54
I'll produce a set of new compiles through the day and post back here when they're available.

I am progressing through these, there are just a few more code changes than expected.

For the main builds, I am proposing providing win32 Generic, win32 P4 and win64 builds. From initial testing, the win64 builds look a fair bit quicker, but I've not done any exhaustive testing. Just for the record, I am building and testing on a q6600 @ 3.2GHz, 8GB RAM running Windows 7 64 bit Ultimate (fully up-to-date) and using ICL 11.1.054.

I should have all the builds ready later this evening, but I'll post back here.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-26 21:47:56
I'm afraid these may not be completed until tomorrow now as the changes are not going quite as easily as was hoped. Sorry about this, but I'd rather try to get this right than rush them out and get it wrong.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: viktor on 2010-03-26 22:04:25
what changes are you making? will you try to get the fixes go upstream?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: nycjv321 on 2010-03-26 22:05:35
does this version of libvorbis incorporate the latest aotuv build? or a better question which would be understood to give better quality?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: HotshotGG on 2010-03-26 22:32:24
Quote
does this version of libvorbis incorporate the latest aotuv build? or a better question which would be understood to give better quality?


No it does not. Monty said he was concerned about any sort of regressions if I understand the release notes above. I am sure they will be incorporated eventually!, but he also might want to double check the source. It happens. The problem with continuously tuning the encoder is just that in some cases there are regressions.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-27 19:11:16
OK, there is a full set of compiles now on Rarewares, but no 64 bit builds at present. The reason for the delay in putting these up was that I was trying to resolve some issues with 64 bit builds but they are still outstanding, at the moment. I will continue to work on these, but I didn't want to delay the availability of the standard compiles any longer.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: viktor on 2010-03-27 21:06:56
OK, there is a full set of compiles now on Rarewares, but no 64 bit builds at present. The reason for the delay in putting these up was that I was trying to resolve some issues with 64 bit builds but they are still outstanding, at the moment. I will continue to work on these, but I didn't want to delay the availability of the standard compiles any longer.

what problems do you face? i'm also maintaining a few builds (http://winbuild.daydreamer.nu/), so i may already have faced similar problems.

Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dukers on 2010-03-27 23:34:41
Good to see Xiph projects alive again. I'm looking forward to seeing aotuv improvements incorporated in official libvorbis.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: forart.eu on 2010-03-27 23:50:13
OK, there is a full set of compiles now on Rarewares, but no 64 bit builds at present.

 
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: callmeace on 2010-03-28 00:19:17
Thanks for the windows builds

Is there going to be a Vorbis Tools package built for Windows also?
I tried to download what I thought would be the binary from:
http://downloads.xiph.org/releases/vorbis/...tools-1.4.0.zip (http://downloads.xiph.org/releases/vorbis/vorbis-tools-1.4.0.zip)

  ..but it contains source files! 

  Thankyou again
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: tebasuna51 on 2010-03-28 19:59:11
The windows binaries from Rarewares have many problems with channel mapping.
The sources don't coincide with vorbis-tools 1.4.0, at least with the necesary remap of multichannel wav input.

in audio.c vorbis-tools 1.4.0 there are:
Code: [Select]
static int wav_permute_matrix[8][8] =
{
  {0},              /* 1.0 mono   */
  {0,1},            /* 2.0 stereo */
  {0,2,1},          /* 3.0 channel ('wide') stereo */
  {0,1,2,3},        /* 4.0 discrete quadraphonic */
  {0,2,1,3,4},      /* 5.0 surround */
  {0,2,1,4,5,3},    /* 5.1 surround */
  {0,2,1,4,5,6,3},  /* 6.1 surround */
  {0,2,1,6,7,4,5,3} /* 7.1 surround (classic theater 8-track) */
};


with support until 8 channels, and the same matrix in oggenc2.85srcs is only for 6 channels:
Code: [Select]
static int wav_permute_matrix[6][6] =
{
    {0},
    {0,1},
    {0,2,1},
    {0,1,2,3},
    {0,2,1,3,4},
    {0,2,1,4,5,3}
};


After vorbis-tools 1.4.0 use the matrix always for wavs until 8 channels:
Code: [Select]
        if (wav->channels <= 8)
            /* Where we know the mappings, use them. */
            memcpy(wav->channel_permute, wav_permute_matrix[wav->channels-1],
                    sizeof(int) * wav->channels);
        else
            /* Use a default 1-1 mapping */
            for (i=0; i < wav->channels; i++)
                wav->channel_permute[i] = i;


But oggenc2.85srcs use the matrix only with a few MaskChannel and never if the wav don't have WAVE_FORMAT_EXTENSIBLE header:
Code: [Select]
        if (wav->channel_map)
            /* Where we know the mappings, use them. */
            memcpy(wav->channel_permute, wav_permute_matrix[wav->channels-1], sizeof(int) * wav->channels);
        else
            /* Use a default 1-1 mapping */
            for (i=0; i < wav->channels; i++)
                wav->channel_permute[i] = i;


Please, anybody can compile (for windows) vorbis-tools 1.4.0 without changes to test the differences?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-28 20:21:40
Actually, it's the source download that hasn't been updated. The compiles use the new channel maps.

Edit: And, the reason the sources haven't been updated is that while the previous versions compiled and ran for 64 bit, the new versions do not. The new versions compile and process FLAC input correctly, but crash on wave input! I will not update the sources until I at least understand why the problem occurs, and hopefully have a resolution.

@Viktor: Although in the oggenc2 sources, the wave file opening and reading routines are changed very little from the previous version, the crash on reading from the wave file occurs without fail. This occurs with the new libvorbis. The new libogg does not cause a problem. What is frustrating is that in the wave file open routines, there are perhaps 6 lines of additional code, the actual wave file read routines are unchanged and it appears to be the reading that causes the problem. As already mentioned, with libvorbis 1.2.3, there is no problem and all works well for 64 bit. I would welcome any comment on this as I am struggling to see where the problem lies. If it's in the new libvorbis, then I don't have the knowledge to deal with it, but unless it's in the initialisation, it seems to occur at the first attempt to read the wave file.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: tebasuna51 on 2010-03-29 03:37:44
Actually, it's the source download that hasn't been updated. The compiles use the new channel maps.

Maybe, but only for wavs with header WAVE_FORMAT_EXTENSIBLE and some ChannelMask.
The remap must be used for all wav files with less than 9 channels.

BTW, the oggdec in vorbis-tools 1.4.0 have the old remap matrix (only 6 channel) and without WAVE_FORMAT_EXTENSIBLE output, maybe your oggdecV1.9.6 can be improved adding ChannelMask for 6.1 and 7.1 (in audio.c):
Code: [Select]
    else if (aufile->channels == 7)
        channelMask = 1807;
    else if (aufile->channels == 8)
        channelMask = 1599;


using this amplied (8x8) remap matrix:
Code: [Select]
    int permute[8][8] = {{0}, {0,1}, {0,2,1}, {0,1,2,3}, {0,2,1,3,4}, {0,2,1,5,3,4}, {0,2,1,6,5,3,4}, {0,2,1,7,5,6,3,4}};


and permute until 8 channels (instead 6)
Code: [Select]
    if (channels > 2 && channels < 9) {
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-29 09:25:16
Actually, it's the source download that hasn't been updated. The compiles use the new channel maps.

Maybe, but only for wavs with header WAVE_FORMAT_EXTENSIBLE and some ChannelMask.
The remap must be used for all wav files with less than 9 channels.

I know that's what it says in the Xiph oggenc source, but if the multichannel file has no WAVE_FORMAT_EXTENSIBLE header, remapping the channels makes absolutely no sense as you have no idea what order the channels should be in and any remapping is only a guess that could be completely wrong. If you can convince my I'm wrong about this (other than what it says in Xiph's oggenc) I'm willing to listen, but to remap channels on the basis of a guess seems daft to me. What would make sense would be an option to specify the channel order in the absence of the channel mask being present in the header.
BTW, the oggdec in vorbis-tools 1.4.0 have the old remap matrix (only 6 channel) and without WAVE_FORMAT_EXTENSIBLE output, maybe your oggdecV1.9.6 can be improved adding ChannelMask for 6.1 and 7.1 (in audio.c):
Code: [Select]
    else if (aufile->channels == 7)
        channelMask = 1807;
    else if (aufile->channels == 8)
        channelMask = 1599;


using this amplied (8x8) remap matrix:
Code: [Select]
    int permute[8][8] = {{0}, {0,1}, {0,2,1}, {0,1,2,3}, {0,2,1,3,4}, {0,2,1,5,3,4}, {0,2,1,6,5,3,4}, {0,2,1,7,5,6,3,4}};


and permute until 8 channels (instead 6)
Code: [Select]
    if (channels > 2 && channels < 9) {

Done and I've bumped the version to 1.9.7.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-29 14:24:16
Just to add to the 64 bit conundrum, the 64 bit compiles that fail on Windows 7 64 Ultimate, run fine on XP Pro x64! May be that will give someone an extra clue.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: callmeace on 2010-03-29 22:02:17
Oggdec download file says v197 , but on rarewares download page it still says v196

  On the rarewares index page it announces a v140 build for Vorbis Tools, but I have looked through the site and can't find it!

Have I missed it, or will it be something forthcoming?

  Thanks
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-29 22:27:44
Oggdec download file says v197 , but on rarewares download page it still says v196

Ooops! I forgot to change the heading on the page. Thanks for letting me know, I'll take care of it.
On the rarewares index page it announces a v140 build for Vorbis Tools, but I have looked through the site and can't find it!

Have I missed it, or will it be something forthcoming?

  Thanks

Actually, to split hairs, it says 'incorporating'. Some of what is in the vorbis-tools release finds its way into my compiles, but I've never provided a 'vorbis-tools' build, per se, and it won't happen any time soon.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: HotshotGG on 2010-03-29 23:27:12
I was able to successfully build the new vorbis-tools packages from the source if anyone has any questions let me know it's tricky, but it's so worth it if you have an older distros like Ubuntu 9.10 and earlier and are stuck in "old synaptic package hell" as I call it ;D. Surprisingly it was the first piece of software that I compiled that actually built correctly, besides writing my own code for the classes I am taking.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: xiphmont on 2010-03-30 01:39:57
I know that's what it says in the Xiph oggenc source, but if the multichannel file has no WAVE_FORMAT_EXTENSIBLE header, remapping the channels makes absolutely no sense as you have no idea what order the channels should be in and any remapping is only a guess that could be completely wrong.


Actually, the Microsoft docs say that if no channel mask is present, the default is all channels are present in order of bitmask.  This is definitely what common usage is following.

OTOH, the Microsoft docs also say that > stereo requires WAVE_FORMAT_EXTENSIBLE, but that feels like a retcon.  I do know that wav files in the wild quite often just use WAVEFORMATEX for > 2 channels and that's normally handled as if it was WAVE_FORMAT_EXTENSIBLE with a dwChannelMask of 0.  In short, follow the default order (L,R,C,LFE,BL,BR,SL,SR...)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: felix26591 on 2010-03-30 01:56:01
How does libvorbis 1.3.1 compare to aotuv b5.7???
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: icedtea on 2010-03-30 04:03:21
xiphmont is aotuv still going to be merged? Last I heard it was going to be merged in 1.3.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: gameplaya15143 on 2010-03-30 05:42:39
oggenc2 -q 0 --advanced-encode-option lowpass_frequency=99

First test resulted in 6 channels in only 127kbps!

<3 xiphmont  thanks for all the great work.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: quadamage on 2010-03-30 07:08:13
xiphmont is aotuv still going to be merged? Last I heard it was going to be merged in 1.3.

I am also concerning about this, by a quick test, version 1.3.1 is a bit faster than 1.2.3
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-30 07:41:36
...
Actually, the Microsoft docs say that if no channel mask is present, the default is all channels are present in order of bitmask.  This is definitely what common usage is following.

OTOH, the Microsoft docs also say that > stereo requires WAVE_FORMAT_EXTENSIBLE, but that feels like a retcon.  I do know that wav files in the wild quite often just use WAVEFORMATEX for > 2 channels and that's normally handled as if it was WAVE_FORMAT_EXTENSIBLE with a dwChannelMask of 0.  In short, follow the default order (L,R,C,LFE,BL,BR,SL,SR...)

And I have the specs and didn't notice!! Thanks, Monty, I'll get this done.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-30 15:35:02
oggenc2 has been bumped to V2.86 to reflect the new channel mapping. New compiles and sources are now available at Rarewares.

I still have the issue where 64 bit compiles will run on XP x64, but not on Win 7 64 Ultimate. If anyone can offer any suggestions or ideas, they'd be most welcome.  Just to mention that FLAC input works fine in both environments, but at the point of the first attempt to read a wave file, integer or float, it crashes in Win 7 64 while working as expected in XP x64. (aif files also suffer the same fate.)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Emre on 2010-03-30 20:46:50
oggenc2 has been bumped to V2.86 to reflect the new channel mapping. New compiles and sources are now available at Rarewares.

I still have the issue where 64 bit compiles will run on XP x64, but not on Win 7 64 Ultimate. If anyone can offer any suggestions or ideas, they'd be most welcome.  Just to mention that FLAC input works fine in both environments, but at the point of the first attempt to read a wave file, integer or float, it crashes in Win 7 64 while working as expected in XP x64. (aif files also suffer the same fate.)


Pipe encoding seems broken. Both generic & P4 builds.

Code: [Select]
Conversion failed: The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters


Win7 64 Bit
C2Q Q9400
Foobar2000 1.0.1
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Zarggg on 2010-03-30 22:09:39
How does libvorbis 1.3.1 compare to aotuv b5.7???

Seconding this question.

Also, unless I'm missing something, it doesn't look like there have been any major quality changes that affect my use of Vorbis (q5/6, 2.0 stereo, 44.1kHz), so I'm guessing I should just stick with aoTuV b5.7 for now.

Can anyone confirm or deny my assessment?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: HotshotGG on 2010-03-30 23:11:37
Quote
Seconding this question.

Also, unless I'm missing something, it doesn't look like there have been any major quality changes that affect my use of Vorbis (q5/6, 2.0 stereo, 44.1kHz), so I'm guessing I should just stick with aoTuV b5.7 for now.

Can anyone confirm or deny my assessment?


Confirm and deny. The new source code implements channel coupling models for 5.1 tracks for example and changes a few minor things that's the "deny" part. The "confirm" part is the source code doesn't include any AoTuV tunings due to the fact the they have to be tested to see if they resulted in any regressions first. While most people equate to the AoTuV tunings as being "better" nobody looks at the opposite whether or not they have actually caused a regression going backwards.  Once that's determined they will be merged into the next release.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-03-31 09:38:09
....
Pipe encoding seems broken. Both generic & P4 builds.

Code: [Select]
Conversion failed: The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters


Win7 64 Bit
C2Q Q9400
Foobar2000 1.0.1

I'm afraid I can't reproduce that here. I've tested on XP Pro SP3 (e4300 @ 3GHz), XP Pro X64 (Atom 330 dual core) and Win7 64 Ultimate (q6600 @ 3.2GHz); all with Foobar 1.0.1. I've tested using ape and wv files, tell me what you're using for input and I'll try that.

(Just as an aside, I'm leaving on vacation just after lunch today and won't return until late on April 11 so if you don't receive any response in the meantime it's because I'll not have any internet access while I'm away, not because I'm ignoring you!!  )
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Emre on 2010-03-31 15:44:34
...tell me what you're using for input and I'll try that.

i tried various sources (lossy & lossless) and i still get this error. once encoding starts oggenc2 immediately crash and encoding failed.
by the way oggenc2.85-1.3.1-P4 works flawlessly. 
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: tebasuna51 on 2010-03-31 20:12:10
I'm afraid I can't reproduce that here. I've tested on XP Pro SP3 (e4300 @ 3GHz), XP Pro X64 (Atom 330 dual core) and Win7 64 Ultimate (q6600 @ 3.2GHz); all with Foobar 1.0.1. I've tested using ape and wv files, tell me what you're using for input and I'll try that.

First, thanks for the new binaries.

The format sources in Foobar2000 aren't relevant because Foobar2000 always send WAV format to the encoders.

Using XP Pro SP3 (e4600 @ 2.4GHz), pipe issues:

For me work Foobar2000 v1.0.1 convert, but using other 'pipes' crash OggEnc2 with Error Code: 0xC0000005 (old oggenc2 work)

Eac3to crash:
eac3to.exe 6w321.wav stdout.wav | OggEnc2 -q 3 -o eac3to_pipe.ogg -
WAV, 5.1 channels, 0:00:20, 16 bits, 4608kbps, 48khz
Reading WAV...
Writing WAV...
Creating file "stdout.wav"...
Writing the destination file failed.  <ERROR>
Aborted at file position 1310720.  <ERROR>

AviSynth pipe crash:
wavi WavSource.avs - | oggenc2 -o AviSynth_pipe.ogg -
Found PCM audio: 6 channels, 48000 Hz, 16 bits, 20.000000 seconds.
Writing WAV file...
Opening with wav module: WAV file reader
Error: Could not write to the standard output.

Faad pipe crash:
faad -w entrada.mp4 | oggenc2 -o Faad_pipe.ogg -
...
Opening with wav module: WAV file reader
(crash)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Jalan on 2010-03-31 20:56:32
Encoding failed in foobar2000 v1.0.1 for me as well using the generic build.

Code: [Select]
1 out of 1 tracks converted with major problems.

Source: "C:\test\01 - Duvet.flac"
An error occurred while writing to file (The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters) : "C:\Output\1 - Duvet.ogg"
Additional information:
Encoder stream format: 44100Hz / 2ch / 16bps
Command line: "C:\Program Files (x86)\foobar2000\encoders\oggenc2.exe" -s 7310627 -Q -q3.500000 - -o "1 - Duvet.ogg"
Working folder: C:\Output\

Conversion failed: The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters

Vista Home Premium 64-bit
Core 2 Duo E8400 @3.0 GHz
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: sauvage78 on 2010-04-03 03:50:23
Same crash here, with generic build+Sempron 3000+ (Single Core Barton)+Windows XP SP3+F2K V1.01

Code: [Select]
Conversion failed: The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dandruff on 2010-04-04 20:35:12
I can confirm the crashes too:

OggEnc 2.86 (libVorbis 1.3.1) from http://www.rarewares.org (http://www.rarewares.org) isn't working in foobar2000 1.0.1! Both compiles (P4 and generic) crash. OggEnc 2.85 is working fine!


Crashes each time I try to convert to a q6.0 quality ogg file:

Code: [Select]
1 out of 1 tracks converted with major problems.

Source: "D:\Music\4 Red Eyes - Oblivion [Hard Edged]\01. 4 Red Eyes - Oblivion.wv"
  An error occurred while writing to file (The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters) : "D:\Music\4 Red Eyes - Oblivion [Hard Edged]\01. 4 Red Eyes - Oblivion.ogg"
Additional information:
Encoder stream format: 48000Hz / 2ch / 32bps
Command line: "C:\WINDOWS\system32\oggenc2.exe" -s 262801399 -Q -q6,000000 - -o "01. 4 Red Eyes - Oblivion.ogg"
Working folder: D:\Music\4 Red Eyes - Oblivion [Hard Edged]\

  Conversion failed: The encoder has terminated prematurely with code -1073741819 (0xC0000005); please re-check parameters



Code: [Select]
Microsoft (R) DrWtsn32
Copyright (C) 1985-2001 Microsoft Corp. Alle Rechte vorbehalten.



Anwendungsausnahme aufgetreten:
        Anwendung: C:\WINDOWS\system32\oggenc2.exe (pid=1888)
        Wann: 04.04.2010 @ 20:49:20.218
        Ausnahmenummer: c0000005 (Zugriffsverletzung)

*----> Systeminformationen <----*
        Terminalsitzungskennung: 0
        Prozessoranzahl: 2
        Prozessortyp: x86 Family 6 Model 15 Stepping 6
        Windows-Version: 5.1
        Aktuelles Build: 2600
        Service Pack: 3
        Aktueller Typ: Multiprocessor Free

*----> Taskliste <----*
   0 System Process
   4 System
316 smss.exe
372 csrss.exe
396 winlogon.exe
440 services.exe
452 lsass.exe
604 svchost.exe
664 svchost.exe
720 svchost.exe
792 spoolsv.exe
1092 Explorer.EXE
1328 hdsp32.exe
1344 hdspmix.exe
1784 totalcmd.exe
1848 firefox.exe
524 foobar2000.exe
1888 oggenc2.exe
1876 drwtsn32.exe

*----> Modulliste <----*
(0000000000400000 - 000000000078a000: C:\WINDOWS\system32\oggenc2.exe
(000000005d450000 - 000000005d4ea000: C:\WINDOWS\system32\comctl32.dll
(0000000076330000 - 000000007634d000: C:\WINDOWS\system32\IMM32.DLL
(00000000773a0000 - 00000000774a3000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
(0000000077b10000 - 0000000077b32000: C:\WINDOWS\system32\Apphelp.dll
(0000000077bd0000 - 0000000077bd8000: C:\WINDOWS\system32\VERSION.dll
(0000000077be0000 - 0000000077c38000: C:\WINDOWS\system32\msvcrt.dll
(0000000077da0000 - 0000000077e4a000: C:\WINDOWS\system32\ADVAPI32.dll
(0000000077e50000 - 0000000077ee2000: C:\WINDOWS\system32\RPCRT4.dll
(0000000077ef0000 - 0000000077f39000: C:\WINDOWS\system32\GDI32.dll
(0000000077f40000 - 0000000077fb6000: C:\WINDOWS\system32\SHLWAPI.dll
(0000000077fc0000 - 0000000077fd1000: C:\WINDOWS\system32\Secur32.dll
(000000007c800000 - 000000007c908000: C:\WINDOWS\system32\kernel32.dll
(000000007c910000 - 000000007c9c9000: C:\WINDOWS\system32\ntdll.dll
(000000007e360000 - 000000007e3f1000: C:\WINDOWS\system32\USER32.dll

*----> Statusabbild für Threadkennung 0x5b4 <----*

eax=0012fdec ebx=00000000 ecx=00345050 edx=00343dc4 esi=00000000 edi=00000000
eip=00418478 esp=0012fadc ebp=0012ff78 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000206

*** ERROR: Module load completed but symbols could not be loaded for C:\WINDOWS\system32\oggenc2.exe
Funktion: oggenc2
        00418466 d9660f           fldenv  [esi+0xf]
        00418469 1f               pop     ds
        0041846a 8400             test    [eax],al
        0041846c 0000             add     [eax],al
        0041846e 0000             add     [eax],al
        00418470 57               push    edi
        00418471 56               push    esi
        00418472 55               push    ebp
        00418473 53               push    ebx
        00418474 8b742414         mov     esi,[esp+0x14]
FEHLER ->00418478 0fb616           movzx   edx,byte ptr [esi]      ds:0023:00000000=??
        0041847b 33c9             xor     ecx,ecx
        0041847d 33db             xor     ebx,ebx
        0041847f 85d2             test    edx,edx
        00418481 742b             jz      oggenc2+0x184ae (004184ae)
        00418483 b801000000       mov     eax,0x1
        00418488 f7c280000000     test    edx,0x80
        0041848e 7414             jz      oggenc2+0x184a4 (004184a4)
        00418490 81e2e0000000     and     edx,0xe0
        00418496 8d6802           lea     ebp,[eax+0x2]
        00418499 40               inc     eax

*----> Stack Back Trace <----*
WARNING: Stack unwind information not available. Following frames may be wrong.
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\system32\kernel32.dll -
ChildEBP RetAddr  Args to Child              
0012ff78 0045bf6c 00000008 00343da8 00342f50 oggenc2+0x18478
0012ffc0 7c817077 02007265 00000000 7ffdf000 oggenc2+0x5bf6c
0012fff0 00000000 0045bfc3 00000000 78746341 kernel32!RegisterWaitForInputIdle+0x49

*----> Raw Stack Dump <----*
000000000012fadc  00 00 00 00 78 ff 12 00 - 30 7b 47 00 00 00 00 00  ....x...0{G.....
000000000012faec  1a 1e 41 00 00 00 00 00 - ec fd 12 00 c0 4f 34 00  ..A..........O4.
000000000012fafc  e8 fd 12 00 01 00 00 00 - c4 97 46 00 80 57 88 7c  ..........F..W.|
000000000012fb0c  88 fe 12 00 8c fe 12 00 - 90 fe 12 00 94 fe 12 00  ................
000000000012fb1c  98 fe 12 00 9c fe 12 00 - 10 02 10 02 10 02 10 02  ................
000000000012fb2c  10 02 10 02 10 02 10 02 - 12 03 10 02 10 02 10 02  ................
000000000012fb3c  10 02 10 02 10 02 10 02 - 14 02 14 02 10 02 12 03  ................
000000000012fb4c  10 02 10 02 10 02 14 02 - 12 03 10 02 10 02 10 02  ................
000000000012fb5c  10 02 10 02 01 03 01 03 - 01 03 01 03 01 03 01 03  ................
000000000012fb6c  01 03 01 03 01 03 01 03 - 01 03 01 03 01 03 01 03  ................
000000000012fb7c  01 03 01 03 c0 9f 00 00 - 01 03 01 03 01 03 01 03  ................
000000000012fb8c  00 00 00 00 01 03 01 03 - 01 03 01 03 40 06 15 00  ............@...
000000000012fb9c  01 03 02 03 02 03 02 03 - 02 03 02 03 02 03 02 03  ................
000000000012fbac  02 03 02 03 02 03 02 03 - 78 01 15 00 02 03 02 03  ........x.......
000000000012fbbc  02 03 02 03 02 03 02 03 - 02 00 00 00 02 03 02 03  ................
000000000012fbcc  02 03 10 02 02 03 02 03 - 02 03 02 03 02 03 02 03  ................
000000000012fbdc  a0 32 15 00 20 01 02 03 - 04 05 06 07 08 09 0a 0b  .2.. ...........
000000000012fbec  0c 0d 0e 0f 10 11 12 13 - 14 15 16 17 18 19 1a 1b  ................
000000000012fbfc  0c 00 00 00 20 21 22 23 - 24 25 26 27 28 29 2a 2b  .... !"#$%&'()*+
000000000012fc0c  78 01 15 00 30 31 32 33 - 88 30 15 00 38 39 3a 3b  x...0123.0..89:;

*----> Symboltabelle <----*
C:\WINDOWS\system32\oggenc2.exe




I've also wrote to the rarewares guys about this ...
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: keicar on 2010-04-10 22:48:27
Same crashes here. See http://www.hydrogenaudio.org/forums/index....showtopic=80147 (http://www.hydrogenaudio.org/forums/index.php?showtopic=80147)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-15 15:59:56
Apologies for the delay, but I've been on vacation!

Problem found and fixed. Version 2.87 is now at Rarewares.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dandruff on 2010-04-15 16:59:18
Thanks John. Working fine now!
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: zanuda on 2010-04-15 17:52:35
oggenc2-87-1.3.1
foobar2000 v1.0.2.1
windowsXP

Quote
1 out of 1 tracks converted with major problems.

Source: "D:\cinema\Barking Dogs Never Bite (2000) NTSC DVD9\VIDEO_TS\VTS_01_1 T80 3_2ch 384Kbps DELAY 66ms.ac3"
  An error occurred while writing to file (The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters) : "D:\cinema\Barking Dogs Never Bite (2000) NTSC DVD9\VIDEO_TS\VTS_01_1 T80 3_2ch 384Kbps DELAY 66ms.ogg"
Additional information:
Encoder stream format: 48000Hz / 6ch / 32bps
Command line: "E:\Soft\oggenc2.87-1.3.1-generic\oggenc2.exe" -s 1445268101 -Q -q5,000000 - -o "VTS_01_1 T80 3_2ch 384Kbps DELAY 66ms.ogg"
Working folder: D:\cinema\Barking Dogs Never Bite (2000) NTSC DVD9\VIDEO_TS\

  Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: robert on 2010-04-15 18:33:42
Could be something else, but where does -q5,000000 come from? Don't you mean -q5.0 instead?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dandruff on 2010-04-15 18:41:42
Could be something else, but where does -q5,000000 come from? Don't you mean -q5.0 instead?


Comes from foobar2000, see http://www.hydrogenaudio.org/forums/index....st&p=698530 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=79762&view=findpost&p=698530)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: robert on 2010-04-15 18:49:34
So, foobar writes localized text into the command line? It seems oggenc doesn't accept this, and it wouldn't work with LAME too, I fear, but would have to check later.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: sauvage78 on 2010-04-15 18:51:47
In my case the fix seems to work. (Edit: I only tested 2.0)

What is this (Everywhere) in the end of the vendor tag ? Does it means something ?
Code: [Select]
Xiph.Org libVorbis I 20100325 (Everywhere)

It's the first time I see this in a vendor tag...
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-15 19:03:33
oggenc2-87-1.3.1
foobar2000 v1.0.2.1
windowsXP

Quote
1 out of 1 tracks converted with major problems.
....
  Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters


I can confirm the same problem. Same set up converting a 6 channel 384kbps .ac3 file of approx 1 hour 56 mins, the conversion failed at approx 1 hour 2 mins with the same message.

I suspect this may be something to do with the new channel coupling in libvorbis, but I'll need to do some more checking to be sure.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dandruff on 2010-04-15 19:17:39
So, foobar writes localized text into the command line? It seems oggenc doesn't accept this, and it wouldn't work with LAME too, I fear, but would have to check later.


oggenc seems to accept it:

Code: [Select]
C:\WINDOWS\system32>oggenc2 -q6,000000 d:\1.wav
Opening with wav module: WAV file reader
Encoding "d:\1.wav" to
         "d:\1.ogg"
at quality 6,00
        [100,0%] [ 0m00s remaining] -

Done encoding file "d:\1.ogg"

        File length:  0m 09,0s
        Elapsed time: 0m 01,0s
        Rate:         9,3867
        Average bitrate: 156,7 kb/s
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Dandruff on 2010-04-15 19:20:13
In my case the fix seems to work. (Edit: I only tested 2.0)

What is this (Everywhere) in the end of the vendor tag ? Does it means something ?
Code: [Select]
Xiph.Org libVorbis I 20100325 (Everywhere)

It's the first time I see this in a vendor tag...


This version is called like this.

Quote
libvorbis 1.3.1 (2010-02-26) -- "Xiph.Org libVorbis I 20100325 (Everywhere)"

* tweak + minor arithmetic fix in floor1 fit
* revert noise norm to conservative 1.2.3 behavior pending more listening testing



http://downloads.xiph.org/releases/vorbis/...orbis-1.3.1.zip (http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.1.zip)
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-15 19:27:20
oggenc2-87-1.3.1
foobar2000 v1.0.2.1
windowsXP

Quote
1 out of 1 tracks converted with major problems.
....
  Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters


I can confirm the same problem. Same set up converting a 6 channel 384kbps .ac3 file of approx 1 hour 56 mins, the conversion failed at approx 1 hour 2 mins with the same message.

I suspect this may be something to do with the new channel coupling in libvorbis, but I'll need to do some more checking to be sure.

Well, further testing tends to suggest that it is not oggenc2 that is the problem. I decoded the 6 channel .ac3 file to a 6 channel wave file, using the convert option in foobar, and then converted the 6 channel wave file to a 6 channel .ogg file, also in foobar, and it completed normally. Anyone have any ideas on this? The issue would appear to be in the direct transcoding of .ac3 to .ogg - memory leak, perhaps? Pure guess, as I've no real idea!
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: zanuda on 2010-04-15 22:25:01
I tried convert 6 channel .ac3 file to .flac
Result. The same error

Quote
1 out of 1 tracks converted with major problems.

Source: "D:\cinema\T2_Audio.ac3"
  An error occurred while writing to file (The encoder has terminated prematurely with code 1 (0x00000001); please re-check parameters) : "D:\cinema\T2_Audio.flac"
Additional information:
Encoder stream format: 48000Hz / 6ch / 24bps
Command line: "C:\Program Files\FLAC\flac.exe" -s --ignore-chunk-sizes -8 - -o "T2_Audio.flac"
Working folder: D:\cinema\The Descent BD\

  Conversion failed: The encoder has terminated prematurely with code 1 (0x00000001); please re-check parameters
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-15 22:52:36
Sorry, I confirm that directly converting the 6 channel .ac3 file to .ogg causes the same error on my test system which is configured the same as yours. However, if the file is decoded to a 6 channel wave file (via foobar) and then encoded to a .ogg file, it completes normally. That suggests to me that the problem lies somewhere in the chain prior to oggenc2 since the input to oggenc2 should be the same in both cases.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: tebasuna51 on 2010-04-19 20:02:13

Quote
1 out of 1 tracks converted with major problems.
....
Command line: "E:\Soft\oggenc2.87-1.3.1-generic\oggenc2.exe" -s 1445268101 -Q -q5,000000 - -o "VTS_01_1 T80 3_2ch 384Kbps DELAY 66ms.ogg"
....
  Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters


I can confirm the same problem. Same set up converting a 6 channel 384kbps .ac3 file of approx 1 hour 56 mins, the conversion failed at approx 1 hour 2 mins with the same message.

Two ideas about the problem:

1) With Foobar2000 1.0 the method to send data to external encoders is using a WAV (with a WAVE_FORMAT_EXTENSIBLE header) with the length values (RIFF_length and DATA_length) filled with a value of 0xFFFFFFFF.
Then we need always, not only with big >4GB wav, use the appropriate parameter:
Oggenc2 --ignorelength
NeroAacEnc -ignorelength
Aften -readtoeof 1
Flac --ignore-chunk-sizes

2) I found some sync problems when use STDOUT-STDIN read method.
I'm not sure, but maybe is a OS problem.
Let me explain the workaround I use in my code applied to the code used in wav_read function in audio.c (oggenc2).

I think when you use, over STDIN:
Code: [Select]
long bytes_read = fread(buf, 1, samples*sampbyte*f->channels, f->f);

you can get bytes_read less than bytes requested without reach the end of file.
This finish the encode for oggenc2 but Foobar2000 still want send data to STDOUT.

For me work a code like this:

Code: [Select]
long bytes_read = 0;
long bytes_to_read = samples*sampbyte*f->channels;
long bytes_read_now = 1;

while ((bytes_read < bytes_to_read) && (bytes_read_now > 0))
{
    bytes_read_now = fread(buf[bytes_read], 1, bytes_to_read - bytes_read, f->f);
    bytes_read += bytes_read_now;
}

Maybe you can try this workaround to see if the problem is fixed.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-19 21:58:09
Thanks for the suggestion, I'll give it a try and report back.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-20 10:42:34
I tried this just now and I'm afraid that I get exactly the same problem at exactly the same point in the transcode.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: robert on 2010-04-20 11:26:03
At what point in the input data stream does the termination happen? At 0x7fffffff ? Some signed int problem maybe?
6 channels at 48 kHz sample rate, each sample 3 bytes (24 bits) : round about at 41.42 minutes ?
6 channels at 48 kHz sample rate, each sample 2 bytes (16 bits) : round about at 62.13 minutes ?
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-20 13:48:41
At what point in the input data stream does the termination happen? At 0x7fffffff ? Some signed int problem maybe?
6 channels at 48 kHz sample rate, each sample 3 bytes (24 bits) : round about at 41.42 minutes ?
6 channels at 48 kHz sample rate, each sample 2 bytes (16 bits) : round about at 62.13 minutes ?

The last one. Edit: 1:02:08, to be precise

What seems odd to me though is that I can decode the 6 channel .ac3 file to 6 channel .wav using foobar convert and it completes just fine. I can then encode the 6 channel .wav file to 6 channel .ogg using foobar convert and that also completes fine. It is the .ac3 to .ogg transcode that fails.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: tebasuna51 on 2010-04-20 14:44:07
The 1:02:08 is the limit 0xFFFFFFFF for a wav 48KHz, 6 chan, 24 bits

I have the same problem if use the standar encoder options for ogg in Foobar2000 v1.0.2.1:
...
Command line: "D:\Programa\Audio\Behappy\encoder\oggenc.exe" -s 1317992330 -Q -q5,000000 - -o "165min.ogg"
Conversion failed: The encoder has terminated prematurely with code 0 (0x00000000); please re-check parameters

I say before than the --ignorelength parameter is necessary. You need go to
File -> Preferences -> Tools -> Converter -> Output formats -> Add New:
Encoder: Custom
Encoder: x:\yourpath\oggenc2.exe
Extension: ogg
Parameters: --ignorelength -Q -q5 - -o %d
Format is: lossy
Highest BPS: 32
Encoder name: OGGenc2
Bitrate:
Settings: Q5

With these parameters I encode a 165 min ac3, 6 chan, 48KHz at 24 bits (the limit for 16 bits is 130 min):
File name                        : 165min
File extension                  : ogg
...
Duration                        : 02:45:28.832
Bit rate                        : 450 Kbps
Channel(s)                      : 6 channels
Sampling rate                    : 48.0 KHz
SamplingCount                    : 476583936
...
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: john33 on 2010-04-20 15:36:26
Thanks for your patience.

My basic error was that I had left the default '%r' option in the codeline!! Correcting that and it completed as expected.

So, in short, it's a matter of paying proper attention to what is included in the default custom codeline and amending it correctly, both things I failed to do when I should have!!
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: rt87 on 2010-05-17 06:33:38
aoTuV post-beta5.7 [20100516] (for tester)

Release Notes translated by Excite Japan.

The test version is opened to the public because it has stabilized very much. It doesn't test with 5.1 ch, and check that there is a heard environment by all means, please. A rough change point from the test version before is as follows.

・Libvorbis 1.3.1 and latest aoTuV are integrated.

・Enhanced new Noise Normalization.

・The dynamic stereo threshold change code renewal. (Became simpler. )

・The sorting application is changed to the method of agreement to new libvorbis 1.3.1. (1.3.1 The speed in total has neither last test version nor a big difference though it sped up based on. The algorithm is different. )

・The code to improve a specific problem is partially improved.

Additionally, the venc front end was made multichannel input correspondence. The wav file to 8ch is accepted. Only 5.1ch of a multichannel coupling is effective as well as libvorbis 1.3.1. This is a limitation of the library side.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: HotshotGG on 2010-05-17 17:55:44
Sweet! Thanks for the update I will have to test it out after and build it from the source here. Thanks for keeping a heads up.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Zarggg on 2010-05-19 16:09:03
Yay! Can't wait for a new oggenc to go on Rarewares.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: towolf on 2010-05-19 22:04:29
Sweet! Thanks for the update I will have to test it out after and build it from the source here. Thanks for keeping a heads up.


Source? Where? I only see an .exe in a .zip.
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Lumar on 2010-08-22 19:20:38
Hello i'm new in the forum so... i'll talk quick. I have a file wich contains raw PCM ... i want to convert the data in this mode:

Audio: 80 Kbps,  10000 Hz,  1 channels,  0x1 = MS PCM,  , ,  Supported

so if anyone can help me just let me know here or join me on skype with skypename: uplink_ltd


Thank you!
Title: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: forart.eu on 2010-08-23 08:51:49
Hello i'm new in the forum so... i'll talk quick. I have a file wich contains raw PCM ... i want to convert the data in this mode:

Audio: 80 Kbps,  10000 Hz,  1 channels,  0x1 = MS PCM,  , ,  Supported

so if anyone can help me just let me know here or join me on skype with skypename: uplink_ltd


Thank you!


Well, well, i'm a mono user too !

BTW 10KHz seems too low for music content, IMHO (if you have voice recordings keep in consideration Speex (http://www.speex.org/) instead).

Choose at least 22 KHz @ q0 (64 Kbps) to have realiable results.

The suggestion is to use Foobar2000 (http://www.foobar2000.org/) in combination with Stereo Tool (http://www.stereotool.com/) (commandline) to correctly "collapse&encode" 44Khz PCM stereo to 22Khz Vorbis mono.
Title: Re: vorbis-tools 1.4.0, libvorbis 1.3.1, and libao 1.0.0 coordinated relea
Post by: Kraeved on 2016-03-28 01:03:16
Could someone be so kind to compile vorbis-tools 1.4 x64 binaries for Windows?
I'm confused to see Rarewares.org still publishes ogginfo 1.1 from 2008.
SimplePortal 1.0.0 RC1 © 2008-2020