I am using Cubase 12 on Windows 10 with an RME Babyface soundcard. In previous versions of Cubase, any change to latency I applied using RME’s soundcard settings window were immediately reflected within Cubase’s Sound Card settings and the audio set perfectly. Now within Cubase 12 I am experiencing the following issue:
1 - I change buffer size from 64 samples to 2048 on the Soundcard (due to playback crackling, etc.)
2 - In Cubase I STILL see the prior lower latency setting (for 64 samples) displayed
3 - When I go into Cubase and select the control panel for the RME and change these buffer settings from there, I no longer get sound., even after hitting Reset
4 - I tried this and changed back and forth a few times without success (restarted Cubase 12 too and it was still silent).
5 - I also set it to No Driver and then reset to the Fireface USB driver (RME) and Cubase 12 still would not accept the change and produce sound.
Again, this worked smoothly in Cubase 11. . . it appears it may not have been tested before the release of the new version ( I have been using Cubase since the 90’s).
I hope Steinberg can add this to your review/updates.
I do not experience any of the problems described by Todd with my RME Fireface UC on Win10. So he might have encountered a problem specific to his computer setup.
This having said, would you care to elaborate on your latency issues?
I also get similar issues when changing buffer rates and it doesn’t matter if I do it through cubase or the focusrite mix control itself.
Like you said, previously I could change buffer rates via either method and it just worked, perfectly every time. I’ve even done it in recording sessions with pro tools and logic dudes sitting next to me and remember them saying “hang on, how did you do that? You just changed the buffer size without needing to restart the DAW, the interface or even the whole machine”
Is this usually the way it works? We’re we lucky before? Why is this all of a sudden an issue in cubase 12?
Hello , same here, i can no longer change buffer size without rebooting cubase, or even my computer! its super anoying.
And i use to be able to record at 96 samples or even less, now i have no sound whatsoever until i put it at 256, (even in almost empty projects)
Anyone had similar issues?
Wow, I am experiencing this as well. I change the buffer size and it shows as if the change took place, but I its not working. The latency that I am getting (quite responsive btw) is the same if my buffer size is 96 as is it as 2048.
I’m thinking this is so important that if I cant get this fixed, I wont be able to use Cubase.
Right now I’m locked into a buffer in which Im not able to use my daw because a single synth clips my CPU. Insane cracks and pops.
I cant get around this and restarting does not seem to affect this. Any chance that there are any other workarounds?
Well I’m using a Steinberg Ur28m as an interface but yes. I can change the buffer size and (both in the interface software and the control panel within Cubase studio Setup) and a it shows the change, meaning if I change it to 512, it will say it’s at 512, but I get no change in CPU and there is no latency when playing keyboard. So I’m pretty sure the number changes but the buffer size is NOT actually being changed. I can’t get it to change no matter what.
If I change it to 2048 buffer size there is no latency. It’s like I’m at 128, right and snappy, but it overloads the cpu performance meter as I need to be higher at certain times.
I wish I at least had what you are experiencing and at least could change the buffer from restarting, but not even that seems to affect mine. I’m locked in .
I tried this in earlier versions of Q base, I uninstalled my audio interface software and reinstalled plus the Yamaha USB driver. I tried my other interface from another studio, which is an RMEUCX2 and even borrowed my other buddies in her face which is a Focusrite Scarlet and none of these gave me the ability to change the buffer size.
So I’m pretty sure the number changes but the buffer size is NOT actually being changed
I think you need to 100% confirm this. Turn off adjust for record latency, run a loopback test at 64 samples and one at 2048 and compare the placement of the two audio files on the timeline.
I suspect your issue is something else and this will confirm…of course the other thing you should always try if having odd behaviour is starting cubase in safe mode with prefs disabled.
Ok, I wasnt exactly sure how to do the loopback you were talking about but I turned off “adjust for record latency”. Then I imported an audio file. I made a “Print bus”, sent the output of thetrack to the printbus and then made that the input of 2 tracks. I recorded the first one at 64 buffer and the second one at 2048. Would this have shown latency? Theyre both dead onn, exactly the same. Not sure if the loopback would show something different.
That being said, Ive never been able to play the piano with 2048 buffer size ever. Not in 10 years have I ever been able to play properly with that amount of latency and with 2048 buffer, I am getting INSTANT (very low latency) response. I could play something super tight and rhythmic and wouldn’t feel anything. Thats the biggest red flag. I will try safe mode.
I know my interface (UR28M) has a loopback function, but I use it for monitoring apple music or youtube, but I wouldnt know how to use it to get something to replay at the exact time consistently.
Apologies…I just tested myself and this doesn’t do what I was assuming. The adjust for record latency is only affecting plugins on the recording tracks, not disabling the interface latency compensation.
If you’re a piano player rather than a sausage fingered occasional synth triggerer like me I guess you would definitely feel the difference. I just can’t imagine how this is happening across multiple interfaces.
Did you try the safe mode yet?
Also for clarity…I assume the piano is a vst?
I had the same problem with my RME UCX2, and post #9 in this thread was the sollution to both, the problem mentionned in that thread, and our problem here. Really happy to finally have solved this, thanks @SF_Green .
Try it out and see if it helps.
“In the RME Control Panel, set your WDM devices to 0. This assumes you have a system audio device if you need WDM. Cubase will then recognize your buffer or even sample rate change without closing and re-opening.”
Edit:
So it seems like turning WDM to 0 disables the ability of the RME to communicate with windows, so you can’t have sound besides when you work in cubase. So this is not the solution. I did some researche and asked Chad Geepeedee, and here is what worked for me:
1. Check for Exclusive Mode Conflicts
Windows can take control of the RME interface if Exclusive Mode is enabled in the Windows sound settings. This might prevent Cubase from adjusting the buffer size.
Steps to Disable Exclusive Mode:
Open Control Panel (Win + R, type control, press Enter)
Go to Sound
Click the Playback tab
Select your RME interface, then click Properties
Go to the Advanced tab
Uncheck “Allow applications to take exclusive control of this device”
Click Apply and OK
Repeat steps 3-7 for the Recording tab
Restart Cubase and check if the issue is resolved.
With this, it’s back to how it used to be maybe a couple of years ago : I can change the buffer size in Cubase flawlessly. However, after changing it in cubase, if you try to use windows audio, it will glitch out because there is a conflict. My sollution for this is to activate “release driver in background” in cubase, then bring some non cubase window to the foreground. Cubase releases the driver, and everything works again.
