Simple ogg syntax help.

[gkedrovs]

oggenc j_train.wav

That produces a file called j_train.ogg at quality level 3.

Let's say that I want quality level 10 and I want to change the name of the file (so I can compare quality level 3 to quality level and everything in between, just because I'm obsessive-compulsive).

According to the manpage, the syntax would be thus:

oggenc j_train.wav q 10 o j_train_10.ogg

You know what I get...? Same deal: j_train.ogg at quality level 3 and the following output:

Done encoding file "j_train.ogg"

File length: 3m 27.0s
Elapsed time: 0m 45.1s
Rate: 4.6021
Average bitrate: 114.8 kb/s

ERROR: Cannot open input file "q": No such file or directory
ERROR: Cannot open input file "10": No such file or directory
ERROR: Cannot open input file "o": No such file or directory
ERROR: Cannot open input file "j_train_10.ogg": No such file or directory

I know... RFTM. I did. I even COPIED the FM onto the command line and got the same deal. Can you help me out a little here...?

Thanks.
-Greg

[bwkaz]

I suppose you've tried -q 10 -o j_train_10.ogg -- right?

I don't know which cracked-out manual you're talking about, but every program I have (except for dd) takes its options with dashes before them. Anything without a dash is either an option argument (like 10) or a filename (which is what your oggenc appears to be interpreting q, o, 10, etc. as).

[gkedrovs]

All my man pages in aterm come up gobbly-gook, so I usually use xterm. For stuff like this, I like to get a hardcopy to read it over, jot notes down, etc. So, I do:

man manpage | col -b > manpage.txt

Did that, brought up the text file in an editor (gedit) and printed. NONE of the hashmarks (hyphens) showed up! What the friggin world is up with that?!

Anyway, I just brougth up oggenc manpage in gnome-terminal and there they were. So...

Kick me in the head.

Thanks, man.
.Greg

[bwkaz]

Character set thing maybe? Does it work to export LANG=C before opening the manpage (using man, not opening the .txt file)?

[gkedrovs]

Yeah. It worked like a charm with the Lang export. What's up with that? Or is that beyond the scope of our thread here...? Should I put that export command in before the editor when I start it up?

export LANG=C aterm

or

export LANG=C xterm

Or would that hose something else?

Or... should that language / character set "adjustment" be in a start-up file somewhere?

NEVER heard of this one before... but, thanks.

-Greg

[bwkaz]

It's something weird with internationalization. I don't really have a clue why a lot of distros don't do it automatically, either.

Anyway, you can just add that export to /etc/profile and /etc/bashrc if you want. I think that'd be easiest.

[gkedrovs]

Thanks!