He confirmed that just:in successfully uses the QuickTime 7 API to write IMX and ProRes encoded video files to network storages.Īs the underlying QuickTime 7 API is still working as expected I conclude that this issue is another bug affecting Final Cut Pro 7 under Mavericks.
I further discussed the issue with the main developer of j ust:in, ToolOnAir’s ingest solution. The temporary capture file with the “-av ” postfix stays within the destination folder with a broken and presumably unrecoverable QuickTime header. All network protocols tested (AFP, SMB and NFS) suffered the same problem on multiple servers. I think that the network connection or the network stack within the kernel stalls. What I can say is that some capture files (like 1 in 20) stop to grow during the ingest on network volumes. They reported that sometimes after stopping the capture within Final Cut Pro 7 using the ESC key the newly created video would not show up.Īfter hours trying to reliable reproduce the issue I gave up.
They are working with SD material encoded as either IMX 50 or ProRes. We have a client that uses Final Cut Pro 7 on several Mac Pros running Mavericks to edit and capture videos on our flow:rage video storage.
0 kommentar(er)
