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 scheduling mlame - lame 3.98 (Read 3086 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problem scheduling mlame - lame 3.98

lame 3.98 - Fedora 8

I have been trying to scheduled mlame jobs in both Kcron and gnome-schedule without success. This is the command I am running currently:
/wav/mlame -o "-b 96 -S" -r /wav/*.wav > /wav/cron.txt

It works if I run that command in the terminal and it actually works if I use the run now options from these scheduling programs. This is the output I capture when it runs as scheduled:

New lame options are '-b 96 -S'
Removing source files after successfully converting
converting of '/wav/wav001.wav' to '/wav/wav001.mp3' failed
converting of '/wav/wav002.wav' to '/wav/wav002.mp3' failed

The permissions on the /wav folder are set to allow all users R/W access. I am working as root for everything at this point.

Has anyone gotten this to work or have information to help?

Problem scheduling mlame - lame 3.98

Reply #1 –
Quote from: gb24119 on
lame 3.98 - Fedora 8

I have been trying to scheduled mlame jobs in both Kcron and gnome-schedule without success. This is the command I am running currently:
/wav/mlame -o "-b 96 -S" -r /wav/*.wav > /wav/cron.txt

It works if I run that command in the terminal and it actually works if I use the run now options from these scheduling programs. This is the output I capture when it runs as scheduled:

New lame options are '-b 96 -S'
Removing source files after successfully converting
converting of '/wav/wav001.wav' to '/wav/wav001.mp3' failed
converting of '/wav/wav002.wav' to '/wav/wav002.mp3' failed

The permissions on the /wav folder are set to allow all users R/W access. I am working as root for everything at this point.

Has anyone gotten this to work or have information to help?



you have the solution???

please sendme if this is solved.

reggards