>> You could also do something like storing your music on a fileserver
>> and running some sort of streaming server. slimp3 is an example of
[quoted text clipped - 4 lines]
> My reservations with a remote server would be the issue of latency,
> as I know throughput would be fine.
The only issue I've seen with this is the latency inherent in the
fact that streaming clients (winamp, xmms) like to buffer streams, so
if you switch to a different song, there will still be a few seconds
of the old song (the buffered bit) before you hear the new one. If
that bothers you, it's easy enough to change the client configuration.
Er, that's assuming remote means "on the local home network, but not
on the client machine itself."
> But if I kept local copies of the music database on every computer,
> that should effectively eliminate that problem.
But, er, why? To me, that's the beauty of a fileserver -- keep data
in one place, use it everywhere. (And, of course, back it up.)
> I've also considered making my own streaming format based off of UDP
> packets (the idea was inspired by Roedy Green's SAX idea, although
> this would be admittedly a significant variation.) I simply love
> UDP packets and I have an inexplicable fascination with killing TCP
> everywhere.
Whatever makes you happy ... =P

Signature
monique
Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html
Luc The Perverse - 25 Apr 2006 03:11 GMT
>>> You could also do something like storing your music on a fileserver
>>> and running some sort of streaming server. slimp3 is an example of
[quoted text clipped - 10 lines]
> of the old song (the buffered bit) before you hear the new one. If
> that bothers you, it's easy enough to change the client configuration.
Ugh . . yes. Delays of longer than about 1/5 second REALLY bother me.
(MenuShowDelay?) Gotta keep it under a few dozen ms.
> Er, that's assuming remote means "on the local home network, but not
> on the client machine itself."
Of course
>> But if I kept local copies of the music database on every computer,
>> that should effectively eliminate that problem.
>
> But, er, why? To me, that's the beauty of a fileserver -- keep data
> in one place, use it everywhere. (And, of course, back it up.)
Latency is the enemy and is the entire point of the project. Latency must
die.
I used to have all my folders hot keyed, but now if I want to find a song
(let alone build a playlist)
I press the windows key + R
Type c:\media\my music\ (hopefully it auto fills)
Press F3
Wait for the dog to stop dancing (Forever? )
Press L or click
Then I wait for the folder list thing to stop updating (3/4 seconds?)
because if not it will lose focus
Then I type in something from the song title
(Don't even ask what you have to do if you type it wrong)
Then I wait 3-12 seconds
Then I double click the song and it starts playing
Then close the window
It's not even enjoyable - I just don't listen to music because of this.
Now this is what I want (of course I would need to be running JVM as a
service to eliminate delay in loading program)
Press Ctrl + Alt + F3
Type name of song
Press Enter
Search pops up instantaniously (<0.1 s)
First ten results correspond to Function keys
Default action for me is replace so I press F4 (for song 4 in list)
Song starts playing and window disappears automatically
So in the time it takes the dog to stop dancing I have started a song
playing and the window I was at before the ordeal is back up and has focus.
Of course I would have different ways to allow multiple song selections, to
enqueue instead of play etc. Higher learning curve, but much much faster.
If I could populate a search result in less than .1 seconds, then I would be
ok with a remote server. But my experiences with databases has been that
something, somewhere makes searches very very slow.
Now I am learning that I am alone in hating latency - as is evident by the
fact that people still use Adobe Reader which has a 3 hour and 25 minute
(estimated) splash screen before a document is displayed. (Long live FoxIt
PDF Viewer!)
--
LTP
:)