-
Batch Rename and Relinking Media
-
Sandeep,
Here you go, I’ve recorded a video screencast. Sorry couldn’t be bothered talking so its only video.
As you’ll see I throw a few 5D Mark II H.264 clips in MPEG Streamclip, transcode to ProRes LT, bring them into X, change the clip names, delete & re-encode.
-
Wow, thanks Tony.
Very cool of you to take the trouble to do this.
Sandeep.
-
Not a problem… Is there any other reason why you use Grinder other than embedding a timecode?
-
We bought Grinder originally to both add Timecode (we used to use QT Change, but the Grinder GUI was easier for newer post interns/assists to deal with) and Transcode to ProRes.
But we’ve stopped using it as a Transcoder as it hangs sometimes when dealing with large amounts of data. Plus Mpeg Streamclip is faster.
-
ah ok I understand.
Why don’t you just let FCPX do the transcoding as Jeremy suggested?
It would eliminate that extra step and allow you to get cracking on the important part which would be keywording, adding favorites and so on. While you work on these, transcoding happens in the background.
When your ready to archive and want to reduce the size of the event, simply go to your finder, allocate the event in the Final Cut Events folder, and delete the optimised media folder which is found in the transcoded media folder.
Also you’ll need to remember that importing your files only creates a reference link, which means you’ll also need to backup the native H.264 files.
Really I’m only repeating what Jeremy has already suggested, but that’s the basic of what you want to do.
-
The workflow you guys have outlined seems pretty solid.
I’m re-running an old FCP7 Project through X this way right now on my iMac at home. Looking forward to taking this new Timeline for a spin.
-
Awesome… In sure you’ll have a few hair pulling moments, but try stick with it, I can garuntee you won’t look back after a few edits 😉
Good luck & let us know if you come across any problems.
-
While the MPEG streamclip method will work, it might cause more errors, especially six months later.
I think letting fcpx handle the transcodes will help you in the long run as it will be the most reliable.
Let us know what you find.
Jeremy
-
I agree Jeremy, X have made it such a breeze to create ProRes 422’s and proxy’s. The fact that you can switch between the two within the app is amazing. The only thing they now have to give us is the ability to transfer or copy a “proxy” event so that it makes it easy to take your projects along with you while on road. Fingers crossed this comes in the next release 🙂
-
Apropos to your point, is there any way to create ONLY proxies and import them into FCPX and be treated as proxies? This would be on a location shoot with limited drive space
I’m thinking of a workflow involving Resolve where you
1) Shoot “log” or RAW,
2) Import to Resolve and apply a LUT,
3) Export to ProRes Proxies,
4) Edit in FCPX,
5) XML back to Resolve,
6 grade the original media & render high quality ProRes
7) XML back to FCP
8) Reconform in FCPXIf I make Proxies externally, it seems FCPX treats them as “optimized media” on import and does not classify them as Proxy Media. Am I missing something?
Reply to this Discussion! Login or Sign Up