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: WMA and MP3 tracks with Foobar2000 (Read 3213 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WMA and MP3 tracks with Foobar2000

Hi everyone! 

I have what I hope is a straight-forward problem.

My friend bought her first MP3 player - a Sandisk Sansa Clip.  The packagin Included a coupon for a free one month trial offer downloading MP3's.  She downloaded 150 tracks, associated with 44 artists.  The tracks are 128 Kbps, WMA format, not MP3 - and this is where the problem begins. 

Using LAME MP3 Encoder, version 3.98.4 she also ripped her first CDs - totaling an another 400+ tracks.  She ripped to MP3, VBR, highest quality and therefore the MP3's run 190 to 285 Kbps. 

Next, she consolidated the WMA and MP3 tracks to a "common main" directory - with their respective artist and album subdirectories. 

Prior to buying the Clip, I told her about Foobar2000.  I explained how great ReplayGain was.  Enthused about what Foobar's RG options could do for her MP3 rips, she installed the software and configured the library to point to the "common main" directory. 

Upon opening Foobar2000 and looking at the library's directory tree, she noticed the none of the WMA tracks appeared or were there.  She called me.  I am not a Foobar2000 expert, but I believe that Foobar2000 cannot read WMA files.  Assuming this as fact, I suggested that she install a free WMA to MP3 converter - she did - Jodix 1.16.

Jodix 1.16 was picked because, unlike ID3 Renamer 3.2, it does not appear to require .NET Framework 4.0 (and I did not want to spend time baby-sitting her install because she does not have .NET 3.0 or 3.5 installed (or any of their respective SP updates). 

When she tried to add files to Jodix's Task List, an error poped up stating she needed (at minimum) DirectX 8.X and therefore it would not allow her beyond that point - translation, no conversion.  We checked System Information > DirectX Tool, and verified that DirectX 9.0c was installed.  We ran DirectX Too and all test passed - no problems, no conflicts - her system appears to be in fine working order. 

To be certain, we installed Microsoft DirectX 9.0c (Feb 10) and the install appears flawless.  Unfortunately, Jodix still responds with the same error message stating that she needed (at minimum) DirectX 8.X and will not allow her beyond that point - translation, again, no conversion. 

Jodix was uninstalled, the Registry scrubbed, and Jodix reinstalled - problem remains.

Right clicking on several WMA files (or tracks), we checked the Properties > Summary > Advanced > Origin, and discovered Protected = Yes.  I do not know how to change Protected = No, and I suspect this may be a key to the Jodix problem.  Accordingly, I have not recommended any other WMA to MP3 converters because I doubt they will work unless Protected = No, and or .NET Framework 3.0 (or higher) is installed. 

I only rip my CDs and have never downloaded any MP3 or WMA file (or track), so I have no idea what the problem may be.

Has anyone had these or similar problems?

Thanks in advance for your suggestions and or recommendations.

Trades4USD

WMA and MP3 tracks with Foobar2000

Reply #1 –
Quote from: Trades4USD on
snip


I think I understand the problem that she has with those downloaded WMA files and, in general, I am washing my hands of it because it appears VASTLY complicated to resolve and I have no interest in spending the time to assist her.

Accordingly, an MODERATOR may delete this post and its original thread.

Thank you.

T4USD