Support and General Use > Audio Playback, Database and Playlists

multi-boot (redirect) and playlist catalogue on devices with no internal storage

(1/2) > >>

7o9:
After recent commits that enable multi-boot (redirect) on x1000 players, I have compiled bootloaders for my Fiio m3k and Shanling Q1 and redirecting works.

My goal is to use the multi-boot/redirect functionality to be able to use 1 sd card in all my (supported) players and this works.

Both of these devices have no internal storage.

What happens though, is that when using the redirect functionality, the sd card gets named '<microSD0>' in Rockbox (i.e. the 'File' browser) and all content of the sd card is now relative to that '<microSD0>'.
Without the redirecting, my 'Playlists' directory is on the same level as the .rockbox directory.
With redirecting, Rockbox expects this in '<microSD0>/Playlists' which does not exist and gets created the first time you select 'Playlist Catalogue'.

When you move the sd card to a different device that also use redirection, you cannot see the 'Playlists' previously create as it is outside of what has now become '<microSD0>'.

Of course the contents of the playlists do not work anymore either because each path needs to have that '<microSD0>' prefix now.

Ideally, I think, on devices with no internal storage this '<microSD0>' would not be visible and the 'root' of the device would again be the actual root of the sd card. This would make it possible to share the playlists again between devices and also allow playlist management tools to make playlists without having to insert that '<microSD0>' prefix.

Possibly a similar argument would apply to the Rockbox database. Currently this is inside the .rockbox directory so for each device you would have to maintain the database individually.

Maybe an example helps to illustrate this:


--- Code: ---SD card layout:

/rockbox_main.fiio_m3k (points to /.m3k)
/rockbox_main.shanling_q1 (points to /.q1)
/Playlists (my non-redirected playlist catalogue with paths without <microSD0>)
/.m3k
/.m3k/.rockbox
/.m3k/Playlists (created when first selecting 'Playlist Catalogue' on m3k, not accessible when using the Q1)
/.q1
/.q1/.rockbox
/.q1/Playlists (created when first selecting 'Playlist Catalogue' on Q1, not accessible when using the m3k)
/Music

On-device 'Files' (with redirect):

/<microSD0>
/<microSD0>/Playlists
/<microSD0>/Music
/Playlists (either /.m3k/Playlists or /.q1/Playlists)

On-device 'Files' (without redirect):

/Playlists
/Music
--- End code ---

Bilgus:
just an observation, hiding the root is a bad idea unless you are actually in the root otherwise you lose access to the 'real' root

better would probably be to go to the volume paths <0> <1> etc without the drive label


As far as I know the items you reference are endian corrected but its still something that needs consideration if/when you start sharing things unique to the device

7o9:
I do not think I understand your first concern. What advantage does it have to show <microSD0> on a device with just one storage device?

My main concern right now is the playlist catalogue, which cannot be shared as it is in the redirected part.

I do not use the database myself right now, so that was only an observation.

PS: I edited my original post as my example was wrong. When using the redirect, all contents of the root of the sd card is under <microSD0> of course. Only the new 'Playlists' created by entering 'Playlist catalogue' is not.

Bilgus:
I don't think it will matter with a single storage using the root -- until you redirect the root then you've effectively blocked yourself from the rest of the card

Bilgus:
as far as the playlist catalog you could in theory redirect that as well but I don't think its important enough to the majority to mainline it

Navigation

[0] Message Index

[#] Next page

Go to full version