Small program to fix the Sansa Clip 8gb slow pitch playing bug.

Hi,

Recently I have purchased the Sansa Clip 8gb device. I have immediately noticed the slow speed playing pitch problem.

Since there is no firmware update available from Sandisk and I liked the device very much I did not want to return it.

I have created a small script that might help you guys to transcode all your MP3 files on the device to 48khz (this way the device plays

the songs in the right speed and pitch).

The script is very easy to operate, just plug your Sansa Clip and make sure it is accessible via MSC and you can browse the files at your PC then

just run:

X:\> SansaClipFix.exe FOLDER_TO_MP3_FILES ,

for example: SansaClipFix.exe g:\audioable

The script is downloadable at: Script

 -=twee

 My solution is even better. I’ll simply buy another brand next time. I should have known better anyway.

You are right !!!

If you think Sansas are the only MP3 players with problems, you’re sorely mistaken. Visit the forums for any player and you’ll find plenty of people looking for help.

Yes, but this is such a lame argument !

You can say that about anything you buy, TV, laundry machine, car, anything … :frowning:

still this is not good enough ! Big company such as Sandisk should have QA their products better before

spreading them down the market !

@twee wrote:

Hi,

 

Recently I have purchased the Sansa Clip 8gb device. I have immediately noticed the slow speed playing pitch problem.

Since there is no firmware update available from Sandisk and I liked the device very much I did not want to return it.

I have created a small script that might help you guys to transcode all your MP3 files on the device to 48khz (this way the device plays

the songs in the right speed and pitch).

The script is very easy to operate, just plug your Sansa Clip and make sure it is accessible via MSC and you can browse the files at your PC then

just run:

 

X:\> SansaClipFix.exe FOLDER_TO_MP3_FILES ,

 

for example: SansaClipFix.exe g:\audioable

 

The script is downloadable at: Script

 

 -=twee

I tried this on a single MP3 file to see how it works, but each time I get this error message:

 Error! could not find lame.exe on the current folder, please download it from http://jthz.com/~lame or http://lame.sourceforge.net/

I put both your script and the LAME executable in the same folder as the test MP3 file I tried to convert.  Any pointers as to what I’m doing wrong?  Try a different version of LAME?

Message Edited by tnmats on 06-29-2009 07:42 AM

First option is to re-download the script again (I have fixed some path issues).

Second one is to change the current folder to the folder where you have extracted the files and run from there,

for example:

Open Start/Run , type cmd.exe

in command prompt, type:

C:\>D:

D:\>CD\Temp

D:\TEMP>SansaClipFix g:\audioable

-twee

@twee wrote:

First option is to re-download the script again (I have fixed some path issues).

Second one is to change the current folder to the folder where you have extracted the files and run from there,

for example:

 

Open Start/Run , type cmd.exe

in command prompt, type:

 

C:\>D:

D:\>CD\Temp

D:\TEMP>SansaClipFix g:\audioable

 

-twee

 

Worked this time.  What I was doing from the command window was trying to execute the file by giving the file pathname directly, not first drilling down to the working path.  When first went to the working directory for the script and then executed the script from that working directory it works.  Thanks for the help.

I noticed the ID3 tag info was gone in the converted file.  Is there some setting to preserve that information?

Sorry , not at the moment, anyhow it is recommended to keep an original copies of your MP3 on your harddrive and just convert the files on the

device only for the purpose of playing them correctly.

-twee

Considering the clip only uses ID3 tags (rather than file name) this may not be the best method for large collections.

The pitch issue only bugs me on a couple of songs so I’m more than happy to wait for sandisk to give us some new firmware, and like a lot (the majority?) of people here I LOVE my clips.  

You are right man, I just created this script for me and shared it with the world. I did not have any intentions to open a company in order to maintain it :slight_smile:

I run it on my Sansa clip with 500 songs (not much but it’s quite nice) … and I can see all the names of the songs and everything no problem at all.

So the player shows not only from ID3 tags, it also shows the name of the file.

-twee

@twee wrote:

You are right man, I just created this script for me and shared it with the world. I did not have any intentions to open a company in order to maintain it :slight_smile:

I run it on my Sansa clip with 500 songs (not much but it’s quite nice) … and I can see all the names of the songs and everything no problem at all.

So the player shows not only from ID3 tags, it also shows the name of the file.

 

-twee

Indeed, thank you for sharing it.  I wasn’t criticizing, just asking.   :smiley:

 I need to check if my player will indeed show just the file name; I tried that once and all I remember seeing was “Unknown” in the album and artist listings.

I still think it is pretty shoddy engineering on Sandisk’s part to allow a player that doesn’t play at proper speed.  I’m a design engineer (IC’s) and we have to check out every function pretty thoroughly before releasing a chip, and let some customers beta test the IC before full release.  If something slips out we make a fix.  This seems like quite basic function to goof up and it’s pretty easy to catch to most anyone who listens to music and knows the tracks they are listening to.

@gwk1967 wrote:
If you think Sansas are the only MP3 players with problems, you’re sorely mistaken. Visit the forums for any player and you’ll find plenty of people looking for help.

 I don’t think they’re the only ones with problems. But I bet they’re the only ones that play everything at the wrong speed and the company hasn’t bothered to even try to fix it (apparently). This is a fairly major flaw. The thing is intended to play music and it can’t even do that right.

   If they would simply post and tell us what the heck is going on, that would be better than being ignored. Are they working on it? Can it even be fixed? Do they intend to offer a firmware version that fixes this bug? That’s all I want to know. I’d rather know about it if they’re not going to bother to fix it. Encoding everything to 48KHZ is a major pain. And if the stuff is already encoded to 41 MP3 when you get it, that means you have to reencode a lossy file. This is not an acceptable solution.

Message Edited by randomprecision on 07-11-2009 03:42 AM

Isn’t here any audio quality loss when converting 44khz FLAC to 48khz mp3? I know that the compression drops some audio information, but how is 44khz vs 48khz mp3 when ripped from 44khz source?