Optimize Windows XP for Firewire &USB Audio Interface during RecordingĪudio Dropout and MultiTrack Recording Latency Troubleshooting Guide Windows XP/7 Audio Recording DAW Tweaks & Optimization Tips For details about optimizing PC for audio, Firewire and USB, you can refer to the following tutorials below: The settings above don’t have any problems with REAPER for both playback and recording in an optimized environment. For example, there is no latency, drop out and pops/click issues using the ASIO buffer size of 512 and driver latency of medium.īear in mind that this depends on the power of your computer hardware, the quality of your DAW and the optimization of your PC for audio. The default settings work out fine after installation. Make sure you set the correct sync source if you are connecting digital inputs.įor most of the time, you would not need to deal with these settings. Digital inputs are usually SPDIF or ADAT. This means there are no digital inputs connected to Saffire pro 40. The normal operation is to set this to internal. But if you would like to select different recording bit depths it would now be done in your DAW software.Ģ.) Sync source – digital data needs synchronization methods. By default, professional recording interface such as Saffire Pro 40 would be using 24-bits. It would be surprising that you do not see options for bit depth. Take note that recording using this sample rate would be consuming a lot of disk space. 44.1 KHz is sufficient for most audio recording applications.ĩ6 KHz is for high-fidelity recording and suitable for any high-end applications. Most recording applications for TV and film would be using 48 KHz as the sample rate. If you cant get output signal after all of that, then I suppose it's possible it's a driver issue, or an issue that Pro Tools has with the Pro 40.There are 4 ways you can adjust the sample rate and these are: 44.1 KHz, 48 KHz, 88.2 KHz and 96 KHz. In order to bypass this, SHIFT click the little output squares, now instead of being blue or red, they'll go grey, which means this is now a normal output and no longer a monitor output, and the pro 40 will send out max volume (+4 dBu) signal from these outputs.(*EDIT: DONT DO THIS ON OUTPUTS 1/2 OR YOU'LL BLOW UP YOUR SPEAKERS/EARS! Unless of course you use something else to feed/control your speakers, in which case. which in most cases, will be a very weak signal, since I doubt too many people monitor at full volume :). Which means if you use the knob to control monitors like most people, having it control ALL the outputs means the outputs will be limited to whatever the knob is set at. In this state, the outputs are controlled entirely by the "Main Mix" knob on the front of the Pro 40. 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. 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.
0 kommentar(er)
