Two midi keyboards worked flawlessly before the latest windows 11 update. Keyboards are in tune with each other but a c note played on my guitar is not a C note on the keyboard. Guitar tuners are correct. Keyboards have 0 (zero) transpose. The note that is playing now is not even a half or whole note off. Something in between notes. Checked the settings in Cubase and everything looks ok there. Anyone find a solution.
Hi and welcome to the forum,
Make sure, there is no Sample Rate mismatch. Make sure the Project and the Audio Device are using the same Sample Rate, please.
We get this problem a lot in my college. A keyboard can randomly start transposing. Only began since the switch from Cubase 7 to 11. Not sure if it’s a glitch or if the students and myself are hitting a key switch somewhere. But it is strange that it’s a problem that we never used to have, and rarely if ever seen in over 10 years of working with Cubase 5 & 7. Now is a daily occurrence.
Hi,
Did you double-check the Sample Rates, please?
What kind of keyboard do you use? Isn’t it sending PitchBend by any chance, please?
Project > project setup > Sample rate | There adjust your sample rate
Hi and welcome to the forum,
This happens if your Project Sample Rate doesn’t match the Audio Device Sample Rate. If one of them is 44.1kHz and the other one is 48kHz, then is shift is around 2 semitones.
It’s not a sample rate issue. This is happening while working in the middle of projects, to certain VST instruments where everything has been harmonising fine until a certain point. and the midi hasn’t been moved so still harmonically makes sense but sounds awful unless you delete the instrument and copy and paste the midi back in. For example might have horns piano and strings, and only one will go out of tune. If it was sample rate they’d all be out of tune with real instruments but they would still harmonise with each other evenmn if it did sound a bit odd. Not only is it irritating from a work flow point of view, but if you’ve adjusted the parameters of the instrument, you’ve basically lost all of that work. Midi keyboard is the Oxygen 49 as a USB going straight into the PC with a M-Audio 192/2 I think is the specific name of the sound card.
1 Like
Hi,
Make sure, your MIDI keyboard doesn’t send any unwanted Pitch Bend data. I have seen several M-Audio doing this already.
When this happened to me once, I found that in the midi editor the transpose was set to -2. When I set it to 0 the pitches were correct.
I just ran into the same problem today with the latest version of Cubase 15 Pro I am using the Roland AE 30 pro wind controller but as Martin suggested I am going to check the sample rate in my audio interface and project set up I hope this solves it because I can’t finish this project I need to submit.
Alan Russell
1 Like
I submitted a post a few days ago with the same- sounding problem. Not a keyboard or Cubase transpose or sample rate issue.
The problem arose in the middle of working on the project, and resolved itself for no known reason either, though it was after I finally sacrificed a 
, and burnt some offerings, coincidence?, who’s to say.
In case it helps, there’s nothing in the original update from OP or even in the recent MIDI updates which would result in something like this.
Lots of folks think of a Windows Update as the last thing that happened because these are always a big-ish event. But almost always, there were other things in-between.
Pete
Microsoft
2 Likes
Is there a way to go back to the CUBASE 15 pro previous update I need to find other options I have a project that needs to be submitted
Yes, multiple users have reported audio issues—including popping, distortion, and forced sample rate changes
—following recent Windows 11 updates, particularly with Realtek audio drivers and external audio interfaces. The issues often involve Windows 11 overriding user settings, forcing 48kHz, or limiting options, causing conflicts with DAWs or audio software.
Common Issues and Symptoms
-
Forced Sample Rates: Windows may automatically switch sample rates (e.g., to 32kHz or 48kHz), rendering, for example, a 44.1kHz or 96kHz interface useless for certain apps.
-
Audio Distortion/Crackling: Involuntary changes in sample rates or conflicts with audio buffer settings result in robotic, distorted, or cracking audio.
-
Broken Functionality: Some updates have caused total audio failures (static/no sound).
-
Bluetooth Limitations: Reports indicate Windows 11 may lock Bluetooth devices to 48kHz, while Windows 10 allowed 44.1kHz, causing audio issues in some apps.
I decided to run an experiment with this intonation issue with regards to my wind controller the Roland AE – 30 pro. I am going to assign the SWAM trumpet by Audio Modeling to run it in a blank project in cubase 14 pro the last updated version. I double checked my sample rate and everything is aligned. Please note that I am using this running on the Windows 11’s latest update I reinstalled all of my drivers for my FOCUSRITE audio interface and USB drivers for my Yamaha Genos midi keyboard.
Verdict: I do believe it’s a Windows 11 problem let’s keep this thread going we need to get this solved
Alan Russell
It may not seem like an important distinction, but it’s needed for troubleshooting.
Windows doesn’t change the sample rate: apps and ASIO drivers do. We’ve been asked for a way to lock that down, but it will break so many drivers if we do that. Nevertheless, it’s still under consideration.
Non-ASIO apps will normally, if not in exclusive mode, just go through our mixer and not change the sample rate. ASIO drivers can generally do whatever they want. Example: If you load up an older project in Cubase with a different sample rate, it’ll change the device sample rate, because ASIO always wins. You can then get stuck trying to change that back after you leave the project.
Best practice, when possible, is to keep your Windows sample rate settings the same as you normally use for ASIO, and to record most of your projects at that sample rate. (I know this can vary by project).
Pete
Microsoft
When your sample is a “C” concert flute and you play it using a wind controller with the C fingering and the note that is being heard as a B natural, then Houston we have a problem
A good plan is to go back to an older Windows 11 update and see what happens
If you draw a note in the Key Editor and play it back, what pitch is heard?
Mlib- i’ll get to that in the morning my studio is closed for the evening
all I could tell you is that before that windows update my project was in C major but after the update when I played the wind controller it was playing the soounding notes a half step down but on playback, the original project was sounding C major all the way And even in the new score editor the notation were notated correctly
Assigning note C to the key editor sounds C on the keyboard
I resolved my issue with my SWAM library using the Roland wind controller and CB 15 Pro For some reason unknown the latest windows update changed the SWAM Gui midi template using the Roland aerophone to a Keyboard default which is incorrect producing incorrect musical notes, it has to be assigned to the Roland Aerophone template and that corrected the problem For my latest project I made sure that template was correctly assigned to all of my wind swam instruments The swan string sections are always assigned to the Keyboard default
Alan Russell