I’m sure my Apollo x8, 1st gen from 2018 is TB 2. And it works still fine for me. With my new PC I can use it with 32 samples buffersize for most of my projects. With my older system with Inter Core i7-7800X I had to use at least 128 samples with similar projects.
But I still have to work on optimizing my PC. I bought it from MusicStore as professionel audio workstation but they only pre-installed Windows without any optimizations.
From some quick searching, it seems like this version should have TB 3. One easy way to tell: TB 3/4/5 have the small USB-C-type port, whereas the TB2 ports have a different format connector.
From Wikipedia, here is the form of 3/4/5:
And from the same source, here is TB2:
Timing wise TB2 was from 2013, while TB3 came out in 2015. Of course, different devices would likely have gotten it later than the Thunderbolt versions themselves came out.
From what I’ve seen in general TB5 ports should be backward compatible with TB3 forward, and there are also work arounds to get TB2 to work by daisy-chaining through a Thunderbolt 3 dock and using a TB3 to TB2 adapter.
You are right. It’s TB3 on my interface.
As much as I couldn’t afford to transition to Mac, it has paid me back twice over already.
Us die-hard PC guys are starting to wonder what we are fighting for … game content?!?
That’s all they have left. Cubase on Mac is way better, it is not even an opinion any more.
I’m too old to read all off the above.
I had the same with a Gigabyte board and intel i7.
I sold the pc and built another.
So it’s an Asus gaming boards with an AMD Ryzen 7.
I made sure I had a cpu with graphics built in and a gaming board that could do 2 monitors and lots of USB ports.
I think it’s the graphics with nVidea and intel i9 that are the problem.
Since i have Ryzen 7 I’ve never had any problems at all
Sorry but that I’m being brutal because you’ll have to sell your pc but in the long run there’s no fannying around with settings.
Indeed, similar experience here. My RyZen system is running stable.
I have an Intel-based system. All good with the odd thing here and there, but overall, works really well.
Short update regarding my Cubase realtime peak issue:
I just wanted to give a short update and close this topic for now.
Steinberg Support has been working with me on this issue for several weeks now. I have provided different reports, project files and performance traces requested by Steinberg, which have also been forwarded to the developers for further analysis.
At first, the analysis pointed towards MIDI because the performance trace showed unusual MIDI-related activity. Because of that I completely checked and simplified my MIDI setup.
For testing I removed everything possible from the system:
The issue still remains.
I can reproduce the problem even with:
Even if I disconnect my MIDI system completely and only play the internal keyboard inside the plugin with the mouse, the realtime peaks still occur.
The important point is:
The problem mainly appears when realtime monitoring is active.
Mixing existing projects works mostly fine because Cubase can process everything differently. But as soon as I want to create new music and play virtual instruments live, the problem appears.
Different instruments behave differently:
So it does not look like a normal CPU performance limitation.
It seems to be related to realtime processing, the audio engine, driver communication or something similar.
Steinberg already provided several troubleshooting steps and special tools to create performance traces. I sent all requested data back to them, but so far the exact cause has not been found.
At the moment I can still use Cubase for mixing, but creating new songs with virtual instruments is currently not really possible for me. For composing and recording I have to use other DAWs until the problem is solved.
I will wait for the next feedback from Steinberg and if we find the actual cause or a solution, I will post an update.
Thanks to everyone who tried to help.
Thanks for the update.
At least Steinberg asked for you to submit Microsoft Windows Trace files. To my understanding, this is the best way to try and troubleshoot system issues of this nature.
You could also look around the internet to see if there are any forums with people who are capable of diagnosing Windows Trace files as well. There was some guys on the Sysnative forum that used to do it a long time ago, but it seems like they have disappeared.
Goodluck
