David Bogie
Forum Replies Created
-
Difficult to visualize your perceptual problem but I can imagine it.
Try Optical Compensation or a bit of Spherize on the intermediate layers.
You might be able to get by with CC Cylinder on those intermediate layers if you’re not doing diagonal moves.
bogiesan
-
Welcome to the family, we were al new to this at some point.
Your .motn project files are like Word files, all they do is tell the application what to do. they have no affect at all on anything anywhere if they’re not actually running. The resources (movies, stills, etc) attached to those project may be clogging up your external storage but they have no impact on your system at all. None.“Od projects” have a horrible way of becoming current projects so be sure you’re offloading them (and all associated resources) to recoverable storage.
bogiesan
-
Yes, you can run FCS on an iMac.
But.
It’s a deaden non-expandable box. You don’t want to unless you are totally comfortable with the limitations.I suggest you shop for a used MacPro.
bogiesan
-
David Bogie
December 14, 2009 at 3:06 pm in reply to: Improve FCP Render Time By Using another Machine or other Hardware Solution?[Joel Peregrine] “I’m the same boat. I’ve been using the Neat plugin more often and am noticing that its slowing down my workflow. I’ve switched to a process that puts all of a projects assets, including renders, on a esata external so I can swap a long render over to another MacBook Pro that I use for rendering, encoding and capturing.”
Ah, running a parallel copy of FCP is a viable solution once the resources and project files have been offloaded and are known to be intact.
Implies a second license for FCP but let’s not quibble about the details.bogiesan
-
David Bogie
December 13, 2009 at 3:43 pm in reply to: Improve FCP Render Time By Using another Machine or other Hardware Solution?Sadly. No, the only thing you can do is add process or speed by upgrading your machine. Consider what this filter is doing, though, and you’ll realize even doubling your computational power won’t make much difference.
Compressor’s Qmaster distributed work technology, AFAIK (unless something REALLY big happened recently), cannot be adapted to processing FCP’s filters.
bogiesan
-
David Bogie
December 13, 2009 at 3:40 pm in reply to: Adding a lower third bug almost quadrupled my render time?q[Tony Brittan] “Have you tried doing the bug in compressor when you transcode for DVD? “
Using the watermark feature in Compressor could be an excellent solution.
bogiesan
-
David Bogie
December 12, 2009 at 11:37 pm in reply to: Adding a lower third bug almost quadrupled my render time?[Anthony Popolo] “I understand each frame had to be rendered, but it makes no sense to me why adding one layer of video quadrupled the render time. At worse case I would think double maybe.
My previously rendered footage (without the logo) was rendered and compressed to SD mpeg2 so I didn’t want to import compressed footage as my base video for the logo version. “You missed all the points I was trying to make and you just keep arguing with everyone else that this shouldn’t be big deal. Your workflow is flawed.
And in your last post you finally let it drop that you’ve been scaling your logo AND you’re using VBR? Sheesh.bogiesan
-
There are no recommendations in anyone’s FAQ that support or suggest editing H.264. Transcode to a editing format.
bogiesan
-
David Bogie
December 12, 2009 at 5:44 pm in reply to: Adding a lower third bug almost quadrupled my render time?Every frame had to be rendered.
You should have imported the previously rendered SD footage and placed the lower third over that and exported to SD. Easy and quick.Going from 720 to SD is a huge computational exercise. Adding transparency complicates everything by another large factor.
Streamlining render and export pipelines takes experience that leads to logical applications of work previously accomplished.
bogiesan
-
[Christopher Kinsman] “Tell your client about the production triangle –
a) Good Quality
b) Fast turnaround
c) Cheap price
– then tell them they can pick any two.
If it’s good and fast, it’s not cheap.
If it’s fast and cheap, it’s not good.
Get the picture?
“I’m working with a new version of that old paradigm: Pick one.
bogiesan