Strange bookmark behavior

[scorche]

If you can't build a stable product, don't build it at all (or don't release it).

Well, we haven't released Rockbox for the sansa, so that solves that?

[AlexP]

I already warned you in a PM.  STOP the personal attacks.  If you feel that someone hasn't understood you, fine.  Calling them a liar for thinking they have is NOT acceptable.

P.S. People work on what they want to (this being volunteering after all).  If someone wants to work on Doom and not something else, then that is their choice.  Neither you nor I have the right to tell someone how to spend their free time.

I'm leaving this thread open for now in case you feel like being constructive.  Any more flaming will not be tolerated.

[Lear]

That's BS.  He fixed a problem, not the problem I was having.

Well, I fixed a problem I found, based on your description, so technically you found it. (Yes, I realize I'm probably splitting hairs here...)

For some reason, he kept insisting that I was trying to resume a file that no longer existed, no matter how I tried to explain it.

That was the only way I could see the problem happening (i.e., the top entry in the folder .bmark file referred to a file that didn't exist, in combination with load last bookmark set to yes).

[Llorean]

Apparently you're missing one important point: IF A DEVELOPER CANNOT REPRODUCE YOUR PROBLEM, THEY CANNOT FIX IT. So, if you want to mail us your Sansa, we can look into it a little more. If you want to spend some time helping us experience the problem ourselves, we can look into it a little more.

If you want to complain about software that ISN'T RELEASED (and try going to the Releases page, and it'll be pretty clear, so unless you want to claim illiteracy, or sheer laziness, your excuses about us releasing unfinished software are frankly laughable) some more, why not actually try to move toward solving the problem, instead of telling us you didn't know you were playing with an unreleased build because you didn't actually read the information available to you before installing the software.

And as for Doom running, believe it or not, porting Doom is a LOT easier than maintaining our playback system and all its myriad features. Keeping playback working with all the various metadata related things is nowhere near as simple as you seem to think it is within this limited environment. If you can tell me how to prevent 250 people from working on whatever they want, when I have no control over them by means such as being able to say "I'll fire you if you don't fix bugs instead of writing plugins", and now to contact everyone on Earth before they hear about our project by other means, and tell them "Don't bother contributing at all if you don't plan to only contribute bug fixes, and not things like games that don't really matter", we can start discussing your dreams of a focused open source project. But unless you have no magical contribution to this, when a random person shows up out of the blue with a new game for us, we'll go ahead an add it, even if the time could've been spent better somewhere else, because honestly: it's already been spent.

Frankly, you've made it rather apparent you have no clue about the difficulty of developing various areas of our codebase, what the project is, or how open source actually works within the context of this project. And if your next post isn't an apology saying "Wow, I didn't realize these things, I thought you guys actually had a means of controlling every person on Earth, but I was wrong" or at least something similar, I'm going to decide that you really have no interest in seeing your problem fixed, and just wanted to spread bile and venom about open source, and remove this discussion, and you, entirely from the forums.

[dogskull]

Is any way to access builds that are older than 30 days?  I would like to try to find a version for the X5 with functioning bookmarks.

I'm using Rockbox on iAudio M5.. It’s something similar to your player. And the last bild that worked properly was r15311-071025. So try to find bild that was released earlier 2007.10.25

[Llorean]

You can compile them from SVN, but we only archive actual builds for 30 days.

[dogskull]

Okay, thanks.  That's currently beyond me but I'll look back to it if I can't turn up a build from another source.

[Taslow]

Any way to make an exception on the archive 30-day thing? If rules are rules, that's cool. Just thought I'd ask for all of us out here who basically use Rockbox because it bookmarks.

Not that you'd catch me b**ching about anything given out for free, but it would be cool to be able to load up an older build (because I know for a fact bookmarking worked perfectly on my e250r for a long time before it went whack)  while this gets sorted out by those of you who actually have a clue about programming this stuff. :-)

[Llorean]

If you don't want features to break, keep your old builds around before updating. Seriously, this is unreleased software, it's more or less your own responsibility to keep old versions around if you need them. Development moves forward, it's always possible to compile your old build from source because we keep every source change archived. But the archived builds will pretty much just go back a month. They're for short term significant problems. If a feature breaks, you have immediate access to the one before. Honestly, you had 30 days to roll back after bookmarking broke.

Anyway, the best solution is to help fix it.

[tahoejoe]

Just thought I'd re-reference this because, for all intents and purposes, there is a "rube goldberg" method for getting bookmarks to work on the sansa E2XX ( I have the 250 R) with some of the later builds.

It's not perfect, but for the Sansa, I find that after you resume play using the bookmark, if you rewind the bookmarked track for a few seconds, it does resume the track close to where you left off ( i.e., the small amount you rewind is the difference).

[Taslow]

If you don't want features to break, keep your old builds around before updating. Seriously, this is unreleased software, it's more or less your own responsibility to keep old versions around if you need them. Development moves forward, it's always possible to compile your old build from source because we keep every source change archived. But the archived builds will pretty much just go back a month. They're for short term significant problems. If a feature breaks, you have immediate access to the one before. Honestly, you had 30 days to roll back after bookmarking broke.

Anyway, the best solution is to help fix it.

Sorry boss....I didn't mean to look like I was whining about it and wanting someone to solve my problems for me. That wasn't my intention at all. I appreciate your viewpoint, I just thought I'd ask because I'm pretty new to Rockbox.

And I assure you many times over, if I knew a thing about C++ or whatever language this is written in, I'd be off the bench in an instant playing my part. However, since I don't, I'll extend a huge thanks to anybody who actually dedicates time to this and I'll take the fix when it comes. Seriously, I just wanted to know if it was possible to have that older archive. It's not, that's cool. I'll just have to chill until the solution comes in it's own due time (since the words "compile your own build from source" don't mean anything to someone with my level of experience).

[AlexP]

I am just guessing, but I reckon 30 days was chosen as a reasonable compromise between having old builds available, but not wasting loads of space etc. keeping really old ones.

Why don't you give compiling a try?  I promise it isn't too hard    On windows, the VMWare platform is a reasonable method of doing it, see here:

http://www.rockbox.org/twiki/bin/view/Main/VMwareDevelopmentPlatform

[Taslow]

Huh....yeah.....that seems like it's worth giving it a shot in the meantime while I wait.

Good call.

[Taslow]

A really nice fellow Rockboxer emailed me a build for the e200 series from Sansa that has perfectly functioning bookmarks. Anybody with a similar problem can drop me a line and I'll send it along, since the appropriate builds are too old to be archived here now.   onmywayup@gmail.com  

[pondlife]

The current build should now have fixed this-  can anyone confirm?

pondlife