Track timing off after using Drumagog

[thebioguy]

OK, I've got this down to a science now.

I can close and open Auria with consistency now. I learned to close EVERYTHING in the background, no matter how small before I begin, and this reduces crashes to about 1 in 10.

BUT

No matter what I do, IF I have Drumagog on a track, then close and open Auria, all of my timing is off. Nothing will fix it other than reloading a Pre-Drumagog file.

Anyone else?

[thebioguy]

Carefull inspection of the waveform shows the timing issue to be sound only. In other words, the waveform is not time shifted, but the audio is not in sync with the waveform. It is lagging behind.

[thebioguy]

Basically, every frozen gog track is lagging behind in audio only. The waveform is still in sync. BUT it only occurs after closing and opening Auria. Reloading project does not resolve the problem.

HELP!

[Rim]

Yes, this has already been fixed. It's a delay compensation issue. Drumagog has a large amount of latency (80ms), which is usually compensated by Auria's audio system, but frozen tracks weren't compensating for this properly. 1.05 fixes this issue. It's in Apple's review process now.

Rim

[thebioguy]

Late to the party, as usual.

OK, I will stop banging my head against the wall and wait for the update.

THANKS!