Michael Phillips
1
COW Coin
Forum Replies Created
-
It can be a viable option as you are only changing the codec from DNxHD to DNxHR. A few years back I wrote a blog about relinking across projects with different frame rates which you may find useful:
https://24p.com/wordpress/?p=22
Michael
-
A transcode process does not change the Tape Name or Source File name. I believe that starting in 8.3 (but definitely in 8.5) is the ability to preserve original clip rate and resolution from a single project. Or you have the option to transcode to project rate which will convert the frame frame.
You will need to look at how you want to finish and adjust the workflow at that phase of the project. For example, edit proxy with different frame rates, conform in Media Composer to camera originals, then transcode to a mastering codec converting it all to the same frame rate, then do your roundtrip.
Something to note with that process is whether or not you like Media Composer’s quality for frame rate conversion.
Michael
-
If PluralEyes is part of the process, then the grouping process will be the same for Adobe and MC. The only thing to be aware of is that it seems that the recent PluralEyes 4 seems to have removed AAF export from the application meaning that is no longer a solution.
MC 8.5 has included audio waveform sync for multicam grouping. It’s a good start and works fairly well as long as you tell it which clips belong together. It gets a little funky on lots of short clips though.
MC cannot change a group clip after the fact – so adding, removing, or correcting sync is not possible without creating a new group clip. Any sequence that used the old group clip will not relink to the new group clip so you would have to replace edit those events.
There are performance issues to be aware of – since multicam assumes multiple stream playback, the codec choice is important as is drive subsystem and connection type. Transcoding to DNxHD will be a benefit.
Those are some things to consider as you make your choice.
Michael
-
Most likely due to the fact that MC 6.0.1 is not qualified for OS X 19.9.x. According to Avid documentation, v6.0.1 is qualified with OS X: 10.7.1, 10.7.2, and 10.7.3.
Michael
-
I wish AppManager had a preference to not launch upon system startup. It provides no value on a day to day basis to be running all the time. When shutting it down, make sure you also go to Activity Monitor and shut down the AppManager Helper as well.
I keep an installer download from the Download Center and then I uninstall AppManager altoegther. I wait to hear about a release, then download from the Download Center. I have a dongle, so that is easier to manage this way.
Michael
-
It’s hard to say – as you mention it is an industry in flux and will continue to be over the next many years. Separating out the theory versus practical system training – it will be based on region, production type, etc. If the goal is to work in Hollywood on studio fare production, there is more Avid than the other NLE’s. If you want to work in a broadcast environment, you will find a mix of Avid and Adobe depending on station. There are a few that seem to be implementing FCPx. but those stories (seen here first) seem to point to Europe more than US at this time.
Different departments withing a studio or broadcaster may use something other than Avid – marketing, webisodes, etc.
Commercial houses, trailers, etc. are all a mix of NLE’s.
Corporate, houses of worship, WEVA, etc tend to more non Avid NLE, and a healthy mix of Adobe and FCP(x).
“Indie” market is also a mix of everything.
It is interesting to do a job search in different areas using Avid, Adobe, etc as criteria. The last time I did one for the Boston area I got:
and:
One can debate pay scale for Avid jobs versus Adobe jobs, etc. I think that has more to do with union versus non-union and not tied so much to the NLE anymore. It would be interesting to hear what other see in their area. especially outside the NY and LA markets.
Michael
-
Oh – right. I did not even notice that. You’re gonna have to transcode in another application like Resolve to make either native OPAtom MXF or other file that is supported for import.
Michael
-
The MXF plug-in is automatically installed with Media Composer since v7. When you select AMA link or Link to, you have the option to select which plug-in you want to use. Try this one first.
Sony plug-ins must be downloaded from Sony and the XDCAM version was the link I added in my previous post. MP4 is supported, but that is the wrapper and not the codec. Avid does not support XAVC-S, but the name of the file would indicate it’s XDCAM, so you’re good.
XDCAM is a longGOP compressed format. Usually I see film transfers use ProRes as a codec, but that is something you discuss with your vendor when submitting the job.
Michael
-
Very strange – I would try quitting MC, then go into each numbered folder in the Avid MediaFiles/MXF folder structure and delete both .msm files, then launch and try again.
Michael
-
Try AMA linking using the MXF AMA plug-in (select it directly, do not use Autodetect) and see if that works. The fact that is mentioned XDCAM might indicate the wrapper/coded used so if that does not work, you may need to download the Sony XDCM AMA plug-in and try that.
https://www.sonycreativesoftware.com/pdzk-ma2
Michael
