Tempo based effects not working in 8.05

[Prime Mover]

Just wrestled with this today. Plugins that use beat or tempo-based timing aren't functioning properly. MOTUs Delay and Echo plugins being the one's I've tried so far. When set to realtime (ie: 200ms), they work fine. But when set to any of the conductor-track reliant settings (tempo, beat, measure fraction), they don't reflect this and continue to use whatever the last realtime setting was set to. I don't use these types of settings very often, so I don't know how long it's been a problem, but it's definitely not working now.

[BKK-OZ]

I'd be interested to see if others are having this problem - I use tempo effects a lot, all in 3rd party plugs and am just about to upgrade to 8.05.

[Prime Mover]

Whooops, lol! I hadn't even kept track of which version I was on. I'm still running 8.04. Updating now, let's see if this fixes it.

[tgreen0406]

I am also having this problem. Please post any solutions you find. Thank you.

[stubbsonic]

The MIDI arpeggiator plug-in delays by whatever the note value is. So if I set the arpeggiator to a quarter note, the first beat will be silent.

[Phil O]

Just tried echo in 8.05. It's messed up here as well.

Phil

[bayswater]

Echo is working properly for me in DP 8.04/OS 10.8 and DP 8.05/Windows 7. The arpeggiator delay mentioned by stubbsonic happens on both setups.

[tgreen0406]

I just spoke with MOTU tech support. They are aware of the issue and said it will be addressed in the next upgrade.

[Phil O]

Thanks for reporting back TG.

Phil

[daniel.sneed]

Hope it get sorted out soon. My mixing scheme relies partly on this feature.

[Shooshie]

Seems there is a lot to fix these days. I do hope they get it all sorted out. I'm dealing with things, too, but I'm not upset about it. This was to be expected when they rewrote the code for DP so that it would fully run in the 64 bit Cocoa environment. There were over a quarter century of code, patches, connections, dependencies, and so forth in the old code, and it's not like you can just paste it into the new code, change a word or two, and it'll run. It will take some time to find all those connections, loose ends, and even mistakes in the old code. I've no doubt that in a year or two we won't remember this stuff, but we still have to live with it for now.

But I'm excited to see where DP goes next, after the patching and fixing of things levels off a bit.

Shooshie

[mrgkeys]

damn it.. I just lost an entire week to this... )(*)(*&(*&^*&%&^$^%.. that's a whole lotta $$$$$ out of my pocket... I have to mix now.. it's off to PT land.. grrrr

[James Steele]

damn it.. I just lost an entire week to this... )(*)(*&(*&^*&%&^$^%.. that's a whole lotta $$$$$ out of my pocket... I have to mix now.. it's off to PT land.. grrrr

An entire week you say?

[mrgkeys]

yep, a week's worth of $$. . landed a mix job for the first of next week.. all tempo based gtr stuff to work on. will do it in PT and be back in DP asap.. After 20 years in DP, I'm nowhere near as fast in PT or Logic. And I'm booked for the weeks thereafter, not sure if I can finish it in time, so I off loaded half the project to someone else. It happens. I'd rather keep my word and deliver on time than screw up someone's timetable and/or money. Though I'm still not sure how you overlook that in an update..No AU tempo plugs work either, so It's got to be down deep in the code. My hat's off to whomever is trying to find it. But I can't mix in DP until it gets fixed. I spent the last 3 months of last year in Logic X and have only started recording an album back in DP this year... Spent a day trying to figure out why I couldn't get the delays to sync.. I should know by now to come here first and post.

[daniel.sneed]

Back in the early days, I used to be pretty good, and fast, at getting delay values, and reverb predelays, out of a small hand calculator.

Think I'm back there for a few weeks...