Folks I keep getting an error when exporting my timeline and wondered if anyone knew what this error is.
Computer Profile:
M2 Max MacBook Pro / 64 GB RAM / 2 TB / mac OS Ventura 13.3.1(a) / FCP 10.6.5
MacBook Pro (M2 Max, 2023)
Tangier, Davis' last post about disk subsystems got me thinking. Like you, I found there are almost no references to error -536870181. However -- converting it to hexadecimal = 0xE00002DB. Searching on variations of that hex number leads to the open source file IOReturn.h, which is part of the IOKit framework used in macOS. There we find:
#define kIOReturnNoSpace iokit_common_err(0x2db) // no space for data
IF that is correct, it implies some kind of out-of-space condition during an I/O operation. It's interesting the error happened when *exporting* a file (which obviously takes lots of space). That said, it might not be a normal "out of space" condition.
It could be some transient issue involving memory usage spilling to the page file (which takes more space but is quickly released). It could be APFS local snapshots consuming space, or even a problem with the drive itself.
Re the project repair function, I have a recent copy of your project (minus the media). I tried the repair and it found no problems.
We still haven't time-correlated the above errors from the system log with the "-536870181" error raised by FCP during export. We need to verify those are happening at the same time. Right now it's just a guess.
However I think the kIOReturnNoSpace error is a promising lead. An FCP user on Reddit reported that error -- also when exporting a file. He also reported logged errors referencing VTEncoderXPCService, which is the host process where the encoders run during export. That process itself can take up lots of memory, which can spill to disk in the page file.
Another complication is APFS has a "local snapshots" facility which can also consume space. I think it's supposed to release those when under pressure, but maybe the thread making the I/O call got tired of waiting and interpreted it as a failure.
I suggest you boot the machine in Recovery mode and run Disk Utility First Aid on each disk volume. To run it properly on the Macintosh HD volume, that should be expanded in the left sidebar of Disk Utility, then First Aid should be run from bottom to top, one pass *each* on "Data", "Macintosh HD", etc. Running it in recovery mode gives the best results because all other activity on the drive is stopped.
Disk Utility should update any space usage metadata that might be off. Then boot the machine, check disk space, take action as needed. Make sure there is *plenty* of extra space on all drives.
Once the system is up, I suggest running Disk Utility First Aid on all other drives. Observe the results of each pass, make sure there are no serious errors.
Yes, updated log only if you get the error again. I'd also like any FCP diagnostic reports from /Library/Logs/DiagnosticReports. You can go there in Finder via Go>Go to Folder (enter /Library/Logs/DiagnosticReports), then do CMD+F in Finder and search that folder for "Final Cut". Zip those files and send them to me, but only if you have another error.
If you have another error, please note the date and time (inc'l time zone) and let me know.
Tangier, Davis' last post about disk subsystems got me thinking. Like you, I found there are almost no references to error -536870181. However -- converting it to hexadecimal = 0xE00002DB. Searching on variations of that hex number leads to the open source file IOReturn.h, which is part of the IOKit framework used in macOS. There we find:
#define kIOReturnNoSpace iokit_common_err(0x2db) // no space for data
IF that is correct, it implies some kind of out-of-space condition during an I/O operation. It's interesting the error happened when *exporting* a file (which obviously takes lots of space). That said, it might not be a normal "out of space" condition.
It could be some transient issue involving memory usage spilling to the page file (which takes more space but is quickly released). It could be APFS local snapshots consuming space, or even a problem with the drive itself.
Re the project repair function, I have a recent copy of your project (minus the media). I tried the repair and it found no problems.
We still haven't time-correlated the above errors from the system log with the "-536870181" error raised by FCP during export. We need to verify those are happening at the same time. Right now it's just a guess.
However I think the kIOReturnNoSpace error is a promising lead. An FCP user on Reddit reported that error -- also when exporting a file. He also reported logged errors referencing VTEncoderXPCService, which is the host process where the encoders run during export. That process itself can take up lots of memory, which can spill to disk in the page file.
Another complication is APFS has a "local snapshots" facility which can also consume space. I think it's supposed to release those when under pressure, but maybe the thread making the I/O call got tired of waiting and interpreted it as a failure.
I suggest you boot the machine in Recovery mode and run Disk Utility First Aid on each disk volume. To run it properly on the Macintosh HD volume, that should be expanded in the left sidebar of Disk Utility, then First Aid should be run from bottom to top, one pass *each* on "Data", "Macintosh HD", etc. Running it in recovery mode gives the best results because all other activity on the drive is stopped.
Disk Utility should update any space usage metadata that might be off. Then boot the machine, check disk space, take action as needed. Make sure there is *plenty* of extra space on all drives.
Once the system is up, I suggest running Disk Utility First Aid on all other drives. Observe the results of each pass, make sure there are no serious errors.
Yes, updated log only if you get the error again. I'd also like any FCP diagnostic reports from /Library/Logs/DiagnosticReports. You can go there in Finder via Go>Go to Folder (enter /Library/Logs/DiagnosticReports), then do CMD+F in Finder and search that folder for "Final Cut". Zip those files and send them to me, but only if you have another error.
If you have another error, please note the date and time (inc'l time zone) and let me know.
I found a fix for this error message.
I am using a Mac Studio M1 Max, 32GB with Sonoma 14.2.1 and FCPX 10.7.1.
I had this error message so many times on a big project that took around 4 hours to export. I tried different things including rendering first (ProRes 422), then exporting as a master file (ProRes 422).
It may help to know I use two plugins throughout the project, Neat Noise (very power intensive) and Colour Finale 2.
I had set all the graphics as its own role and turned them off as I wanted this export without any graphics visible.
I believe all the original files are held on my main drive LaCie 6big Thunderbolt 3. I am not 100% as perhaps I have an image for the project on the same drive I am exporting to.
I was exporting to a LaCie d2 Professional, 10TB Thunderbolt drive (single drive). Although this drive works fine, I thought perhaps the issues I am having is with this export destination (the whole drive not the just the folder on the drive).
So I tried exporting to another drive I had available LaCie Rugged Thunderbolt, USB 3.0, Orange/Grey 4TB (two drives set as RAID 0 so faster than 1 single drive) and the export worked first time. So my suggested solution is to change the export location. A drive that has none of the project files on it so it only has to write data and not read at the same time. This may not be the actual issue but changing the drive I export to has resolved this issue for me. Perhaps there is an issue with the original drive I was exporting to. Maybe because my second drive was faster it could write the data quicker.
For example, the first drive I exported to cannot playback 4K UHD ProRes 422 files without becoming choppy and skipping frames. The second drive plays the files very smoothly without any frames being skipped.
I also have a few tips that help me avoid export errors and failures. If I have a big project that I feel is complex and utilises power hungry plugins, I do these steps before exporting:
Perhaps it's because I clear the cache when restarting but this has helped me overcome other errors and failed exports many times. This particular error message spoken about in this post still occurred after doing this which is why I resorted to changing the export destination.
Also, I find compressor very unreliable with big projects so I build my custom export settings in Compressor then save them as export options in FCPX. I do not export using Compressor.
Good luck!
Tangier, that was reported by a Reddit user when exporting to ProRes from an M1 Max. He said it only happened if the source contained multiple lanes where both were visible on screen, e.g, PiP, etc. Versions not stated. Another user reported it when exporting to ProRes on an M1 Ultra on 10.6.2.
The Reddit user reported the console logs contained the below errors. You might check for those or similar.
One of them said it did not happen on export to H264. You might try that for comparison. If it is specific to ProRes output, that could imply some issue with the M2 Max ProRes engine or the software layers above that. It obviously should not happen.
The M1/M2 Max and M1 Ultra are the only Apple CPUs that have multiple ProRes engines. I believe they are used in parallel for cases involving multiple streams such as multicam. On ProRes export with sections of multiple layers showing, it's possible they are using one for decode and one for encode and there was some synchronization issue.
There was a previous "incorrect frame order" FCP bug introduced in 10.6.2, apparently as a side affect of an FCP performance optimization involving the M1 Max and Ultra CPUs. That was fixed on 10.6.4. Maybe this is a variation on that.
Console errors reported by Reddit user:
VTEncoderXPCService ERROR AppleProResHW (0xd3c24c88): GetEmptySpotInFrameInfoArray(): Timedout, could not find an empty spot
VTEncoderXPCService ERROR AppleProResHW (0xd3c24c88): ProResEncoder_EncodeFrame(): Could not get space in FrameInfoArray
Tangier, I examined your console logs, and there are some SQLite errors. You can look at the timestamp and see if that correlates to one of your problems. First a few comments:
I loaded your "Anxious-TC Cut 3c" project (albeit without data). 1 hr 38 min, 1,764 clips. Big but not that big. Very nice looking timeline from an organizational standpoint. It behaves much faster than the previous versions I examined.
I examined your library and the Cut 3c project with a SQL database editor. I ran the SQLite commands PRAGMA integrity_check and PRAGMA foreign_key_check. They both returned no errors, but that is a low-level check.
Re your system log, the wording implies FCP sent a SQL query which exceded the capability of SQLite. Each question mark "?" is part of a parameterized query that in a later phrase of query construction will be replaced by a value. However SQLite must reserve memory for those, and there is a limit. It didn't run out of memory, it was probably rejected by the SQL parser for submitting to many parameters.
One possibility is there was some hugely complex timeline structure which led FCP or the CoreData framework to build and submit that query. My cursory look at your timeline didn't show anything obvious. Another possibility is FCP just made an error or became "deranged" due to some other issue. E.g, maybe it obtains the number of placeholder "?" it's supposed to send from some other object or data structure, and that was not initialized properly, causing it to send the excessive number of parameters and cause the error.
When it says "I/O error" I don't think that means a system-layer error. I think that is boilerplate verbiage reporting that the SQLite call returned FAIL.
Please send me an updated system log file (I only need that one file). You should be able to get that at /private/var/log/system.log. Zip that and send it to me.
Please make note of the time of day (inc'l time zone) of any major errors you get and what you were doing at the time, so I can compare to the timestamp in the log.
2023-05-08 20:53:59.481504-0700 0xd6cf3 Error 0x0 29715 0 Final Cut Pro: (libsqlite3.dylib) [com.apple.libsqlite3:logging] too many SQL variables in "SELECT 0, t0.Z_PK, t0.Z_OPT, t0.ZFLAGS, t0.ZIDENTIFIER, t0.ZNAME, t0.ZTYPE, t0.ZCATALOG, t0.ZMETADATA FROM ZCOLLECTION t0 WHERE t0.Z_PK IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,
2023-05-08 20:53:59.482209-0700 0xd6cf3 Error 0x0 29715 14 Final Cut Pro: (CoreData) [com.apple.coredata:error] error: (1) I/O error for database at /Users/tangierc/Desktop/Anxious/01 FCP Projects/Anxious Build 3b.fcpbundle/_Anxious TC Edit/Anxious-TC Cut 3c/CurrentVersion.fcpevent. SQLite error code:1, 'too many SQL variables'
2023-05-08 20:53:59.514762-0700 0xd6cf3 Error 0x0 29715 14 Final Cut Pro: (CoreData) [com.apple.coredata:error] error: SQLCore dispatchRequest: exception handling request: <NSSQLFetchRequestContext: 0x600132b48000> , I/O error for database at /Users/tangierc/Desktop/Anxious/01 FCP Projects/Anxious Build 3b.fcpbundle/_Anxious TC Edit/Anxious-TC Cut 3c/CurrentVersion.fcpevent. SQLite error code:1, 'too many SQL variables' with userInfo of {
NSFilePath = "/Users/tangierc/Desktop/Anxious/01 FCP Projects/Anxious Build 3b.fcpbundle/_Anxious TC Edit/Anxious-TC Cut 3c/CurrentVersion.fcpevent";
NSSQLiteErrorDomain = 1;
Some more info: Assuming the assumption is correct about the hex form of that error number mapping to kIOReturnNoSpace // no space for data, that is a kernel-mode error. That could explain why the raw error number is displayed. If a higher-level I/O call such as fwrite() fails, it produces an error code which the app can look up. If a kernel-mode error happens, that code may be returned but the app has no idea what that is, so it merely displays the number.
The previous suggestions I made were oriented around a possible (but not certain) out-of-disk space condition. Those steps make sense, but it's quite possible the "no space for data" error does not refer to disk space. It could refer to some kernel-mode issue like out of buffer space. That could be caused by a kernel-mode driver bug or some resource constraint.
Overall, the general nature points to a lower-layer problem. It might be useful to run Activity Monitor, select the "Memory" tab, and do a few screen caps while the export is running.
In reviewing the log and config data I received, I notice two of the disk volumes are formatted as ExFAT. Those are /Volumes/Anxious 3 which is 18TB with 2 TB free, and /Volumes/ANXIOUS 4 which is 12TB with 9TB free.
Ideally those should be HFS+ or APFS (maybe HFS+ if rotating media). Maybe those are ExFAT for Windows compatibility? FCP will work with ExFAT but it's not a transactional file system so is more susceptible to metadata inconsistencies during a crash or forced shutdown. It also does not support FCP features like inode lookup, hard links, etc.
HFS+ and APFS have mechanisms to automatically mitigate fragmentation, but ExFAT does not. We don't know if that is related to this problem, I just mention this in passing. One of those ExFAT drives only has about 11% free space, so that might be a concern.
wondered if anyone knew what this error is.
This is a common error message. If you search for “536870181” you will find many similar questions.
-Solution-
1. Start FCP while holding option+⌘ and delete the settings.
2. Delete rendering files. Select library →File →Delete generated library files →Delete rendering files: All
3. Create a new project →Migrate all edited contents
4: Increase the remaining capacity of the export location or change to a location with more capacity.
5: Change export settings. Change the format from “Video and Audio” to “Computer”
6. Change codec. ProRes →H.264.
7. Change project settings from 4K to FHD.
8. Identification of error location. Export half and quarter of the timeline and look for where the error occurs.
--
Please give it a try as others may have better ideas.
*I received a notification from “louffi”, but why can’t I find it?😓
Tangier, I just took a blind stab at reproducing it on my M1 Ultra running FCP 10.6.5 and Ventura 13.3.1(a), unfortunately without success. I tried three 4k/23.98 ProRes 422 multicam layers, each scaled to show output on the screen, total duration about 5 min. I exported that to 4k ProRes 422 and 1080p ProRes 422 both with and without pre-rendering the timeline. I never saw the error and nothing in the console log.
Unfortunately, the error does not indicate a frame number or position on the timeline where it happens.
Please check your console logs for errors, whether your timeline is showing multiple layers on screen, and how long of a timeline is required to reproduce it. If you can duplicate the project, then cut the timeline in half, then 1/4, etc. and still see the error, that would tell use more. If you can get it to that point, try removing all the effects and see if it still happens.
I worry about symptoms like this -- if it's a thread safety or synchronization error related to the multiple encoders, that is exactly the type of bug that can slip by testing.
changing the drive I export to has resolved this issue for me.
Questions about each drive.
--
Q1:What type of format is it?
Q2:How many GB of capacity and remaining capacity?
Tangier,
Oops. Well, I've been having a few more "misses" than "hits" when trying to sort things, lately... ;-)
I've never heard of Glyph until you mentioned them (doesn't mean anything). Depending on how old those drives are, and how much they've been used, the cables could be an issue. I've heard reports of "bad" cables being shipped with various drives.
I avoid using anyone else's drives when working on a project. Too many unknowns. So, I almost always load up media on my RAID or SSDs, in order to be sure things will work properly. Years ago I was bitten a bit by the bad power supply brick issue that many LaCie drives had (and was fortunate to not have any catastrophic failures).
I have seen that specific error code mentioned for drive-related issues, but it isn't very specific or helpful.
Power cycling all gear sometimes helps to clear up some issues. Beyond that and standard troubleshooting, I've got nothing more to offer. I hope you get that sorted, sooner than later...
Cheers.
Hey Joe, would it be possible for the "derangement" of FCP occur because of a HW issue?
How about the "hidden" Project Repair function in FCP?
The two people I've dealt with a couple/few years ago with the same error message had drive issues or bad cables. I realize that the error message isn't very specific.
Tangier and Joe, I wonder if having the Library on a separate drive from the media has any relevance here?
Tangier, have you tried making a custom preset in Compressor and making that available in FCP, and then using that preset to send to Compressor?
Ran some export tests today. There was one failure and I didn't grab the console information. For some reason things seem to be working right now and I can't think of anything that's changed. I should be happy, but I don't like that this can happen at any time and I don't know what triggers this behavior.
I wanted to test if the issue was writing to different destinations; one of my source drives or to the MBP's SSD.
Tests (exporting ProRes Proxy) in order:
Setup: MBP / Two USB-C 3.1 Gen 2 drives connected directly to MacBook Pro M2 Max vis Thunderbolt 3 cables
(later in the day)
Setup Change: Same MBP / Two USB-C 3.1 Gen 2 drives connected to MacBook Pro M2 Max via two USB-C cables through a CalDigit TS4 Dock, connected to MBP via Thunderbolt 4 cable. MBP in clamshell mode, monitor out to 34" LG Ultrawide monitor (mentioning all of this in case the monitor or CalDigit has an impact on this issue)
Due to success I haven't tried Compressor method yet.
Tangier, I added stabilization to several clips, used BRAW Toolbox to add a bunch of BRAW clips to the R3D and ProRes stuff, set the FCP viewer to "proxy preferred", exported the 60 min timeline to 1080p ProRes 422, also tried Apple Devices 720p, and it still didn't fail.
That is on M1 Ultra. I guess I could try it on M1 Max, and maybe I could try it tomorrow on M2 Pro.
Tangier, that CalDigit dock is powered. I bet that's the difference (well, guessing it is). What are the specs of your external drives? Seems like maybe the MBP isn't providing enough power or the TS4 just provides more... I heard of similar situations. Hmm.
Thanks Joe. I'll take a look at everything you mentioned and evaluate my timeline. I have never had problems exporting until yesterday. The first time it was a frame error. I quit FCP, deleted a few markers and it worked. Then I started getting this error. I need to think about the editorial changes made yesterday that may have brought this on. There weren't many at all. This export error comes with trying to export a ProRes Proxy. Timeline is in proxy preferred playback mode.
The timeline is about 98 minutes long, set at 3840x2160, 23.98 fps. It has a mix of 8K Red down to 6K and 4K Blackmagic video. This particular timeline is using proxies made from the Red and BRAW Toolbox-created clips at eighth decode quality. I tried exporting the first 30 minutes and that failed very quickly. I'm going to try exporting a few random short segments of the timeline and see if I get successful exports.
The only difference between being able to previously export my timeline and changes I made yesterday are:
I thought that perhaps it's due to my BRAW Toolbox clips (of which I have many) potentially causing the problem. I've had a lot of problems working with those clips that I have never seen before in all of my years of using FCP (X) am getting help from the developer Chris. I intend to post about this later perhaps on FCP.co to get some additional minds on some very strange anomalies happening to see if it's the M2 architecture, Ventura, or FCP, or something else.
Final Cut Pro error -536870181
