|
Title: RAM Buffer Post by: Jack on August 06, 2007, 11:06:37 pm Hi Peter
With this latest version I am waiting about 20 seconds between tracks over a 100mb/s network, however I configure it, whereas the previous version was maybe 3 or 4 secs. So presumably, whatever you changed to help out with slower connections has made me much "gappier". Even with a local drive, tracks that blend with each other on CD, there is a momentary gap. Much more irritating when playing loud, as I usually do. Hence my question or request, is it possible to have a user configurable RAM buffer that could be as large as say 1 gig & start to refill when down to 15/20 meg or so. This obviously would take care of gaps, just meaning a delay before play commences, which you get anyway if you load a large WAV. Memory is so cheap & I usually have a gig & a half sitting idle! Think of it as saving the planet, we could all turn off our servers or external hard disks an hour earlier at night as all would be in RAM on the playback PC! Just a thought Jack Title: Re: RAM Buffer Post by: PeterSt on August 07, 2007, 12:19:21 am LOL Jack ... Besides that it could be done (pre-load a whole, say, Playlist), I don't understand what is happening with you. First of all, 3 or 4 secs for a track over a 100Mbs network ... hardly believeable. That would be 4 x (roughly) 10MByte equalling 4 minutes playtime or so. But ok, if your tracks are all that short ... possible ... 20 seconds would be 20 minutes playtime. That too is unlikely, since 4 minute tracks would load in 4 seconds. Haha. All 'n all you currently have 9 seconds for loading a track; if that also doesn't work for a local drive (even PATA) ... what is going on ? And of course you say it has gone worse, and actually I didn't even change anything ! well, not that I know of. Not from 0.9g to 0.9h. What Engine are we talking about anyway ? Peter PS: Didn't your disks spun down in the mean time ? Title: Re: RAM Buffer Post by: PeterSt on August 07, 2007, 12:44:53 am And Jack, because your data seems inconsistent to me :) could you please check whether it's indeed the loading time that's holding things up ... You could look at the disk activity lamp at the server ... When you see that loading just starts too late (like 2 seconds before the end of a track instead of approx. 9), could you measure whether the running time of a track is correct ? ... like a track of 4:00 minutes taking 4:10 ... |