So I installed a new interface, Orion 32+.
Cubase 14 cuts all above 10k on inputs. Cubase 13 works just fine and all other DAWs as well.
I’ve attached a video with the problem. Just add YouTube.be/ infront
ot_Sp7hqfYU
So I installed a new interface, Orion 32+.
Cubase 14 cuts all above 10k on inputs. Cubase 13 works just fine and all other DAWs as well.
I’ve attached a video with the problem. Just add YouTube.be/ infront
ot_Sp7hqfYU
Sample rate mismatch by accident? Like the one that cuts highs is set to 22k instead of 44.1 or higher?
In the video you can see that the settings between Cubase 14 and 13 are the same and I’m not changing anything in the interface.
Ah, ok.
Your video link doesn’t actually “link” for me when I click on it. Just type out the address or add a direct link or something.
Ok.
Maybe try to open up C13 and run the test generator using white noise instead of a sine wave, and then record that into an audio file. Then import that audio file into C14 and see what the behavior is by using a spectrogram to verify the frequency response.
That way you avoid the possibility of the test generator being broken.
I suppose you could just record a sinewave sweep instead if you prefer sine waves for testing.
Thanks. Can you explain exactly what I’m looking at though, in terms of the signal chain? It’s not clear to me.
Its Orion 32+ gen 4 connected to itself from output 4/3 to input 4/3
I think you misunderstood what I meant. Record the file in Cubase 13. If you do that, and if Cubase 13 works as it should, then when you import that into Cubase 14 and just play it back it should be full range there as well, right? I think I’m seeing the recorded file having that low pass applied, so that means that either the problem is in playing back of audio files in Cubase 14, or you recorded in Cubase 14 instead of Cubase 13.
The only other thing I can think of is problems with phase and a doubled signal somehow. I would make sure (since it isn’t clear to me) that you are sending out a single mono signal to one output, and just to make sure record that signal onto a different numbered input, so for example out 3 in 4. Just to avoid any potential mistakes.
That’s pretty much all I can think of now.
Sorry for not being clear on explaining, it’s not my best side :). I would agree with you that it is some sort of phase cancellation. But when I try out the same experiment on 44100kHz instead of 48000kHz it cuts all above 5-6 K, so I believe there is some misalignment on sample rate somewhere.
I’ve patched (physically on patchbay) output 3/4 directly to input 5/6 and still the same result.
Send out a mono signal through just a mono path, not “left only” in a stereo path. In other words create two mono audio tracks, create a mono out and a mono in, and do the test that way. If that’s different and gives you a correct result then maybe the signal is getting cross-fed at some point after Cubase 14. In other words suppose you are able to pan a stereo output’s individual channels center. I know that sounds “dumb” but in some applications that’s actually possible.
That’s why I think the entire chain would benefit from being entirely mono. And it’s interesting that even though the response is limited the actual signal peaks higher.
Very strange. I got nothing.
Thanks for trying to help. Really appreciate it. I still think it’s something internal in Cubase 14 engine as all other DAWs work perfectly fine and even Cubase 13.
For what it’s worth I use an Orion 32+ Gen 4 here with Nuendo 14. I’m not getting the issues you’re experiencing.
However, I’m on Windows 11 and the unit is connected via RME MADI.
RME… solid as usual.
I guess it’s time for me to move to protools. Hate to do it after 24 years with cubase. Know every menu and every shortcut in muscule memory.
Isn’t that a bit of a weird move? Switching to Pro Tools? So everything was fine until you got the Orion, and now you blame Cubase?
Cubase Pro 14 and Orion 32+ (1st gen) on a Mac Studio (M1 Max) here and I have no issues like anything that the OP describes and frankly clueless as to why the issue is limited to CP14 and no other DAW. Any word from Antelope tech support? They can be decent to deal with.