I remember having a similar error problem come up earlier in the year. Its always good to use the kext utility to refresh or repair things. Also, which version of PT9 you using? Since updating to 9. Worth a try? Click to expand Hi, I had the same problem I'm using an onboard sound device, so i can't test it with an external device. I solved moving my entire project to desktop, because i was working on a Verbatim external USB hardrive. So, i moved the entire project, kext utility, restart my hackintosh, and bouncing at this moment!!!
Hope it can be usefull to someone with the same error. Pro Tools 9 is where avid really got anal about a few things. Despite opening PT to work with "any" audio interface, older digidesign equipment which has already had support dropped is still unsupported at best some won't work at all. That being said, 9. RickydB said:. Any updates on the solution? Seems like I've tried everything by now. Nothing really seems to make the problem dissapear entierly.
One possibilty is that the onboard firewire interface is the culprit. I'm going to try with a separate PCI-Card tomorrow to eliminate this possiblity. If this is a no-go I'm really interseted in hearing other solutions! Never, ever open the internet while Pro Tools is open. It is preferable to not use the internet at all on your Pro Tools computer unless you are downloading or updating recording software or sending tracks or mixes.
Otherwise, do not open up a web browser anywhere near Pro Tools. Your experience may be different but this was and has been mine. Since I instituted the no internet on the Pro Tools computer on mission critical days, I have not had many problems. If you do start getting crashes because use of the internet was unavoidable of the computer has been under heavy usage and is very hot another potential killer for smooth operation of Pro Tools you must shut down the computer completely and allow at least the aforesaid ten minutes, sometimes even more.
My conclusion is that it is neither the hardware nor the software that causes this problem but rather the idiosyncrasies of how software and hardware interact. This is particularly so on older machines or, at least, so it seems.
Part of the problem is that the software has become very complex and the machines are becoming underpowered. It does seem that those with next generation machines that have minimum quad core and 32 gigs ram are not having these problems. Those with older quad core machines and maximum 16 gigs ram need to be a bit more careful.
These are large sweeping generalizations but at least its an idea. I had my software and hardware checked, re-checked, uninstalled, fresh installed, newly installed, re-installed and everything else you can imagine and nobody could find a problem with either. It was not until I started noticing that the machine could operate Pro Tools well in the morning if I did not first use the internet and that when it did falter a shutdown of at least ten minutes corrected the problem.
I believe it related to a buildup of charges in the devices component as well as a build up of heat. That is all I can add to this. Not very technical but it works for me. My Studio. I posted this on another forum but the answer might apply here too as nobody has mentioned it yet Been having the same issue on I went into the little menu at the right hand side I think its called the regions menu or something I went there selected all unused audio and removed them from the session I didnt move them to trash immediately my whole session changed.
I do t know if that will help some people who are having it with 5 tracks going and such but if you are just at the end of a mix and everything is going to hell try clearing your unused regions.
Today I was able to get this error to stop by disabling WiFi. It's a recommended best practice from Avid, but I don't always have to do it. For some reason today the errors were fierce, even on sessions with a single dialog track. Using the ethernet via thunderbolt display continued to work fine. Top Mentioned Manufacturers. This is another known example of where Pro tools can report a error. While playing back Pro Tools 11 and listening to audio from the internal headphone output from a MacBook Pro computer, if the headphones are unplugged a error may occur.
If the headphones are disconnected while Pro Tools is idle and not playing back, audio may no longer come out of the speakers on the MacBook Pro. To resolve this, either plug the headphones back in to continue monitoring audio, or restart Pro Tools to hear audio from the built-in speakers on the MacBook Pro. This is likely to be on a Windows machine.
Download and install the driver for your audio interface download drivers for Avid interfaces. Hold the N key down immediately after launching until the Playback Engine window opens to select your device.
If the same error occurs, Avid recommend you try the following Right-click the Speaker Icon you can see on the lower right side of your screen. Then, click Playback Devices. Do the same in the Recording tab beside Playback on top of the dialogue box After all the Playback and Recording devices are disabled, try to run Pro Tools First again.
If it runs, you can enable all the sound devices again. Although the error is most likely to happen in Pro Tools First, it can happen in other versions of Pro Tools when it cannot find an audio interface.
One user with Pro Tools Finally, re-activate the correct audio device and drivers and it worked fine. Please choose another audio device. Their fix was to go to Playback devices on the Windows toolbar and make sure the Apollo was enabled. Then go into Recording devices and make sure the Apollo was disabled. The most likely reason that an AAE Error would pop up is that you have an out-of-date plugin in your plugin folder.
More specifically a bit plugin in a 64bit version of Pro Tools. Prior to Pro Tools 10 all plugins, as well as Pro Tools, were bit code. Pro Tools 11 was the first version of Pro Tools that was bit and so this error was very common in the early days of Pro Tools However, it is possible to install an older bit plugin and so trigger this error message. The solution to a Pro Tools AAE Error message, is to make sure you have the latest version of all your plugins installed.
This is a weird one as the suggestion in the error message is completely misleading. Either way, what this may actually mean is that Pro Tools is looking for a missing file or drive, which might occur if the session's storage device becomes unmounted. The advice is that you ensure the session's storage volume is still available, and then quit and relaunch Pro Tools. There is no way to adjust AAE's preferred size.
There are usually two main ways Pro Tools reports errors DAE can't get audio from the disk fast enough. Your disk may be too slow or too fragmented. The leading cause of the error is recording, playing back, or bouncing to a drive that is literally "too slow or too fragmented". A lot of the advice relates to older computer systems with Firewire or USB drives etc. In my experience errors come up at the point Pro Tools cannot get all the data on and off the session drive fast enough.
That can be because the data is too fragmented, ie bits of the audio file are spread across the drive, but again things have moved on so much that fragmentation isn't always the issue. Also, the reasons for error messages can be many and varied, but can include the fact that the computer is too busy to serve Pro Tools in a timely manner, which could be background applications running and so on. Disk too slow or too fragmented" is a variation on the same problem but in this case, it is the PCI bus that is getting clogged up so that Pro tools can't get the data fast enough.
Disk Cache came to Pro Tools Vanilla in version Even so, it is still possible to get errors with Disk Cache. Avid recommends that you wait until Disk Cache has finished caching the timeline to begin playback.
Check your Disk Cache settings. Some users have reported that if it is set to Normal Pro Tools can still produce or errors. Increasing the Disk Cache to say 10GB providing you have the memory for it may resolve the problem. Look at any application that might be scanning drives creating catalogs etc, as they will make the hard drive have to work harder.
Spotlight indexing has been found to cause "disk too slow" errors while recording in Pro Tools. You can disable Spotlight indexing:. Audio tracks with lots of edits, as can be created when using Beat Detective, can also cause errors. Bounce to disk, Consolidate, or using Track Commit all can help. If you have a lot of tracks in a session then consider splitting your audio tracks up across multiple drives to prevent this error.
Partitioning large drives into volumes no larger than around 9 gigs in size can help prevent fragmentation. But partitioning drives can also cause issues and again this largely relates to older systems. Large drives now rarely need partitioning for performance reasons.
Firewire drives have been known to cause errors. AAE Error is likely to pop up when you are attempting to Destructively Punch into or process a file.
It indicates that an attempt has been made to write to the same file multiple times during processing. The advice is if the error occurs repeatedly when attempting a particular operation, quit Pro Tools and reboot the computer. Then try again. This error usually pops up when the hardware buffer size is too low and relates to other CPU Overload Errors at Low Buffer Sizes, but the key issue is low buffer sizes.
In the Pro Tools When using Pro Tools In the dual 6-core CPU example, the desired Host Processor setting to avoid errors strictly related to this bug would be However, this bug is not known to occur on single CPU configurations.
A DAE error can be encountered when recording large track counts at high sample rates and low buffer sizes with the HD Native Thunderbolt interface, Pro Tools This is an issue specific to the non-Retina MacBook Pro computers 8,1 8,2 and 8,3.
Use a different computer Retina MacBook Pro computers do not encounter this error. Turn Disk Cache off while recording at higher sample rates.
0コメント