I'm running a MacBook Pro with M1 Max Pro chip and 8TB ssd for audio/video production.
Trying to record DAW tutorials for music production using Cubase 12, porting audio into OBS via Loopback (to control exactly which mixing board channels will be recorded from Allen&Heath Qu16 mixing board).
Running a big mix... 20 virtual instruments, 30 tracks+ is no big deal for this machine. And for video I'm recording from a 1080p webcam and window capture of the DAW at same (1920x1080) and outputting to mp4 at same. No problems with the video... all smooth as silk.
But there is intermittent crackling in the audio (digital dropouts) about 30% of the time when I start playing Cubase. This NEVER happens when OBS is not running.
I have increased the buffers in Cubase massively as well as set 'ASIO guard' to high. Still crackling. The audio performance meters in Cubase are under 20% cpu load and less on disk load (everything is on SSD).
Any ideas how I can resolve this OSB problem? Can't be a load issue because the machine is barely breaking a sweat here. Has to be some kind of unhappy software problem.
Trying to record DAW tutorials for music production using Cubase 12, porting audio into OBS via Loopback (to control exactly which mixing board channels will be recorded from Allen&Heath Qu16 mixing board).
Running a big mix... 20 virtual instruments, 30 tracks+ is no big deal for this machine. And for video I'm recording from a 1080p webcam and window capture of the DAW at same (1920x1080) and outputting to mp4 at same. No problems with the video... all smooth as silk.
But there is intermittent crackling in the audio (digital dropouts) about 30% of the time when I start playing Cubase. This NEVER happens when OBS is not running.
I have increased the buffers in Cubase massively as well as set 'ASIO guard' to high. Still crackling. The audio performance meters in Cubase are under 20% cpu load and less on disk load (everything is on SSD).
Any ideas how I can resolve this OSB problem? Can't be a load issue because the machine is barely breaking a sweat here. Has to be some kind of unhappy software problem.