PDA

View Full Version : New plugins/screensaver: MusicInfoSCR.pm & NoSetup.pm



Ralph Edington
2005-02-01, 15:57
Michael,

I still have a small behavioral issue with your fine plug-in. "jump back"
or more specifically "don't jump back" still isn't working the way I'm
hoping...

Example of unexpected behavior when MusicInfoSCR is turned on:

1. Start a playlist (.m3u) playing.
2. Wait three songs.
3. Press the "+" key to remove the current song from the playlist.
4. Note the song that gets removed is not the current song, it's the first
song that played.

Apparently, the "+" action gets invoked as of the "now playing" information
that was LAST displayed, i.e. the first song that started playing in the
playlist gets deleted, not the current song.

At least that's how it certainly seems to be working for me at the moment, I
just tested it.

This can be a little confusing, as if I want to "+" (remove) songs from a
playlist, I have to remember to press "now playing" first, otherwise the
action is unpredictable.

Cheers, thanks, keep up the good work!

RE



> -----Original Message-----
> From: discuss-bounces (AT) lists (DOT) slimdevices.com
> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com]On Behalf Of Michael
> Herger
> Sent: Tuesday, February 01, 2005 1:46 PM
> To: Slim Devices Discussion
> Subject: [slim] New plugins/screensaver: MusicInfoSCR.pm &
> NoSetup.pm
>
>
> [..]
> > So - with time in bottom right the bottom left scrolls even though it
> > doesnt need to and the time itself doesnt show up.
> > i'm now on the settings i thought i was on to start with (nothing
> > bottom right) and it's fine so dont worry about it. still odd
> > behaiviour
>
> The PLAYTIME setting is somewhat confusing as it uses the state of your
> normal "Now playing" button: you can cycle through played time,
> remaining
> time, played with progress bar, remaining with progress bar and nothing.
> If you had it set to nothing it will show exactly this - nothing. Press
> the "Now playing" button and you will see the time.
>
> BTW: I just uploaded v1.3 of the plugin which will limit the PLAYTIME's
> progressbar (which you don't use...) to half the line length and fixes
> some bugs.
>
> --
>
> Michael
>
> -----------------------------------------------------------
> Help translate SlimServer by using the
> SlimString Translation Helper (http://www.herger.net/slim/)
>

kdf
2005-02-01, 16:27
Quoting Ralph Edington <ralph (AT) edington (DOT) com>:

>
>
> Michael,
>
> I still have a small behavioral issue with your fine plug-in. "jump back"
> or more specifically "don't jump back" still isn't working the way I'm
> hoping...
>
> Example of unexpected behavior when MusicInfoSCR is turned on:
>
> 1. Start a playlist (.m3u) playing.
> 2. Wait three songs.
> 3. Press the "+" key to remove the current song from the playlist.
> 4. Note the song that gets removed is not the current song, it's the first
> song that played.
>
> Apparently, the "+" action gets invoked as of the "now playing" information
> that was LAST displayed, i.e. the first song that started playing in the
> playlist gets deleted, not the current song.
>
> At least that's how it certainly seems to be working for me at the moment, I
> just tested it.
>
> This can be a little confusing, as if I want to "+" (remove) songs from a
> playlist, I have to remember to press "now playing" first, otherwise the
> action is unpredictable.

This isn't so much a bug with the Plugin, as a case of using a screensaver is
something it was not intended to be. A screensaver is there for the case when
player input is largely idle. When a button is pressed, the screensaver modes
passback the function to the previous mode, which having been away was never
updated to the latest song. The server does not define a screensaver in the
same way as a normal button mode. There might be a way to trick it by having
the plugin update the 'browseplaylistindex' parameter. However, I'm not sure
there is a way to pass a param through a 'jump back'. You might also try
implementing the ADD function in the screensaver and bypass the 'jump back'.
That would have to be an experiment.

-kdf