It’s been a long while, but I have seen this issue, perhaps a year ago. This might take a little coffee.
I think we might have an issue with processor overhead here. AAX format involves a higher bitrate and larger files. I think you might have a case of the memory is formatted with 4KB clusters. This formatting can happen when the player is initially set up, or any time that the player is formatted using Windows.
The problem is that Windows likes those little 4KB clusters. The optimum cluster size for the Sansa is 32KB clusters.
If you switch over to MSC mode, you can check the cluster size (allocation unit size) by using the chkdsk utility from a command prompt. In a nutshell: Settings > System Settings > USB Mode > MSC, then plug her in to the USB port. On the PC, find the connected Sansa and see which drive letter has been assigned to it. Then from the Run box (start >Run, then a prompt will pop up, or enter cmd for an msdos prompt)
For example, if the drive letter is E: , you can enter chkdsk E: in the command window. . After running chkdsk, it will ask, “Do you want to save as files?” enter N or “no” for now. The result will look something like this:
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
The type of the file system is FAT32.
Volume SANSA CLIPZ created 7/23/2011 9:46 AM
Volume Serial Number is 3841-02C1
Windows is verifying files and folders…
File and folder verification is complete.
Windows found errors on the disk, but will not fix them
because disk checking was run without the /F (fix) parameter.
Convert lost chains to files (Y/N)? n
4 KB of free disk space would be added.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
7,716,112 KB total disk space.
1,975,284 KB in 1,572 hidden files.
2,564 KB in 608 folders.
5,300,860 KB in 1,805 files.
437,396 KB are available.
4,096 bytes in each allocation unit.
1,929,028 total allocation units on disk.
109,349 allocation units available on disk.
Windows will display the allocation unit size. If you see 4,096 bytes listed, there you go. Note something interesting I just discovered on this device? Youbetcha. I have been using a teeny size following tinkering some time ago, and never reformatted. I’ll just blame it on Windows.
The Sansa loads your music or book file into memory in clusters. The File Allocation Table tells the player (or any computer for that matter) just where the next section of your file is, so it can be read. If you have a large file like a book or a long music track (classical music involves long tracks), the player is really bust parsing that huge table. When the display is illuminated, priorities change a little bit, as the player is handling a different set of tasks. I remember now, the stuttering ceased if we would refresh the screen.
Coffee is a wonderful thing. This issue was from 2008. When you mentioned the screen, something sounded familiar.
What you’ll need to do is reformat the device with 32kb clusters. The hard part is that the format clkears all media from the player, and you’ll need to reload afterwards. First be sure that you have copies of your media on the PC.
Then use the nuclear option , the handy Format function un the player itself. On the Clip Zip we have a different option, the external memory can also be formatted from the player. I’ll bet that your Audible files are on the Internal Memory. If so, Settings > System Settings > Format > Internal Memory > Yes.
The Sansa’s built in format command optimizes the memory with 32KB clusters. Open the Audible Manager and transfer your audiobook again. And enjoy the book without-out-out skipping.