So the brute force fix in progress now is the AE is double clicking each clip in the timeline which loads the clip with ins and outs in the source monitor. Then drag the clip down to an upper track and voila a clean clip with no skipped frame and once placed in the timeline the clip inherits the color correction from the already color corrected V1. Not ideal but workable for now until we figure out what is causing the skipped frame.
One interesting part is the clip obtained from double clicking the original clip in the timeline has an in and out that when dragged down into the timeline is consistently one frame long. Sounds like one part of Resolve acts like an edl style outpoint and another part doesn't. That's just a guess on my part but that is consistent with the behavior we are seeing.
--- In Avid-L2@yahoogroups.com, "johnrobmoore" <bigfish@...> wrote:
>
> So today on further analysis it turns out the skipped frames are actually in the Resolve timeline. When we go to sections with a skip we can see the source time code actually jump one frame at the skip. This makes sense giving there is a skip but this are within clips on the timeline. There is no edit point reflected in the clip that would account for a 1 frame shift. Also if we find the clip in the media pool it is clean with no frame skip and if we cut that into the show timeline on an upper track there is no skip there.
>
> The skipping clips came in as an aaf from Avid and it's not all the clips just every so often. I can't help still thinking there is some misinterpretation of 29.97 to 30 or vice versa going on. As far as I know all the settings involved in this are set to 29.97 or perhaps 59.94. Kinda frustrating.
>
> --- In Avid-L2@yahoogroups.com, John Moore <bigfish@> wrote:
> >
> > This one hour show was offlined in Avid using downconverts from multiple Red Epics. The finished offline sequence was decomposed in avid and then stringouts of the reels were made into timelines to facilitate exporting aafs of the string outs linked to the origial R3D files. This was done to transcode the need footage to DNX 220. Apparently the AE could not get his Avid 6.x to do the transcodes from ama linked R3D files. My similar system does but his doesn't. So the transcodes were done in Resolve. I'm not sure if those transcodes were then linked back up in Avid and a new aaf of the timeline was sent to Resolve for color correction but that is my guess at this point. The problem we are seeing now is that the .mov in ProresHQ exported from Resolve of the final show is skipping frames ever minute or so. These are a complete skipped frames that I have confirmed are not skipped on the original R3D files. My gut feels like something is
> > going on between 29.97 and true 30. The footage was shot 29.97P but I'm wondering if in one of the myriad of transcodes there could have been some link in the chain that was trying to in essence frame rate convert and thereby caused the skipping frame every so often. I stepped through field by field or Psf by Psf to be more accurate and it's definately skipping over a complete frame. Nothing like a frame being doubled up it's a missing frame that exists in the original. Anybody seen this type of behavior? I was not involved in the workflow so I'm trying to back engineer something that hasn't really been engineered from the start. TIA
> >
> >
> > John Moore
> > Barking Trout Productions
> > Studio City, CA
> > bigfish@
> >
> > [Non-text portions of this message have been removed]
> >
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (3) |
No comments:
Post a Comment