Jeff Kirkland
Forum Replies Created
-
I’m mostly editing 4K ProRes on either a 4K or 1080p timeline so prefect playback is rendered. Unrendered playback is a little choppy but acceptable – although it can take a couple of seconds for playback to ramp up and smooth out, which I put down to a slowish hard drive.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Interesting thread… I have a BMD mini monitor and never change it to match my project resolution or frame rate. Most of my projects are 25p.
I just recently did a clean install of my Mac Pro, specifically to test if the BMD drivers were doing anything to slow down or cause problems in FCPX. I edited three days with no BMD drivers and three days using the mini monitor, but for me at least, there wasn’t any difference to playback or reliability ithat I could see.
Perhaps I’m just lucky I get to use 25p…
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
It’s always better to start with the highest resolution you can. If you want to deliver 1080 then edit the 720 into a 1080 timeline.
I personally don’t have an issue with FCPX scaling 720p to 1080p. The 720p footage usually only needs a little sharpening to my eyes – but I have a friend who would consider it unwatchable and would have to spend hours putting all the 720p footage through some arcane process to uprez it to 1080p.
It’ll really only takes a few minutes to create a project, throw some 1080 & 720 clips on the timeline, and render it out. Then you can make the decision.
At the end of the day, whether it’s good enough will be entirely up to you, but as I said first up – I think you should alway edit at the highest resolution you need. You can always render that 1080 timeline at 720p if you decide the scaling quality just isn’t working for you.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Whatever it was shot at, I’d create a project that matches your delivery format and edit in that.
FCPX should automagically handle everything under the hood. Obviously if you choose 1080, the 720p footage is going to be blown up and slightly soft.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
for some reason I can’t edit my own posts so I’ll add here…
What I guess I’m asking is that when you slect an angle, the multiclip on your project timeline gets cut at that point you should now be able to slect either side of the cut. You’re saying you can’t do that?
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Just a recap… You sync your clips, creating a multicam clip. You add the multicam clip to a project timeline. With the multicam clip selected, and the multicam viewer open, you select angles. When you do this, you should see cuts on the timeline as if you had used the blade tool.
This is not happening? The multiclip on the timeline doesn’t get bladed? (Is bladed a word?)
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Or you could probably just load the xml into a text editor and do a search/replace to remove the .mov extension from the file names.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Im always cautious about running them both on the same computer. I find I have many more mysterious slow downs and weird happenings when they’re co-existing. My first choice would be to do as Andy said and install on a seperate partition.
I can’t remember the exact details but support for legacy FCP Studio has actually gotten a little better in recent years. I know issues that DVD Studio Pro has had since Lion were fixed in Yosemite.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Depends on the type of gradients you want to make. You can use the gradient generator in FCPX for simple ones. Beyond that you need the current version of Motion to publish new generators. Motion is cheap and really does add to the flexibility of FCPX.
Of course there’s nothing to stop you creating the gradient in the old version of Motion and just rendering the final clip for use in FCPX.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Not a lot of help – but if you’re compressing in Handbrake and other apps and the uploaded file is still wrong then I doubt it’s anything that FCPX is doing. I can remember any number of posts from people having exactly the same sorts of issues with FC7.
From my experience, there’s always at least a gamma shift going from anything OSX to YouTube.
Keep in mind that you are looking at a colour managed preview in FCPX, Quicktime, etc but once it gets to YouTube, all bets are off.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland