Limit Bookmarks to One Per Track

[bluebrother]

How many files do you realistically have that you need to keep parallel bookmarks in, but for some reason cannot put in different folders?

Why not create a playlist for each file and play the playlist instead of the file? That could be done with a few lines of shell script.

[reunted]

Again, it's "one bookmark per playlist"

That is only true if the Unique Only option is on, otherwise you can save 10 bookmarks per playlist to Recent Bookmarks.

Instead of starting from the Unique Only option which is restricted to one per playlist, you start with the many per playlist option and overwrite bookmarks as new ones are added on existing bookmarked tracks.  This allows you to have one bookmark per track and up to 10 bookmarks for all tracks in one folder.  I don't need the bookmarks to span across multiple folders.  There is no change required to Rockbox's playlisting method.

[Llorean]

Bookmarks are stored per playlist. New ones are added on existing bookmarked playlists not tracks. Storing them per track would be new either way, they're store per folder or playlist currently. So yes, a change would be required to Rockbox's playlisting method to recognize bookmarks on a per file basis.

Again, why not try telling us why your files can't be in separate folders (which is generally trivial to accomplish) and maybe we can give you other suggestions to solve your problem - what exactly is your use case?

[fml2]

I can very well understand the motivation and will probably implement it. Actually, I think we could/should have this option for "ordinary" (not recent) bookmarks too, i.e. that each track is present no more than once in a .bmark file.

But first I need to understand how the new "Update on Stop" setting works and what exactly it does...

[torne]

It creates a bookmark on stop if the bookmark file already exists. If it doesn't exist, the previous behaviour happens.

[fml2]

He-he, since both the playlist name and the file name are stored in bookmarks, the option "Unique per track" should be not that hard to implement!

[fml2]

A patch has been added to FlySpray: FS#11473 - New bookmarking option: one per track. Please try and comment.

[stan]

I think this is a great idea, but don't know how to work with a patch.  Can you put this feature into the build?

[fml2]

I created the patch and posted it here on the forum, on the maling list and on IRC. There wasn't much feedback, so that I think there are not many users interested in it. Since the patch adds some bytes to the binary and since I personally don't use bookmarks much, I will not commit the patch any time soon. I'd need more opinions to do (or not to do) this. But I still like the idea and wonder why this option didn't exist from the very beginning on.

[oayz]

fml2, thanks for your effort. I also believe this is nice feature. One reason you are not getting feedback is that there a quite a few people around who do not mess with patches and associated private builds (stan, me and I bet original poster).

If our bright developers could only figure out how to publish patches in compiled form ... Can we set up server based compile? Something like:
- pick the patch
- select target platform
- post your email address
- receive private built

[fml2]

One reason you are not getting feedback is that there a quite a few people around who do not mess with patches and associated private builds

For me, it's not a question of ready to use builds but rather a question of stated interest (or lack thereof). If many enough would say "Yes, i want this feature", I'd commit it. The feature (its implementation) adds code complexity and binary size, so I need something to justify the commit. Write here, ask and nag in IRC -- and you'll get it! :-)

[oayz]

OK, so far only 3 people are interested (reunted, stan, oayz)

[ajthorton]

1

[Confuseling]

...How many files do you realistically have that you need to keep parallel bookmarks in, but for some reason cannot put in different folders?
...

Call it a kind of 'overdetermination', being able to get to about the same result through multiple paths, suited to different use cases.

I only use my MP3 player, and Rockbox, for podcasts and audiobooks. The podcasts range between half an hour and an hour and a half, and are sometimes quite dense, so the possibility of bookmarking each episode individually, whilst still retaining the ability to keep them all in the same folder for ease of browsing, would be welcome.

I could use playlists, but one of the attractions of Rockbox for me is the fact that I can ignore such unnecessary complications for my mode of use as these and tags, and just use file browsing.

+1

[hukka]

+1

I bought my player primarily for listening to podcasts. The feature being talked about here would be better than nothing, although preferably I would like to see the same kind of bookmarking functionality in Rockbox as in the OF of my Sansa Clip+, where it will just automatically remember playback position for files in the Podcasts directory.