Mike Kahn
Forum Replies Created
-
Depends on what you are doing…I am doing two shows with Alexa, one is ingesting straight ProRes HQ, editing and delivering tapeless as DVCPro HD through FTP to the network.
The other is shooting ProRes 4444, we import it, line up camera rolls in FCP, export DPX files using Glue Tools, ingest the DPX into our telecine machine (basically treating the Alexa as if it was a film camera), exporting graded dailies as DNxHD 36, bringing that into avid for offline.
-
You should get a second hard drive to use for media. You should not be using media and the application from the same drive.
-
Thanks for the suggestions. It is not a user account issue. I have tried as the old user (editor) as well as a new user and still have the same issue.
As for using different software, I don’t feel I am asking that much of the system. I nesting and cropping the top and bottom is too much, then maybe this isn’t a pro system after all. The render was held up at the first instance of text, coming on the second video layer, at the opening credits.
I don’t think it’s a RAM issue since FCP can only use 3G of ram no matter how much you have in your system. I’ve watched the RAM usage in Activity monitor as it starts a render and when it comes up with the error and there is more then enough.
As for the self contained file, I have created one, brought that in and cropped but then if you want to make any changes before the output, you have to start all over again. The editor likes to watch the film down with the mask on as a last check to make sure the film is how he wants it. Usually he has some minor tweaks before output. With a self contained file, those tweaks become major issues.
-
I’ve thought about that, but some shots have zooms and other things that will effect that way of cropping. Also, there are some composite shots that would need to be adjusted.
-
I reverted the Firmware to 32-bit. If the editor continues to have issues I will go back to the 64-bit.
The window told me I was up to date with the firmware driver.
Thanks for your help Gary, I really hope this will fix the problems.
Mike
-
[gary adcock] “did you manually update the firmware on the card?”
I have not do a firmware update. Is the Kona 3 different from the Kona LHi in terms of updates? Occasionally I will build a system with the LHi and I get a pop up window telling me to update the firmware. I can’t remember this ever happening with a Kona 3 set up.
I will try this as soon as I can get on the system and see if it fixes the issues.
-
Sorry to be confusing. I was using avid unity for storage but took it off and went to internal drives, thinking the unity was causing the playback issues and crashing.
I am using the kona 3 8.0 ndd drivers. I have trashed the preferences and that had not fixed the issues.
-
Not positive, but I think I’ve resolved a General Error 88 by making sure that the device control was set to the frame rate of the deck and not the sequence.
Either that, or it was having an out point in the sequence.
I think it’s one of those two things.
-
I have put the media onto internal 2TB Striped Raid (2x 1TB internal drives) and most of the crashing has gone away but the playback stutter is still present.
Anyone ever experience anything like this?
-
I’m having my own issues with the Unity today but you’re are might be easier to fix.
1) You’re client drivers for the unity are outdated. They my clients are on 5.3.1. From the read me:
“The Avid Unity MediaNetwork v5.1.4 client software fixes this issue so that Final Cut Pro clients can render effects and function normally when switching between the Finder and back to the Final Cut Pro application.”5.2 brought support for snow leopard but had finder issues. 5.3.1 fixes these.
2) I have my clients work locally and back up to unity. This keeps the files from being locked when trying to save. It also keeps people from working on the same project and overwriting.
Maybe this will help you, as for me, I’m putting everyone on local storage to see if my issues clear up…
Mike