[Nano] Instead entering database, going to files list after turn on

[JaQs]

Hello.

I have problem with my Nano.

This is possible in Nano, when I turn on this (and I have selected "Resume Playback" on start screen) and press "select" button, entering to database, but concretely to Artist tracks (when I selected "All Files" or once of his/her albums in database) which I listened before turn off, but don't move me to folder which include while playing track?

It's like Sansa Clip, when We pressed down button and selected "back to music list".

P.S. Sorry for my English.

[AlexP]

I had a little trouble understanding your post.

Do you mean that once you have resumed playback after a restart, if you press select you would like to be taken back to the database query that produced the current playlist, but instead you get taken to the filetree?

As far as I know, follow playlist will not take you back to the database.

[JaQs]

Do you mean that once you have resumed playback after a restart, if you press select you would like to be taken back to the database query that produced the current playlist, but instead you get taken to the filetree?

Yes, that's it.

Is it possible?

[AlexP]

Not that I'm aware of at the moment unfortunately.  However, I may be wrong so we will see if someone else chips in.  I don't use the database myself.

[Chronon]

No, it doesn't appear that this information is saved through a reboot.  If you press select prior to a reboot you are taken back to the database listing that you chose.  After a reboot the playlist is resumed, but pressing select now seems to use the file browser to display the directory containing the currently playing track.  (I have "Follow Playlist" turned on.) 

I don't use the database very much either, so I had not noticed that change in behavior until JaQs pointed it out just now.

[Llorean]

It's not a change in behaviour.

Playlists don't store database queries. "Follow Playlist" should take you back to the file browser, because it's really impossible to know how the song was added to the playlist, and the playlist entry is just a file path. If "Follow Playlist" is off, you end up back at the database screen because that's simply the previous screen.

[Chronon]

Prior to a shutdown I end up back in the database if I press Select.  I don't end up in the file browser pointing to the location of the current file.  After a shutdown the follow playlist setting appears to do its thing.  I am set to follow the playlist in both cases.

[Llorean]

If you insert more files into the playlist from other queries, does it actually follow all of them properly?

[Chronon]

I would expect it to also follow the playlist in this situation. 

After a short test I find that if I press Select from the WPS it goes to the most recent database screen.  I can navigate around within the database or settings and if I return to the WPS then pressing Select will return me to the most recent database screen.  If I navigate to any location with the file browser and return to the WPS, then Select will follow the playlist to the directory containing the currently playing item.

[Llorean]

This is more or less what I expected. Basically, it's not really feasible to follow  the playlist within the database (for example, a song may not even meet the same query conditions after you've played it since it may have come from the never-played category) and a song can show up in dozens of places in the database so you can't just attempt to match.

[Chronon]

Right.  But should the "Follow Playlist" setting override attempts to follow the database?  It would seem more consistent to always enter the file browser if this setting is enabled.  The change of behavior I mentioned before referred to always following the playlist after a reboot but not before.

If I turn off "Follow Playlist" Select will still always return me to the file browser after a reboot -- though, in this case it's always to the root directory.  Prior to reboot it always returns me to the previous screen of either the database or file browser (whichever I left).

[Llorean]

Yeah, I *definitely* think it should always go to the file browser if the setting's enabled. I think it's more or less a case of "nobody's set it up to do this yet" for that.