11/22/2023 0 Comments Cubase 12 upgrade from 11![]() Please contact your Sweetwater Sales Engineer for questions or information. Cubase 12 licensing is now fully digital and no longer requires a Steinberg USB authorization key. Instead, we are being treated like guinea pigs and not customers. This package features exclusive upgrade pricing for owners of Cubase Artist 11. Nothing we can do to solve all of this until another update.Īll those people that have spent time and effort to make the program work deserved to be paid in my view.Įveryone that purchased this program should have had a 100% working one from the start. The people getting the dongle problem is all related to the stuck on video. I find that there is answers from steinberg employees on this site, but an impossible Tech support.Īdding to a closed Artical About a dongle, the guy had a valid comment showing a screen with problems which i got also when Stuck on video was not there after deleting dll and saving. It is a wait and see situation i am afraid until this all is sorted. Most supports come back usually within 24 hours at the minimum. It is terrible that support ignores tickets and i have put one in since March 5th There is still loads of us getting nowhere. Why does 12 run with all hell breaking out.Ī lot of people have made workarounds to get it to work and suceeded so they say. Groove Agent 5 works best with 2 cores selected with hyperthreading in bios = OFF.Īnd it remains playable/glitch-free if Halyon cores are on (2 cores) or OFF, when playing along with a GA5 drum loop on 2 cores.Īnd definitely, for my ThinkPad i7 at least, hyperthreading should be switched off when using either CB11, or CB12.I am sure all of this e-licencer thing and Stuck on video player is all connected. I then repeated both experiments with ASIO4ALL selected (512 buffers = Input 13 ms Output 20 ms) and it was aceptable with hyperthreading OFF but unplayable with hyperthreading ON.Ĭonclusion: Steinberg has an issue with hyperthreading /core handling that existed in CBPro11 and is even worse in CBPro12. It did not matter which core state is selected in either GA 5 or Halyon i.e. RESULT: Both GA 5 and Halyon were rendered UNPLAYABLE. I then rebooted and switched hyperthreading = ON in BIOS ( 4 cores now available) and repeated Experiment 1 and 2. RESULT = NO glitching with just the drum loop running - playing Halyon was glitch-free.RESULT = marked glitching with just the drum loop running - playing Halyon made it worse. ![]() Hyperthreading switched OFF in BIOS = 2 cores available. ![]() Latency settings: INput = 8.9 ms Output = 31.5 ms.Running Groove Agent 5 on a drum loop (Beat Agent) and playing Halyon SE3 on a synth lead (Hammer something): So I experimented with hyperthreading /multicore states within my CBPro12 update this morning: Since turning OFF hyperthreading, I’m now running Latency down to 4 ms for recording with no glitches whatoever, whereas, before, 40 ms wouldn’t be enough to stop glitches, and the huge latency was unusable for recording anyhow. Turning off background processes in WIN 10 doesn’t work on its own, but with hyperthreading turned off too, the problem is solved. This is why glitching is often absent at the beginning of a session, then gets progressively worse as background process covertly slip into the core(s) you are using for your DAW. Hyperthreading allows background processes to hijack and use the spare capacity of a core that APPEARS to be idle. Thanks to all who suggested doing this on here, and on other DAW forums. ![]() Glitches are absent for 1st minute or so of play, then become more frequent as play rolls on.Ĭomplete cure achieved by TURNING OFF HYPERTHREADING in BIOS setup (Lenovo Laptop Core i7). Glitching seemed random in C11Pro, except it was definitely time-use related. The quoted box below shows an old post I made on this forum sometime ago in response to glitching in C11Pro: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |