It may be fat, but it's fast. Browsing seems more fluid, even with my
meager 124 album directory. 6.3 used to freeze a lot (but continue
playing) and not allow me skip track with remote until the end of the
song. That never happens anymore, even when sending .wav to the
player.
The new volume con
* Skunk shaped the electrons to say...
It may be fat, but it's fast. Browsing seems more fluid, even with my
meager 124 album directory. 6.3 used to freeze a lot (but continue
playing) and not allow me skip track with remote until the end of the
song. That never happens anymore, even when sendin
I'm running 6.5b on a KuroBox with 128MB RAM and a 266Mhz processor. I
had some problems, but only when running Random Play while transcoding,
and then fixed them by enabling the option to fork the audio stream
process.
I don't think it's taking much more RAM (I was using 6.3 with MySQL as
well)
oreillymj;134257 Wrote:
> The browser UI is nicer although I don't like the playlist commands
> scrolling with the playlist.
I agree. It would make sense to have the playlist commands in the
frame above.
But hasn't it always been like this?
> Also making the same config changes to multiple pla
BTW - I wasn't trying to be rude or negative, just some first
impressions.
Browsing on the SB iteslf is definitely smoother and faster, my only
gripe is memory use. Slim.exe is now sitting at 81,988K in task
manager. MySqlD.exe is using 17,192k.
That's with a library of 8320 songs.
I just though
Quoting JJZolx <[EMAIL PROTECTED]>:
oreillymj;134257 Wrote:
The browser UI is nicer although I don't like the playlist commands
scrolling with the playlist.
I agree. It would make sense to have the playlist commands in the
frame above.
But hasn't it always been like this?
nope.
http://bug