Michael Phillips
1
COW Coin
Forum Replies Created
-
It can work both ways – your already synced clips will still be sync clips most likely renamed clipname.sync.new
If you intended to do 1/4 frame slip sync, then an import is the only way to make that work when in a 35mm/4 perf project. AMA linking and transcoding, even in such a project will not work. If that is not needed, then you are good to go.
Michael
-
Here is that whitepaper:
https://www.avid.com/~/media/avid/files/hero-products-pdf/media-composer/avid-metadata-logging-tracking.pdf?la=enIt is still mostly valid but does not reflect any changes from Media Composer 7.0.3 and later. If you are working HD and offline proxy type workflows, then it should be fine.
Michael
-
Media Composer only accepts an ALE file for import and merging into existing clips. An ALE file is a somewhat enhanced TAB separated file in the fact that it contains a header and a separates of columns versus data. You need to convert that CSV into a TAB file, usually in Excel, and then in a text editor, remove all the extra TABs that Excel like to add and make sure the last event has a return character. I usually do this in TextWrangler while viewing invisible characters. Once all this is done, and the header is appropriate for your project type. Somewhere out on the Avid site is a whitepaper on ALE creation and metadata logging and management where there is a section on creating ALE files.
Michael
-
Glad it all worked out. Good luck with the rest of the project.
Michael
-
Certainly setting the frame rate different than the source can create issues between timecode to essence boundaries and such so that is an issue that needs to be corrected.
That being said, in my opinion, ALE import is not recommended at all to relink to media and make master clips. Especially when audio is involved. See my blog: https://24p.com/wordpress/?p=247
I will also say that when working with RED files, I prefer using RedCineXPro to make the native MXF files as they provide a one-step creation of MXF, AAF and ALE to merge. For digital camera workflows this somewhat outdated whitepaper from Avid still has some good information and has a pretty in-depth session for RED.
Michael
-
The first thing I would questions is why shoot 24.000 for a 25.000 delivery unless you have 23.976 and DCP deliveries as well.
And if that is the case, I question why record 25fps TC on audio when picture is a 24 – those should be the same to make post a little easier.
And with all that being said – try importing the 25fps TC audio into the 24fps project. Audio does not have a frame rate other than a rate defined by calculating samples from midnight. You will be prompted for a frame rate when importing, choose 25, MC will recalculate for the 24fps project and see if your errors go away.
Issue here is that timecode will get converted so EDL’s back to original BWF files will not be correct. You can change all the timecodes within the files (I recommend on a copy) to 24 using Sound Design’s WaveAgent. The import into MC. Wave Agent allows TC to be recalculated or not. See which one best fits your needs. Speak to your audio post folks if possible.
Michael
-
As mentioned in previous posts – you do not get any of the oversampling if your editing 4K footage in a 4K project. The only time that may come into play is if your source footage is greater than the project/timeline size, and event then it may depend on overall percentage of source to target ratio as you can read about here:
https://endcrawl.com/blog/2048×1152-is-a-total-crock/
Combine this with the fact that Media Composer’s resize algorithms are decent, but not great and are not optimized for scaling versus scaling down, your “quality” mileage may vary.
I reference this quality issue on a blog I wrote about stabilization, 4K, and FrameFlex:
https://24p.com/wordpress/?p=253
Michael
-
Typically in this type of workflow you highlight the sequence, transcode with handles that way you are only transcoding what you need. It sounds like you did all the source clips instead?
Michael
-
Make sure under the “special” menu (depending on what version you’re running) that render on the fly is checked. That may have gotten changed at some point.
Michael
-