Convert Ogg to Mp3 with ffmpeg?

[samweller]

I've downloaded a bunch of stuff that says ffmpeg and mp3 hoping I have the right stuff.  My command is

Code: [Select]

ffmpeg -i soundpollution.ogg soundpollution.mp3
well it appears I can't cut or paste with Aterm.  Anyway it says "unsupported codec for output stream."

Do we have the codec to download to enable this?

[perthie]

If you had ogg-vorbis.tczl and lame.tczl, you could use

Code: [Select]

oggdec $1.ogg ; lame $1.wav $1.mp3 ; /bin/rm $1.wav

[samweller]

Yep that works.  Thanks.  Seems a little long to have to do for about 100 songs.  But that might have to do.  Thankyou for the help.

[perthie]

Seems a little long to have to do for about 100 songs.

Then how about:

Code: [Select]

for X in *.ogg ; do
  Y=${X%.*}
  oggdec $Y.ogg ; lame $Y.wav $Y.mp3 ; /bin/rm $Y.wav
done



[samweller]

perthie-

Thanks for the response.  I've been looking at it and can't quite figure what to plug in to the variables.  All my music is at /mnt/hda4/mu51c.  Then inside the mu51c folder are folders of bands and the songs themselves are in those.  Does Y=./mu51c?

[mikshaw]

The variables are automatically populated according to whether or not there are *.ogg files in the current directory.

for X in *.ogg <-- this sets X to the name of an ogg file in the current directory.  The loop repeats once for each ogg file.
Y=${X%.*} <-- This sets Y to the value of $X without the filename extension.

This script works only for a single directory, so you'd need to cd to the artist's folder, run the script, cd to the next artist directory and run the script, etc.

If you want to do this automatically from mu51c you'll need to nest this loop in another one.

I haven't tested, but it would be something like this....

Code: [Select]

for D in /mnt/hda4/mu51c/*; do
if [ -d "$D"]; then # if it's a subdirectory in mu51c
cd "$D"
for X in *.ogg ; do
  Y=${X%.*}
  oggdec $Y.ogg ; lame $Y.wav $Y.mp3 ; /bin/rm $Y.wav
done
fi
doneIf this works, it should also work from any directory, so you wouldn't need to cd to /mnt/hda4/mu51c first.

[samweller]

mikshaw the results were

Code: [Select]

sh: [d-: not found
By the way, can you cut and paste in Aterm?  I have no middle button.

[maro]

@samweller:
looks like you've entered something like

Code: [Select]

[d- which is not the same as

Code: [Select]

[ -d
Please also note the space between the [ and the -d, that is another thing to be mindful of.

Furthermore I'd like to share a general piece of advice since I see an awful lot of for loops showing up in this forum here. Sample code:

Code: [Select]

for VAR in *.ext ; do ..... done When one uses an expression like *.ogg in a shell command the shell is going to expand this expression and is going to textually replace the *.ogg with all the file names that match this term. That process is called globbing and it's fine as long as you can be sure that there are only a limited number of files that match. But if there are a lot of file names the result can exceed the maximum length of a command that the shell can handle. I'm talking of experience here when I say that the outcome can be quite nasty. At best the command will just fail, but depending on how the loop is constructed I've seen pretty poor outcomes (e.g. files lost etc.)

So what's the solution? Simple: use a while loop instead. Sample code:

Code: [Select]

ls | grep '\.ext$' | while read VAR ; do ..... done The pipe ensures that no matter how many iterations it won't cause the aforementioned problems.

Furthermore, in your case assuming you want to convert all files "below" a certain direrectory, why not use find instead? I would probably do:

Code: [Select]

find /mnt/hda4/mu51c -type f -name *.ogg | while read FILE ; do
        BASE=${FILE%.*}
        oggdec ${BASE}.ogg ; lame ${BASE}.wav ${BASE}.mp3 ; /bin/rm -f ${BASE}.wav
done

If you do any of these loops and you are not sure if it will work, I'd suggest to test it out on a smaller subset. To achieve this you could use

Code: [Select]

find /mnt/hda4/mu51c -type f -name *.ogg | head -5 | while read FILE ; do to test the loop but limited to the first 5 files.

I can't give you the exact hint on how to solve you copy&paste problem, but the middle button can be emulated by pressing both buttons at the same time. I'd therefore suggest to use xsetup.sh and try out the different 2 button mouse types. This changes the Xvesa parameter in your .xsession file. You will have to restart X (by performing an 'Exit to prompt' and using the startx command). Also depending on your setup you'll have to ensure that the change "survives" you next reboot.

[combo3]

mikshaw the results were
By the way, can you cut and paste in Aterm?  I have no middle button.

Highlight the text you want to copy and then press Shift+Insert to paste in the terminal.

[mikshaw]

@maro

I've heard you can also use the -exec action with the find command to prevent problems rather than using a pipe to while

To be honest, though, I've never seen the problems encountered by yourself and others in using a for loop.  It might be an issue of having filenames with spaces, which can easily break a for loop.  Personally I don't allow spaces in filenames on my system if I can help it, and as I said I've never run into problems with for loops even on directories with thousands of files.

[maro]

@mikshaw

I agree that the -exec option for find can also be used, but in my experience is less flexible than a pipe into a 'while read' loop. In some cases I found a pipe into xargs a good solution, but that is fairly close to the -exec option anyway.

Regarding the spaces in file names: that would be an issue for anly kind of loop or xargs construct, but the remedy is to enclose the entire term with the variable in double-quotes (e.g. "${BASE}.ogg").

The point I've tried to make might be seen as a matter of taste and it could well be the use of full length path where each filename ended up being > 80 characters that caused the issue. I just recall that I had nasty cleanup job on my hands when this occured on a production system.

[samweller]

Thanks a million combo3.

[^thehatsrule^]

IIRC `find -exec` is generally faster than using pipe+xargs, and that pipe+xargs is generally faster than using shell loops, ie 'for'.

There shouldn't be any problems with spaces if `while read` is used, but for loops will.  This is controlled by $IFS, i.e.

Code: [Select]

IFS="
"Hm, this is a bit OT.