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. This is another common error on Pro Tools that can occur in a wide range of circumstances.
Pro Tools ran out of CPU power. Try deactivating or removing Native plug-ins. AAE error Pro Tools This can occur if you are pushing the CPU too hard.
If using a Click Track in Pro Tools Avid report this problem was resolved in Pro Tools The temporary workaround is to render the click using Commit or offline bounce and import after bounce deactivating the Click Track. If this error is occurring with a real-time bounce, try enabling the Offline option in the bounce dialog box or bounce to a track, rather than use Bounce To Disc. This error code can be caused by a plug-in. Track down and remove the offending plug-in and should be good again.
The troublesome plug-in doesn't have to be in your session. Just being in the Plug-ins Folder is enough. It seems to manage the sudden CPU spikes that can trigger errors.
Some Windows users have reported improvements when Hyperthreading is turned off, although it would seem this is much less helpful for Mac users. Avid even went as far as to canvas Pro Tools users with a customer survey on errors especially on Windows 7 and 10 systems. There is a post on the Pro Tools Ideascale on this too. Real-time bounce to disk fails with an AAE error.
Avid reports that this was fixed in Pro Tools But suggested workarounds for previous versions are Check Your Plug-ins - errors can be caused by having older plug-ins in your plug-ins folder. So check your plug-ins and make sure that they are all up to date. This is a Windows-only error and seems to be more common when trying to use Pro Tools First for the first time.
If you get an AAE Error message then the advice is to right-click on the Pro Tools icon and choose Run as administrator this gives you the appropriate permissions to run Pro Tools. AAE Error is also plugin related. The most common reason for this error is that there is at least one plugin in your plugin folder that has not been activated. Another user had reported having the same problem with these plugins and it turned out that the plugin was not registered….
The time the error occurs is when Pro tools loading up. It loads up to varifi then access violation occured, unable to read location: 0x pops on the screen.
This is a video forum. You will probably have more chance of help from the audio forums here:. The v1. Right click Protools app and go to properties. Check run as administrator. Head over to the compatibility tab and no matter what windows you are running check the box and run compatible for Windows xp.
Apply changes and restart protools. I tried everything suggested and got no where. This was the only thing that worked for me. Opened right up, allowed new sessions and opened old sessions with no problems. Forums » Community Help Center » Community Issues and Suggestions » Access violation occurred, unable to read location: 0x Latest post Tue, Dec 11 PM by ajpryor I also notice it seems to occur after the last file is written.
For instance, this used to occasionally occur after I would write a Drumagog 4 file doesn't happen with D5. By immediately deleting the pass of D4 that I just wrote, the error would go away. I have to say I have had absolutely no problems with my different audio cards - the Core audio picks it right up with no issues. It's solid, invaluable.
Thank GOD I decided to take the plunge. Top Mentioned Manufacturers. Facebook Twitter Reddit LinkedIn. Subscribe to our Newsletter. By using this site, you agree to our use of cookies.
0コメント