-
Multicam Headaches – Any Suggestions?
-
FCP X smooth cam operates the same way and is plenty fast. Is there some other benefit? Does it do a better job?
-
Regarding Core Melt Lock & Load x, it is applied to a single clip as a filter and only analyzes the visible portion of that clip. On my system analyzes in just about real time.
The built in smooth cam appears to analyze and entire clip, not just the visible (or used) portion. Plus it takes about 10x real time to do analyze.
The downside of Lock & Load is that it is serialized (2 installs) and requires more processing power to playback than the built in stabilization.
I hope this helps.
——
T. Payton
OneCreative, Albuquerque -
Here is a comparison video for lock&load:
——
T. Payton
OneCreative, Albuquerque -
Built in smooth cam CAN only analyze the part of the clip used. You have to open the clip in it’s own timeline or in the angle viewer if it’s a multiclip. Then slice out the part you want used. Not perfect, but ensures it’s being applied before anything else I suppose.
From there, it seems a 40 sec clip takes about 4 min. in my tests.
-
Thanks again to all those who took the time to help me resolve my multicam issues. I was able to muddle through my edit, dealing with the constant spinning beach balls, occasional crashes, and interface glitches. However, when I went to set roles for my audio tracks in preparation to export, FCPX crashed repeatedly. I attempted to reboot, then retry setting the roles, but then the entire computer crashed and rebooted itself.
In desperation, I copied my files back over to my G-Tech drive, then loaded up the project on a friend’s 2011 iMac. Even though he’s running an i5 with 8 GB RAM, everything played back perfectly smoothly with no issues whatsoever. I was able to set roles and export the master files without any issues.
There’s obviously something wrong with the FCPX installation on my MacPro. Since X is the only app exhibiting these issues, I think it’s going to be best to continue doing all my multicam work in FCP7. I have a stable environment, and I’m very confident in the workflow. While I will continue to use X for small one-off projects, I have no confidence that I can deliver my stage event productions to my clients in a timely manner using FCPX with my current hardware.
After seeing my project run on a low-end iMac, I’m sure that many editors can be very successful using a loaded i7 iMac for their workstation. My big hangup is having to replace my PCI video card, and losing my internal drives. Assuming a new MacPro is released in the next 6-9 months, I’ll give X another shot at a multicam project. If not, I’ll likely be exploring other options to replace FCP7 and my MacPro.
MacPro 8 core 2.8 gHz, 16GB RAM, Assorted Firewire Hard Drives, Final Cut Studio 3, Final Cut X, Adobe Production Premium CS6, Logic 8
-
Sounds like an OS issue on your machine.
It unfortunately happens. On my MacPro Adobe CS4 suddenly stopped working last summer. I tried everything to get it to work, but it after a few days each app would begin locking up and not be able to be launched again. I reinstalled a half dozen times, and finally gave up.
On machines that are depending on as much as ours are, it really is best to have a plan to reinstall the OS occasionally as preventative maintenance.
I for one have never had a problem with FCP X that wasn’t caused by a corrupt preference file, third party plugin, or corrupted font. You can see some more notes here:
https://forums.creativecow.net/thread/335/47480#47485
——
T. Payton
OneCreative, Albuquerque
Reply to this Discussion! Login or Sign Up