Michael Phillips
1
COW Coin
Forum Replies Created
-
This is not true. I have been using FrameFlex and DaVinci for several versions now including keyframed versions from the timeline. You need to make sure you select “use sizing information” when importing the AAF. It works with FrameFlex only on the source clips. FrameFlex only on the event, or FrameFlex on the source and additional FrameFlex on an event in the timeline. The one thing it does not support is the new “rotate” functionality.
But your mileage may vary with different aspect ratios or if source clips have any baked in letterboxing.
Michael
-
Then I would suggest exporting as OP1a via the AMA export and select the DNxHD codec you want to use. I wrote a blog on the process and may work well for you.
https://24p.com/wordpress/?p=278
Michael
-
If going from one MC to another MC, just copy the MediaFiles directly along with project and bin or just bins and move to the other system.
If it is AMA linked, that that is a different matter.
Michael
-
In most cases, you can right click on a clip or clips and go to the playback tab of the source settings and set it to project rate. You cannot arbitrarily set it to any rate, just clip or project. This will play back at frame-for-frame.
Michael
-
If I recall, the first FCM command defines the record side, then, if different, the second one defines the source. In my example, with mixed sources, it does not seem to indicate that the second event is drop frame. So something strange going on there either by FCM or by ; or : in the timecode.
You change timecode by clicking in the START field for that clip and entering a new value. Or use of the AuxTC columns to track a different timecode if needed, including DF or NDF.
Michael
-
That EDL looks correct. First FCM defines the record side which does not change, and the second one defines the source side assuming that all the sources are NDF. In my example, with mixed sources DF/NDF it does not seem to flag to the DF clip properly.
Michael
-
In MC 8.8 with the embedded list tool, I made a 3 event EDL with a drop frame timecode sequence as 29.97i
First source event is NDF
Second source event is DF
Third source event is NDFTITLE: Untitled Sequence.01
FCM: DROP FRAME
000001 FORS0001_02 V C 01:16:05:03 01:21:53:18 01:00:00:00 01:05:48:25
000002 FORS0001_01 V C 03:08:37:15 03:14:40:26 01:05:48:25 01:11:52:06
000003 FORS0001_02 V C 01:14:40:26 01:21:53:18 01:11:52:06 01:19:05:14And while the numbers are correct, the second event does not come across as DF as there is no FCM command nor ; in the timecode fields. Something to contact Avid about and get their thoughts on the matter.
Michael
-
I can’t remember the order if the first FCP is for the record side or the second one. But if you have both listed it seems to me that it is doing the right thing. I will look at how 8.8 behaves and let you know.
Michael
-
Typically you will see an FCP command for the record side, then for the source which is what you are probably seeing. Is this still using the standalone EDL Manager?
Michael
-
Are your deliverables progressive or interlace? Or are you using frame rate as shorthand for 29.97 progressive and 59.94 interlace?
Michael