Greg Williams
Forum Replies Created
-
Yes we do capture on multiple systems, but they all have identical setups, everything was freshly installed when we got the systems, but the optimized issue probably is not related to the render problem, I just threw it out there.
We use a Facilis system for our central storage.
https://www.facilis2.com/techspecs.html
-
We had the same issue with the Kona 3 and Tiger. Ultimately we downgraded our driver software to version 4 on the AJA site like another system we had, and no longer do we crash. Not sure if this will solve your issue, but it is sure worth a try.
Use the Unistall utility for version 5 or 5.1 Aja Driver, and then download version 4 and try that.
https://www.aja.com/html/support_kona3_swd_arc.html
Greg
-
What is your capture/monitor card? I know we had this issue with our Kona 3 card for awhile until we went back to an older version of the software utility.
Greg
-
Dumping the render files isn’t the answer for this issue as it is occurring in brand new sequences/brand new projects on the first render. We are replacing lower 3rd graphics in long form broadcast shows, so it is more I/O work than anything. The sequences will render after 4 or 5 tries successfully, but it has become a nuisance in our workflow and I am just trying to get to the bottom of why I would get this error when the file is not in use. I also do get occasionally a message saying my video is not optimized for FCP? Could this be part of it? I don’t know why I would get this when I have digitized the media using FCP, it doesn’t make any sense.
Thanks,
Greg -
Yes the files in the timeline have been rendered out of AE for use in FCP in the animation codec. AE is not open, nor is any other application that I know about is open and spotlight is also completely unchecked for indexing anything.
Thanks,
Greg