Fades always re-computing on a project (?)

[Tommy D]

I have a tune I'm working on with a lot of small crossfades (drum edits). Every time I open the project all of the little fades re-compute, taking a lot of time. I thought once a fade was created it was "remembered" by the project and didn't have to be computed every time.

Any thoughts why this is happening?

[jr213]

I think it just does this for project files opened in 4.6 that were created with a previous version. 4.6 uses a different (and slightly buggy) method of calculating fades that is supposed to be faster, though I don't see it.

[Tommy D]

Thanks jr...Well, this was a project that originated in 4.6...hmmmm....

Hey, we're kinda neighbors. I'm live down near San Antone....

[Adam YW]

we are new DP users and are having the EXACT same issue with fades re-computing that you posted about here. We have done drum editing which has a gazillion fades and it takes like 10 minutes for the session to re-calcuate them every time.

Did you ever figure this out? HELP!!!! Can anyone help??

Adam

[bigcityrecording]

I've been having the same problem.... It's embarrassing when a client is sitting with me and their track is glitching because of background processing.

Anyway, I think the problem is that it's doing a BUNCH of background processing: fades, file analysis, finding beats, etc., and it doesn't show you in the processing window either.... So, you have to go to Preferences/Settings, General: Background Processing and turn off the things you don't need, which for me is most of them....

That seems to fix it for me for now...

paul

[BobK]

I've been getting this problem intermittently.

It's not because the files were created in an earlier version - I've been working on the same files in 4.61 for a while now.

It even happened twice on the same file today, during two different work sessions. Hadn't turned off the computer, or even worked on another DP file, in between these sessions.

It's really annoying. I have to wait a few minutes for the fades to be calculated before I can start working.

Anybody?

[dosuna11]

Perhaps merging the track will help

[BobK]

Merging shouldn't be necessary, and it begs the question of why the crossfades have to be recomputed when they'be already been computed and stored in the 'fades' folder.

[Fibes]

I've got a 4.61 project that just started doing this and came here to post and found out i'm in the same boat as y'all.

Hmmm.

Very weird.

[BobK]

Update:

I emailed magic d about this yesterday, but haven't heard back.

I called MOTU tech support this morning (at least it was morning here on the west coast) and to my surprise got through the first try.

After checking with somebody else there, the tech (forgot his name) came back and said it shouldn't be doing this.

At his suggestion, I created a new file, then did 'File->Load' and loaded in all the data from the problematic file. After background processing was done in this new file, I saved and closed it. When I reopened, it started all over again with the processing, so no dice.

Next he suggested, for some reason, that I try a 'Save as'; I did this (without duplicating audio data) and it still didn't help. When I reopened the file, processing started again.

That's all he could come up with. He said it's not a 'known issue' with DP 4.61. (OK, but maybe it WILL be...)

I also tried opening a backup version of this file from another hard drive, but got the same results.

In this particular file, it took 6 min, 10 sec to do the processing (with no other work going on). With this many fades, I may have to do merges before I'm really done editing as a work-around, just so I don't have to wait so long.

[Splinter]

I have run into this as well on random projects without rhyme or reason. The other wierd fade issue is the fade that won't stick. What I mean is, no matter how many times I add a fade to a particular edit and save the project, when I open the project back up the fade is gone... hmmm.

[Fibes]

They need to get on this ASAP.

[Arceo]

Just to state that I had both issues (recomputin of fades and "not stiky" fades) randomly. I can't narrow down the causes of such behaviour it just happens now and than...

Cheers

Arceo