Nikolas Bäurle
Forum Replies Created
-
Do you have background rendering turned on? That can slow you down, and it generates a lot of files, every single change you make gets rendered automatically, then you make speed changes adding optical flow for example or add 3rd part effects and X spends its time background rendering like crazy, so any time you move your mouse it starts beachballing to pause the rendering and start rendering again once you stop, it happens on older macs and drives very often. I would delete your renderfiles on a regular basis if you background render.
-
I had the same problem over a year ago editing a feature length experimental art film, shot on xdcam ex. It is full of color corrections, fast edits, sound filters. Was using my 8 year old FW800 500GB Raid + 2011 MacBook Pro, i7. Until then it had bee outperforming even my newer LaCie drives. Suddenly with X and about 20 hours of footage, 60 min cut, X would pretty much come to a standstill, up to 30 min beach balls, the project could take about 15 minutes to load on certain days, relinking about 10 min… duplicating a 500 GB event inside x took about 12 hours.
When an got my LaCie thunderbolt drive everything worked perfectly fine, on the same MacBook. On my new iMac there’s practically no stalling whatsoever.
My old drive still works with my laptop very well, just not long X projects.FCPX generally has problems with older hardware, in my experience. The places I’ve used X at all had problems with their drives. I had a job cutting 3 min image clips last year on a 12 core MacPro, pimped out machine. At first the Raid died, and even after getting the new one it was slow., I ended up using my MacBook with my old 500 Gb Raid Drive:-)) worked like a charm.
“Always look on the bright side of life” – Monty Python
-
That could be it.
-
The iMac i7 works very well, I doubt you’ll need more. But then its a question between need or want. The new Mac Pro will be much more than most of us need anyway, but many will still want one. And once you own one your needs might change.
If you can afford to I would wait. If your clients don’t care about render times that much you should still be fine with your current setup.
“Always look on the bright side of life” – Monty Python
-
Neat Video has a very good noise reducer
“Always look on the bright side of life” – Monty Python
-
I left the default settings . Blend Mode: Normal opacity:100%
-
This is a before and after using compound
6276_multicamdissolveonwhiteproblem.png.zip
6277_multicamdissolveonwhitewithcompoundsolution.png.zip
“Always look on the bright side of life” – Monty Python
-
-
It’s not ignoring the white, what’s happening is that by adding the white you have a double white layer where the image is and a single white layer over the black portion. It’s happens in Legacy as well, compounds solve this. I’ve never done it with a multicam though, it’s very possible that there’s some funky stuff going on, I’ll see if I can recreate the problem when I get home.
You could move the Multicam to the secondary storyline and layer the portions adding dissolves to each, by default X adds them at the beginning and end of a storyline. Perhaps there’s something going on with the cross dissolve and the multicam.
“Always look on the bright side of life” – Monty Python
-
You can easily create handles by extending your footage past the compounds in and out points, inside the compound. The process with the white background is very similar in FCP7 using a compound, and its actually the fastes way to do so for what your trying. I do it quite often for one of my industry clients whenever I get compressed crappy grafics on white.
“Always look on the bright side of life” – Monty Python