> What if we split the difference here? We could have the bitrate field stay > as a number, but what if the directory server was smart enough to group > bitrates under "Modem", "DSL", etc. headings? This way you'd keep the > bitrate field showing, but still be able to search for the streams > appropriate for your connection speed.Remember that I've described low level storage values that will be in the database, not how these values will be presented to users. Certainly grouping bitrates as you say is the better way to present the info to users. I'm also going to try to have a 'speed tester' available so that people who have no idea what they are doing can at least have an easy way to figure out what they can handle. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Oddsock wrote:> how about instead of bitrate, something more generic like "Quality". > This should be a number, which (in the case of application/ogg) might be > 64 (as in kbps) or (in the case of audio/mpeg) might be 30 (as in FPS). > I would say, for most media types, it would be a bitrate, but not all.I think the bitrate is important, since the user is usually concerned about the network load his listening will cause. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Sep 17, 2001 at 06:04:00PM +0300, Akos Maroy wrote:> >how about instead of bitrate, something more generic like "Quality". > >This should be a number, which (in the case of application/ogg) might be > >64 (as in kbps) or (in the case of audio/mpeg) might be 30 (as in FPS). > >I would say, for most media types, it would be a bitrate, but not all. > > > I think the bitrate is important, since the user is usually concerned > about the network load his listening will cause.What if we split the difference here? We could have the bitrate field stay as a number, but what if the directory server was smart enough to group bitrates under "Modem", "DSL", etc. headings? This way you'd keep the bitrate field showing, but still be able to search for the streams appropriate for your connection speed. - -- "Nothing's the same anymore." - Cmdr. Jeffrey Sinclair, Babylon-5, "Chrysalis" -----BEGIN PGP SIGNATURE----- Comment: For info see http://www.gnupg.org iD8DBQE7phIhAmwSMwnpLHgRAlg9AKCxemTvtyGjbvJVI2boIzkwdcKCUQCgsfAx QdmAQDa/NUEmEse+kxYudk8=ovMa -----END PGP SIGNATURE----- --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.