Digital Performer 11.34 version

[crduval]

• Fixed a bug causing DP to reexamine all previously skipped plugins of the same format in addition to the selection when attempting to reexamine specific VST2 or VST3 plugins from the Audio Plug-in Preferences.

I literally just saw this one only minutes before seeing this post. Nice timing, MOTU!

[Phil O]

I was having a problem with a project where I would get a crash after a particular sequence of clicks leading to "show takes." I opened the project in 11.34 and no crash. The project still crashes in 11.33, so there must be some under the hood fixes MOTU hasn't mentioned. So far all seems well with 11.34.

Your friendly neighborhood Phil

[stubbsonic]

DP 11.34 is still crashing after merging soundbites. I think it's roughly every 4th or 5th merge. I have to Force Quit.

[HCMarkus]

I was having a problem with a project where I would get a crash after a particular sequence of clicks leading to "show takes." I opened the project in 11.34 and no crash. The project still crashes in 11.33, so there must be some under the hood fixes MOTU hasn't mentioned. So far all seems well with 11.34.

Your friendly neighborhood Phil

I had the "Crash on Show Takes" problem, but it disappeared for me with the 11.33 update.

Go figure.

No problem merging here on 11.33. Also, never experienced the VST rescan issue. More "Go figures."

I'm gonna' install 11.34 today.

[bayswater]

• Fixed a bug causing DP to reexamine all previously skipped plugins of the same format in addition to the selection when attempting to reexamine specific VST2 or VST3 plugins from the Audio Plug-in Preferences.

Didn't know that was a bug either. I just thought that it was a gigantic time suck to be endured. Yes!

Same here because I never have more than one or two VST plugins. Is there a good reason to use one if an AU is available? I know there are things a VST3 does that AU won't but I rarely have a use for those things.

[HCMarkus]

Is there a good reason to use one if an AU is available? I know there are things a VST3 does that AU won't but I rarely have a use for those things.

Side Chaining requires VST3 for some plugins... Arturia Vocoder for one. And ARA for Melodyne and Vocalign needs VST3, too.

[Michael Canavan]

Is there a good reason to use one if an AU is available? I know there are things a VST3 does that AU won't but I rarely have a use for those things.

Side Chaining requires VST3 for some plugins... Arturia Vocoder for one. And ARA for Melodyne and Vocalign needs VST3, too.

Reason Rack as a VSTi3 allows you to use all of Reasons MIDI tools, from chord devices, step sequencers, drum machines, etc. etc.

On that line almost any VSTi with it's own built in sequencer is capable of sending MIDI to another VSTi. So for instance the MPC VSTi can send a track to another drum or even keyboard track to fire proprietary sample libraries like Opus, Damage, and any number of Kontakt libraries etc.

Logic Pro used to only have AU MIDI FX slots, which near no other DAW has, so the AU MIDI FX would work inline in a slot on a track, and only the MIDI out to the AUi would sound, effectively useless with drum machines like the MPC. Now they also allow an AUi to send MIDI to another track. So in a few years we shoudl see AUi's be capable of what VSTi's have been capable of since VST2 15 years ago.

[dwilliams]

Installed. Already had a couple of crashes but no more than 11.33. Can't wait to try the hardware inserts (the main reason I installed) but I'm on the road. Will update after testing.

[James Steele]

Is there a good reason to use one if an AU is available? I know there are things a VST3 does that AU won't but I rarely have a use for those things.

Side Chaining requires VST3 for some plugins... Arturia Vocoder for one. And ARA for Melodyne and Vocalign needs VST3, too.

Yep... and likewise you have to use the Console 1 VST3 to get full features and bidirectional communication between the Console 1 hardware and DP.

[James Steele]

Installed. Already had a couple of crashes but no more than 11.33. Can't wait to try the hardware inserts (the main reason I installed) but I'm on the road. Will update after testing.

You'll be pleased about this. It used to be that when you first loaded the a project containing Hardware Insert plugins, audio tracks with a Hardware Plugin on it would play out of time. The workaround was to open each instance and click in the sample offset value box and re-enter it. I ended up making a Keyboard Maestro macro to do this and ran it immediately after opening a project. I have not seen this issue again since updating to DP 11.34. From what I can tell, they have this issue solved. It took years, but it's solved. I'm not nearly as tempted by Pro Tools as I was before, but MOTU/Avid need to do some work on EuControl support.

I actually had in depth exchanges with MOTU regarding this issue and like to think that some of the info I provided helped track it down. I could be wrong. (For example, it used to be that when pinging for round trip latency in the plugin, the first ping would return some wildly incorrect number that would be influenced by the latency of plugins on your Master Fader and require a second ping.)

[HCMarkus]

Installed and ran 11.34 for four hours yesterday, editing and mixing a simple two-vocal, MIDI piano project.

No issues encountered.

[bayswater]

Is there a good reason to use one if an AU is available? I know there are things a VST3 does that AU won't but I rarely have a use for those things.

Side Chaining requires VST3 for some plugins... Arturia Vocoder for one. And ARA for Melodyne and Vocalign needs VST3, too.

Yep... and likewise you have to use the Console 1 VST3 to get full features and bidirectional communication between the Console 1 hardware and DP.

Yes, I understand the routing functions of VST3, ARA, etc, but are there any advantages of a basic VST effect over the AU version? Efficiency? OS compatability? I thought at one time, they all used the same code with changes in the way they interface with the DAW.

[Irimi Nage]

Did they fix groove quantizing not working at all?
Quantize preview not working?
Audio preview with option-spacebar not working?

I just had to restart because DP was ignoring automation. The send knob is automated down, yet there is still a ton sending to the reverb. I get this one a lot. Any fix there in the new version?

I ask because on occasion I've updated and regretted it. Thanks for any info

[James Steele]

Yes, I understand the routing functions of VST3, ARA, etc, but are there any advantages of a basic VST effect over the AU version? Efficiency? OS compatability? I thought at one time, they all used the same code with changes in the way they interface with the DAW.

I also have Cubase Pro 14 (and Pro Tools) installed on my Mac, which is why I install VST3 (and AAX) plugs in my Mac. I use AUs in DP except for Console 1 and Melodyne, and the odd plug-in where VST3 works but AU has issues. But if I re-scanned a VST3 in DP, it used to re-scan all my VST3s even if DP doesn’t use them.

[James Steele]

I ask because on occasion I've updated and regretted it. Thanks for any info

You can always rename “Digital Perfomer.app” to “Digital Performer 11.33.app” (for example) in the Finder BEFORE installing the newer version. They can both exist side by side in your Applications folder, so you can try the newer version for a while and still have the ability to run the older version if you wish.

Once you trust the newer version you can delete the older one.