Lame won't work -- sometimes
Hi all,
I use streamripper to record a daily radio program, then lame to re-encode it. Problem is, one day lame works, and the next day it doesn't, so about half the time I have to process it with Audacity instead, which takes a lot more of my time. The stream rips are done by a cron job, with the same streamripper options every time. When it doesn't work, it gives the normal output of runtime options, but the instant it gets to the progress bar, it quits with no error message or indication of what went wrong, like this: Code:
user@dell:~/streamripper$ lame -a -b 16 tnp30_2013_03_21_09_31_02_64k_kbrt.mp3 tnp30_2013-03-21_16k_kbrt.mp3 (This is on Debian Wheezy, in case it matters.) |
Did you check the logs too? It is hard to tell since the output doesn't point errors, does it create any file at all?
Here some links maybe it helps: http://lame.cvs.sourceforge.net/view...tml/links.html http://linux.die.net/man/1/lame Regards |
Thanks for the reply. I think I may have fixed it by running streamripper with --with-id3v1. It's worked for 2 days now, and if it works for a couple more days I guess it's fixed. I never did find what lame was objecting to, but I guess it's something to do with the ID3 tag.
|
Well it happened again today, so I was wrong about the ID3 tag being involved. But I noticed that lame was reading the sample rate incorrectly, so I tried --mp3input to force lame to read the input file as MP3 instead of MP2, and it worked. The man page says lame assumes MP3 if the extension is mp3, but apparently that's incorrect.
|
All times are GMT -5. The time now is 03:33 PM. |