Can't play mp3s through 'Files' option (Sansa c200)

[krisdb]

I have the Sansa c200, with the latest build of Rockbox and my mp3's are DRM-free(mostly podcasts).  I haven't done any major customization to rockbox, after a clean install, besided change some colors, equalizer and some other basic options.  

I have one directory under the Music folder, that I will drill down though the 'Files' menu option to play mp3s, instead of through the Database.  When I'm done listening to the mp3, I will manually delete it from the Sansa.  After about a week or so of adding/deleting files from this directory, I can no longer click on a file in that directory and play it.  The little 'loading/playing' icon will show in the top right when I click any file in that directory, then disappear.  I have no problems with mp3's in other directories or by playing the files through the Database.

Any help would be appreciated.

[GodEater]

Have you tried running a scandisk / chkdsk on your sansa ?

[krisdb]

Thanks for the reply.  I ran a scandisk, but it didn't fix the issue.  I misspoke in my first post, I didn't have the latest build, but I just updated to the r16109 version, but it didn't fix the issue.  I still click on the file and the little play icon in the top right shows for a second, then disappears.  Any other mp3, outside of that directory, will play, and the mp3s will play through the database.  

[Strife89]

Maybe a corrupted file table? You could rename the folder and rebuild the database....

Can you access the songs through your computer properly? (Access one through a file browser to be sure.)

[krisdb]

I was able to play the file through Windows Explorer, no problem.  I renamed the directory on the Sansa and attempted to play  an mp3.  It would bring up the WPS, but not actually play the file.  I updated the database, then rebooted, it said it was committing some files, then I was able to play the files in the renamed directory.

Edit:  I've been playing around with trying to pinpoint this issue and it get stranger.  Its seems that the software will not recognize the files in the directory unless I do a manual update of the database (I have rockbox set to auto-update).  Even then, after an update, I have to reboot and if I try to play a file, the player will freeze and I have to take the battery out.  After doing another reboot, the files will play fine.  If I do another reboot and try to play a file, it will either play a different file in the directory or freeze up.

[krisdb]

Well, I guess I'm done using Rockbox.  I know its free, but I wasted money buying the Sansa so I could use Rockbox.  I would recommend anyone who is thinking of getting a Sansa c200, so they can use Rockbox on it, to think twice (unless you enjoy manually removing the battery, multiple times).  For me, it is just completely unusable in its current form, for what it stated it did and what I was hoping to use it for.  I'm guessing the ipod versions get more attention than the Sansa versions.

[Llorean]

The sansa versio is also nearly a year younger than the iPod version. And people like you who experience problems that nobody else with the player experience rarely seem to understand that as we are not mind readers and can only fix it if you can find out enough information about it.

[markun]

Well, I guess I'm done using Rockbox.

Too bad we can't give you any money back. I hope you will have better luck in future.

I'm guessing the ipod versions get more attention than the Sansa versions.

The ipods also have their problems with rockbox, like short runtime (although it's being worked on)

[krisdb]

The sansa versio is also nearly a year younger than the iPod version. And people like you who experience problems that nobody else with the player experience rarely seem to understand that as we are not mind readers and can only fix it if you can find out enough information about it.

That's fine, except I posted this issue twice (first time over two weeks ago on the 6th http://forums.rockbox.org/index.php?topic=14796.0 and this post), and got ZERO responses.  I tried to offer as much information as I could (and tried to figure out as much as I could on my own), but it gets to a point where I couldn't give more information without some kind of proper feedback, which I didn't receive.  Even something like "we are looking into it".  I mean, yeah, I could wait a month to get some kind of feedback and another however many to pinpoint the issue, but constantly pulling the battery out of my Sansa because its crashed gets old quick.

I'm not trying to complain about Rockbox, because its free and does alot right, but its just meant as warning to anyone thinking of getting a c200 to use Rockbox's stated features (like I did), to be wary.  This is open-source software, which means its probably being developed during the developer's free time, so you won't get fixes and responses like you would with commercial software.  Just the nature of open-source software, I guess.

[saratoga]

Even something like "we are looking into it".  I mean, yeah, I could wait a month to get some kind of feedback and another however many to pinpoint the issue, but constantly pulling the battery out of my Sansa because its crashed gets old quick.

Can't you just reset it by holding power like on the e200?

I'm not trying to complain about Rockbox, because its free and does alot right, but its just meant as warning to anyone thinking of getting a c200 to use Rockbox's stated features (like I did), to be wary.  

In the c200 case its because its brand new.  The port was added in September, and it really is beta.  If you're expecting a polished product, you're probably a year too early.  Buy something like the Gigabeat or even e200 which have been around a bit longer or else except that you're going to be finding bugs that no one knows how to fix just yet.  

And anyway I don't think anyone ever claimed that the c200 port was particularly stable or even that it worked beyond basic playback, so I'm not sure that any warning is necessary.  It sort of goes without saying that an unfinished beta is going to have issues.

[krisdb]

of course, I'm not expecting a polished product, but I didn't know that playing/deleting a file constitutes an "advanced" feature.  Actually, someone did say that the c200 port worked beyond basic playback.  Specifically on the "What is Rockbox? Why should I use it?" page for your site (which I read before purchasing my Sansa):

"Rockbox for the SanDisk Sansa c200, e200 and e200R series features a large amount of plugins (games, applications and "demos") allow you to have some fun when you're bored, or put one of our multiple applications to use: open files with the text viewer, time yourself with the stopwatch, view some JPEG photos, perhaps watch a video or two, or turn your Sansa into a desktop clock with the clock plugin. Support for microSDHC cards, On-The-Go playlist creation and adjustment, full file bookmarking support, and Recording with a variety of settings and features are more key points of Rockbox for the Sansa c200 and e200 series."

Unless you consider a stopwatch and watching videos "basic" functionality.  I guess it was my mistake in assuming that, since you were able to get videos playing on the Sansa, that playing/deleting a file would work fairly well.

Holding down the power button does turn it off, but not when Rockbox freezes my Sansa up, then I have to pull the battery out.

I find it funny that I don't get any responses to my issue for over 2 weeks, but when I post I'm ditching Rockbox, I get nice prompt responses.

[Lear]

of course, I'm not expecting a polished product, but I didn't know that playing/deleting a file constitutes an "advanced" feature.

So you do delete the file from within Rockbox? Because I also listen to some podcasts on my e200, but I delete the old ones from the PC, and I haven't seen this problem at all. If so, it could mean there is a problem in the filesystem code in Rockbox.

Have you enabled bookmarks in any way? If set to auto-load bookmarks, it could cause somewhat unexpected behavior if you keep deleting files...

As your testing suggest that the database is somehow involved in this (though I don't see how, if you play the file through the file browser), you could try adding a file named "database.ignore" (without quotes) in the podcast directory and see if that makes any difference.

Also, when the problem appears, checking the disk from Linux could be worth a try. I had a problem on one player that scandisk didn't find, but would blue-screen Windows if I tried to delete a certain file. The Linux FAT checker fixed it for me.

[pixelma]

Even something like "we are looking into it".  I mean, yeah, I could wait a month to get some kind of feedback and another however many to pinpoint the issue, but constantly pulling the battery out of my Sansa because its crashed gets old quick.

Can't you just reset it by holding power like on the e200?

Yes you can power off a hanging c200 the same way as on e200 - hold power for about 15 seconds.

So you do delete the file from within Rockbox? Because I also listen to some podcasts on my e200, but I delete the old ones from the PC, and I haven't seen this problem at all. If so, it could mean there is a problem in the filesystem code in Rockbox.

I was thinking this too and wanted to suggest some proper tests - meaning repair possible file system errors, installing a fresh build and music, do what you think you did causing this problem (a week of deleting/copying or whatever files only on your Sansa) and if the same problem occurs again - check the "disk" for errors again and file a proper bug report. But then there was this statement that there were no file system errors...

I guess it was my mistake in assuming that, since you were able to get videos playing on the Sansa, that playing/deleting a file would work fairly well.

I don't do this kind of operations very often but used it sometimes and didn't have any problem with it on my c250 yet. Edit: I mean "deleting a file".

[krisdb]

I was thinking this too and wanted to suggest some proper tests - meaning repair possible file system errors, installing a fresh build and music, do what you think you did causing this problem (a week of deleting/copying or whatever files only on your Sansa) and if the same problem occurs again - check the "disk" for errors again and file a proper bug report. But then there was this statement that there were no file system errors...

As stated, I ran a scandisk using Windows XP and received no errors.  Since my first post, two week ago, I've installed a fresh build twice and deleted files from the Sansa ONLY using Rockbox (I rarely delete files using my computer).  Approximately a week after I install a fresh build and use the Sansa normally (adding/deleting/bookmarking), I get the playback issues.

One other thing to note, I am using auto-bookmarking and I have the database set to auto-update.

Should I file a bug report?

[MarcGuay]

One other thing to note, I am using auto-bookmarking and I have the database set to auto-update.

- The Database Auto-Update is unrelated as that only affects the Database browser.
- The problem is probably the result of deleting files with bookmarks.
- Everybody knows your first post was two weeks ago.  Some people never get a reply.
- The fact that you've run into a small, weird, and rare problem while doing a small, weird, and rare task doesn't make Rockbox unusable on the c200 series, especially when there are perfectly good alternatives available (deleting the files on your PC or browsing with the Database).
- Good luck.  Hopefully someone with some bookmarking knowledge can help explain this behavior.