God. We don't know why. But it's true, that is a problem.

OFFLINE bounce works though.

Evan Evans

I consistently have this problem. It is so irritatiing that I now leave my computer running overnight (with my Logic and Finale files open) when I am working on a project so that I do not have to "prime" the samples again.

Does anybody at VSL have any theories about this?

Michael Matthews

I'm experiencing the same thing with 4GB RAM.

This is what happens in my tests mentioned in my thread about measuring RAM usage when using EXS.

My observation on the subject of swap files, active and free memory seemed to show that sample headers being loaded were passed to swap files when memory usage was above a certain level BUT that there was Free and Available memory still listed - the default is 1 swap file although you can "delete" this with certain utilities. How the system decides what to page out is I believe beyond our control but once you invoke play then gradually those sample headers get put back into RAM and presumably other data (part of Logic or system) get put out to swap files. You can then play without the dreaded Core Audio overload in those situations where you are "close to the limit" which with 1.5 GIG in my case was showing 485MB free. Does anyone know what is "ring fencing" that 485 MB as presumably not being available for sample headers ie preventing its immediate use?

I haven't double checked those numbers tonight but I think I am in the general area.

Note: if loading instruments manually as you build an instrument set, I think there does not appear to be as great an occurance of the overload situation compared to if you load a file with them already set up.

What I was looking for in that recent thread was statisics on swap file usage with 4 GIG of RAM. Simply does it go above 1 when loading instruments such as those I listed?



Stuart

I agree with that. In the days when I was using boxes (Proteus 2 etc) it seems it was only polyphony that got in the way. The other day I re-scored an item that was originally done with Proteus sounds with VSL. Proteus now sounds more like a child's toy.

Longing for the day when issues like those in this thread are a thing of the past.





Stuart

I have some consistent crashes with Logic Pro 7 as well, although not specific to VSL. It turned out that Altiverb needed a fix -- is it possible you're using Altiverb, and that may be the problem? It was causing core audio overload + subsequent crash. If that's the case, you may want to email the Audioease support guys. Just a thought.

Kerry

....however 'Journaling' is not relevant in OS 10.2.8 and that is where my experiance lies.

Stuart

Thanks for the advice. Well, we don't have any family jewels anyway!
Probably like you I have been working with constantly buggy software for years starting way back with Cubase XT and early ProTools systems - before that it was giant 24 track machines - reals of expensive 2" tape etc. I had my 24 track machine in the hall of my house (no room in studio). Why any visitors didn't lose their fingers when I was fast rewinding I'll never know. I am inured to trying to get my head around the technicalities and also the fact that the software companies use us as unpaid quality control staff. Anyway we might as well make hay while the sun shines.. Apple are probably, as we speak, working on a program that replaces the musician!

It is possible to do this with Disk Utility.
Is that a bad idea? - Patrick, why do you say this should be done using the original boot disks?

best,
John

Hmm, it seems to have worked for me. For the moment I'm not noticing any undesired side-effects. I'm running 10.3.6 on a dual 1G G4.
And I have noticed a rather pleasant speed increase in VSL, well rather it doesn't cough and splutter so much when it's trying to "get used to" a big arrangement.

Fingers crossed,
John