strange thing happens..
when I select an audio track, everything works normal, but if I select an instrument track, cubase is making those “krechts” sounds…
it is the same on any instrument track, while playing the keyboard, or playing the project.
while the project plays, I move the selection from the instrument track to an audio track, and those sounds stop, and everything sounds normal again
Hi,
is automatic record enable for selected audio and MIDI tracks checked in the preferences (Edit/Preferences/Editing/Project & Mix Console)? Try to uncheck it.
Have you tried to increase the buffer size?
Hi,
Once you select the Instrument Track, the Record is enabled (by default: Preferences > Editing > Project & MixConsole), so the track becomes “live”. So it’s not pre-processed with the ASIO Guard and the Buffer Size, and the data is processed in real-time, so it needs much more CPU power.
I’m not sure what “krechts” means, but, if you mean sort of like a burst of static or crackling every so often, I saw something like this yesterday. It was a simple project, with only one instrument track (Arturia Pigments – latest version). It didn’t matter whether Cubase was playing back or I was just playing sounds through the instrument. I checked out the sample buffer size, and it was at the maximum (2048 samples since I work at 96 kHz), which made it all the more surprising. I tried setting it down to 256 samples (what I’ve typically tracked at with my older, much slower system), but it was the same.
I ultimately ended up shutting Cubase down, rebooting my MOTU 828x, then starting Cubase again with the same project. No more problem. So my thinking is that something must have gotten hosed up in the MOTU interface’s driver, or somewhere in the coordination between Cubase and the driver. It’s not something I’d seen before in Cubase 15 (on Windows 11), nor had I seen the exact same issue on my older WIndows 10 system, though Pigments (and several other Arturia virtual instruments) could have problems in breaking up when playing polyphonically.
yes, you were right,
when I unchecked record enabled it stoped making the sound.. but I use an m2 processor on my mac studio computer, with 64GB ram, one should expect it will have enough cpu to handle 32 samples of buffer size. and I actully see in the cpu activity monitor, that it is not using even 10% of its capacity..
First of all, it’s good news that the culprit could be identified and that there’s a workaround.
Record enabled shifts the processing of a selected track to the real-time path like @Martin.Jirsak explained including its routing and groups/fx involved. Which brings me to the question: what kind of VSTi, routings and fx do you see on the problematic tracks? Maybe there’s some 3rd party plugin involved that needs an update?
Do you have the issue you describe in the original post with a larger buffer like 64 or 128?