Michael Phillips
1
COW Coin
Forum Replies Created
-
There should be no performance issues if editing at DNxHD 115 (23.976) compared to DNxHD 36 (23.976) if your drives/raid are fast enough to support the data rate. Also, how are these drives attached to the CPU? I would look there first to not have to go through a transcode process. Also check to make sure you have enough drive space to hold both the DNxHD 115 and the 36.
If you do go down the transcode route, it’s fairly straightforward. Take your .sync clips, hilight them, go to transcode, select DNxHD 36, there should be no need to select audio as it will be on the same system. then OK. You will see several new clips being created with .new. One of them will be the sync clip that you will continue to use for editorial. Move those to a new bin for the editor. DO NOT DELETE original clips when doing so. When done, you can highlight sequence and do a relink to highest resolution and it will connect back to the 115.
Michael
-
Was there mixed frames rates in the timeline to start with? If so, there may be some +/- 1 or 2 frame adjustments happening in the timecode.
Michael
-
Just do a consolidate from the AMA linked files. It should be as fast if not faster than an import as it is a copy. If it is a fast import, then it’s probably a wash.
Michael
-
This came up during beta and the solution for now is to go to your IMPORT settings and “ignore alpha channel.” I know it’s not the most intuitive place to put AMA settings (as in not in the AMA settings), but it is the workaround for solving this particular issue. But there is still no metadata support other than file name and timecode.
I was able to grab the BMC Film LUT (if used) and imported into MC v7.
Michael
-
hmmmm… don’t know what to say other than an uninstall and reinstall of MC and the 1.8 plug-in?
Michael
-
I don’t think full metadata roundtrip is possible – it depends on what was done in Pro Tools as well as number of additional tracks, etc. Complete fluid, flexible, and automated Change Management would be a fantastic feature but a complete solution is a challenging task. Containers ala Avid DS might help the process in the interim, but there is no support for that.
Typically, the Media Composer would make changes on scenes or mix down from Pro Tools and a change list is created for picture that is handed off to the sound editor to make the changes.
Michael
-
It’s a start, but unless the START and END match exactly, you’re still out of luck. A quick test would be to import the ALE for the same clip that should match it. If none of those fields match, you are better off logging by copy/paste.
Michael
-
I are you installing version 1.8? 1.9 seems to be for v7.
https://avid.force.com/pkb/articles/en_US/Download/en394823Michael
-
Source File column was introduced with AMA which I believe came in a later version than 3.5. I am trying to remember how an in import is tracked in that version in order to enable a “merge”.
What I used to do in earlier versions, is first import the ALE, then do a “batch import” into the master clips created by the ALE file. But… unless the ALE reflects EXACTLY the START, END and DURATION, the import process will add or remove frames resulting in a wrong representation of the assets.
In your scenario, import the assets, and see what column are populated. One of then should be the file name. If it is not TAPE or SOURCE FILE, you will not be able to merge.
Michael
-
I don’t hold out much hope for that to work. I love MovieSlate and own it myself, but in order for a merge or batch import to happen, having the filename of the camera and Start and End timecode match exactly for each clip doesn’t happen. You will most likely have to merge it my some other means in an application outside of Media Composer. I would start with the following step:
1. AMA to your camera originals
2. Display in bin the following columns: Source File, Start and End
3. Export an ALE
4. In Excel, FileMaker or such, merge, or copy/paste info from MovieSlate ALE
5. Save out as ALE format and merge again.Also note that any locators/markers done in MovieSlate will not import onto source clips as Avid only allows Markers to be imported or exported with sequences.
Michael