obviously remove played and skipped tracks don't work with autoplaylists.
What is the difference between remove played and skipped tracks with the checkbox, and the same option that can be set for a playlist?
One small question/request - would it be possible to (option?) change playback order on playlist change rather than on playback?
That doesn't make any sense to me. The playback order is related to the current playing playlist. Why should it be changed, when you switch to another playlist?
you switch to a playlist and you can imediatelly see the playback order for the selected playlist
On starting a playback session, the attributes, which are specific to a playlist, are set. They will be reset on stopping a playback session. ... Changing the attributes for the playing playlist will take affect on the following playback session.
2) I use a naming convention for my playlists eg. "s_blahblah". The s_ denotes a singles ie. non-album related playlist. Could you please implement a wildcard naming convention (a la SQL) to allow one playlist settings to be applied to any playlist matching the criteria.
1) Implement a context menu for each playlist so that only it's attributes could be changed/viewed from the menu system rather than via settings
So when exactly begins / stops a "playback session"? With the choosing of an playlist (and playing an arbitrary track in it)?
What do you think about an option to send the removed tracks to a special playlist to delete the files later from this playlist? This would be very usefully for me for my podcasts.
Very nice component, thanks for this.Only one very minor issue. For some reason foo_whatsnew keeps showing the "new" features of this plugin every time i start foobar (instead of only showing them once).
I can't reproduce it here, although I'm alway using foo_whatsnew, even in my test environment. But I recognized a similar issue, not related to foo_playlist_playback_attribute, when I used foo_menu_addons. Are you using this component?
My request: Adding integration of "stop after current" behavior for individual playlists.
1. Could you use the new case sentence style for the name of the commands?
2. Wouldn't main menu -> edit be the better place for assigning playback attributes as this submenu is related to current/active playlist?
Another thing I thought of; would it be possible to make defaults? Say, any playlist not specified should follow these attributes?
Quote from: odyssey on 06 August, 2009, 06:03:27 AMAnother thing I thought of; would it be possible to make defaults? Say, any playlist not specified should follow these attributes?It's already there. If you choose the global value for an attribute, it uses the fb2k standard settings.
QuoteQuote from: odyssey on 06 August, 2009, 06:03:27 AMAnother thing I thought of; would it be possible to make defaults? Say, any playlist not specified should follow these attributes?It's already there. If you choose the global value for an attribute, it uses the fb2k standard settings.Who said fb2k's standard settings are my preffered settings? I suppose the default fb2k setting is "Default" i.e. non-shuffled?
Quote from: Fractal_Mortality on 06 August, 2009, 03:46:27 AMMy request: Adding integration of "stop after current" behavior for individual playlists.It ist not very useful IMHO. It will only produce playlists which will stop after each track. What can be done with this?