|
From: Mark K. <mar...@co...> - 2003-10-28 18:00:19
|
On Tue, 2003-10-28 at 09:31, be...@ga... wrote: > excellent ! > the mlock and sched_setscheduler warnings are becaue a regular user > cannot call these functions. > It might occur you get mlock errors as root too, but this means > that the preloaded RAM size (preloadsize * number of samples in a GIG file) > exceeds the available physical memory. > See my response to Robert. > Sorry that I haven't gone back through the archives yet, but educate me. Is this revision streaming from disk? I understand the architecture where the first portion of the loaded gig files are in memory and then GSt has to do a seek and start getting the rest of all notes being played. Is this what you are doing in this revision? And what's the current legal state of the 'stream from disk' patent? Has anyone determined if this is a problem for this tool? I typically load 16 libraries in GSt as a starting point. (Good Sounds.gsp) They encompass about 6GB of disk space - obviously too much for memory... (And I do understand that you are only handling a single gig file and not a performance file at this time.) Thanks, Mark |