Sansa C250, song restart problem

[rickd]

Hey, are there any sansa c250 users on here that use rockbox firmware? If so, do you experience a glitch while trying to restart a song? When you hit the rewind button, it will rewind like it supposed to, but the song will not restart for nothing. You have to go to the next song, and then go back to the previous song quickly in order to restart a song. It's annoying.

For the past 2-3 wks, rockbox's firmware has had this glitch, and I am talking about every single firmware upgrade too. Everything else about the firmware works fine though.
 
Please fix this problem a.s.a.p.

 
Thanks
 
 

[cool_walking_]

I don't have a Sansa, but you should search on the bug tracker to see if it's been reported already, or report it yourself.

From your post, it sounds like you already are, but if I don't say it someone else probably will: before reporting a bug, make sure you are using the latest bleeding-edge just-downloaded-this-minute current build.

[rickd]

I am using the latest build. Notice that I said in my very last paragraph

"For the past 2-3 wks, rockbox's firmware has had this glitch, and I am talking about every single firmware upgrade too. Everything else about the firmware works fine though."

I tried every single update and all of them have this glitch. I first started using Rockbox around the first of this month or so and it was fine, but there was however, a problem with dead space after FFW or RWD-ing a song. I updated and the problem was fixed, but I updated again to see whatelse was done to it, and boy do I regret that I did that.

I tried to report this glitch on the bug page, but I honestly don't see anywhere on that page where you can report anything. There are no options.

[cool_walking_]

You have to register for flyspray.  It's a separate registration to the forums.  Then once logging in, an "Add new task" link appears.

[Llorean]

He asked because most people who say latest don't follow our definition of it. Considering there have probably been near a hundred builds in the last three weeks your statement that you've tried all of them makes me think you have been using the dailies? Or did you go back and compile all the revisions you missed while sleeping?

[rickd]

I've registered to both, yes. Somehow though on the bugs page, I still don't see the option to file a report.

I catch the updates at least twice a day. Maybe I don't get all of them, but in this scenario, it doesn't matter. Even though it may update several times a day or whatever, there were little to no changes in the Sansa C250 firmware here lately. This particular bug has been present for the past 3 wks.

[cool_walking_]

You don't see this?

[AlexP]

Even though it may update several times a day or whatever, there were little to no changes in the Sansa C250 firmware here lately.

Just as a point, most updates to Rockbox apply to all players Rockbox runs on (swcodec anyway).  There isn't a separate Rockbox for each player, it is the same Rockbox with different drivers for the specific hardware.  A commit may not mention a specific player, but it likely applies to it.

Also, a problem may become apparent due to a seemingly unrelated change.  It may not be caused by the change, but it may have been hitherto hidden.  I'm not saying that has happened in this case, but you cannot assume anything.

[Llorean]

And this is why we ask you give us the specific most recent revision you've verified the bug with, and if possible the exact revision the bug began with. You've given neither.

It becomes worse because A) we don't know what you mean by "latest" and B) we don't want to have to go and calculate "at 1:57 AM CST the most recent build available should've been svn revision X unless he used dailies then he would be using Y, but if the build took longer than usual he might've been using Z..." Just post the number please, and make everything just a little bit simpler all around.

edit:
r17274 on my c200 does not show this problem. Could you describe exactly how to reproduce it? I can restart songs easily.

[rickd]

You don't see this?

Honestly, that "Add New Task" button is not showing up at all for some reason. I'm still logged in to flyspray too. I don't get it.

Just as a point, most updates to Rockbox apply to all players Rockbox runs on (swcodec anyway).  There isn't a separate Rockbox for each player, it is the same Rockbox with different drivers for the specific hardware. 

I am aware of that already. I mean, it's quite apperant when you go to the page to dwld the firmware.

What I'm saying is that the specific commands for Sansa C250 have the glitch in it, while the commands for other players might work just fine.

And this is why we ask you give us the specific most recent revision you've verified the bug with, and if possible the exact revision the bug began with. You've given neither.

It becomes worse because A) we don't know what you mean by "latest" and B) we don't want to have to go and calculate "at 1:57 AM CST the most recent build available should've been svn revision X unless he used dailies then he would be using Y, but if the build took longer than usual he might've been using Z..." Just post the number please, and make everything just a little bit simpler all around.

edit:
r17274 on my c200 does not show this problem. Could you describe exactly how to reproduce it? I can restart songs easily.

When I say "LATEST", I literally mean the latest. It's that simple.  Just like now, I am using the CURRENT version "r17281-080427".  I can close out of the page and come back to it right now as we speak, and it is still that version as of YET.

[Chronon]

Honestly, that "Add New Task" button is not showing up at all for some reason. I'm still logged in to flyspray too. I don't get it.

It sounds like you're viewing a cached version of the page.  Try clearing your cache and reloading the page.

It seems there's a little tension over what is meant by "latest build".  rickd, no one is claiming that you didn't get the very latest build.  The point is that when someone says that phrase we have to make a guess about what is meant by that.  It turns out that sometimes people think of a daily build as the latest or they simply don't know how often the code gets updated.  We can avoid any ambiguity if people simply tell us what revision they are using as that is a unique identifier for the code that they are running. 

I trust your diligence in meaning "latest build".  But it is still more convenient for any interested developer to have a revision number for which they can quickly download the source from SVN.  I think you will agree that it makes sense to make it easy for people to help you.

For the purpose of tracking this down it will help if you can give a recipe for how to reproduce this bug.  Apparently, Llorean has not been able to reproduce this on his player.

[rickd]

There is no tension. lol. Not on my part at least. Sorry if it seems like I am getting an attitude or something everyone. It's VERY easy to misunderstand someone's statements when talking online. That is why I really don't bother with forums unless I have to, like in this case.

I understand what you are saying, and the confusion should be solved already as I have already stated which firmware version I am using. Sorry for the misunderstanding I may have caused.


As far as getting a receipt goes on how to reproduce the bug, I am not sure on how to do that.

[Chronon]

Okay.  I just wanted to be sure.  I wasn't sure what to make of the caps combined with bold face.  And, I agree there's no more confusion.   

When I said "recipe" I meant a set of instructions for how other c2x0 users can reproduce the behavior that you're seeing.  Can you try clearing your settings and see if that has any effect on this behavior?  (Save a config file first if you want to save your current settings.)

[bascule]

For the past 2-3 wks, rockbox's firmware has had this glitch, and I am talking about every single firmware upgrade too.

It would be even more helpful if you could go back and pinpoint the exact revision at which it started to display this behaviour, as this gives a good indication of the commit that may have caused the problem.

If you can't compile prior versions, then at least determine which of the daily builds it commenced in and I or someone else can check the revisions in-between.

I have a C240, but I don't update v. often. However, I would check this out if you could narrow the search down a bit first.

[rickd]

Okay.  I just wanted to be sure.  I wasn't sure what to make of the caps combined with bold face.  And, I agree there's no more confusion.  

When I said "recipe" I meant a set of instructions for how other c2x0 users can reproduce the behavior that you're seeing.  Can you try clearing your settings and see if that has any effect on this behavior?  (Save a config file first if you want to save your current settings.)

All of my settings are cleared and the bug is still there. Basically, there are no instructions to give on this song restarting issue. It's just when you hit the rewind button to restart a song, it will just rewind about a millisec. or so and continue playing. Rewinding a song works just fine, but restarting a song doesn't. I don't get it.

Another thing that I noticed too is that when you go to Setting>General Settings>Playback>Fast-Forward/Rewind, there is a glitch there as well. It is as followed...........

There are two options there.....

1. FF/RW Min Step
2. FF/RW Accel

You can go in and make changes into option number 2, save it and come out of it, but when you go back into the Fast-Forward/Rewind directory again, option 1 is always goes back to being selected and the changes made to option 2 revert back to default, in other words...option 2 never takes any affect as it always goes back to option 1.

Weird.