[Jeff Kirkland]

10.4 now has roles based clip selection. You can use the arrow keys to select the next/previous clip based on its role wherever it may be in the stack.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

pressing ‘C’ should select the clip on the primary storyline that’s under the playhead.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

Yes, EditReady handles mxff files just fine – or at least everything I’ve thrown at it so far.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

Different codecs perform differently when it comes to playing them back. When it comes to playback it’s more about the effort the computer requires to decode it than the actual bitrate. Pretty much everything about the Mac and FCPX is optimised for ProRes. Not surprising as it’s Apple’s own codec.

Editready has a couple of advantages (amongst its many) that might apply to you First, it’s not as awkward to use as Compressor if you’re batch encoding a lot of footage which can be a huge timesaver and second, it will read and embed as much of the original clip’s metadata as it can when transcoding. Compressor will leave all that behind, especially if the source is from a DSLR or camera that keeps the metadata in a seperate file on the camera card.

Anyway, enough of a sales pitch for Editready ????. Glad I could be of some help.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

[Cherin Bower] “My question is, is there a difference between the video imported to FCPx and create optimized media and the original source file? “

When FCPX optimises media it essentially creates a ProRes version of your file at whatever quality setting you set the project to (HQ, 422, or LT). That optimised file is used internally while you are editing. When you export, FCPX would use the original 1DX media to export from if it’s still available or the optimised file if not.

I’d guess that inside compressor the 4k for Apple devices preset is probably the closest to your export from FCPX. Otherwise you could create a new Quicktime Movie preset and use the Quicktime encoder’s settings, which I think you tried and liked? (sorry don’t have your earlier post in front of me.)

I personally use EditReady to convert pretty much anything I edit to ProRes – usually ProRes LT unless I need the extra quality for some reason. H264 just isn’t a great codec for editing – it can slow things down a lot – and I figure hard drive space is cheaper than my time.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

I’d say the only way to get an effect as clean as that is to rotoscope. Any plugins I’ve tried to produce that effect tend to be a bit hit and miss and just look like a badly posterised photo. The cartoon plugin in Resolve is actually pretty good and might get you close – or you might look at some cartoon/comic book actions for Photoshop (which people often forget can process video as well). But even with a plugin to automate it there would be a lot of clean up work to get it to the level of that sample video so it’s still not going to be cheap.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

Given that FCPX uses the same encoding engine as Compressor, the only reason for a file size difference between sending clips from FCPX to Compressor and just batch encoding in Compressor is the output settings. To speed things up a little you could send one clip from FCPX to compressor, save those settings as a preset and then just batch encode within Compressor

You might also try an application like Editready which is specifically designed to batch transcode footage to ProRes or h.264, amongst others. Not sure how it handles the 1DX files but generally if QuickTime can read it, so can Editready.

You could also try the free version Davinci Resolve for the batch transcode. Import the footage, edit it all to a timeline and then get Resolve to output the timeline as individual clips in whatever format you want.

Having said all that, I’d personally just open the originals in FCPX to view them. If that’s where you’re going to edit them and you have to review and organise the footage in there to prep for the edit anyway, then why not? I’d personally avoid any option that took a high quality original and transcoded it to a more compressed one, which most of you preferred options above would do.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

what about restoring the auto backup File?

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

You can see the source of the issue from the amount of spill on her hair. Avoiding it in the future comes down to better lighting and moving her further away from the green screen.

Fixing what you’ve got, you could dial down the spill removal until the pink goes away or do what you’ve done but add a shape mask to the colour mask to isolate her hair from her face. If she’s moving a lot you’ll either have to track it with something like Track X or do it manually. With enough feathering you don’t need the track to be amazingly accurate, just ball-park, so it shouldn’t take too long – unless it’s a three hour interview or something.

I’d personally do the key, get the editing done, then send the final result to resolve and track a colour mask there to do the final fix of her hair. Just way better tools than in FCPX.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland

[Jeff Kirkland]

What happens when you rename the clip to just .mov? Is it happening with .mov files from everywhere or just the one site? It’s possible the web site has something that is making Safari misinterpret the file type and break the downloads, so maybe try downloading the files with a different browser.

—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland