Francois Stark
Forum Replies Created
-
Open Final Cut Pro -> audio/video settings -> Device control presets
Select the device control setting that you are using and hit edit;
Change the capture offset and test.Test it by just capturing a short piece and checking frame accuracy.
F
-
Thanks
-
Hi all
Thanks for the input, but nobody answered my question…How can I uninstall FCS2 in order to re-install FCS1?
And yes, we have been using XML V3 to get projects from FCP 6 to FCP 5.1.4. It works pretty well, except for all our boris 3D titles that get replaced by gradients. We also stay away from speed changes, since we all know that reconnecting media on speed changed clips are unpredictable. And the xml process forces FCP to reconnect to the media.
I suppose the best way to uninstall would be a clean re-format and install. I suppose I’ll have to go over to leapard on the client’s system, re-install MS office, pull all the email over, copy all documents, and then install FCP 5, upgrade to 5.1 and then up to 5.1.4.
How does FCP 5.1.4 run on leopard? Does quicktime use the same version on 10.4 and on 10.5? I suppose that would be quite a rare installation…
Regards
Francois -
Another cause that increases project file size up disproportionately is nesting.
We found that a project file size can jump from 12 MB to 150 MB within two 5 minute autobackups once we started nesting…
So maybe you have some nests you can collapse or get rid of – see if that brings the project size down.
Regards
Francois -
After reading through this thread there seems to be a few common elements:
* FCP with a capture card – AJA or BM
* Lots of RAM
* Internal drive arrays
* Mac Pro and to a lesser extent G5’s
* Long rendersAdd all this together an what do you get?
HEAT!
The Capture card gives off heat, Lots of RAM as well, Drive arrays, and the CPU’s a lot more heat when rendering.What is the result of this heat?
* The capture cards could be running a lot hotter than they were designed for
* The PSU has to supply power to generate all this heat – it could also not be up to supplying all this power continously when renderingI have many G5’s running FCP, and two G5’s running Pro Tools. They are all quite stable – average about one-three crashes per month. Not too bad. None of them have internal drive arrays. Most have two internal drives – one boot and one general data and backup drive. Most have 2.5 to 3.5 GB RAM. All have LSi fibre channel cards for our SAN.
I have only one Mac Pro. It has had a AJA Kona LHe and LSe card, 3 GB RAM and has always had an internal 3 drive 1.5TB array. It used to freeze up at random times. It has had two motherboard replacements, one CPU and one CPU heatsink replaced. It seems the problems have at last been solved since it’s been running fine without a fibre channel card, with a Kona LSe card for the past two weeks. Next step is to get it back onto our SAN. But if it gets unstable again, I’m going yo take out the three drive internal array and see if it improves the situation.
Maybe it’s the heat or the PSU!
Regards
Francois -
Hi Jeremy
Thanx! This did the trick.
Regards
Francois -
Hi Jeremy
Thanx! This did the trick.
Regards
Francois -
Next stupid question: Why are you using that strange size?
-
I use quickeys to do repetitive tasks in FCP. Helps a lot.
https://www.cesoft.com/products/quickeys.html
-
Hi Walter
Some of us will never be in a position not to do upgrades mid-project.
We are now doing our new daily soapie on FCP, and will be moving our first daily soapie over (from AVID) within a month.
These projects have about 60 episodes in editing at any stage on our SAN – from digitising, off-line, 1st approval, final approval, subtitles, on-line and grading, playouts, audio mix, etc.
So, the only way we have to do upgrades, is to upgrade one system only, and test, test, test. Open finishes projects, digitise, playout, grade…
So even the “number one rule” has exceptions and workarounds…
Thanks
Francois