AC3 -> Ogg Vorbis problem
Reply #9 – 2005-12-31 15:45:17
I kept on my laptop an AC3 file impossible for me to encode with foobar2000 and any oggenc.exe compile or version. I've just downloaded the latest oggenc 2.8 generic compiles on rarewares. The source is 2h14'57'' long and correspond to a 384 kbps mono but 2.0 encoding. SummaryENCODED WITH FOOBAR2000 0.83 DISKWRITER (CLIenc) encoder floating source processed ended at aoTuV unchecked AC3 2h04'16'' aoTuV checked AC3 1h33'12'' aoTuV unchecked WAV¹ 2h04'16'' 1.1.2 unchecked AC3 2h04'16'' 1.1.2 checked AC3 1h33'12'' 1.1.2 unchecked WAV¹ 2h04'12'' ¹ WAV file obtained by decoding the AC3 source with foobar2000 0.83 (48KHz/16 bit) => I can't encode this file with foobar2000 and/or oggenc. Using stdin or not doesn't change anything. The use of "pass floating point data" change the behavior: without this option the encoding always stops at 2h04'16'' and with this option checked the process always ends at 1h33'12'' (exactly what StephanV noticed yesterday). Then I tried to use directly oggenc.exe in a "cmd" window. Source is a WAV file (AC3 decoded with foobar2000)DIRECTLY WITH OGGENC 2.8 (source = WAV file) encoder source processed ended at aoTuV WAV 2h14'57'': OK 1.1.2 WAV 2h14'57'': OK => no problem. oggenc2.exe is working fine here and therefore only fail when it's associated with foobar2000 0.83. Finally, I tried with foobar2000 0.9 beta with the same WAV file as source but I can't manually change the encoder location (once the oggenc's directory is specified, you can't apparently configure a new one). The test is not possible.