Pro Tools must be restarted for these changes to take effect. Every time I try to change this, I get this message "ASIO device properties have been changed by the device control panel. I go into the Pro 40 software (called Saffire MixControl) and change the ASIO buffer size to a higher number (I've tried 1024 samples all the way to 3072 samples). So, I figure that maybe I need to increase my audio interface's buffer size manually to match Pro Tools' 1024 samples. So, I increased the buffer size to its highest, 1024 samples, and I tried tweaking everything else in the playback engine dialog, and nothing changes. In most cases, a larger HW buffer size will prevent the problem." If this occurs often, verify your sync cables or try changing the HW Buffer Size setting in the Playback Engine dialog. As I said, a number of people on this forum recommended this hardware for me, so I expect this to work.įurthermore, if I ever try to press play in the Pro Tools transport controls, whether if attempting to record audio/use MIDI, or not, I get this error message: (-9129) "Audio processing could not complete due to conflicts with other CPU tasks or a potential clocking issue. However, there is some major compatibility issue with Pro Tools. So there's nothing intrinsically wrong with my audio interface, since it works on its own with my computer. The input meters are not affected, but the DAW meter in my audio interface software is lit up very high. Whenever I open a session, new/old/whatever, there is an incessant buzz of clicks from the audio interface. The software interacts perfectly with my mic/line inputs, but the problem begins once I start Pro Tools. Now it does, and the audio interface's software works fine on my computer. Before I got the PCI card, my audio interface would not connect to my computer. It uses firewire ports, which connects to a SIIG Firewire 3-port PCI card (Texas Instruments TSB43AB23 chipset, highly recommended to me) on my computer. I have Pro Tools 10.0, the student academic version, and when I asked for advice earlier on this board for an audio interface, I was recommended the Saffire Pro 40. I'm still in the process of trying to start a Pro Tools recording system, and I am a novice with getting everything straightened out. I'll try to explain this the best I can, but I am hardly an expert, and I don't know at all of how to fix this problem. The firmware and driver update should now be complete! If you accidentally skip the firmware update at the end of the installation, you can run the update from within SaffireControl PRO by selecting 'Update Firmware.' from the 'Hardware' menu.Hi.Run the firmware update which appears at the end of the installation process.Important Installation/Updating Information! Please follow the steps below to update your Saffire PRO firmware and drivers:."Desired" and "Active" digital sync states.Saffire PRO version 2 includes several major changes including:.Resolves an issue with the firmware updater in Mac OS Leopard and Windows XP service pack 3.Added metering disable option to the contextual menu.Fixed a problem with syncing to S/PDIF.Added support for Vista 32-bit Saffire 2.3.Co-installer added, allowing for easier re-installation.Fixed a problem with the DSP firmware update. Fixed a crash in SaffireControl upon closing of effects Saffire 2.5.The firmware updater can be found in Program FilesSaffire on Windows or in /Applications/Saffire on Mac OS. NOTE: Once you have installed the Saffire software and drivers, you will also need to run the firmware update. Windows 7 users should note that legacy firewire drivers should be installed BEFORE connecting and installing ANY Saffire devices on their system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |