Bug 1882 - Shoutcast plugin does not use INPUT.list for navigation.
: Shoutcast plugin does not use INPUT.list for navigation.
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming To SlimServer
: unspecified
: All All
: P5 enhancement (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-27 14:02 UTC by Michel Marti
Modified: 2008-09-15 14:36 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Marti 2005-07-27 14:02:31 UTC
It would be cool if navigating internet radio playlists on the SB would work
like in local playlists, e.g. pressing button 3 on the IR two times would jump
to the first entry starting with letter 'e'...
Comment 1 Michael Herger 2005-07-27 14:13:45 UTC
Are you mainly talking about shoutcast streams? What other radio stations?

And does anybody know why this got assigned to me?
Comment 2 Blackketter Dean 2005-07-27 14:18:03 UTC
Michael: Sorry about that, not sure why...
Comment 3 Michel Marti 2005-07-27 14:24:08 UTC
I'm talking mainly about shoutcast streams since  shoutcast has tons of entries.
I did assign this directly to Michael since I thought that he maintains the
shoutcast functionality (at least the web-interface)?!?...
Comment 4 KDF 2005-07-27 14:38:43 UTC
I have seen other users request that very large lists use the scheme from
shoutcast plugin, where entering numbers goes directly to the number entered. 
altering this in shoutcast, could be yet another 'I want the old way back" battles.
Comment 5 Blackketter Dean 2005-07-27 15:04:00 UTC
If they are sorted (and they appear to be) then we should be using the standard jump mechanism for 
letters (push 5 twice to jump to the first item starting with K).  The number entry thing here is not really 
consistent with our UI standard.

We can look at changing the standard to allow direct entry, but that's a separate issue.
Comment 6 KDF 2005-07-27 16:36:17 UTC
agreed.  just making sure everyone is prepared to duck :)

having shoutcast converted to use INPUT.List would take care of the numberscroll
issue, and possibly thin down the code a bit.
Comment 7 Michel Marti 2005-07-28 11:49:17 UTC
Whats the point of entering the number of an entry? How would a user know which
number corresponds to a certain entry anyhow? And since the list is not constant
(streams come and go), you can never be sure that entering number X brings you
to the same entry...
Comment 8 Michael Herger 2005-07-29 07:46:04 UTC
I thought of INPUT.List too... BUT there are those "recently played" and 
"favorite streams" at the top I would not want to find in the middle of nowhere. 
You therefore can't just sort the list. We would have to mark them with some 
prefix. Or use the externRef?

I would have looked at this, but as I'm going to leave for a two weeks vacation
... ;-)
Comment 9 Blackketter Dean 2005-07-29 08:09:12 UTC
I'd suggest that if you want those playlists separated out from the large sorted list, they should be at 
the level above, rather than mixed in.  That way we can have a sorted list and use the standard sorting 
navigation.
Comment 10 Michael Herger 2005-07-29 08:18:25 UTC
Do you mean something like:

Recently played
Favorite
Genres
   Alternative
   Bebop
   Rock
   Zulu

?
Comment 11 Blackketter Dean 2005-07-29 08:34:55 UTC
Exactly.  72 items in the top level menu is too many.

Comment 12 Michael Herger 2005-07-29 08:45:04 UTC
Ok, as this isn't a high priority change I'll do some more digging when I'm back 
in about two weeks. But feel free if you're in a hurry :-)
Comment 13 Michael Herger 2005-07-29 13:36:15 UTC
Bad news: the genre sort order is user definable. It's not always alphabetically - though this is the 
default and will in most cases never be changed. Even worse: default for the "most popular" 
streams is the number of listeners. But in that case it seems ok to me, as I wouldn't be looking for a 
specific stream, but rather browse through that list to satisfy my curiosity about what people listen 
to.

I'd agree that there are - once again - too many options. I'd like to know how many users are using a 
custom genre file... I never found a single user who could give me his file to do the testing.

Removing user defined sort order and custom genre definitions would imho greatly simplify the 
plugin. 
Comment 14 Michael Herger 2005-08-15 14:04:55 UTC
Dean, shall I have a try with these shoutcast browser changes, though they might 
limit some existing options (eg. sort order)?
Comment 15 Blackketter Dean 2005-08-15 14:10:58 UTC
Yes, please take a try at it.   (I'm fine with resorting the genres and presenting the user with a sorted 
list.)
Comment 16 Michael Herger 2005-08-15 21:20:38 UTC
I don't understand what you mean about the resorting. Shall we limit it to the 
default (by name)? 

I'd really like to keep the "most popular" by listener. But this would be the 
exception.
Comment 17 Michael Herger 2005-08-17 15:36:38 UTC
I checked in change 3992 which should already contain the new player interface.

What about the web? I'd leave it as is, with the full list in the top level. 
Browsing a web page isn't as awkward as on the player. What do you mean, Dean?
Comment 18 Michael Herger 2005-08-20 08:46:25 UTC
Checked in change 4009.