Still an Ocean-Ways-Studio-issue when reopening projects

[Audiorizon Studio]

After the non-resistance of OWS-plugin-settings when reopening a (logic -)project disappeared with the last UAD-update, I still got a problem when reopnening my projects (latest logic pro version), when OWS is used. Already with an UAD-workload under 55% in the projekt, the OWS-plugins drop out with that UAD-power-exceed-message when project is loading. (Normally problems like that only appears at a workload of above 90% of my 18 shark-processors.) Only projekts with OWS-plugins are affected and only this plugins drop out. You may switch off some other UAD-plugins, than opening new instances of OWS, copy/paste the settings and then switch on the others again for a workaround. After that, everythings runs without problems, even if you significantly increase UAD-charge, but not, if you opening another OWS-instance.
Another problem is, that you risk dropout of all OWS-instances, if you are opening another OWS, although being in slight-UAD-charge-spheres.
Both not gravely problems, but a bit inconvenietly.

Best reagds
Audiorizon

 

[RogueM]

it’s not a new issue, and has to do with the tracks order and plug-ins population. I doubt it will ever be fixed (and to be fair I’m not sure that can come from UA, on the current hardware architecture at least).

 

[DanButsu]

Indeed. To avoid this, I put the tracks with the big heavy plugins at the top/left of the DAW so that they load first, then lighter plugins can load around them.

 

[Neotrope]

Indeed. To avoid this, I put the tracks with the big heavy plugins at the top/left of the DAW so that they load first, then lighter plugins can load around them.

same here

 

[Audiorizon Studio]

Thanks! I will try that! (Even I don`t know, if logic "reads" from left to right! lol)
Best regards