@Another User said:
...tell me: what sense would be in getting samples from a harddisk, read them into a buffer on (another) harddisk and make an application believe they will be immediately available - none (ok, using a solid state disk this would probably work). means: i can't beleive logic allows the OS to store streaming buffers on a harddisk ... ahh - you're talking maybe about audio-tracks?
no I am not talking about audio-tracks. I am talking about Audio Instruments, nameley EXS24mkII with VSL samples loaded. let me explain in detail:
The sense is that without having to rewrite their application, LOGIC could take advantage of any faster methods of data I/O that the OS would allow. You have to think with an open mind. Do not presume to think that RAM might be the fastest I/O method around. Soon we may see some new technology on a PCI card that stores data in crystals using laser data retrieval. Who knows? But, with the right drivers and the right OS update, OSX will do what it needs to give any program that needs HIGH PRIORITY I/O, the data from that location.
The point is, the computer is supposed to be the monster machine not the application. The application is supposed to provide functionality. And the OS in Apple's case is what makes it all happen. The OS manages prioiritized tasks as best as it can. If the OS ever gave control of it's host machine's RAM to an applicataion you would surely have machine crashes. But since OSX traps every application to their own space in virtual-land, it doesn't harm the system in any way because all I/O from the application goes through the OS. This is what gives us our new smile [:D] when an applicaiton crashes, and we don'thave to restart our computer and debug conflicting extensions and all that old school stuff. You just re-launch the app.
So, to answer your question, it makes all the sense that making OSX in the first place makes to have the data requested by LOGIC that it expects to be in RAM to be treated with the highest priority by the OS. Although the OS puts some of what's supposed to be in RAM onto the HD, with modern computers it is becoming to be irrelavant. But instead of having Emagic make Logic aware of how every different system reacts to different RAM installations etc., the OS just does it all. So as new computers come out and new technologies come out, all your old apps work without rewrites. Because if Apple comes up with some new more efficient way of passing fast data I/O of Applications, then Apple will supply the update, and ALL of teh applications running on that computer will benefit.
hoenstly, it's the way it should be. The technology should be harnassed by the OS first. It's not the application's place to assume that a certian computer or configuration is best for itself. if that were the case you'd see applications written only for specific computers/configurations.
OSX really is a beauty. I cannot even fathom all of it's beauty. Very few can. You'd have to know all that's going on under-the-hood to really appreciate it.
Now, to continue to answer your question about the effectiveness of such management, I think Emagic put a limit on how many samples you can have open to sort of optimize the live playback of their EXS sampler. Imagine if Logic had no limit on the number of samples that could be open. You could load 200,000 samples and OSX would put maybe 1.5GB in RAM and 15GB on disk buffer. When you playback, each stream would start with 10% in quick RAm playback and 90% coming from disk. This would result in anyof the following:
1) stuttered playback intially
2) Logic reporting disk too slow
3) overload alert
I think since Emagic knows how OSX works, they didn't wnat that happening. Which is why (in my other posts) they imposed a maximum of 8,192 files open at one time. And maybe that's based on installed RAM. They query that on opening logic (ever see the message "setting up memory buffers????) and than give you a scale(proportion) that would keep the disk stream buffers mostly in RAM to the point where live playback wouldn't suffer. The limit that Emagic imposes (if they do, it is still my presumption), would automatically ensure that most strams are coming from the RAM.
So ,if that's true, than Emagic did there own sort of "forcing" the system to use RAM, but ina creative way. unfortunately their creative way was to limit how many samples you can have loaded, even though OSX would let you load (based on my calculations with 2GB Ram), about 5-times as many, or around 50,000 samples. That's the practical limit under OSX right now. With Panther it will become UNLIMITED. Only dependant on how much you want to bog down your computer. (now do you know why companies use these boxes as servers? because they won't crash when there's lot's of users. Just go slow. And Panther will destroy the competition in this area)
You might be able to load 50,000 samples on current G4 systems, and the CPU might be able to handle playback, but the disk retrieval may be too slow to make it happen live without stuttering or completely stopping. So you mixdown the whole thing, or solo tracks, or deal with some occasional stuttering.
I much prefer a working unlimited system that works better when I use it the better way, than a system which LIMITS me. Say "NO" to limitations!
Evan Evans
