SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to convert all my WMA's to MP3's. The problem is that LAME keeps crashing during transcoding. It also crashes when running KAudioCreator when ripping a CD. This has happened atleast twice in each process. When I say crash, I mean the system actually hard locks and I have to push the reset button.
I'm running LAME 3.98.2 on Slackware 12.2 with most of the security updates.
Would there a log created during the crash to try and figure out what happend? Should I just roll back LAME and hope it works?
Distribution: Slackware13, Solaris11, OpenSolaris, Windows 2008 Server
Posts: 12
Rep:
I think latest version of Lame is v3.98.1 (September 2008), ahh ok , i found it latest version really is 3.98.2 on download page. After compile it works just fine. KAudioCreator also, i dont know how you are converting wma to mp3, but wav to mp3 is fine. KAudioCreator makes temporary wav and after that convert it to mp3. I have Slamd64 12.2, but it is the same as Slackware 12.2
Try --verbose option, and what command do you use? Im not sure but i think you cant convert directly wma to mp3
I'm trying to convert all my WMA's to MP3's. The problem is that LAME keeps crashing during transcoding.
I'm not sure lame can transcode directly WMA files into MP3.
While googling, there are numerous examples of WMA file conversion into MP3 that do the following:
convert WMA file into WAV file using mplayer
convert WAV file into MP3 file using lame
If you want a versatile audio/video converter, I would suggest to install ffmpeg. You can compile ffmpeg and its dependencies using Slackbuilds available at www.slackbuilds.org
Distribution: Slackware13, Solaris11, OpenSolaris, Windows 2008 Server
Posts: 12
Rep:
Quote:
Originally Posted by gegechris99
I'm not sure lame can transcode directly WMA files into MP3.
While googling, there are numerous examples of WMA file conversion into MP3 that do the following:
convert WMA file into WAV file using mplayer
convert WAV file into MP3 file using lame
If you want a versatile audio/video converter, I would suggest to install ffmpeg. You can compile ffmpeg and its dependencies using Slackbuilds available at www.slackbuilds.org
Thanks for the suggestion. I am able to encode about 4-9 songs before hard locks using the script. I then used the command recommended by disturbed on a 2.5 hour wave file. It hard locked about 5 min into the encoding. Long story short, I ran the memtest86 and it found one bad byte in my RAM. It found this sometime during the 9 hours the test was running. It seemed to only show up once tho.
Here's my question from this point, would one byte really hard lock a system on a MP3 encoding? I'm having a hard time believing one byte would hard lock 4 different times. Or would actually be a random piece of....RAM.
Please excuse my ignorance, I want to understand what's actually happening. I will be moving my RAM around to test that as well (3 sticks).
Well, moved my RAM around and used different sticks. I'm trying to attach a picture of the screen. Sorry for the quality. Appears to me that the memory controller has went bad, maybe? Thanks for your help. I guess I'll try moving to a more hardware based forum and not clog up the Slackware forum. Once again thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.