Hi there,
There are 2 quite major issues I have found:
1. In Cubase & Nuendo, when initiating Machine Learning using the default settings, the whole system becomes unstable and unusable. Understandable in a way but the issue is that is then impossible to quit the plugin and restore the machine to a usable state. The only way out of this is to hard close Cubase/Nuendo using Windows Task Manager.
2. In Wavelab 12, initiating Machine Learning even with less cores being used, Wavelab immediately crashes.
If I can supply any further info or help to test any future version etc. please do let me know.
Cheers,
Phil.
W11 | Intel i9 | 128GB RAM | nVidia 4090 (4K @ 65") | FF UCX | UAD2 QUAD
MAutoDynamicEq - Machine Learning issues
-
Phil Pendlebury Phil Pendlebury https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=253570 - KVRer
- 20 posts since 29 Mar, 2011 from Dubai, UAE
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14325 posts since 15 Mar, 2008 from Czech republic
Hi Phil,
the machine learning uses lots and lots of cores by default (in fact all of them), Cubase/Wavelab is also very hungry, so these probably collide. I'd recommend lowering the number of threads in the machine learning. Also make sure you are using the newest version.
the machine learning uses lots and lots of cores by default (in fact all of them), Cubase/Wavelab is also very hungry, so these probably collide. I'd recommend lowering the number of threads in the machine learning. Also make sure you are using the newest version.
