(818) 308-4607 Los Angeles, CA
This is a list of all error messages supported by the Error Lookup function in Crash Analyzer.
2 GB file limit exceeded | Avid Media Composer |
3x crash service down | Compressor |
A database is corrupted | Final Cut Pro X |
A file of this name already exists | Final Cut Pro |
A serious error has occurred! It is recommended that you immediately save your work and restart the system | Avid Media Composer |
AAFDomain: Failed to open file for reading | Avid Media Composer |
AAFExportMedia() - Unhandled descriptor type. Neither Video, Audio, or Data | Avid Media Composer |
AddMediaSample Failed | Avid Media Composer |
ADM_COREAUDIO_UNDERRUN | Avid Media Composer |
ADM_DIO_ERROR_OCCURRED, DIOerr: Flamethrower timeout | Avid Media Composer |
ADM_DIO_ERROR_OCCURRED, DIOerr: No valid input signal | Avid Media Composer |
ADM_PLAY_NOT_ARMED | Avid Media Composer |
Adobe Premiere Pro failed to return a video frame. Canceling the operation | Adobe Premiere Pro |
AMEResourceManager::ReconfigHW_LegendBoB_play()Error [2147483657] unable to: legendBob->SetIOMode | Avid Media Composer |
AMEResourceManager::ReconfigureRasterSize() Error [2147483656] unable to | Avid Media Composer |
An error occurred loading database | Avid Media Composer |
An error occurred while configuring QuickTime using the current capture preset. Please quit Final Cut Pro and check your hardware configuration | Final Cut Pro |
An unspecified error occurred while performing a conform action on the following file | Adobe Premiere Pro |
AParamItem::UniqueidentifierToParamID - unable to convert UID to paramID | Avid Media Composer |
Assertion failed: kCGErrorSuccess == err && displaysCount > 0 | Avid Media Composer |
Audio/Video is unexpectedly no longer coming into the system | Avid Media Composer |
AUDIOEXPORT_INSUFF_DISK | Avid Media Composer |
AUTO_COMP_NO_SYNC | Avid Media Composer |
BAD_MAGIC | Avid Media Composer |
Binsave: error deleting bin file | Avid Media Composer |
BlipPlayer::NonThreadedPlayBlipField: Timed out waiting for single frame player to stop. If scrubbing a complex sequence of unrendered effects, consider rendering them for better performance | Avid Media Composer |
Bus error in main thread | Avid Media Composer |
Can't load database | Avid Media Composer |
Cannot create the AMA sample mapper to play this clip | Avid Media Composer |
CANT_UPDATE_NON_AVID_OPTIMAL_CONTAINER | Avid Media Composer |
Catalog too new | Final Cut Pro X |
CM_OFFSET_OUT_OF_RANGE | Avid Media Composer |
Codec not found. You may be using a compression type without the corresponding hardware card | Final Cut Pro |
Codec Error | Final Cut Pro |
Compiler File Error | DVD Studio Pro |
ConvertToAAF() not implemented for this component type | Avid Media Composer |
CORE_UNABLE_TO_DO | Avid Media Composer |
COREAUDIO_OUTPUT_DEVICE_NOT_STARTED | Avid Media Composer |
Correction can't be applied without a current monitor | Avid Media Composer |
Could Not Create File | Soundtrack Pro |
CRUMB_EXISTS | Avid Media Composer |
DE_NO_COIN | Avid Media Composer |
Device Error | DVD Studio Pro |
DID READER::XraiseUnexpectedStreamStatus async file system error | Avid Media Composer |
DIDDescriptor: GetAAFProperties: XDCAMHD Unsupported resolution | Avid Media Composer |
DISK_FILE_ALREADY_EXISTS | Avid Media Composer |
DISK_FILE_NOT_FOUND | Avid Media Composer |
DISK_INVALID_FILENAME_SYNTAX | Avid Media Composer |
DISK_UNIX_ERROR | Avid Media Composer |
DOMAIN_COPYOUT_FAILED | Avid Media Composer |
DSPPublishing error -29 | Final Cut Pro X |
Effect does not apply | Avid Media Composer |
Error compiling movie. Codec compression error. This codec may be unable to support the requested frame size, or there may be a hardware or memory problem | Adobe Premiere Pro |
Error compiling movie. Disk Full | Adobe Premiere Pro |
Error compiling movie. Duplicate file | Adobe Premiere Pro |
Error compiling movie. File not found | Adobe Premiere Pro |
Error compiling movie. I/O Error | Adobe Premiere Pro |
Error compiling movie. Invalid output drive | Adobe Premiere Pro |
Error compiling movie. Out of memory. To maximize available memory, set the rendering optimization preference to 'Memory' | Adobe Premiere Pro |
Error compiling movie. Unable to create or open output file | Adobe Premiere Pro |
Error compiling movie. Unable to save file. Destination file is in use by Adobe Media Encoder | Adobe Premiere Pro |
Error compiling movie. Unable to save file. Destination file is in use by Premiere | Adobe Premiere Pro |
Error compiling movie. Unknown error | Adobe Premiere Pro |
Error compiling movie. You do not have permission to create or delete the output file | Adobe Premiere Pro |
Error: Unknown file | Final Cut Pro |
Failed to get the number of contiguous bytes from the AMA Plug-In | Avid Media Composer |
Failed to initialize audio hardware | Avid Media Composer |
Failed to find coincidence point on tape | Avid Media Composer |
Failed to save. Unknown store type, format, or version | Final Cut Pro X |
FILE_OTHER | Avid Media Composer |
Final Cut Pro cannot save changes to projects or Events. The disk where your projects or Events are located may be full or unavailable, projects or Events may have moved, or permissions may have changed | Final Cut Pro X |
FlamethrowerOHCIManagerCoreRep ... No running thread to receive message Pyromaniac DIO FirewireBOBEventThread (null) | Avid Media Composer |
FlattenMovieDataToDataRef | General |
General Error | Final Cut Pro |
General Error 34 | Final Cut Pro |
General Error 41 | Final Cut Pro |
Illegal angle situation. Only the main video angle will be simulated | DVD Studio Pro |
Image is too large to be loaded | Avid Media Composer |
Import error - the video bit depth is unsupported | Adobe Premiere Pro |
Import was aborted due to a timecode break | Final Cut Pro X |
Incompatible GOP structure | DVD Studio Pro |
INVALID_FILE_NAME | Avid Media Composer |
KCAV: Activation code validation failed | Avid Media Composer |
KCAV: Failed to get Activation code attributes | Avid Media Composer |
Layer 0 exceeds the maximum layer size allowed | DVD Studio Pro |
Legend Audio Communications Error, Hardware Underrun | Avid Media Composer |
Locator could not be created | Avid Media Composer |
Long GOP cannot be exported | Avid Media Composer |
Marker could not be created | Avid Media Composer |
Menus cannot exceed 1GB in total size. Reduce the amount of data in your menus | DVD Studio Pro |
Metadata writing in progress | Adobe Premiere Pro |
Movie export from procedures FAILED! errcode 4294965987 | Avid Media Composer |
MPEG2IBPCODEC_ERROR_IN_BITSTREAM | Avid Media Composer |
MSM: No directory specified_3 | Avid Media Composer |
MVL_INSUFFICIENT_SPACE | Avid Media Composer |
MXF_DIDMAPPER: ReadRange- End Sample Index Exceeds on-disk index entry count | Avid Media Composer |
NO CHUNK | Avid Media Composer |
No compressed data format found for specified VCID and video format | Avid Media Composer |
No media can be written to any mounted drive. Please check write permissions | Avid Media Composer |
Not Enough Disk Space In Target Folder | DVD Studio Pro |
Not enough memory to import the requested file | Adobe Premiere Pro |
NSURLDomainError -1001 | Final Cut Pro X |
NSURLDomainError -1012 | Final Cut Pro X |
NTSC assets cannot be imported into PAL projects | DVD Studio Pro |
Offset Too Big | QuickTime |
omfiHPDomain_BAD_MAGIC | Avid Media Composer |
omfiHPDomain_INIT_FAILED | Avid Media Composer |
Operation not allowed | Final Cut Pro |
Operation not supported filename:creating | Avid Media Composer |
Out of Memory | Final Cut Pro |
PAL assets cannot be imported into NTSC projects | DVD Studio Pro |
PGLUE_IMPOLITE_PORT_NUMBER | Avid Media Composer |
PMM_AUDIO_MISMATCH | Avid Media Composer |
PMM_INSUFFICIENT_MEDIA | Avid Media Composer |
Portions of a sequence use Motion integration, but Motion integration is not installed | Final Cut Pro |
Project is unreadable or too new for this version of Final Cut Pro | Final Cut Pro |
Publishing to YouTube Failed: NoLinkedYouTubeAccount | Final Cut Pro X |
Publishing to YouTube Failed: ServiceUnavailable | Final Cut Pro X |
Publishing to YouTube Failed: The request timed out | Final Cut Pro X |
Range specified for Dup is outside range of component | Avid Media Composer |
Render Error: Insufficient disk space | Final Cut Pro |
ScriptSync Error: The file could not be created | Avid Media Composer |
Segmentation fault in thread "Main thread" | Avid Media Composer |
Seq Header Duplication | DVD Studio Pro |
Sequence error: unable to add clip to sequence | Final Cut Pro |
Sequence refers to non-existent track in clip | Avid Media Composer |
SFPlayConsumer::Execute TIMEOUT | Avid Media Composer |
SQL could not be executed | Avid Media Composer |
SQLite error code:1, 'too many SQL variables' | Final Cut Pro X |
SWDC_CodecInterface_Task::Execute() CONSISTENCY CHECK FAILURE ERROR | Avid Media Composer |
The Build Location folder contains a VIDEO_TS folder(standard DVD content). You must remove the VIDEO_TS folder from the Build Location in order to proceed with Build/Format of a HD DVD project | DVD Studio Pro |
The document could not be opened | Final Cut Pro X |
The drive containing the source material is not available. Using the drive specified in Media Creation settings | Avid Media Composer |
The Help library requires Javascript | General |
The file has an unsupported compression type | Adobe Premiere Pro |
The font dictionary can't be read | Adobe Premiere Pro |
The operation couldn't be completed. (com.apple.Compressor.CompressorKit.ErrorDomain error -1) | Final Cut Pro X |
The operation couldn't be completed. Permission denied | Final Cut Pro X |
The operation couldn't be completed. Invalid argument | Final Cut Pro X |
The project appears to be damaged. It cannot be opened | Adobe Premiere Pro |
The selected SAN location is already in use | Final Cut Pro X |
The system is running low on memory (100% full). It is recommended that you close some bins and save your project before opening any more bins | Avid Media Composer |
There are no media drives available. You will only be able to import shot logs | Avid Media Composer |
There is not enough clip media to create the transition | Final Cut Pro X |
There were errors linking to AMA files | Avid Media Composer |
This project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type | Adobe Premiere Pro |
Timed out obtaining dynamiclink server connection | Adobe Premiere Pro |
T1P:ATM Parse Error | Adobe Premiere Pro |
Unable to connect to background process | Compressor |
Unable to create search data directory | Avid Media Composer |
Unable to initialize OpenGL. Make sure Video Desktop is disabled | Color |
Unable to open file 'Media Tool'. File does not contain a valid Avid domain header. Cannot open launch Media Tool | Avid Media Composer |
Unable to relink AMA clip to selected file. It may be incompatible with the original. (ie: file type, edit rate, track list, duration) | Avid Media Composer |
Unable to stop spring buffer's fill thread | Avid Media Composer |
Unable to write shared user settings file. Make sure directory exists and is accessible | Avid Media Composer |
Unsafe Operation Attempted | Adobe Premiere Pro |
Unsupported compression in file | Adobe Premiere Pro |
Unsupported format or damaged file | Adobe Premiere Pro |
Unsupported resolution | Avid Media Composer |
VDM3_VideoOutputCvtr::ExecuteRequest: Unexpected state | Avid Media Composer |
Wrong type of download was found | Avid Media Composer |
Your tape format has audio at 32000 and your audio project settings were expecting 48000. You need to change your audio project setting and re-record | Avid Media Composer |
12 | General |
14 | Final Cut Pro |
34 | Final Cut Pro |
0 | QuickTime |
-30 | QuickTime |
-33 | General |
-34 | General |
-35 | General |
-36 | General |
-43 | General |
-45 | General |
-48 | General |
-50 | Finder |
-50 | QuickTime |
-108 | General |
-111 | Avid Media Composer |
-120 | General |
-1712 | General |
-2000 | QuickTime |
-2001 | QuickTime |
-2002 | QuickTime |
-2003 | QuickTime |
-2004 | QuickTime |
-2005 | QuickTime |
-2006 | QuickTime |
-2007 | QuickTime |
-2008 | QuickTime |
-2009 | QuickTime |
-2010 | QuickTime |
-2011 | QuickTime |
-2012 | QuickTime |
-2013 | QuickTime |
-2014 | QuickTime |
-2015 | QuickTime |
-2016 | QuickTime |
-2017 | QuickTime |
-2018 | QuickTime |
-2021 | QuickTime |
-2022 | QuickTime |
-2023 | QuickTime |
-2024 | QuickTime |
-2025 | QuickTime |
-2026 | QuickTime |
-2027 | QuickTime |
-2028 | QuickTime |
-2029 | QuickTime |
-2030 | QuickTime |
-2031 | QuickTime |
-2032 | QuickTime |
-2033 | QuickTime |
-2034 | QuickTime |
-2035 | QuickTime |
-2036 | QuickTime |
-2037 | QuickTime |
-2038 | QuickTime |
-2039 | QuickTime |
-2040 | QuickTime |
-2041 | QuickTime |
-2045 | QuickTime |
-2046 | QuickTime |
-2047 | QuickTime |
-2048 | QuickTime |
-2049 | QuickTime |
-2050 | QuickTime |
-2051 | QuickTime |
-2052 | QuickTime |
-2059 | QuickTime |
-2062 | QuickTime |
-5000 | Avid Media Composer |
-5000 | General |
-6662 | QuickTime |
-8058 | Finder |
-8072 | Finder |
-8960 | QuickTime |
-8961 | QuickTime |
-8962 | QuickTime |
-8963 | QuickTime |
-8964 | QuickTime |
-8965 | QuickTime |
-8966 | QuickTime |
-8967 | QuickTime |
-8968 | QuickTime |
-8969 | QuickTime |
-8970 | QuickTime |
-8971 | QuickTime |
-8972 | QuickTime |
-8973 | QuickTime |
-8974 | QuickTime |
-8975 | QuickTime |
-8976 | QuickTime |
-8977 | QuickTime |
-8987 | QuickTime |
-8992 | QuickTime |
To view the solutions for these error messages, please download Crash Analyzer. Unsupported error messages can be added using the submission link within the application.
The FCP Versioner application is delivered on a disk image. While the application can be opened directly from the image, for reliable operation of the software we recommend installing it to your Applications folder.
To do this, open a new Finder window by going to File > New Finder Window, navigate to the Applications folder and then drag the FCP Versioner application into the folder. You may be asked to enter your administrator password.
Once this is complete, eject the disk image and launch FCP Versioner from your Applications directory.
If a client machine is highlighted in red, it means it is not connected. Here are some things to
try to resolve the issue:
1. If you have set the client to listen on a specific network interface (by default it is set to Any), make sure that the interface is connected to a network that the admin computer is capable of accessing.
2. In the Security pane of System Preferences, make sure the Firewall is not set to Allow only essential services.
3. If the Firewall is set to Set access for specific services and applications, make sure Pro Admin.app and ProClient are added to the list (ProClient is located at /Library/PreferencePanes/Pro Client.prefPane/MacOS/ProClient).
4. In the Pro Client pane in System Preferences, toggle the switch to the Off position, wait a few seconds and then toggle it back to On.
5. Try disabling your network connection and then re-enabling it. If you are connected to a wireless network, this will involve going to the Airport icon in the top-right corner of the screen, selecting Turn Airport Off, waiting a few seconds and then switching it back on.
If you are connected to a cabled network, it will require unplugging the cable, waiting a few seconds and plugging it back in.
6. If you are on a corporate network, you may have a hardware firewall. In this case, go to the Pro Client pane in System Preferences, specify a custom port and make sure this port is open on your firewall. Also try opening 35011, which is the fallback port if something goes wrong.
7. Download and reinstall Pro Client on the affected systems.
8. You may also experience success by closing Pro Admin and reopening it.
Try the following steps if Editmote is unable to connect to your computer.
1. Make sure that the Editmote Preference Pane is installed on your Mac and that the switch is in the On position.
2. Ensure your Mac and iOS device are connected to the same wi-fi network.
3. Make sure you have the latest versions of Editmote and the preference pane.
4. In the Editmote preference pane, try turning the switch off, waiting a few seconds and then turning it back on again.
5. Try force-quitting the Editmote iOS app by going back to the home screen, double-tapping the Home button, tapping and holding over the Editmote icon in the panel that pops up, then tapping the X or - symbol next to it.
6. If you have set the preference pane to listen on a specific network interface (by default it is set to Any), make sure that the interface is connected to a network that your iOS device is capable of accessing.
7. In the Security pane of System Preferences, make sure the Firewall is not set to Allow only essential services.
8. If the Firewall is set to Set access for specific services and applications, make sure the Editmote preference pane is added to the list (it is is located at /Library/PreferencePanes/Editmote.prefPane/MacOS/EditmoteListener by default).
9. Try disabling your network connection and then re-enabling it. If you are connected to a wireless network, this will involve going to the Airport icon in the top-right corner of the screen, selecting Turn Airport Off, waiting a few seconds and then switching it back on.
If you are connected to a cabled network, it will require unplugging the cable, waiting a few seconds and plugging it back in.
10. If you are on a corporate network, you may have a hardware firewall. In this case, go to the Editmote preference pane in System Preferences, specify a custom port and make sure this port is open on your firewall. Also try opening 36015, which is the fallback port if something goes wrong.
11. Try choosing a specific network interface and port to listen on and then connect manually to this IP address and port from within Editmote.
When you use Plugin Manager to disable a plugin, the plugin file is moved to the directory /Library/Application Support/Digital Rebellion/Pro Maintenance Tools/Plugin Manager Disabled Plugins.
If your trial expires and you do not register the software, you will need to manually move files that you would like to enable back to their proper location. The files are stored in the disabled plugins folder under their original hierarchy so it's easy to see where the file came from.
The first time you run MC Repair, it may find a large number of files with incorrect permissions. This could take 5-10 minutes to fix depending on how may files need to be repaired.
While it does this, it may appear to some users that the application is no longer functioning. This is unlikely to be the case and we recommend waiting for the application to finish processing.
In future versions we will make it clearer that processing is still taking place and the application is functioning correctly.
The first time you run CS Repair, it may find a large number of files with incorrect permissions. This could take 5-10 minutes to fix depending on how may files need to be repaired.
While it does this, it may appear to some users that the application is no longer functioning. This is unlikely to be the case and we recommend waiting for the application to finish processing.
In future versions we will make it clearer that processing is still taking place and the application is functioning correctly.
Issue: When importing files with forward slashes (/) in the title, Batch Renamer displays them as a colons (:). For example, My_Image_5/5/11.jpg is displayed as My_Image_5:5:11.jpg.
In OS X forward slashes separate folders and cannot be used within a filename, so the Finder substitutes forward slashes for colons behind the scenes. Batch Renamer displays the filename exactly as it exists on disk with colons instead of slashes.
Workaround: Find & Replace the colons instead of the slashes.
This occurs when you have both FCS Maintenance Pack and Pro Maintenance Tools installed on the same system.
To remove the duplicates, download the FCS Maintenance Pack uninstaller from the Pro Maintenance Tools support page and run the uninstaller to remove FCS Maintenance Pack. Make sure the option to remove shared files is deselected.
Alternatively, you can keep FCS Maintenance Pack on your system and simply hide FCS Maintenance Pack within the launcher. To do this, go to View > Hide Groups > FCS Maintenance Pack.
If you experience a crash in one of our iOS applications, we recommend that you file a bug report and send us the log directly. While iTunes does automatically submit crash logs to us, it waits for a certain threshold to be met before doing so. This limits our ability to fix automatically-submitted crashes quickly and some more obscure bugs will never meet the threshold and so we'll never know about them.
Crash logs are copied to your computer when you sync with iTunes. They are located at ~/Library/Logs/CrashReporter/MobileDevice/[name of device] and/or ~/Library/ Logs/CrashReporter/MobileDevice/[name of device].symbolicated. You can submit these to us via the Report a Bug link on the relevant application's support page or by using the Leave Feedback link within the app itself.
If your Digital Rebellion software does not accept the registration information you received by email, please ensure the following:
The registration dialog will close automatically if the information was accepted.