Michael Phillips
1
COW Coin
Forum Replies Created
-
If you look at the MediaTool, is all the media there?
Michael
-
Hmmmm… didn’t help as much I would have liked, but maybe others have an idea. In recreating the db, was it refreshing existing links or just AMA linking anew and going from there?
Michael
-
Version of Operating System?
Version of Media Composer?
What were you doing at the time to create the error message?Michael
-
I export as DNxHD or DNxHR from Media Composer as OP1as it is very fast and you don’t need to render or do mixdown beforehand. Select sequence and export as OP1a and in the dialog box you can select which codec data rate.
Michael
-
Any DNx codec inside MOV wrapper will not play anymore. If you want something universally playable then you will want to make an H.264/M4V of your OP1a export from Media Composer. MXF OP1a can be opened and transcoded in Compressor, Adobe Media Encoder, and Handbrake, Shutter Encoder, etc.. It can be opened and played in VLC.
Michael
-
https://avid.force.com/pkb/articles/en_US/Compatibility/The-future-of-Avid-DNx-on-the-Apple-platform
QuickTime wrapper (MOV) and 32 bit codecs, etc. have been deprecated. DNxHD/R are fine as long as it’s in a different wrapper. I moved away from MOV years ago and use MXF OP1a.
Michael
-
A workaround is to change your project to HD, make your titles and go back to whatever it was. There may be softening as a resize is being applied.
Michael
-
Chances are you are in a greater than HD resolution project. Title Tool only works up to HD. Blue Titler was an interim stop-gap solution to allow HD+ size titles to be created. Titler+ was added in more recent versions of Media Composer to deal with HD+ resolution title creation, but it has its share of hit and miss as well if you read the forums.
This was added in 2018.12:
https://avid.force.com/pkb/articles/en_US/How_To/How-to-create-a-title-with-the-new-Titler
Michael
-
Great! There’s a lot of legacy workaround practices still in place that does not behoove the newer workflows in more recent versions of Media Composer. Avid has not updated its detailed workflow guide since before there were greater than HD project sizes but would be quite helpful.
Michael
-
I just did a test:
1. 48.000 fps native clip. Recorded and playback metadata as 48.000 fps.
2. AMA Linked into a 23.976p project and timeline
3. Edited the 48.000 fps clip into a sequence, set the motion effect to be 100% playback (resulting in 23.976 playback) and exported an AAF.
4. I also took the same clip and vide source settings set it to be project rate (from 48.000fps to 23.976fps). This changes the master clip to now be slomo at 23.976. Edit that into a sequence and exported an AAFIn both cases, the AAF conform in DaVinci Resolve linked to the camera master file (48.000 fps) and resulted in the proper slow-motion playback as expected.
With newer versions of Media Composer there is no longer the need to open clips in a their native frame rate project. Also, I am unclear as to what you might have done in that 60fps projects when you say: “After slowing down the 60fps transcoded media in project 2 I have copied the Master clips” Whatever happened here may have broken any kind of link to the original camera master.
Motion Effect Method:
Source Settings Method:
Michael
