DP 11.22 (and 11.21) Crashes When Closing Projects

[fusion58]

Oh and of course, although there's a good chance enabling the VST3 will work, keep in mind that down the road if you switch to the AU version, projects in which you used the VST3 version may show the plugin missing. Although perhaps you can have both active at once. Not sure. I've done it with VIs and they will often show up twice in the plugin menu and I have to remember which is which.

Yep. When the plugin shows up more than once in DP’s list, then DP doesn’t identify which is the AU version and which is the VST. Hard to keep track.

[bayswater]

Where are you looking? The plugin type is shown clearly in Preferences, along with whether it is in the current list of plugins DP will use. For that matter, it shows the type in the plugin chooser too. Where doesn’t it show?

[James Steele]

For that matter, it shows the type in the plugin chooser too. Where doesn’t it show?

In the hierarchical menu you get when you right click the effects insert. I prefer using it over the Effects Chooser window.

[bayswater]

For that matter, it shows the type in the plugin chooser too. Where doesn’t it show?

In the hierarchical menu you get when you right click the effects insert. I prefer using it over the Effects Chooser window.

Ah, right. I don’t use that very often. I’ve done the custom categories in the Chooser which is a good overall way to get at plugins you know.

[James Steele]

For that matter, it shows the type in the plugin chooser too. Where doesn’t it show?

In the hierarchical menu you get when you right click the effects insert. I prefer using it over the Effects Chooser window.

Ah, right. I don’t use that very often. I’ve done the custom categories in the Chooser which is a good overall way to get at plugins you know.

Me too. It’s very customized. I just prefer using the menu that pops up with right-click rather than the Effects Chooser window.

[fusion58]

Where are you looking? The plugin type is shown clearly in Preferences, along with whether it is in the current list of plugins DP will use. For that matter, it shows the type in the plugin chooser too. Where doesn’t it show?

I meant when you load the plugin as an insert in a track.

For example, if I have a mono audio track and I want to insert the mixIR3 plugin in the track, then DP will show multiple instances of the plugin without specifying which one is the AU version and which is the VST in that view.

[bayswater]

DP will show multiple instances of the plugin without specifying which one is the AU version and which is the VST in that view.

Right, so just use the plugin chooser and its list will show the versions, or use plugin preferences to remove the versions you aren’t going to use, so they don’t show up in the plugin lists

[fusion58]

Well, after testing both the AU and the VST3 versions of the MixIR3 plugin in isolation, it turns out both plugin versions cause DP to crash in the same manner. I'm disappointed as Redwirez claims the plugin supports Apple Silicon. I guess I'll have to wait until I hear back from the company's support desk for further instructions.

[James Steele]

Well, after testing both the AU and the VST3 versions of the MixIR3 plugin in isolation, it turns out both plugin versions cause DP to crash in the same manner. I'm disappointed as Redwirez claims the plugin supports Apple Silicon. I guess I'll have to wait until I hear back from the company's support desk for further instructions.

That’s a bummer. Hopefully it will get fixed. One last thing you could try is… if you have something like Blue Cat Audio PatchWork, you can try and open it inside of that using PatchWork as a shell. Sometimes I’ve gotten plugs to work that way… acknowledging of course that is temporary and less than ideal workaround.

[Ombre]

Hi,
I had exactly the same problem. So I threw away DP, made a complete reinstall and boot DP with MAS and Au plugins only.
So far I realized that the problem came from some VST3 plugins. In fact, the problematic plugin was Komplete Kontrol from Native. I remove it, used the AU version and everything works fine.

[James Steele]

Hi,
I had exactly the same problem. So I threw away DP, made a complete reinstall and boot DP with MAS and Au plugins only.
So far I realized that the problem came from some VST3 plugins. In fact, the problematic plugin was Komplete Kontrol from Native. I remove it, used the AU version and everything works fine.

Good to know. AFAIK, the only plugs you really NEED to run as VST3 is Melodyne (required by DP) and in my case I have to run the Console 1 plug as VST3 since only that format supports the complete feature set of that plug. Also, it might be that anything that (like Melodyne) uses ARA might need to run VST3.

[HCMarkus]

Also, it might be that anything that (like Melodyne) uses ARA might need to run VST3.

VocAlign current version must run VST3 is ARA is to be used.

[James Steele]

Also, it might be that anything that (like Melodyne) uses ARA might need to run VST3.

VocAlign current version must run VST3 is ARA is to be used.

Good to know. I'm thinking anything that uses ARA in DP requires using the VST3 version.