David Eaks
Forum Replies Created
-
Just saw this article on RedShark, thought you guys would be interested-
https://www.redsharknews.com/production/item/463-this-is-a-groundbreaking-video
-
No problem! If I had to pick one thing to explain why Prores is higher bit rate, I’d say because its easier for your computer edit with it. Ever try to edit a 2 hour multicam clip with a few angles of H.264 (in an App that supports it natively)? Not so pleasant. Convert to Prores and its not a problem at all.
The 50 Mb/s cameras you’re referring to are recording in a 422 codec, keeping that crucial picture information for grading, compositing etc. For higher end work they bypass in-camera compression via HD-SDI and record 444 or uncompressed externally. But that’s getting out of my territory, I’m happy with shooting to Prores LT on my Ki Pro and editing in FCPX.
-
[Jeremy Garchow] “Have you tried the custom naming options after import?”
Oh man… somehow it has eluded me. I don’t really need to do a lot of clip naming and organizing in my daily work though. With a quick Google search I found and read this-
https://www.kenstone.net/fcp_homepage/fcp_x_batch_rename_clips_young.html
It does look good. Now if they could just stick that function into the import window.
-
Bret Sherman-
“but I’ve never felt like I should waste the disk space or time doing that.”Do it any way. Waste disk space? What? That’s what it’s for.
But its understandable that over time, all those little cards build up and waste a ton of space on your media drives. So don’t back them up there. Similar to Jeremy, my method is to first copy the cards to a dedicated external drive, then import individual clips in FCPX to the media drive as needed. Gives that extra layer of redundancy, in case the media drives fail and then the backup explodes, at least the SD Cards Drive is still there. If not, there is a disaster and you need to stop, drop and roll, get to high ground or flee to the bunker!
I agree though, there needs to be a preference for option for naming on import. I miss the old L&T custom naming conventions (but I don’t miss waiting for that window to finish processing). It would be nice to have a section of the import window to set metadata and custom name appends etc, which would apply to imported clips. Or a toggle that enables a little pop up for each I/O selection, where you can name the clip or add a keyword etc. before importing. The FCPX import window still needs a little more paradigm shifting.
-
Log and transfer is bringing in the clips as Prores 422, which is about 17MB/s. Which is exactly what should be happening. You are on the right track, there is no need for a higher quality setting.
Your camera is recording AVCHD at 24Mb/s, log and transfer is making it into Prores at 147Mb/s (or 17MB/s). A matter of big B or little b. Notice that the Prores clips are much larger in file size than the original AVCHD clips.
-
like method A) from Bernhards post, but in FCPX, I found that: Exporting your final HD project and bringing that file back in to an SD timeline, exporting the SD, then importing that to Compressor for DVD as normal produces results that are close to hardware scaling with either AJA Ki Pro or Matrox MXO2.
I’ve mentioned it a couple times but no one has ever replied with comments about this method in FCPX. I’m curious of others opinions.
As an alternative to the above, you can just change the project settings to SD then export. But I found a bug with that method. Where the text of a title, only if it is in a secondary storyline, will not scale down properly and words can even end up being larger than the screen size. This issue does not show up in the timeline, only on export. Simply cut/paste the title to fix it before exporting. On the other hand, if the HD project needs a lot of long rendering, better to just do it once during HD export, as in the first method. So to avoid having to render all the effects again in the SD timeline, at the same time as scaling down.
-
Yeah, a while ago I created a few Smart Folders intended for importing files from. Got them all set up just right, but before testing an actual import from a smart folder… That didn’t work out.
What I did was add some often used folders to my favorites in the Finder sidebar, which show up in the FCPX import window as well. Would it be possible to make a smart folder that collects folders, which have the files you want in them? Then add it to the favorites list in hopes that files in the folders within the smart folder are actually importable.
-
Mark Morache-
“-keystroke for audio crossfades (extend audio and add fade?) across all selected clips”That would be very handy indeed!
-
How far into the edit are you? I’d recommend that you export a small test clip and see if the problem shows up in the exported file.
The one time I had this problem, the only thing I found to fix the issue was to create a new multicam clip. Even with the same media as before, the new one was fine. Never found any explanation or fix.
-
I assume you have the destination for the Job set to your media drive? I like the default destination set as same as source.
If you open Compressor, with nothing currently processing, and click “clear” in the history window, do all the items dissapear? Or are some left? If some are left, try going to Compressor> Reset Background Processes> and choose “reset and cancel all”. Maybe check out Compressor Repair and Preference Manager from digital rebellion as well.
FWIW I’ve run the same general setup of MBP w/SSD (OS and Apps only) & 500GB (Media drive) internal drives, using Compressor with job actions to encode and burn Blu-ray and DVDs successfully for quite awhile… So, at least we know its possible. What are your system specs and OS/App versions?