When I close down a project, it seems that in the past few months, it takes forever (ok one to three minutes) to clear out the project. I have a pretty fast computer (see Signature), and yes my projects have more tracks (20 to 30) than in the past but I'm just trying to find out if this is normal.
 
I did an experiment where I just loaded a simple project one MIDI track, saved the project, closed it and it closed almost instantly. I then added an audio track with no plug-ins and again it closed as soon as I clicked the X. I then cleared all the tracks and loaded one of my typical tracks with 5 plug-ins (Tape, Fab Filter EQ, iZotope 8 Dymamics, iZotope 8 Vintage Limiter, Insight). When I closed the project it took 6 seconds to clear the project. I then added another identical track and it now took 12 seconds to clear. Every additional track added an additional 6 seconds.
 
Does this seem normal?
 
Walt
 

Midi is the thing that usually takes time to save.
 
Normal depends on your drive type. Lots of midi definitely slows down project save times.
 
Without midi, projects usually save very very fast.

You say that you have a track with 5 plug-ins then you duplicated the track many times.  IF you are adding all 5 plug-ins to each track then yes it will take some time to shut down.  I would put those plug-ins either on a buss or on 5 different buses.  This will give you only 5 plug-ins total and not 5 per track.

gswitz
Midi is the thing that usually takes time to save.
 
Normal depends on your drive type. Lots of midi definitely slows down project save times.
 
Without midi, projects usually save very very fast.

Thanks, but saving a project is not the problem. It takes between 1 to 2 seconds to save a project. I was discussing closing down a project to work on another one. A larger project (that's already saved) will take up to 3 minutes to close. If this is normal then fine.
 
I do have some projects with some MIDI with a lot of CC lanes and yes they slow things down, but I understand that.
 
Walt
 
 

MarioD
You say that you have a track with 5 plug-ins then you duplicated the track many times.  IF you are adding all 5 plug-ins to each track then yes it will take some time to shut down.  I would put those plug-ins either on a buss or on 5 different buses.  This will give you only 5 plug-ins total and not 5 per track.

Sorry Mario, but I didn't make that clear. I duplicated that track without any audio just as a test. I normally use templates that have my desired plug-ins.
 
Most of my tracks have different instruments i.e. trpt, clar, sax, guitar, accordion, vocals, so I need different parameters for the plug-ins. If I do have duplicate tracks (to thicken the sound) of a particular instrument or vocal, I do bring them to a stereo buss as you suggested.
 
It just doesn't make sense to me that it takes 1 to 2 seconds to initially save a file, but 3 minutes to close it down.
 
Walt

My projects take ages to close.
I just go in to task manager and kill the process - if I'm in a hurry to open up another one.
I don't know what it's doing, when a file closes.

My projects also take a good few minutes to open...

I would try to narrow it down to a plug in first because its one of the easiest tests to do.
Are you running Kontakt or any other Synth that loads samples ?
My projects close fast, then I have to wait between 5-8 seconds before I see the start screen in order to load another project.

chuckebaby
I would try to narrow it down to a plug in first because its one of the easiest tests to do.
Are you running Kontakt or any other Synth that loads samples ?
My projects close fast, then I have to wait between 5-8 seconds before I see the start screen in order to load another project.

I'm going to try narrowing down and get back to you. I'm not running Kontakt for the experiments I tried, but do use it in many projects.
 
Walt

chuckebaby
.....My projects close fast, then I have to wait between 5-8 seconds before I see the start screen in order to load another project.

Do you use several plug-ins in you tracks?
 
Here's what I got for numbers:
Blank project, add one audio track from my templates with 5 plug-ins as in my original test. Same result, 6 seconds to close. Note that my timer starts when I click the X icon and ends when the Start Screen is done loading.
Eliminate Insight - 6s
Eliminate Ozone 8 Vintage Limiter - 6s
Eliminate Ozone 8 Dynamics - 4s (and it wasn't even enabled, whatever that has to do with it)
Eliminate Fab Filter Pro EQ - 4s
Eliminate Ozone 8 Vintage Tape - 4s
Eliminate track - 3s
Therefore the Start screen takes 3 seconds to load.
 
I then loaded 10 Audio tracks with no plugins - 3s to close
Cleared all tracks and loaded 10 tracks with the above plug-ins - 62s to close.
 
The reason I brought this all up is that everyone was saying how the latest updates have really improved operational speeds, open projects, etc. including your statement that your projects close fast. I'm seeing 3 minutes to close a big project with a fairly fast computer. If that the way it is, que sera sera.
 
Since some in this tread have stated that it takes forever to close a project, I'm going to assume it's just the amount of plug-ins, song content, MIDI including CCs that determine closing times and that I don't have anything wrong with the software or my computer. Thanks to all those that responded.
 
Walt
 
 

In my orchestra template, where I use many instances of Kontakt, in addition to multiple instances of Virtual Sound Stage, in addition to buses with Altiverb, Ozone, etc, this also takes several seconds to completely unload.
It seems that the unload time is proportional to the amount of RAM used.
But this delay is inexplicable, because if I kill the Sonar.exe process directly in the Windows Task Manager, it releases the RAM immediately, without any problem for Windows, nor for the project ...