- #Pro tools playback engine windows audio device how to#
- #Pro tools playback engine windows audio device install#
- #Pro tools playback engine windows audio device driver#
- #Pro tools playback engine windows audio device code#
#Pro tools playback engine windows audio device how to#
Here’s a quick tutorial on how to disable all sound and recording devices in the Playback Devices menu before starting Pro Tools: If this workaround works, you can re-enable all the disconnected audio and recording devices (with Pro Tools running) and use the audio suite as normal.
![pro tools playback engine windows audio device pro tools playback engine windows audio device](https://i.ibb.co/cLnzQSc/pt-output1.gif)
Several users who have encountered this problem have confirmed that they were able to resolve it by going to the Playback Devices screen and disconnecting all currently connected sound and recording devices before restarting Pro Tools.
#Pro tools playback engine windows audio device code#
If this problem occurs on a Windows computer, this error code may be caused by a conflict between your ASIO-compatible device and the built-in sound devices. Disable all sound and recording devices (PC only) If you still see the same 6117 error, or if the Playback Engine screen does not appear at all, go to the next suggested solution below. When this screen appears, select the Avid device, then press OK and check if you can use PRO Tools normally. This will bring up the Playback Engine screen, where you can select the AVID device. Some users who also encountered the -6117 error reported that they were able to completely bypass the error code by pressing the N key immediately after starting PRO Tools. To do this, right-click on the Pro Tools home screen and select Run as administrator from the context menu. It may be helpful to open Pro Tools with administrator privileges. How to solve the Pro Tools “AAE Error – 6117”īefore proceeding to the other troubleshooting steps below, first, check to see if you can force the Playback Engine window to appear on the Pro Tools home screen. If you are experiencing this problem on a Windows computer, it is likely that this error code is caused by a conflict between your ASIO device and the built-in audio devices. It is probably happening on a Windows machine.įor this reason, at the beginning of this troubleshooting guide, you should make sure that you are using the latest version of the audio interface driver.
#Pro tools playback engine windows audio device driver#
This error means “no device” and is probably due to a missing driver for your interface. “AAE Error – 6117” when using Pro Tools First. What causes the “AAE Error – 6117” error in Pro Tools?
![pro tools playback engine windows audio device pro tools playback engine windows audio device](https://venturebeat.com/wp-content/uploads/2019/09/office_365_2.png)
#Pro tools playback engine windows audio device install#
You just need to follow a few simple steps and eventually install the universal audio driver. However, some users still report the error code AAE 6117.įortunately, the solution to AEE error 6117 is quick and easy. They claim that this problem should no longer occur in Pro Tools First 12.8.2. It usually occurs when another application or process uses an audio driver.Īvid eventually solved this problem in subsequent updates. This is one of the most common error codes for Pro Tools First users. It is recommended that you select a different audio device.īasically, this error code indicates that Pro Tools was unable to detect or work with the audio driver installed on your computer. The AEE 6117 error indicates that Pro Tools was unable to initialize the selected audio device. Understanding what the message means is the first step in fixing any error code. If you don’t know how to solve this problem, there are several troubleshooting steps you can take to fix AAE Error 6117 when using Pro Tools. One of the most commonly reported errors is AAE Error 6117, which is an audio driver problem. Pro Tools is one of the most widely used DAWs, despite some known limitations and bugs.