Hello. Thanks for replying.
As my last comment about that reads, I will try anything, yes. However if disabling virtual cores is what works, do you think that might be an issue for the long term? From your own perspective?
Let me rephrase – if disabling all virtual cores works to solve this ASIO issue inside cubase, the love I have… for my damn production environment, my love and passion for music, and my nature as a tireless systems administrator will lead me to disabling those cores for sessions, and re-enabling them when done. Yes. This is not a long term workaround, however.
One thing that would help is if steinberg CONFIRMS this, and RECOMMENDS this, instead of the OPPOSITE, which can be found here> https://helpcenter.steinberg.de/hc/en-us/articles/206625630-Hyperthreading-Simultaneous-Multithreading-and-ASIO-Guard
“Enabling SMT/“Hyperthreading” while ASIO Guard is active usually has a positive effect on the overall system performance and is the recommended combination. Only in rare cases - e.g. with projects using many “live” tracks - SMT can still lead to performance issues. Again, please refer to the dedicated ASIO Guard article for details.”
Do you see my problem? I want OFFICIAL recommendations from steinberg that can AT LEAST allow me to work around this issue without major issues. I dont use “many live tracks”, and have been testing ONE TRACK and seeing issues sometimes.
And the hash iLok and eLicenser generate based on my hardware config? That will become invalid when CPU/core count changes. I would like to hear this from Steinberg. I am trying to get steinberg to do actual troubleshooting with me, via email, or here, or somewhere, but they so far have not.