35 minutes for file to load.

[toodamnhip]

Wow, how stupid. I hadn’t updated my signature in FOREVER. Updated now. Thanks..

[wylie1]

Last time I had extremely long load times was just before one of my drives failed.

[ccrane]

I too sometimes have the long load/insert plug-in issues. It only happens with very dense sequences. These sessions will typically have about 10 effect inserts per track (though not all filled), 80 aux busses and 100+ tracks. I will have many tracks bussed to a couple of auxes (music and vocal stems for instance) and then will have those aux tracks bussed to another summing master aux and then finally to an audio track to record. Additionally many tracks are pre-auxed (i.e drum stems) before getting sent to the music and vocal stem auxes. So that's a lot of auxes feeding into other auxes. The slowdown starts to happen when I route the master summing aux track to the mixdown audio record track. Also super slow when I record arm the mixdown audio track. The most I've had to wait is around 5 hours. Usually it's about a half hour or so. After that point things are ready to go, sometimes the audio engine turns off and I have to turn it back on after waiting for DP to be ready to record. If I were to add a plug-in on the master fader it would also take a long time to initiate.
What I think is going on is that a lot of information is being routed through the auxes and finally into the record armed audio track and either ADC is being recalculated or DP is just bogging down trying to get all of the audio information narrowed down. If I unarm the audio track and remove it's input the sequence behaves ok again. Reloading the seq into a new project does not help with this particular issue. At times I've had to use audio hijack to record my mix. This has been my experience with DP since 5.13 and Leopard, and on different computers. I now have a 12core Mac running DP 7.24 with plenty of ram and a stable OS (SL). Plug-ins are all real time and buffer is set very high:1024+.
In my opinion, auxes are at times DP's Achilles heel - they sometimes exhibit buggy behavior (unexplained latency - always fixable though) and I believe at times get corrupted. Perhaps the extreme slowness is all because of the Wave's 8 plug-ins I'm using. I have also noticed Apple's AU pitch plug-in when used in high quality mode can also can slow down a session. Ram usage/limit is not the issue as it happens with sequences that are using under 2GB of memory.

[toodamnhip]

I too sometimes have the long load/insert plug-in issues. It only happens with very dense sequences. These sessions will typically have about 10 effect inserts per track (though not all filled), 80 aux busses and 100+ tracks. I will have many tracks bussed to a couple of auxes (music and vocal stems for instance) and then will have those aux tracks bussed to another summing master aux and then finally to an audio track to record. Additionally many tracks are pre-auxed (i.e drum stems) before getting sent to the music and vocal stem auxes. So that's a lot of auxes feeding into other auxes. The slowdown starts to happen when I route the master summing aux track to the mixdown audio record track. Also super slow when I record arm the mixdown audio track. The most I've had to wait is around 5 hours. Usually it's about a half hour or so. After that point things are ready to go, sometimes the audio engine turns off and I have to turn it back on after waiting for DP to be ready to record. If I were to add a plug-in on the master fader it would also take a long time to initiate.
What I think is going on is that a lot of information is being routed through the auxes and finally into the record armed audio track and either ADC is being recalculated or DP is just bogging down trying to get all of the audio information narrowed down. If I unarm the audio track and remove it's input the sequence behaves ok again. Reloading the seq into a new project does not help with this particular issue. At times I've had to use audio hijack to record my mix. This has been my experience with DP since 5.13 and Leopard, and on different computers. I now have a 12core Mac running DP 7.24 with plenty of ram and a stable OS (SL). Plug-ins are all real time and buffer is set very high:1024+.
In my opinion, auxes are at times DP's Achilles heel - they sometimes exhibit buggy behavior (unexplained latency - always fixable though) and I believe at times get corrupted. Perhaps the extreme slowness is all because of the Wave's 8 plug-ins I'm using. I have also noticed Apple's AU pitch plug-in when used in high quality mode can also can slow down a session. Ram usage/limit is not the issue as it happens with sequences that are using under 2GB of memory.

5 HRS???
WOW..That’s when it’s time to go to bed and wake up and hit record.

[MIDI Life Crisis]

Frankly, in such instances, clearly something is wrong with the file. Waiting hours or even half hours is counter-productive and for me, counter-intuitive. It's them time to find and fix the problem for there is clearly a problem. In most if not all cases, tracking it down shouldn't take more that a 10 minute call to MOTU.

[toodamnhip]

Frankly, in such instances, clearly something is wrong with the file. Waiting hours or even half hours is counter-productive and for me, counter-intuitive. It's them time to find and fix the problem for there is clearly a problem. In most if not all cases, tracking it down shouldn't take more that a 10 minute call to MOTU.

LOL, aren’t we the eternal optimist?

Often, one has a great mix and cant go back. So all altruistic sentiment of what one should have to put up with goes out the window to save a mix.

[ccrane]

Frankly, in such instances, clearly something is wrong with the file. Waiting hours or even half hours is counter-productive and for me, counter-intuitive. It's them time to find and fix the problem for there is clearly a problem. In most if not all cases, tracking it down shouldn't take more that a 10 minute call to MOTU.

Ah, I knew this would get a little attention. I agree that something is indeed wrong. Clearly waiting around so long for a program to do it's thing is no fun. It is only an issue when it comes time to mix down the track, or bounce a file, the sequence works fine until the routing and record arming begins. Usually it does not happen to the extreme degree of several hours - that was one session. Still on a complex sequences a wait of at least a few minutes is the norm, and a very complex (to me anyway) sequence such as I described above may take considerably longer. I'm curious if anyone else routes auxes into auxes into auxes with tons of plug-ins into an armed track on a session that is similar to how I previously described. As I mentioned before Waves or another plug-in may be causing some of the long wait issues. If I figure out the culprit I shall report back.

[toodamnhip]

I haven;t had it as bad as you with 5 hrs. But one thing that has been a long term issue is EDGE EDITING soundbites when routed to a stereo track. Once a file gets big, if I start edge editing, I get lots of long spinning beach balls. Really sucks. Clearly it is related to routing into a stereo track. If it gets bad enough, I will un route, going out the regular outs 1-2, do my edits, and the re route to a stereo track.

[cuttime]

My 2¢, forgive me if I'm redundant or dense:

Check your Activity Monitor, see where the resources are being used.
Boot in Safe Mode-See if it makes a difference.
Check your io: http://www.aja.com/en/products/software/ Look for Mac system test.

[ccrane]

I haven;t had it as bad as you with 5 hrs. But one thing that has been a long term issue is EDGE EDITING soundbites when routed to a stereo track. Once a file gets big, if I start edge editing, I get lots of long spinning beach balls. Really sucks. Clearly it is related to routing into a stereo track. If it gets bad enough, I will un route, going out the regular outs 1-2, do my edits, and the re route to a stereo track.

Yeah, it's usually not nearly that bad, thankfully.
Do you get the edge edit beachballs even with "Audible Mode" off?

[toodamnhip]

I haven;t had it as bad as you with 5 hrs. But one thing that has been a long term issue is EDGE EDITING soundbites when routed to a stereo track. Once a file gets big, if I start edge editing, I get lots of long spinning beach balls. Really sucks. Clearly it is related to routing into a stereo track. If it gets bad enough, I will un route, going out the regular outs 1-2, do my edits, and the re route to a stereo track.

Yeah, it's usually not nearly that bad, thankfully.
Do you get the edge edit beachballs even with "Audible Mode" off?

Dunno, always working in audible mode. I will have to try that, good idea. That’s just the little round speaker icon in consolidated window right? Never really played around with it much for trouble shooting. But ti makes sense that maybe that could create a problem.

[MIDI Life Crisis]

It's not so much being an optimist as a realist. I save very often. If I did an edit or two and the save was inordinately long, I'd undo a few edits and try again. If need be, I'd go back in time machine until I figured it out. I think that's a better plan than hanging on to a project I know is damaged because my work is perfect and unrepeatable. Tedious to do sometimes? Certainly. Impossible? I haven't hit that wall yet.

[Gabe S.]

I have 10.6.8. In DP 8, I've found random files that work fine, and then all of a sudden, on the next open, it sits there just like you described. For me, this happens when the computer has been on for a long time.

I found that if I restart the computer, the file opens fine again. But trying anything else without restarting is worthless for me.

(I've never waited 35 minutes.....too impatient for that)

-gabe

[Killahurts]

I found that if I restart the computer, the file opens fine again. But trying anything else without restarting is worthless for me.

This.

Works so well for me that I restart before I open any big DP file to do serious work.

FWIW, I've opened very large templates before, spread over two or three computers with VE Pro- many dozens of Kontakts and other VI's on each machine, dozens of stereo and mono audio tracks, automation, etc.. I've never had a file take over 5 minutes to load.