Recalculating Fades on Open every dang time...

bigcityrecording · Post by **bigcityrecording** » Fri Mar 17, 2006 8:53 am

I thought I had finally figured out how to make DP 4.61 behave with recalculating crossfades. I did this by turning off analyze sound bites (analyze only when needed). I thought that applied to fades, but it does not.

What I can't figure out is why on some songs not matter what I do, on OPEN DP always recalculates the fades. This can take 10 or 15 minutes all the while glitching on playback. But, it doesn't do this on every song, just on some.

Does anyone have any insight on this?

Thanks!

G5 dual2.5g/tons of RAM/OSX10.4.5/DP4.61/2408mk3

dubbeljee · Post by **dubbeljee** » Tue Mar 28, 2006 5:28 am

I have the same problem only on one project 44.1 Khz 16bit the other projects I 'm currently working on are 48Khz 24bit and they don't have that problem. My powerbook is now computing fades for about an Half our

JJ

dppimp · Post by **dppimp** » Tue Mar 28, 2006 8:36 am

I am having the same problem as well. It seems to happen on most of my sessions.

dubbeljee · Post by **dubbeljee** » Tue Mar 28, 2006 1:00 pm

workaround : save project as DP 4.12 (no need for duplicate audio) open in DP 4.52 and forget 4.61

JJ

Frodo · Post by **Frodo** » Tue Mar 28, 2006 1:27 pm

dubbeljee wrote:workaround : save project as DP 4.12 (no need for duplicate audio) open in DP 4.52 and forget 4.61

JJ

WOW!! That just blows my mind!!!

Thanks, JJ. Have you told MOTU about this? If so, how did they respond?

BobK · Post by **BobK** » Tue Mar 28, 2006 1:37 pm

I've had this problem intermittently and so have others:

http://www.motunation.com/forum/viewtop ... highlight=

MOTU tech support sent me a couple of suggestions, which I haven't had the time to try: trashing all the Fade files before opening the project, so DP will rebuild them, and going way back in the undo history (on a saved copy), saving that under a different name, and seeing if the problem goes away.

Please contact them about this so maybe they'll work on a fix if they haven't already started.

beubbo · Post by **beubbo** » Tue Mar 28, 2006 4:46 pm

dubbeljee wrote:workaround : save project as DP 4.12 (no need for duplicate audio) open in DP 4.52 and forget 4.61

JJ

Hi JJ,

Do you mean you're still using DP 4.52 ? Are you on Panther or Tiger ? Which OS version ?

Thanks in advance.

Frodo · Post by **Frodo** » Tue Mar 28, 2006 5:30 pm

BobK wrote:....and seeing if the problem goes away.

It's still troubling that such wording could be handed to a user as a solution. It begs the question "and if not....?"

This really bothers me.

lsdd · Post by **lsdd** » Tue Mar 28, 2006 5:59 pm

No probs here on Panther....Looks likes a Tiger from here.
I could be wrong.

Adam YW · Post by **Adam YW** » Tue Mar 28, 2006 9:06 pm

we have had this problem on our recent project, but only on one session. Very annoying but we think we know why. Our engineer comped the drum tracks together and merged the soundbites, then went through and edited the drums, creating hundreds of tiny fades. In that session where the merged files were edited DP recalculated them each time they opened. In the other sessions where we did not merge the files before editing, DP does not recalculate the fades.

What we were trying to accomplish with the merging was (in PT speak) consolidating, where the many soundbites (or "reigons" in PT speak) are combined into one. Apparently DP does this differently and if you edit the merged soundbite DP has to recalculate the fades.

Does this make sense? Anyone know how to (PT speak) "consolidate" in DP?

BobK · Post by **BobK** » Tue Mar 28, 2006 11:06 pm

Frodo: I think the tech's point was to try to find a point in the project's history where the problem happened, particularly to see if it was related to the number of fades, or to some particular action, or to see if the problem could be reproduced. I agree that if I went way back in the history and the problem went away, that wouldn't help the problem at hand, though it might help MOTU find the cause.

I haven't had time to do any troubleshooting, and have been working on other files that didn't have this problem. I think going back in the undo history is a long shot, but I bet merging the soundbites will help. There were a lot of fades - I'd heavily edited several vocal tracks - but my computer is fast, and this really shouldn't be happening. I didn't want to merge soundbites till I was closer to being done editing and mixing, but may have to do it anyway.

dubbeljee · Post by **dubbeljee** » Wed Mar 29, 2006 1:29 am

well it only works as long as you keep saving as DP 4.12 as soon as you save as 4.52 you can start again calculating

PB 1GHz 1GB Ram 0S 10.3.9 used to use 4.61 now use 4.52 but is less stable

I 'think that you can solve the problem by saving as DP4.12 and it doesn't matter witch version you use

i did not trash prefs run disk utillity or wath ever because no time
JJ

dubbeljee · Post by **dubbeljee** » Wed Mar 29, 2006 3:23 am

bad luck today workaround doesn't work anymore
found out fades are calculated way faster when all windows are closed

and the project contains merged files something I usually not do

Now I'm finishing the project I assume the best I can do is Merge all soundbites in the tracks so there are no more fades. and for the future never merge soundbites.

any other suggestions?

JJ

Fibes · Post by **Fibes** » Wed Mar 29, 2006 8:03 am

I have a project that has zero merged soundbites that calcs fades at open. Sorry, wrong bug tracker...

Adam YW · Post by **Adam YW** » Wed Mar 29, 2006 9:54 am

hmmm... This is a VERY annoying bug in DP. Digidesign is such a bitch with their astronomically priced and Digi-only hardware policy. That's why I'm using DP and I like it, but I hate things like this that make me want to be using PT. Fix it MOTU!