Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: problem converting to ogg vorbis (Read 3446 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

problem converting to ogg vorbis

edit: I wanted to edit the topic title to add foobar version 0.9.5b1

2nd edit:
Problem at least partially solved by usage of
Tool : Xiph.Org libVorbis I 20050304
What makes me even more wonder about ogg vorbis builds, as i downloaded befores everal builds from aotuv and official ogg, even specialized to my Pentium 3, but none worked, until I got above specified.





source file is a flac 1.2.1 song file.

A window pops up after very short time:

Error writing to file (Die Pipe wird gerade geschlossen.  ) : file://F:\music\# Previews of new albums\01 - Erl-King.ogg

^^ you recognize the folder where I wanted to store the ogg song,

(Die Pipe wird gerade geschlossen.
translates to:
The pipe is closed currently/now.
^^ I hope, the translation helps.

The file stops at 4096 B size.
When i tried ogg-preview files, it stopped already at 0 B file size.


This happens, when I want to create ogg previews, but also, when I use the built in ogg preset 160 k , q5 , and also with custom ogg presets.

I have tried out ('located') more than 1 ogg encoder, new ogg2enc.exe from rarewares
, renamed to oggenc.exe, and an oggenc.exe from a general downlaod site, and a recent aotuv oggenc.


Conversions from flac 1.2.1 to mpc 1.16, or to wav, and flac 1.2.1 to flac 1.2.1 perform well

problem converting to ogg vorbis

Reply #1 –
i don't get this problem. i used Blacksword's build.

edit:what's your command line?

problem converting to ogg vorbis

Reply #2 –
Problem at least partially solved for now by usage of
Tool : Xiph.Org libVorbis I 20050304
What makes me even more wonder about ogg vorbis builds, as i downloaded before several builds from aotuv and official ogg, even specialized to my Pentium 3, but none worked, until I got above specified.



commandlines were the normal preview creation inside of foobar 2000 0.9.5 b1 of the converter,

and eg this one:

-s %r -Q -q-1,000000 - -o %d

or the built in specified preset by the quality slider.

Could it be a reason for the problem, that i had before located my unsuccessful trial oggenc builds in a custom directory of my choice ?
When i got the working build, i also created a codecs directory inside the foobar2000-095 directory and located this one there.

problem converting to ogg vorbis

Reply #3 –
I can't reproduce the problem on XP SP2 with the current oggenc2.84-aoTuVb5-P4 build from rarewares.

I tried the default -q4 setting (which seems to use "-s %r -Q -q-4.000000 - -o %d") and my older saved "-Q -q4 - -o %d" command line. I tried the preview generation tool and the standard file converter. The destination folder was "E:\# Previews of new albums". Everything worked fine.

Quote
Could it be a reason for the problem, that i had before located my unsuccessful trial oggenc builds in a custom directory of my choice ?

The encoder should work from any directory. I don't know what happens in your case, but have you tried to reset the memorized encoder file location(s) in fb2k? You could gather all Ogg Vorbis encoder related files to a new "archive" folder and place only the preferred version of oggenc.exe file in a new "ogg encoder" folder. I did this when I wanted to clean my about 25 different saved Ogg Vorbis conversion settings (which pointed to various old encoder locations).


BTW, can anyone explain the purpose of the -s and %r arguments? I know that -s = --serial and it creates an individual serial number, but I don't know why it is used. I searched, but couldn't find any information about the %r argument.
 

problem converting to ogg vorbis

Reply #4 –
Quote from: Alex B on
BTW, can anyone explain the purpose of the -s and %r arguments? I know that -s = --serial and it creates an individual serial number, but I don't know why it is used. I searched, but couldn't find any information about the %r argument.
Because oggenc uses a very weak pseudorandom number generator for stream serial numbers, we must provide externally-generated stream serial numbers to make output Ogg files safe to chain together. The %r argument is a special workaround for this scenario - it passes a pseudorandon mumber from foobar2000's internal generator to the commandline encoder.
Microsoft Windows: We can't script here, this is bat country.