Rockbox Technical Forums
Support and General Use => Audio Playback, Database and Playlists => Topic started by: adamf663 on November 23, 2007, 11:46:20 AM
-
I just switched to using rockbox on an apple ipod gen 5.5. Previously I ran it on cowan iaudio x5.
I'm having some strange behavior when resuming from a bookmark (from the 'recent bookmarks list'). I don't use the database/id3 feature; I always use the file view to select.
What happens when I resume a bookmark is that it displays the playback screen with the correct track location for a brief instant, and then jumps to a file view of the root directory. If I hit play, it plays the correct track, but at the beginning.
If I hold down the play/pause button to make rockbox stop playback and then select a bookmark, it works correctly.
-
I can confirm that behaviour for the gigabeat (I have gotten so used to it I automatically press stop now). Thanks for bringing it up. I'll to file a bugreport on flyspray for it.
EDIT:
Okay, there it is: http://www.rockbox.org/tracker/task/8215
-
I've seen this (or at least similar) on my iPod 5g. I can't recreate it with any consistency at all but it happens frequently enough to be annoying when it does happen. I haven't reported it because of the lack of reproducibility, and it always seems to happen when I'm out and by the time I come back to a computer it's out of my mind.
I use the "Recent Bookmarks" menu item in which I have the most recent bookmark for each of my 5 playlists (2 of them, the most frequenly used, dynamic. I'm not sure if it only happens on dynamic, or only happens on static, or happens on both. I'll pay more attention the next time it happens).
-
I have a similar problem on the Sandisk Sansa e250r. It records the bookmark(only when accessing the track from the file menu, not the database), but when I try and go back to it, it starts at the beginning of the track, but the timeline shows the "recorded" time of the bookmark. I can't get it to resume the bookmark at the right place in the track.
-
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).
-
I have the same problem on my iAudio M5
But it doesn't work correctly neither if it played at the moment nor if I pushed Pause befor. It begins to play from the beginning of the bookmarked track in both cases
The problem began since Rockbox version r15311-071026.
Version r15294-071025 worked propperly on my iAudio M5
I can't see the changelog for r15311-071026 so I don't know which changes made the mentioned problem
Does anybody know how to solve the problem?
-
There are a couple of other threads with some of us experiencing the same problem on our e250/280's and other models. I originally thought it was isolated just to post-power-cycle because my bookmarks seemed to work as long as I hadn't restarted my player in the meantime; but it seems like there are multiple situations and different models where bookmarks aren't functioning correctly on any builds in the last week (or more?). I can't remember exactly when mine stopped working but I'll start loading some old builds until it begins functioning again and post on it.
-
Just started using Rockbox on my iaudio X5. Â I am experiencing basically the same problem. I can save a bookmark and it shows up in the bookmark list. However, when I play the bookmark it starts at the beginning of the file, not at the correct location. Most of my listening is to lectures and audiobooks, so bookmarks are critical to me. Â Has there been any progress on this? Â Is there a recommended build that I can go back to? Â I am running version r16354-080219.
-
rockbox is f*cked up when it comes to bookmarking. I had a multi-page thread (http://forums.rockbox.org/index.php?topic=14995.0) going about bookmarking issues in the Sansa c200, which resulted in nothing, except a band-aid. I wouldn't get your hopes up about a fix coming soon, as the developers feel it is a "rare" and "subtle" issue that doesn't effect too many users. I tried using hacky ways to mimic bookmarking (ie, looking at the timestamp and manually fast-forwarding), but I ended up ditching rockbox and using the original firmware, as there was no point, for me, to use rockbox without bookmarking.
What drives me nuts is that they were able to get plugins and an image viewer and skins and games working, but not something as basic as bookmarking. I heard that's a big problem with open source software, the developers want to work on the cool and flashy features, but not the "boring" and useful features.
Open source software is like communism, good idea, in theory...
-
And yet here your are complaining while other people are working on fixing the problem. You pay them NOTHING yet feel justified in complaining when their contibutions aren't fast enough, while you yourself contribute nothing at all. Do I detect a false sense of entitlement here?
-
And yet here your are complaining while other people are working on fixing the problem. You pay them NOTHING yet feel justified in complaining when their contibutions aren't  fast enough, while you yourself contribute nothing at all. Do I detect a false sense of entitlement here?
Many of us do appreciate the hard work of the developers and I agree that the comments of krisdb are uncalled for.
-
Just started using Rockbox on my iaudio X5.... Â Is there a recommended build that I can go back to?
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
-
I just thought I should mention that I did fix one problem krisdb found (and I could reproduce), that when you tried to resume a (folder) bookmark for a file that no longer existed, nothing would happen. This was particularly bad if load last bookmark was set to yes, in which case no file in that folder could be played directly. The fix is to play the selected file in that case (i.e., act as if there was no bookmark when the bookmarked file can't be found).
I don't know what the remaining problems could be caused by, as bookmarking works well on my e200, playing MP3 and Vorbis files.
-
I just thought I should mention that I did fix one problem krisdb found
That's BS. He fixed a problem, not the problem I was having. 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. I just gave up. Explaining it to my wall was more productive.
I wasn't going to respond to my homeboy Llorean, but the more I thought about it, the more aggravated I got. I'm so sick of open-source developers using the "its free" card as an excuse for a crappy products. You know what? If you can't build a stable product, don't build it at all (or don't release it). All you do is drive people away from open-source, and make them feel guilty if they speak up. At this point, I wish I had never heard of Rockbox, because I bought my Sansa specifically to use it. On top of that, for some reason, I was supposed to know that the Sansa version was less than a year old and not stable. How the f*ck am I supposed to know that? I go to this page: http://www.rockbox.org/twiki/bin/view/Main/WhyRockbox, look at all the features and assume they must be working. Where does it say on that page these features may or may not work?
And its not like I'm complaining about some fringe feature, like why I can't get Doom to run on my c200 (good use of time on that one, btw). Its something as basic as bookmarking, which isn't as "cool" as plugins and image viewers. WTF, who wants an image viewer on the c200?
This is why I avoid open-source software altogether. Its just a pattern of this, unstable products that don't work as stated, then you speak up and they throw back the "its free"/"you don't contribute" card. Not that it matters, I don't even use Rockbox anymore and steer people I know who were thinking about using it. I tell him its buggy and if you ask for support you'll get condescending responses (Llorean) or no help at all.
-
I was about to start writing a huge rant about this, but decided to condense it down to this:
No one is twisting your arm to use Rockbox. If you don't like it, fine. Get rid of it and don't come back. THAT is the beauty of free and open source software: If you don't like it, then you don't have to use it. Pick an alternative. And we'll gladly give you a refund for the money you paid. ;)
We'll discuss this further when you get frustrated with the abusive power of DRM, vendor lock-in, buggy proprietary software, and basically no choices in life.
-
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?
-
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.
-
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).
-
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.
-
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
-
You can compile them from SVN, but we only archive actual builds for 30 days.
-
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.
-
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. :-)
-
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.
-
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).
-
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).
-
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 :P On windows, the VMWare platform is a reasonable method of doing it, see here:
http://www.rockbox.org/twiki/bin/view/Main/VMwareDevelopmentPlatform
-
Huh....yeah.....that seems like it's worth giving it a shot in the meantime while I wait.
Good call.
-
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
-
The current build should now have fixed this- can anyone confirm?
pondlife
-
Just installed r16415 (for the Sansa e200), and bookmarks are working fine for me now. :)
Tested both regular memory and sdcard, power off and back on again. Resumed from the correct location every time so far.
Rockbox rocks, as do the many people working to make it work. Thanks all!
-Sol
-
I agree completely.
The new version works very well. I knew this would eventually be fixed. The Rockbox team are incredibly talented and dedicated.
What some folks here absolutely fail to understand is that every build that comes out is essentially "beta" software.
The last official release of rockbox, was 2.5 and was for the ARCHOS only. So if you are running any other version, you are esentially running beta code.
And I must admit, that Rockbox "beta" is more stable than many other peoples "release code".
Rockbox is open source and relies on the volunteer work of dozens if not hundreds of people who do this for a hobby. That is why this board gets a little snippy when some little "snot" comes on and "demands" stuff be fixed, or asks step by step installation questions that are clearly stated in the manual, or asks the same question 600 times (like when is Rockbox going to be available for the 2nd Gen I-Pods????)
It's almost as if these goobers think that somehow because they own an MP3 player that the Rockbox team is somehow "obligated" to develop for them. Or, if they do own a "supported" player, they feel that the team is somehow obligated to "fix" any unsuspecting bugs immediately, or keep vast libraries of code available from the beginning of time.
Note to those users.....That's what your original firmware is for. You have an I-pod with issues? contact Apple. Don't like a feature on your Sansa? Let Sandisk know.
Rockbox has made my player much more versitile than the original firmware that came with the device. It's database handling and feature set outstrips the original feature set on my Sansa Rhapsody. Rockbox even supports SDHC, something the Sandisk swore up and down was not possible on that hardware.....
But even so, I would not for once ding Rockbox for what it "doesn't" do.
I have 15975 archived, so that I can roll back to it should this build have some unforseen issues. But once I am happy with this build, it too will go in my archive.
And a final thing.....Don't upgrade to the newest build, simply to change the number....If you see a feature set or bug fix you like, great, give it a try. But if you stick with a build you are happy with and only "upgrade" when you see a specific fix or feature set that directly affects you.
You'll be much more satisfied.
Thanks again to all for this great firmware/software. My hats off to you all.
-
or keep vast libraries of code available from the beginning of time.
Just as a note, we do in fact keep "vast libraries of code from the beginning of time". Every commit done to the rockbox code base since the project started (more or less) is available in svn. The thing we don't do (because disk space is a finite thing), is keep libraries of builds heading back into previous epochs. You get one month gratis. If you want a build from earlier, then you must show willing, and LEARN HOW TO BUILD IT YOURSELF.
-
Thank you for your kind words, but I must point out:
or asks the same question 600 times (like when is Rockbox going to be available for the 2nd Gen I-Pods????)
Rockbox works reasonably on the 2nd gen iPods. It doesn't however work on the 2nd/3rd gen Nanos, the Classic, and any shuffles :)
-
What I meant to say was 2nd Gen I-Pod Nanos
Unfortunately I am at work and can only get to this forum through a web proxy, and while the web proxy would let me post, it did not allow me to edit after I saw my blunder. So my Bad.
-
I know what you meant, I was just being facetious :)
-
Hi,
I have just downloaded rockbox for the first time last week and I seem to have been stung by this problem with the bookmarks on my 80gb ipod video. I have just downloaded todays version - 03/03/2007 and it still seems to be misbehaving.
As such, this is my first post ...
After reading this thread and trundling through the forums... I understand I cannot simply download the 25/01/2008 build that appeared to work. I also don't appear to be able to download the source code for this version either ... or I am looking in the wrong place?
Is there anything I can do?
Any help is much appreciated.
Thanks,
Neil.
-
What problem? More than one has been discussed in this thread.
As for getting old versions of the code, use SVN (aka subversion).
-
I cannot create a bookmark while playing a mp3 audio file, using the context menu. The auto create options do not seem to work either on my ipod.
After searching the forums I was pointed in the direction of this thread and I got the impression from previous posts that the bookmarks were working fine...
-
With firmware from the last week or so, I have been able to create and resume bookmarks on mp3 files ( but not wma files where the file resumes at the beginning but not stopping point) when playing from the "file" menu ( but not the "database" menu) on both the sansa e250 and c250. If you are using the database to play files, I don't think it is possible to create bookmarks.
-
Nice one. Thanks for the help.
It is the same on my ipod. I cannot create bookmarks when using the "database", but it would appear that I can when using the "files".
-
Nice one. Thanks for the help.
It is the same on my ipod. I cannot create bookmarks when using the "database", but it would appear that I can when using the "files".
Correct. This is the way Rockbox works. You cannot create bookmarks if playback is started from the Database.
-
Is there a specific reason for this?
-
bookmarks require a playlist (either stored as m3u(8) or as a recipe how to create it) to work on. The recipe is easy in the case of playing a directory (use all files and possible shuffle them) but very difficult in the case of the database. Nobody has done it and it might be better to use a different approach there. But again nobody has stepped forward and done it so until that time we are stuck with the current situation.
You can always save the current 'dynamic' playlist to a file and use a bookmark there.
-
Bookmarks are working now!
I take back everything I said.
Rockbox FTW!
Also: 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
-
Bookmarks are working now!
Maybe take a look at the bug report you opened in flyspray, test it again, and see if it can be closed? Â That would be a pretty classy move...
-
I can confirm bookmarks working in the iaudio X5 build from 3/4/08. Thanks for this fix! Now I can really begin to explore the Rockbox world.
-
Maybe take a look at the bug report you opened in flyspray, test it again, and see if it can be closed? That would be a pretty classy move...
I'm not a classy person :-*
-
I'm not a classy person :-*
Duh.