Quote:
Originally Posted by Crizdee  1. Control surface compatibility… when returning to plugin that has been set already, the plugin does not send its current parameter position to the control surface!! So the control surface is showing default parameter positions and not the actual positions of the plugin. This causes problems when you want to tweak settings!! You touch the control surface rotary encoder and the settings go to default??
2. when saving presets using the pro tools presets menu! Recalling presets and the plugin parameters do not change to reflect the new settings!! Adjusting the preset that has been recalled its difficult and can cause randon settings!!
3. The BIGGY!! Duende will crash pro tools. Some days as many as 7 crashes!! All caused by Duende and the crash logs confirm this. Mostly when closing one session and opening another that have SSL plugs inserted. But also some session will just randomly crash? the more plugins the more it seems to crash. Again all crash log indicate Duende. |
1) You should mention the DAW and control surface. I myself am not having this issue and haven't heard much about it.
2) Which plugins? Most Duende plugins have been designed so that presets are loaded and saved with the corresponding buttons at the lower left corner.
3) This is a problem for a lot of people, and was for me, but has more or less passed. In our case, the crash logs were always reporting Duende as the culprit but it was actually another FW device on the same FW bus (a video decoder) conflicting with Duende. Remove the other box, the crashes stop.
Another thing that can happen is that Duende, or the DAW, won't tell Duende hardware to clear out prior DSP usage upon closing a session, and if the DAW crashes it DEFINITELY won't clear out the DSPs. So next time you go to open a session with a lot of Duende plugins it crashes because the DSPs fill up, even if you're technically under your limit. There isn't enough room for the old and the new together.
The fix for that is simple: with your DAW closed, turn Duende off, then back on, then reopen the session.
We've been through everything with Duende and I think we've found about all of the available workarounds. It's a shame that that is the case, but there seems to be nothing else we can do (did someone just whisper "UAD...?")
If you really want help you'll have to start listing system specs. Otherwise, you're just blowing off some steam. Which is OK, too -- we've all had to do it.