![]() ![]() Note that by default, simply clicking on them enables or disables them (Red/Blue). On the right hand side of mix control is a series of boxes representing the analog outputs, these need to be enabled in order to get any output from the Pro 40. Make sure that the outputs you want available to your daw are set as "DAW 1, DAW 2, DAW 3" etc. It does require setting routing up properly in Mix Control initially though, which can be pretty confusing. (Well.Technically it's always running since it's part of the Pro 40's driver, but you don't need to actually use it). I don't use Pro Tools, I use Reaper, but the only time I ever use Mix Control is when I need to make changes to buffer settings, otherwise I never open it up as it doesn't do anything useful for me on a normal basis, and Reaper has no issues addressing all inputs and outputs without it running. Just watch it over and over until it sinks in. That video really helped me start to understand what the point of the software is and how it works. I would suggest watching Graham Cochranes video about this on thr Recording Revolution channel. It can be a little intimidating at first but the more you use it, the more it will make sense. MixControl gives you a ton of flexibility with how you want to setup headphone mixes and hear what you want to hear in real-time. This is the beauty of the MixControl software because it is zero-latency monitoring that is independent from pro tools which I think is amazing. If you monitor inside pro tools, you will experience latency even if you take the h/w buffer size down as low as you can get it. You can use MixControl as your zero-latency mixer and bypass all the monitoring inside pro tools (which i recommend), or you can bypass the MixControl mixer and monitor everything inside pro tools. In terms of using it with pro tools, you have two options. I've tried trashing both "MOTU Audio System Preferences" and "Preferences" from the DP Preferences folder and relaunching, but it doesn’t help.Well, first off, you do have to use the MixControl because that is the driver for the interface so it does need to be open and configured correctly to use the interface. I know the Saffire (see sig below) is behaving OK because it's already set to 96000 bps for both input and output - I've checked this in both Audio MIDI Setup and Safire MixControl - and it's working fine with other software. This goes on until I eventually click Cancel in one of the dialogs, after which of course I have no audio. If I click OK in either dialog, I just get back, after a delay, to the same error alert. ![]() These are both as I always have them, I'm pretty sure (though I must admit, I seldom tweak anything in the Studio setup). Pre-fill file buffers for Quick Start: checked The options are Hardware Setup and Studio Setup, neither of which helps because they're both already on the correct settings as far as I can see:Ĭonfigure Hardware Driver shows CoreAudio (the only option) at the top, with Saffire selected in the list, then:Īutomatic Plug-in Latency Compensation: checked (MotuAudioSystem Mas MasCoreAudioWorkThread.cpp, 148 )" (The two numbers in the vary.) If I try launching DP or opening an existing project that uses audio (or going to Setup -> Audio System -> MOTU Audio System), it goes through the usual plug-in loading procedure, then there's a long pause after WahPedal, and I get this alert: I have run DP successfully since the upgrade - just playing back my last project by way of testing - but now I can’t get anywhere. Just about to start on my first serious project since upgrading to DP8, and the MOTU Audio System refuses to load.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |