My wife has a Clip Jam that she uses for audiobooks. She has been having an issue that has been baffling me. Note that she uses MP3 files.
She loads up a bunch of books and then some of the discs don’t show up. They are visible from Windows Explorer when I hook up the Jam to the PC. But not from the Jam itself.
I just discovered that there is a 2000 song/file limit for the Clip Jam internal memory.
Also saw this, from SanDisk:
- Deeply nested folders (many folders within folders) and long file names can use more than one entry in the database. Due to this if you have deeply nested folders or long file names the actual number of songs may be less than the database limitation.
There are no long nested folders for her, but the filenames… That could be an issue. But how long is “long” here?
Does anybody know the details of this? How exactly do long file names affect this, beyond just guessing? Does anyone know how to pull the database up and view its structure? As a programmer that’s what I’d like to be able to do. Or is this so propriety in design that I’m wishing on the moon?
Another related question:
Does having a lot of other tags in the metadata affect the database size? She does have that. Title, artist, album, even comments on who the reader is, etc.
I haven’t yet counted the number of files she has on her Clip Jams–she has them and isn’t around at the moment. But I’m guessing this may be the problem, because she just bought a new one thinking the old one had a hardware problem.
Thanks for any insights.