- #Saffire mixcontrol program mac os#
- #Saffire mixcontrol program drivers#
- #Saffire mixcontrol program pro#
Having LED meters, as opposed to just a single LED that only lights to show the onset of clipping, helps diagnose problems by confirming that a signal is present, even if it cannot be heard, therefore narrowing down the source of the problem. Five-step input LEDs give a clear indication of the signal level, helping to ensure that a healthy signal level is going into the unit. Focusrite even include a reverb plugin, along with compression and EQ plugins too.Īnother noteworthy feature is the LED display. This in itself would have been good but Focusrite, through their Mix Control software, allow different mixes to be sent to each headphone output, along with effects as well! This means, for example, a vocalist could have some comfort reverb added (but not recorded) to his/her mix, while the engineer could have a dry mix.
One such feature is, as already mentioned, the two headphone outputs, each with its own volume control. However, the Saffire has some features that make it stand out from the crowd. I’d really like to be able to get back to how things were in terms of stability.There is an abundance of audio/midi interfaces on the market using USB or Firewire, so the choice can be overwhelming. Happy to help with more information if needed, I already tried a lot of different things to try to improve this situation.
#Saffire mixcontrol program mac os#
I think maybe something changed on the Mac OS side that means mixed audio rates playback is not handled properly. I previously had problems with apps that try to force output streams to 44.1kHz (I’m on 48kHz) and I wonder if it’s less problems of this kind if I stick to 44.1kHz for everything in the future.
This is an issue when using other audio apps alongside cubase (e.g.
#Saffire mixcontrol program drivers#
But there is something about cubase’s interaction with Saffire drivers on MacOS that wrecks normal browser/iTunes playback on my system (even if cubase itself works fine). Thanks for this, I think the problem I have will be worse for those using the bigger interfaces and those in dual interface mode, because I notice that increasing the latency can help avoid issues. It will be difficult to track all this down, but please keep reporting. So with the postings so far, it doesn’t seem that we have a general problem with the Saffire, but we do have issues on different individual machines. Didn’t used to have to do that, but something changed and I never found what! And it’s a solution that doesn’t work for every job.Ī quick try of C9 shows them behaving same as C8.5. But still can happen.įrustrating … but I usually end up routing system sounds away from the DAW interface to work-around. It’s less likely to happen if cubase uses a longer buffer setting. The saffires worked perfectly with cubase until about a year ago, at which point they both became a lot more fussy about a) clocking and b) multi-client operation.īrowsers, iTunes, CV tools etc can have distorted / crackly operation while Cubase is running, even if cubase itself is working fine.
#Saffire mixcontrol program pro#
I actually had a second pro 40 but I exchanged it for a Scarlett, because there’s some problems with the midi output on the Saffires. (and please also tell which Cubase version you’re on) Is there anyone out there who works with a Focusrite Saffire Pro 24 DSP in conjunction with Cubase? I’m sure there must be.ĭo you have or had any issues with that Focusrite interface? In a different forum some user reports crunching/crackling noise in the audio as soon as Cubase 9 is running (even in the audio output of other programs).Ĭould people please speak out that even don’t have any issue with their Saffire and Cubase?
0 kommentar(er)
