On 7-Sep-05, at 1:30 AM, Philip Meyer wrote:
1.
I was playing music from a playlist. I listened to the whole of track
one, so track 2 was playing. From the Now Playing screen, I pressed
up-arrow to view track 1 and pressed and held down the Add button to
zap the track. This actually zapped the currently playing track,
rather than track 1.
Single-press Add removes the displayed track from current playlist, so
I assumed Zap would also apply to the currently displayed item, not
currently playing item. Is this intentional? Can I suggest this is
changed on a bug report?
you could, but the current behaviour has been discussed in another bug
report:
http://bugs.slimdevices.com/show_bug.cgi?id=512
resulting in the current behaviour, as a match to the way 'add' works
for deleting tracks from the current playlist.
2.
As a follow-on, when I went to slimserver web interface to restore the
incorrectly zapped files (I did it twice), I noticed that I had two
zapped tracks, but they were the same track - ie. duplicate entries in
the zapped playlist. I am pretty sure that when I zapped the two
tracks, they would have been tracks 2 & 3, as I was trying to zap
track 1.
If you feel like trying it again, let us know the steps for a
reproducable case.
3.
When I upgrade the server, is the zapped playlist retained or is it
wiped? What about when performing a complete rescan?
it is like any other playlist. it remains as long as you leave it
there. complete rescan would simply reload it into the db like any
other playlist. It is only a way to record info, and is not special in
any other way since that leaves the option to the user as to how to
make the best use of the feature for her/his needs.
4.
Does this mean that SlimServer doesn't store a playlist if it can't
find any playable entries?
I have no idea any more. a lot of noise about this one lately.
-kdf
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
