So give it a try, and let me know. If it works, I'll include it in the release itself.
As for SHN, I actually have never heard of it before. Always been a FLAC man myself. - Nov 30 2005
Oh, this might be overly pedantic, just remember to have amaroK open, with some MPC files in the playlist before you run the script from console.
Also, make sure that the first panel of the script indicates that you have the package required to decode MPC. - Nov 03 2005
If you mean something else, let me know. - Oct 24 2005
As for the next two errors, "could not find" and "rm...", what's happening is that the decoder you're trying to use, for whatever reason, isn't actually decoding the source file into temp.wav, and since you aren't creating temp.wav, you obviously can't encode it or remove it. If you're trying to transcode a musepack file, these are the exact errors you would get since you don't have mppdec installed. I suppose that's what's happening. If not, give me more info about the decoder step in your conversion (or try a different type of source file and see if that works). - Jul 19 2005
Start amaroK from a terminal. (Most likely simply "amarok" will do.) Now, when you run the script, the terminal will give you the output of the mplayer command, which decodes the wma, and lame which encodes to wav. It will also give you what the error is if one of the commands doesn't work. My guess is it's probably an issue with mplayer.
Oh, also, watch the top-level of the directory where the transcoded files should end up--if you never see "temp.wav" appear, then you know there's a decoding problem. - Jul 18 2005
But, here's a version of the script which may (or may not) decode your .ape.
The command line options for MAC are dead-simple, so I probably have the right decode command, but of course I can't check this.
If people give me positive feedback that this works, I'll put it into a formal release. Until then, just use the script here. - Jul 03 2005
Can you email me more information?
Like, if you remove those 5 or 6 files, do you still get the problem? Or does it happen after any 5 files? What type of files are they? If there's a particular file that's gumming up the works, have you tried decoding/encoding that particular file on the command line? In the top level directory where you're saving the transcoded files, is there a temp.wav file? If so, is it of a song that was successfully transcoded, or is it of a song that didn't get encoded?
Answers to any of these questions would be helpful to me. My suspicion is that the decoder is hitting a file it doesn't like and killing the process. Though in that case there should be some error output...
Anyway, please, if this has happened to anyone else, also email me any info you can give me. Email can be found in my username link. - Jul 01 2005
My recommendation is people should never convert from one lossy to another (or a different bit-rate of the same format) just for the sake of having it in a different format. As the poster noted, quality will *always* decrease. If you have to do the conversion (iPod won't play my ogg and I can't re-rip!), well, you gotta go what you gotta do. If the conversion is optional (I'm using 180kbps mp3, but I could fit everything on my Rio Karma if I converted them to 128), then try the conversion on a 10 or 20 tracks, and see if you can tell the difference. That way you can decide for yourself whether the loss in quality is sufficient to stop you from doing the conversion. - Jun 04 2005
Until I can think of slick way to make both groups happy, I think I may leave the burden on you to clean the mp3 songs from the amaroK playlist window, leaving only the oggs. I will, though, think about a solution. - May 16 2005
I'm lost with all of this encoding stuff. If anyone can help, or at least guide me to good places to learn how to solve the problem myself, I'd appreciate it. Several hours on Google, and I don't know much more now than when I started searching. - May 11 2005
To all: thanks for the kind words. - May 07 2005
Traceback (most recent call last):
File "/home/mlmitton/DownloadFiles/superkaramba/liquid_weather_plus/liquid_weather.py", line 13, in ?
ImportError: No module named os
I'm using Suse 9.3 which comes with Python 2.4--is this possibly the reason why I get the Python error? I know one of the fixes from SK .35 to .36 was to be able to use Python 2.4. Is the same thing happening here? Also, when I just run Python from the command line, it has no problem importing the modules that LW3.11 uses. - Apr 22 2005