@Antoine-B yes, I think Cubase has everything most people need, I’d love to see them look at the performance and stability over any new features and plugins.
Would be nice to see if people would pay for this though as an upgrade?
personally if they could get Cubase as efficient as reaper or better then i think that would be a huge selling point as it would be king of the Hill then.
We have hugely powerful CPu’s now but maxing out with 22% system usage seems incredibly wasteful.
M
We can all sit here and guess or test until we are blue in the face. I would love for Steinberg to explain exactly what data elements are used to drive the performance meter. At the end of the day, the control (the meter bar) has a min value and a max value. An algorithm is used to reduce any considered elements down to a single number that is used to drive the meter bar. I doubt it has anything to do with CPU load and is more likely a reduction of how timely the processes being monitored are staying compliant with program objectives.
So the question is… Steinberg, what is the performance meter considering internally?
I agree on the performance enhancements BUT this should not be an upgrade, this should come as a free update ASAP 
I will most likely pay for C15 eventually, but I really cannot wait to see a free update.
Thanks for confirming, that offline rendering can be problematic.
And that puts some of the earlier entries in this thread under a different light.
Indeed - it’s a trade-off. Sometimes I lean one way, and sometimes the other. It really depends on the individual project I’m working on.
If the crash is repeatable, it may be possible to get a dump file:
Damn! I never heard of Audiogridder. It REALLY does work. This is crazy. Thanks for this one!
Has anyone tested what the latency implications are of using AudioGridder to host VSTfx/VSTi vs loading the plugins natively? I’m thinking particularly when the AG server and plugin is running on the same machine.
you can set AG to have no extra latency at all , or you can have 2x 4x 8x your buffer size which gives extra performance at the cost of latency. This can be set globaly or per plugin as well.
M
Purposefully add no additional latency or measurably not adding any?
I only have limited experience using AudioGridder and that was with the server app running on a secondary computer. In such a case there will definitely be measurable latency added regardless of settings.
I was wondering if anyone has actually tested this.
I tested AudioGridder against VEP in the classic client/server model (2 systems) a while back, and AG had measurably more latency than VEP, but that’s to be expected given its architecture. The added buffering options, including "no added latency, " don’t reduce process/transport/network latency at all of course, as you already indicated.
Record-enabled tracks were particularly bad, again as expected, since that forces the entire chain to process on Cubase’s real-time, serialized thread. VEP wasn’t as bad, and I actually ended up purchasing VEP as a result, but I let the technical novelty of the solution get ahead of my real-world production workflow requirements (or rather, “choices”) and found that I still liked using record-enabled tracks with rather significant effects chains and just couldn’t deal with the overhead. Even with VEP it was a consideration. I’m not sure how well AG reports latency back to the host either, so it wasn’t necessarily a “fair” comparison of the two solutions (or maybe TOO fair 
)
I did NOT test AG on the same local system, but wouldn’t use it like that anyway for the same reasons stated above, but these were on an MBP M3 Max at the time, which was already performing remarkably. I DID try the VEP server component “locally” on the MBP, but only to verify that templates and saved projects utilizing VEP worked seamlessly whether I was in the studio’s client/server environment or on the road with a local:local setup (and they did).
If the nature of folks’ configurations affords them better multi-threaded scaling on Cubase on Intel/Windows architectures with AG, then that’s fabulous. But since something as simple as record-enabling a couple of track can introduce significant latency and drops outs you wouldn’t have locally, and that one can’t identify or control, you really have to make sure you’re solving for the right problem with it - neither solution is a panacea (in my opinion). But people have to do what people have to do!
AG reports its latency perfectly and is sample accurate. I mixed this album
https://open.spotify.com/album/6TuBYfa1sMOsRiCHPaHBqW?si=CSnz062NR8yBbwBoaMwnAw
Using AG and 2 machines as it was pre my 9950x machine ,and had zero issues with PDC from the slave machine.
M
Sorry, that’s a Spotify link and you’d have to create a free Spotify account. Knowing what Spotify does to music - no can do. Sorry…
They have been ripping of musicians since the very start and now they are pushing their own AI generated content without marking it as such on to their playlists (Velvet Sunset). Too much is too much.
That’s awesome! It’s great they’ve fixed the latency reporting.
Unfortunately, as these threads tend to go, this was a necro from the split thread where a user duplicated posts from the “Cubase 4 core limit” thread, which then turned into “audiogridder forces Cubase to use more cores” (which it doesn’t) which then turned into “audiogridder on the same machine makes the APM show less peaks” (which, of course it would) and now “audiogridder does what it’s supposed to do in a client/server model.”
I didn’t reply to the other thread because your original comment was “I only used audiogridder for a testing” which seemed inconsistent with the “audiogirdder solves everything” comment, so I just figured I’d drop the subject. I was just answering @mlib’s question, and all that data still stands and was validated.
These “scope creep” threads quickly get OT, so I’ll leave this one alone.
All that said, if you make the kind of music you make, it doesn’t matter what you do or how you do it. I think your work is excellent, and I’ll leave it at that.
Thanks.
MUSIC | Marcus Cliffe
Find your own ground
When running AG locally on the same machine, are there any properties that you have to set up first to get it to work properly. I am getting an error message that states it failed to bind to the server port 55056, and to terminate the application blocking the port. Have no idea what that refers to.
It appears that I had a weird issues of an instance already running. For those on windows, this page helped me solve the issue.