Bug 8220 – Allow for sorting of radio stations by bitrate

Bug 8220 - Allow for sorting of radio stations by bitrate

Summary:

Allow for sorting of radio stations by bitrate

Status:	CLOSED FIXED

Product:	MySqueezebox.com
Classification:	Unclassified
Component:	Internet Radio
Version:	unspecified
Platform:	All All

Importance:	P5 enhancement (vote)
Target Milestone:	Falco
Assigned To:	Andy Grundman

URL:
Keywords:

Depends on:	6859
Blocks:
	Show dependency tree / graph

Reported:	2008-05-23 09:32 UTC by Dan Evans
Modified:	2008-12-15 12:24 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Evans 2008-05-23 09:32:43 UTC

(from rn# 080523-000282)

Customer requests a method to sort radio stations on SN by bitrate.  Seems like a useful enhancement.

Comment 1 KDF 2008-05-23 10:16:34 UTC

depends on which source for stations.  Many are just served up by the provider.

Comment 2 Tom Hiller 2008-05-27 17:57:54 UTC

I tend to gravitate towards higher bit rate Shoutcast stations.  When connected to SN, SC displays Shoutcast station bit rates, so I thought a setting to sort on data rate might be useful, and perhaps, not difficult to implement given the bit rate is already present.

Comment 3 Andy Grundman 2008-08-08 11:07:29 UTC

Punting.

Comment 4 Andy Grundman 2008-09-23 16:06:40 UTC

*** Bug 9574 has been marked as a duplicate of this bug. ***

Comment 5 Andy Grundman 2008-09-29 12:39:24 UTC

Shoutcast has been rewritten and support for the new directory is available as of 7.3 change 23330.

Please test the new listing and features and let me know of any issues.

Comment 6 James Richardson 2008-12-05 10:39:25 UTC

As of (sv) r5231/r24205, Internet Radio stations now list the bit rate after the station identifier.  This is on the WEB UI.

Player UI does not list bit rate after station identifier

Comment 7 James Richardson 2008-12-15 12:24:12 UTC

This bug has been fixed in the latest release of SqueezeNetwork!

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.