Michael Phillips
1
COW Coin
Forum Replies Created
-
Nexidia supports a couple dozen languages and dialects and language packs were available to purchase for both ScriptSync and PhraseFind. Whether Avid’s implementation stayed updated with latest versions might be a reasons for a more limited set of languages as new ones get modeled over time.
Michael
-
Resolve will make MXF native DNxHD and lates version makes DNxHD is using MC 8.3.
Michael
-
Script Based Editing is what the feature was called before the phonetic transcript alignment was added (Nexidia technology) at which time it was rebranded ScriptSync. While waiting for the licensing issues to be sorted out, script based editing still exists and does provide a unique view of the coverage available to me as an editor and the ability to select line(s) and take(s) for review, etc. I am editing a short right now where I manually synced the takes to the script for just this purpose. I wish Avid would take this view more seriously as the functionality hasn’t changed since it was first introduced in 1996-7 – other than “hold slated on screen, and of course the phonetic sync capabilities.
The phonetic sync is what really brought the feature to the masses as it eliminated the one major pain point of the process – which is syncing. Transcripts can be done faster manually, but when dealing with multiple takes takes more time manually.
But once lined, it is a great way to edit. And no, there is no such thing in other applications although Lightworks did show a script line view back in the 90’s but the Ediflex patent held up. That patent is one that Avid got in a deal when Ediflex went under and Script Based Editing was implemented from a new design. But that patent has now expired (3-4 years ago?) so there is no real reason why we won’t see similar solutions coming to market. Avid does have additional patents which refer to auto-lining using speech technology which covered the use of technologies like Nexidia, but even those are set to expire relatively soon.
There’s a bit of history lesson in what should be a quick answer, no other NLE’s have it (at this time).
Michael
-
I believe if you make a copy of the clips, they still relate to each other when making changes. I am not sure, but that seems to be the issue based on your description. SubCap is another example of a solution that had a promising start, but has never been updated or refined, so one has to work within its limitations. When you do, it works fairly well.
One thing I would try is exporting your current SubCap track and then add a new SubCap effect to an upper track and import the file back in creating new SubCap events on the timeline which should now be unique and able to be edited without affecting other clips.
I also not believe that “mute clip” new in v8 applies to the SubCap effect which would allow you to turn off and on the individual subtitle, but I may be wrong. Using one of the smarttool red/yellow arrows, select a SubCap effect and right-click – is there a mute clip selection available?
Michael
-
Typically you would copy the files to the Avid MediaFiles/MXF/ folder. Launch Media Composer and import the AAF file. This should relink automatically. Then highlight all the master clips created from the AAF import and do a “merge ALE” into those clips (see import settings for shot log – last check box).
I do not recommend importing an ALE and doing a relink – while it can work, it can be more problematic for audio relinking and there have been reports of files becoming unlinked down the road. The AAF has the ID needed for the clips’ picture and sound essence.
If the AAF does not automaticaly relink, then there might be a problem with the AAF – next thing to try is put those files into their own numbered folder, then from a bin, import the mob.msm file (can’t remember which one exactly, I am not in front of a system right now) that is in the folder after you launch MC. Then do the ALE merge as mentioned.
Michael
-
Unclear as to whether you were renaming the files themselves or keeping a separate log. Renaming files can be dangerous for certain formats like XDCAM, RED, and other that depend on a sidecar metadata file. Typically self contained .mov files are OK to change unless it is an ARRI type recording which also provides either an XML or ALE type metadata files to use that has more than just timecode.
Organization wise, it sees fine – how clips get logged and parsed to bins it defined by program and editor preferences.
Michael
-
How to relink to different frame rates after a transcode – might help if you’ve already started down that path.
https://24p.com/wordpress/?p=22
Michael
-
There are only two user definable metadata fields that can be displayed as “clip text” in the timeline:
1. Name
2. CommentsAnd the “comments” does not come from a bin column, but the comments attached to each event in the timeline via the record side menu “Add Comment…” which was designed for EDL comments back with the original Avid/1 Media Composer in 1990.
The question that comes to mind is why you don’t want to change the clip names? The orignal file name is being tracked in either the Tape or Source File column, and if you want an additonal level of redundancy, you can duplicate the Name column into the Labroll or Camrol column for list generation if needed (EDL) and then change Name to something relevant like Scene_Take. This is way productions have been done for decades, even in the more recent file based world.
The only time this comes up (as it is not the first time I have heard this request) is from users that come from an FCP background. MC uses different linking and metadata management functions, so this is not an issue.
Michael
-
If you are referring to LUT support color management, that first showed up in 7.x. If you are referring to monitor display color management, then that was with 8.3. Are you referring to some other color management?
Michael
-
Did you start in MC or in Resolve?
Was it AMA linked in MC, then transcoded?
Or linked to camera orignals in Resolve for the conform?
When you say “dragged new AAF” was it really a “new” AFF or the same AAF used in the conform?
AAF should not go into the MediaFiles folder. Only the MXF files. Put the AAF elsewhere like on your desktop to be imported.
DNxH4 at 4K can still have too high a dat rate for your system drives and connectivity, thus the need for yellow mode.Michael
