Have you tried reformatting your computer and starting from scratch?
If Cubase 11 works, I don’t see any reason, why formatting should solve the issue?
Also you’re losing everything on your machine by doing so. Here the Support has to take a look on it. It cannot be, that people have to reset their entire system in cases like these.
Now if your system has issues in general and also other versions do not work properly, then a reset is advisable.
There’s a lot of differences between Cubase 11 and Cubase 12, if it were just a minor update with a couple new features between the two, I’d be more inclined to agree.
I’ve never lost everything on my machine by reformatting, I just do a backup before hand.
Doing a clean reformat in these situations, the purpose isn’t necessarily to fix the problem directly, but to be able to troubleshoot from a guaranteed clean slate where both Cubase 11 and Cubase 12 are fresh installs with no previous settings lurking around. For example, it could be that after a reformat he then starts having the same trouble with Cubase 11 - which would be a good thing, because it would probably narrow our focus to what the problem likely is.
The proper scientific and engineering ethic here, if the problem has occurred for this long - is to start from scratch and incrementally test everything after each install.
It could be different settings related,
it could be corrupted settings related,
it could be mobo bios related,
it could be graphics related, ie is C11 using dedicated GFX and C12 using CPU gfx?
it could be security related.
it could be Apple device transfer related,
It’s much easier to start working through these things from a clean slate.
btw, I did a search in this thread… didn’t see anyone suggesting Safe Start?
Thanks for care, one person from Steinberg team already took my project, so I hope it helps
Not because of war, just because of Steinberg’s politics: online support was never enable here. I can buy online, but I can’t get a service, thats a little frustrating, but there is really first time for many years I need support
4 machines, 2 of them were brand new, just out of the box. It’s 100% C12 malfunction
1 Like
Did you do Apple Device transfer?
Of course no
So you did two clean installs?
How early on did you test C12 on the fresh laptop?
Can you start a new thread? its a bit difficult to sift through all the scattered info here.
title the thread, “Still having C12 performance problems, Mac Book Pro”
Point form, explain your problem and all troubleshooting steps youve taken thus far without success.
then give us
Computer:
- Mac Book Pro model/year
- CPU
- RAM specs - amount and speed
- OS version
- Motherboard/BIOS version
- Graphics card
- Anti-virus and any other 3rd party computer management software, backup, dropbox etc.
- Post picture of OS performance/power/graphic settings
- Did the dealer/yourself do hardware tweaks
Interface:
- make/model
- Drivers version
- firmware version
- connection type
- Post pictures of your interface settings
Cubase:
- Post pictures of your of your Studio Setup>Audio System settings
- Post pictures of your in-Cubase Interface settings and ASIO control panel
- Post video of your performance meter at the buffer setting you want with an empty project
- Post video of your performance meter with a typical session, list any plugins used
It will be much easier to make sense and compare to other users
I see, i didn’t know that about 10.5
Also, I agree 100%. It’s just that I am seeing many posts about nightmares on C12. I am yet to upgrade as I am scared to death with everything I read on this forum.
On the other hand 11 works well (enough) for me and so I am not going to risk it until I hear that people are happy enough…
1 Like
Just download the demo?
I also heard that once installed, people have trouble even accessing 11, licensing issues etc., so, I think I will wait…
1 Like
It’s a demo license, it wouldn’t affect C11. It’s completely separate, there’s no cross verification.
Either way, just do a backup/restore point of your system before installing.
99% of people aren’t having problems… It’s already at 12.0.5, there’s a good chance there won’t be anymore updates, but it seems the release itinerary has changed so who knows.
1 Like
hey, cheers, I am very attracted to some of the the features. I might take the plunge after I finish a couple of projects…fingers crossed…
1 Like
Hi @Tj99 ,
I was referring to the Audio Connections. I’ll adjust my description. Thanks.
@erdwandler , have you already made visible your Channel Latency in the mixer window? It’s an easy way to identify where the latency is piling up in your project.
You find the Channel Latency in the Setup Window Layout of the mixer window, just where you would enable left and right zone and all other visible elements of the mixer page.
4 Likes
Ok, so here is a weird one…I have been having all sorts of strange performance issues with Cubase 12 pro on Win11 pro.
Mainly the performance meter going crazy when certain plugins or VST instruments were running.
For example, I have Slate Audio VSX on my headphone control room output, and enabling it would eat about 25% of the available performance meter at a 128 sample buffer which is really excessive compared to in Studio One 5.5.
As soon as I loaded a virtual instrument and armed the MIDI track to record, the performance meter would go crazy, with spikes, pops, and audio drop-outs.
When I bypass Slate VSX, things would usually settle down, but sometimes after an undisclosed period of time, the performance meter would start randomly spiking again.
Sometimes, even just one single instance of Kontakt 6, playing back a single chord sequence from an 8dio strings library would cause the Cubase performance meter to spike every time notes were triggered.
So, I thought to myself that this didn’t happen in Cubase 11 pro, so I would reinstall it and see how it performed, and make a video showing the performance difference.
The difference was huge! In Cubase 11 pro, Slate VSX was no longer having much of an effect on the performance meter, and neither was Kontakt.
The same project that was making Cubase 12 go crazy, was running stable with around 10% usage, which is what I would expect from my system at that sample buffer.
So, then I load up the same project again in Cubase 12 to record a video of the performance there for comparison…
Now it is reflecting the same performance as Cubase 11! No weird performance spikes or usage from Slate VSX. No performance spikes when triggering MIDI data from Kontakt.
So basically, reinstalling Cubase 11 fixed whatever the performance issue was with Cubase 12. I can’t explain it, but I have left the Cubase 12 project open, and the performance meter is still behaving as expected now that I have both Cubase 11 and 12 installed.
2 Likes
Are you on Mac or on Windows?
There’s definitely something weird happening with that combination: Windows 11 Pro, Cubase 12, Kontakt, and latencies of 128 samples or lower. I’m experiencing something similar in Kontakt with the Electric Sunburst Deluxe instrument. Sometimes just playing a chord with three or four notes causes the performance meter going to red on my Ryzen 5800x. That was fine in Cubase 11.
1 Like
I’m also using the Control Room, by the way.
1 Like
This is the new new Kontakt under new leadership no?
it could be Kontakt side? Or is it fine in other DAWs… Other DAWs aren’t as big in code as Cubase though.
It’s Kontakt 6, not the latest 7. It could be a Kontakt issue, yes, but it behaved better in Cubase Pro 11.
2 Likes