Michael Phillips
1
COW Coin
Forum Replies Created
-
I agree that AMA is a work in progress for all workflows, but as an FYI, you can create AAF from AMA linked media by checking “edit protocol” on the AAF export settings.
Michael
-
Have you tried AAF into Resolve? If there is no “=” equal sign on the cut between the two events, then it is two events. If they are continuous and only have a cut added, then EDL Manager might be optimizing the list to show as one long clip. Is that what is happening?
Michael
-
You shouldn’t need to be in multicam mode to see source. Once values are set in the TC24 column based on the conversion method I mentioned in my last post, they are available above the monitor.
Michael
-
Job is correct – basically SMPTE does not define an NTSC format at 23.976 or 24 frames per second. So from a metadata perspective, 30fps NDF or DF represents the video format being captured while the actual media is native 23.976 for editing. 1080p on the other hand does have a 23.976, and 24 defined by SMPTE. 720p behave like NTSC again.. SMPTE.
But working in NTSC 23.976 still allows you to track 24fps timecode in two dedicated columns – you can derive the 24fps based on the START and Pullin columns by doing a command-D or control-D of the START timecode column and selecting TC24 or AuxTC24 from the pop-up column. MC will not track both timecodes. It will also track 25fps, 30fps with no pulldown, PAL with pulldown, etc. basically representing any type of format that might have 24fps on it – whether it is native or not.
Once HD hit the market and there was a 23.976 and 24 defined, most “24p” projects gravitated towards towards those project types to have the 1:1 timecode relationship in the START column. DNxHD36 was added as the offline resolution just as 14:1 was for NTSC. DNxHD36 is roughly 3x the storage needs of 14:1 without about 10x the picture quality. 🙂
Michael
-
I started a thread on this at Reduser, so as to not duplicate posts, you can see it here:
https://www.reduser.net/forum/showthread.php?84627-Baselight-AVX-Plug-in-now-available-for-MC
I gave a high level view of differences depending on workflow. The continued discussion has some interesting insight as well.
Michael
-
The z400 is a nice machine and is supported by Avid. I am still running an 8600 as well as a z800. My only OS X is a MacBook Pro. But there is an interesting “control” being brought on by Apple – probably more so than the big scandal of a few years back of Microsoft loading its own browser on its own operating system. I am curious as to what is considered a monopoly in business – hardware, operating system, and purchasing software – everything getting funneled through the 30% cut.
Michael
-
usually when you buy a company, you also get all pending and granted IP belonging to that company. Unless those applications were licensing IP from other companies at the time, then it would have been negotiated at the time. I don’t believe that Apple dropped FCP7 development because of IP issues. It’s probably a combination of old code, starting from scratch anyway, and new business models that can better take advantage of the Apple store and in-app purchases allowing Apple to better manage their 30% of everything they don’t develop themselves.
Michael
-
And more to follow:
Michael
-
Then they must have used a syntax in the conform side to only look at the first 20 characters to go from:
B030C002_120819_R1XC_3cP_DNxHD_MXF
to:
B030C002_120819_R1XC
Michael
-
Andrew – I just got a response from Gamma & Density and they fixed the “Tape” metadata to be correct in v5.1.2. You may want to start using this version in order to have a better reference to the source file.
Mchael