1st problem with 8GB Clip already...

Oh man, this is not good.:cry:

The only reason I noticed this problem is because I am an audiophile and I pick up on things, but this one was really blatant.

I thought the Clip was playing music a tad bit slower than it normally does on my computer as certain beats I just know.  But I just confirmed it by playing a few different tracks, FLAC, CBR 128, CBR 320.  Any song I play, if I start it out in the beginning timed exactly with the computer, after a few seconds it starts to shift.  And by around 15 seconds, you can easily tell that the Clip is already “behind” in playing the song.  And even if I give the Clip a head start, eventually the computer version catches up and again, the Clip starts to fall behind.  It seems as if the Clip is playing the song 5% slower than it should be.  If it makes a difference, I have the latest firmware on it, 02.01.32A** **

What is up with that?:cry:

Its a reported bug. They tried a fix in the last firmware this past week but many have said it was not enough. The Developement team is working on it.

Ok, thanks.  I was hoping it’s not just me.

Now that I’ve noticed it, it’s really starting to bug me as some songs I can really notice that the song isn’t playing at the proper speed.

Is there an older firmware I can flash to until they fix this problem?  I shouldn’t have been so quick to flash it out of the box.

@warrior1986 wrote:

Now that I’ve noticed it, it’s really starting to bug me as some songs I can really notice that the song isn’t playing at the proper speed.

 

For whatever reason, the clip is optimized to 48KHz sampling rate instead of 44.1KHz. This was reported by some user earlier (davek?).

I resample my flac files on the fly while encoding to ogg and copying to the clip and I have no issues with 48KHz so far. There is a small error too, but it’s unnoticable for me. I’ve already tried 2 different 8GB clips and I’m willing to bet that either the whole batch here is broken or all V2 models.

Fortunately, I’m not an audiophile and I don’t hear any difference in quality between both sampling rates, so I think it’s a good way to go while waiting for the firmware fix.

Message Edited by bungl on 03-01-2009 05:11 AM

@conversionbox wrote:
Its a reported bug. They tried a fix in the last firmware this past week but many have said it was not enough. The Developement team is working on it.

I don’t think they tried to fix THIS bug last time. They targeted some mp3 cbr playback issue which I believe is something different, because THIS bug is filetype insensitive. Saying “but many have said it was not enough” is misleading, because it implies they actually did a fix, which is not truth.

The clock rate issue is in the works.  Just a little QA time will be needed.

µsansa

@bungl wrote:


@conversionbox wrote:
Its a reported bug. They tried a fix in the last firmware this past week but many have said it was not enough. The Developement team is working on it.


I don’t think they tried to fix THIS bug last time. They targeted some mp3 cbr playback issue which I believe is something different, because THIS bug is filetype insensitive. Saying “but many have said it was not enough” is misleading, because it implies they actually did a fix, which is not truth.

 

 

The Change log said “Music plays slow – mp3 192kbps 44KHz CBR” This to me means they made an attempt in the right direction. when I say “It may not have been enough” I mean that this attempt may not have been the complete fix, meaning it may have only fixed part of the playback issues that people are experiancing.

@microsansa wrote:

The clock rate issue is in the works.  Just a little QA time will be needed.

 

µsansa

Cool, thanks!  I was starting to think that if only there was some way to speed up the CPU.:smiley:

I just tested my ver 1.,  2 Gig clip with the new firmware and  a 1,000 Hz sine wave test tone Mp3 file, when played back from the clip measures at 1,007 Hz.

If you listen to the 1,000 Hz and 1,007 Hz tones at the same time, you can clearly hear that they are out of tune.

This is important to people (like me) who like to play musical instruments along with the recorded music on their Clips.

This problem means that the music coming out of the clip is slightly (but noticeably) out of tune with real world.

In my test example, the Clip is slightly higher in pitch (plays slightly faster) than normal.

Though a small problem for non musicians, it is a big problem for musicians who want to use the Clip for practicing along with or for providing backing tracks to play along with at a performance.

Thanks for the firmware updates Sansa

Please fix this problem in the next firmware update.

Happy Trails…

@wavysclip wrote:

 

I just tested my ver 1.,  2 Gig clip with the new firmware and  a 1,000 Hz sine wave test tone Mp3 file, when played back from the clip measures at 1,007 Hz.

If you listen to the 1,000 Hz and 1,007 Hz tones at the same time, you can clearly hear that they are out of tune.

This is important to people (like me) who like to play musical instruments along with the recorded music on their Clips.

This problem means that the music coming out of the clip is slightly (but noticeably) out of tune with real world.

In my test example, the Clip is slightly higher in pitch (plays slightly faster) than normal.

Though a small problem for non musicians, it is a big problem for musicians who want to use the Clip for practicing along with or for providing backing tracks to play along with at a performance.

 

Thanks for the firmware updates Sansa

Please fix this problem in the next firmware update.

 

Happy Trails…

Wow, that’s incredibly strange.  The problem I have on my Clip is that the music is playing too slowly.  Your issue is exactly the opposite, that the music is playing too fast?

How is that possible?

@warrior1986 wrote:


@wavysclip wrote:

 

I just tested my ver 1.,  2 Gig clip with the new firmware and  a 1,000 Hz sine wave test tone Mp3 file, when played back from the clip measures at 1,007 Hz.

If you listen to the 1,000 Hz and 1,007 Hz tones at the same time, you can clearly hear that they are out of tune.

This is important to people (like me) who like to play musical instruments along with the recorded music on their Clips.

This problem means that the music coming out of the clip is slightly (but noticeably) out of tune with real world.

In my test example, the Clip is slightly higher in pitch (plays slightly faster) than normal.

Though a small problem for non musicians, it is a big problem for musicians who want to use the Clip for practicing along with or for providing backing tracks to play along with at a performance.

 

Thanks for the firmware updates Sansa

Please fix this problem in the next firmware update.

 

Happy Trails…


 

Wow, that’s incredibly strange.  The problem I have on my Clip is that the music is playing too slowly.  Your issue is exactly the opposite, that the music is playing too fast?

 

How is that possible?

I just played the same song on my 8GB Clip vs. a CD player. A 3:12 song on the CD player, the Clip was almost 2 seconds behind at the end of the song. I can’t say if both machines go from pause to play with the same immediacy, however, so it’s not the most scientific of tests. That said, it’s nothing I have noticed just by listening…I just tried it because most say it plays fast, and you thought yours was a little slow. Weird. I’m still going to use the Clip all the time though. :wink:

Hmm, so it seems like the speed issue is all over the place.  While yours is barely noticeable to be slower, especially if it’s only 2 seconds behind in a 3 minutes, mine is comparatively REALLY bad.  By the time the song hits 30 seconds on mine, it’s already a full second behind, likely even a little more.:cry:

I’ve got a couple CD’s with 20 minute songs…I wonder what would happen there? Either way, I don’t have time to mess with it today.

I think what I’ll try to do when I get home tonight is to re-encode some of the songs that are currently on the player to CBR 192 MP3 files, since the firmware notes specifically mention that bitrate as having been fixed.  The recode will come from FLAC files, CBR 320 files, and VBR files.  Then retest and see.

Message Edited by Warrior1986 on 03-02-2009 08:19 AM

@marvin_martian wrote:
I’ve got a couple CD’s with 20 minute songs…I wonder what would happen there? Either way, I don’t have time to mess with it today.

The clip will be off by ~25 seconds by the end of the song :wink: Well, I never tested anything that long, but it was over 5 seconds with a 5 minutes track on both of my 8GB clips.

@warrior1986 wrote:
I think what I’ll try to do when I get home tonight is to re-encode some of the songs that are currently on the player to CBR 192 MP3 files, since the firmware notes specifically mention that bitrate as having been fixed.  The recode will come from FLAC files, CBR 320 files, and VBR files.  Then retest and see.

That won’t probably help you, but try it, who knows… :wink: My temporary advice is different. Re-sample to 48KHz. I know, sounds stupid. But 48KHz is almost accurate, for whatever reason. Until they fix 44.1kHz pitch error, I’m sticking to 48KHz.

I just checked my 8gb Clip with *.32 firmware it lags by 3 seconds at 8 minutes playing a FLAC file.

This product sucks I would NEVER have bought this thing if I knew about this bug.

There is another bug playing FLAC where if you fast forward it will pop at some point only playing beginning to end is clean.

Then there is the playlist bug where it will not see a file name with a German character.

If I recall correctly, a fix is in the works and is in QA testing right now.

@miikerman wrote:
If I recall correctly, a fix is in the works and is in QA testing right now.

Yes, but it also means there are a few months left before it’s released…

@bungl wrote:


@warrior1986 wrote:
I think what I’ll try to do when I get home tonight is to re-encode some of the songs that are currently on the player to CBR 192 MP3 files, since the firmware notes specifically mention that bitrate as having been fixed.  The recode will come from FLAC files, CBR 320 files, and VBR files.  Then retest and see.


 

That won’t probably help you, but try it, who knows… :wink: My temporary advice is different. Re-sample to 48KHz. I know, sounds stupid. But 48KHz is almost accurate, for whatever reason. Until they fix 44.1kHz pitch error, I’m sticking to 48KHz.

Any free program that I can use to do the resampling?  I use dbPowerAmp for all my converting and encoding, but it doesn’t seem to have anything to do resampling.