View previous topic :: View next topic |
Author |
Message |
daba5443 Guest
|
Posted: Tue Sep 24, 2002 11:04 am Post subject: How do I use oggenc with multiple files? |
|
|
Hi.
I have searched the net not finding info that is specific enough fo me to understand and use about this, so please hear me out before you give me a RTFM...
I want to use oggenc native. I want to be able to encode multiple songs and I want to be able to give oggenc the info from a file (using the -n option?). Now, how do i do that?
The info that I have is:
Quote: | Usage: oggenc [options] input.wav [...]
[...]
-n, --names=string Produce filenames as this string, with %a, %t, %l, %n, %d replaced by artist, title, album, track number, and date, respectively (see below for specifying these). %% gives a literal %.
[...]
-d, --date Date for track (usually date of performance)
-N, --tracknum Track number for this track
-t, --title Title for this track
-l, --album Name of album
-a, --artist Name of artist
-G, --genre Genre of track
If multiple input files are given, then multiple instances of the previous five arguments will be used, in the order they are given. If fewer titles are specified than files, OggEnc will print a warning, and
reuse the final one for the remaining files. If fewer
track numbers are given, the remaining files will be
unnumbered. For the others, the final tag will be reused
for all others without warning (so you can specify a date
once, for example, and have it used for all the files)
|
Now, can any of you help me with how the string (file) is supposed to look like?
/Yours Daniel |
|
Back to top |
|
|
Tuna Guru
Joined: 19 Jul 2002 Posts: 485 Location: Berlin
|
Posted: Tue Sep 24, 2002 1:14 pm Post subject: |
|
|
i guess that -n only defines the naming of the outcoming file.
for example you have some out.wav and you do some oggenc with the -t and -l options you define a naming with -n, so your resulting file will be called "Artist - Songanme.ogg".
if im not mistaken oggenc cant encode mutiple files at once.. write a nice little bash script that encodes all ogg files from a directory or something like that. or check out abcde - i think it had some directory processing mode that will let you encode multiple files at once.
oggenc *.wav would have been a nice option...
edit: urr.. yes well.. or do like the manual says.. oggenc 1.wav 2.wav someother.wav |
|
Back to top |
|
|
daba5443 Guest
|
Posted: Tue Sep 24, 2002 4:23 pm Post subject: |
|
|
I will start to learn Bash. Beginning now.
/Daniel |
|
Back to top |
|
|
checkyoulater n00b
Joined: 01 Aug 2002 Posts: 30 Location: Toronto
|
Posted: Thu Sep 26, 2002 2:28 pm Post subject: how I do it... |
|
|
Not sure if this will help, but here is how I make all my Oggs...
Extract/create the wav's any way you want. I personally use either Grip (if I am in X) or cdparanoia from the console. I prefer Grip, as you can set variables, as far as album name, artist, location, and it gets track names from freedb.org.
When that is all done, I go to the console and from the appropriate directory type oggenc -q 8.6 *.wav
This doesn't add any tags, however. To tag all my oggs and mp3's, I use Easytag, which can be emerged. Easytag makes it easy enough to quickly tag identical artist, album, year, etc, fields. All you really need to type in multiple times is the track name.
Then, just delete the wav files.
Too many steps? Perhaps, but it has been working well for me so far. As far as the oggenc -q 8.6, it just sounds good to me. A good tradeoff of file size, and quality. I can' really notice the difference between 8.6 and 10, but I sure do notice the difference in filesizes. |
|
Back to top |
|
|
Tuxisuau Apprentice
Joined: 04 May 2002 Posts: 213 Location: Catalunya (Europe)
|
Posted: Thu Sep 26, 2002 2:55 pm Post subject: |
|
|
abcde _________________ IM me at tuxisuau@jabber.7a69ezine.org |
|
Back to top |
|
|
paul138 Guru
Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON
|
Posted: Fri Sep 27, 2002 4:57 pm Post subject: Oggenc |
|
|
It's not quite what you want but you can make a small small script to encode them like so:
Code: |
#!/bin/bash
for filename in $[ls *.wav]; do
oggenc optionshere '$filename'
# Optional: will delete the wav file.
# remove the hash mark to enable
# rm '$filename'
done
|
Put that in a file and call it, say, oggit.sh and then
Copy it (as root) to somplace like /usr/bin, exit root session, and cd to your directory full of wavs. Run it and go have a coffee
You can then update the tags with Easytag (a very nice prog IMHO)
ED:
If you wanted to get tag names from the .wav file name you could try (not tested):
Say the format was:
01-Artist-Album-Title.wav
Code: |
#!/bin/bash
for filename in $[ls *.wav]; do
tracknum=$(echo $filename | cut -d'-' -f1)
artist=$(echo $filename | cut -d'-' -f2)
album=$(echo $filename | cut -d'-' -f3)
title=$(echo $filename | cut -d'-' -f4)
oggenc optionshere -l'$ablum' -t'$title' -N'$tracknum' -a'$artist' '$filename'
# Optional: will delete the wav file.
# remove the hash mark to enable
# rm '$filename'
done
|
I'm sure theres a better way to do that, but it'd work as long as none of the names have a - in them _________________ Talk is cheap because supply always exceeds demand. |
|
Back to top |
|
|
daba5443 Guest
|
Posted: Sat Sep 28, 2002 8:41 pm Post subject: |
|
|
Thx. Wonderful. Now I am happy
/D |
|
Back to top |
|
|
kode54 n00b
Joined: 16 May 2002 Posts: 42
|
Posted: Mon Sep 30, 2002 3:42 am Post subject: |
|
|
oggenc can encode multiple files at once. You need to specify the tags for each input file before the path/name for each particular file.
oggenc -l x -t x -N x -a x file.wav -l x -t x -N x -a x file2.wav
You only need to specify the naming template (-n) once, or you can choose to provide one fixed output pathname (-o) for each input file, any input files without a matching output name will use the template.
I once encoded all 41 audio tracks from a game CD on a single command line using oggenc. Even though it was beta3, I don't really feel like reencoding the whole lot just yet. Probably doesn't make a difference, but it was the win32 port, running under Windows 2000 Professional. I doubt you could fill most of an 80x25 text window with a single command line under Windows 9x/ME. |
|
Back to top |
|
|
paul138 Guru
Joined: 09 Aug 2002 Posts: 370 Location: Ottawa, ON
|
Posted: Mon Sep 30, 2002 12:57 pm Post subject: C |
|
|
See, I knew there would be a better way _________________ Talk is cheap because supply always exceeds demand. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|