Forum Replies Created
-
Glad you got it fixed. That’s not something I’d have even thought of. You can do a lot of handy things by opening the source clip as a timeline and making changes but disabling the video probably isn’t one of them 🙂
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
If you select your project and look under the file menu, you’ll see the option to remove your render files. Theses are all the files created in the background above and beyond your original and optimised media. These include things like the thumbnails that FCPX shows when you look at a clip, the audio waveforms, etc.
Deleting these so FCPX has to remake them will flush out any corrupt background renders. Copying the project to a new library and choosing not to copy the render files will also achieve the same thing if you’re worried about media going missing.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
I’ll start by asking the usual… have you tried deleting the render files? I’ve found most weird stuff like that comes from a corrupt render. If not try re-linking the media and / or resetting preferences.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Most of my projects are corporate documentary with the occasion foray into television commercials.
To be honest, if I were planning to edit any great amount of h.264 footage, I’d be looking at a high end 27″ iMac. My 2012 model leaves the Mac Pro for dead with native AVCHD etc. but as soon as you get your footage into ProRes, you start to feel the benefit of the Mac Pro.
I started out looking at the base Mac Pro but ultimately the one I got, the default 6 core made more financial sense than upgrading the four core.
I think 32gb of RAM is the sweet spot for FCPX, along with the beefiest GPU you can get, then more cores. Apps are relying more and more on the GPU so I think that’s the place to initially spend your money on future proofing.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Agreed. I usually convert to ProRes but occasionally the project is small and needs a quick turnaround so I get lazy. Iif the going gets too tough for the Mac Pro I move the project over to one of my 27″ iMacs.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
I’m using a stock 6-core Mac Pro and i have yet to run into something I can’t edit but it does struggle a bit with 4k h.264 from my GH4s.
The most important upgrades are GPU and RAM. Those are the two factors that, if underpowered, will turn your shiny New Mac Pro into a boat anchor the fastest.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
My best guess would be dirt on the sensor. Maybe something that’s not going to budge with just blowing on it. I used to see that all the time with my Sony FS100. It seemed to constantly attract dust and dirt.
Get a magnifier and take a close look across the sensor for something stuck there.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Jeff Kirkland
June 23, 2015 at 3:16 am in reply to: Is FCP X running a bit slow cause I’m using a OWC ThunderBay 4?I think you’re probably right about the OWC drive. i think you said you were using the drive in it as individual drives rather than a RAID? It could even be on of the drives being faulty rather than the box itself.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Jeff Kirkland
June 19, 2015 at 8:36 am in reply to: Is FCP X running a bit slow cause I’m using a OWC ThunderBay 4?it could well be the drive but it could be anything, I once had a FCPX playback issue with beachballs and dropped frames that turned out to be caused an external audio interface but only if it was plugged into a port of a particular USB hub.
I spent two days rebuilding my entire system from scratch and making notes at every step to find that one. Sometimes it can be fixed with something as simple as deleting your FCPX preferences.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Jeff Kirkland
June 19, 2015 at 8:30 am in reply to: Is there any reason not to put everything in one event for a big project?I always use a lot of events for the sake of my sanity. I tend to treat them like you would folders in other NLEs. I then use keyword collections to further refine my footage. But it’s all just personal preference.
I don’t have any particular system. Events could be scenes, days, cameras, or sometimes even camera cards. Just whatever feels right as a natural top level for organising the footage.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland