08-06-2015 08:06 PM
One Fuze went bad due to water (actually sweat) damage that fried the screen. The other 2 along with the with the 3 Zips all seem to run into memory issues that freeze the player and require a hard reset followed by a reformat. The time between freezes decreases until it's not worth the effort anymore.
08-06-2015 11:59 PM
The memory issues may be due to corrupt files, and not a player problem. I use a small plastic bag to prevent my Clip players from getting wet. Flash memory will wear out if you write to it too many times, although it seems like flash memory(even the least expensive of decent enough quality) should be good for at least 1,000 writes. I rarely change the music on my players though.
08-07-2015 04:40 PM
With Audiobooks, I writing 2 - 3 times per month (large files, though anywhere from 300 - 600 MB per book). It's unlikely ot be corrupt files because I've alays been about to revert to the Clip+ with the same file and get good performance. While the + is a long term workhorse, I use it mostly as a backup.
08-10-2015 09:37 AM - edited 08-10-2015 09:42 AM
I've used Clips (Cllip+ and Sport) for audiobooks for years so here is my experience.
1. It seems that audiobook parts needed to be loaded on in order for this player to play them in order. Annoying but true. Such an easy thing to fix but Sansa just never got it.
2. If you have them in order and it is till mixing them up, make sure you dont have your music shuffle on. I had one library audiobook stored in my Music folder and went crazy with it playing out of order til I realized I had my shuffle on! I now make sure I don't load a library audiobook into my Music Folder. And I always add them to the player in order.
3. The Clip Sport is no good for Audibles Enhanced Mode and I had to reload all my books into Mode 4. In the Enhanced Mode, it also took forever for a book to come back after pause. As someone said, it took longer and longer the more you got into the book. It is annoying to have to have your books in multiple parts (unlike the Enhanced mode where they come in one part only).
Another problem with Enhanced is that my Sport skipped the last few minutes at the end of every book--totally unacceptable! Sadly, my old Clip+ did take Enhanced mode and I loved it. Battery life terrible on that old Clip, and why I keep using Sport.
4. Just wanted to add that I have never had a Clip or Sport break after the first month. Two didn't work after a week or so and Amazon sent me new ones immediately--even before they received the broken one back! I have had numerous Clips and they seemed to last well for me. Except for the clip part, which inevitably breaks off!
Just wanted to add that the Sport is newer than Clip+, so why doesn't it use Audibles Enhanced Mode??? It is a step backwards, IMHO, and really a bummer!!
08-10-2015 09:46 AM
3300- 600 MB per book? In how many files? What format and bitrate? For spoken word podcasts, I convert them to 32kbps mp3 mono right after I download them to save space. Using a low bitrate also increases battery life. If a speaker is moving while he is talking, listening to it in stereo can give a dizzying feeling. The Clip Sport has a less capable processor than the Clip+, although its power usage is only around 45% of that of the Clip+. The Clip Sport might have trouble with very large files in certain formats.
08-10-2015 08:40 PM
Audible Enhanced mode comes in an Audible specific format as a single file that works out to about 28MB per hour. Depending on the narration speed, most books will average around 10 - 15 hours, 7 - 8 hours is on the low end for most novels and it's not unusual to find audiobooks in the 15 - 24 hours range. The longest I've seen is Atlas Shrugged at 62 hours. As such, a 4GB player is more than adequate.
08-11-2015 01:40 AM
"Audible Enhanced mode comes in an Audible specific format as a single file that works out to about 28MB per hour. Depending on the narration speed, most books will average around 10 - 15 hours, 7 - 8 hours is on the low end for most novels and it's not unusual to find audiobooks in the 15 - 24 hours range. The longest I've seen is Atlas Shrugged at 62 hours. As such, a 4GB player is more than adequate."
The problem is that the Clip Sport has a rather limited amount of ram, so it is likely to choke on larger files, especially if they are in a format that is more complicated to decode than mp3. I guess Sandisk should have probably said ouright that the player can't play very large files. Having said that though, the Clip Sport only uses around 45% of the power that the Clip+ and Clip Zip use, so they could make a player with huge battery life that still light and small using the Clip Sport circuitry and a somewhat larger battery than the Clip Sport has. Most people don't tend to play very huge files. They tend to play mp3 files that are typically 15 minutes or less, or podcasts that might be up to an hour or two, but that are at a low bitrate(perhaps 32kbps?).
08-11-2015 05:01 AM
Thanks. This is the frist description beyond merely stating "hardware limitations" that actually explains the issue with audiobooks and clearly indicates that a firmware update is unlikely to ever address the problem. It also suggests that the direction Sandisk seems to be going is unlikely to ever consider designing a player that will meet my set of features for the ideal audiobook device.
08-11-2015 05:57 AM
Rather than blaming Sandisk, you should blame Audible. I don't know why they need to use such huge files for audiobooks, and why they can't break up an Audiobook into a number of files. i don't use audiobooks, but do download podcasts. Many that I download are already at 32kbps, but those that are at a higher bitrate I convert down to 32kbps before putting them on my player. There is no need for high bitrates for spoken word files. For music a bitrate of 256kbps or 320 kbps is recommended. For voice files though, 32kbps mono is fine.
08-11-2015 09:41 AM
Actually, those "recommended" (from where?) bitrates for music are relatively high and my hunch is that the average person wouldn't see (hear) much, if any, difference with music ripped at a much lower rate. Years ago, I tested it out and couldn't see (hear) a difference starting at a bit less than 192 kbps, for music. I also recommend ripping using VBR (variable bit rate) with a higher end at the top--it just makes sense to me, for the software to use more data space where it might be needed, and less space where it is not.