- Posts: 35
- Joined: Wed Aug 22, 2012 11:11 am
- Location: Germany
Hi!
Since updating to DR17 (17.1 behaves the same way) on our Win10 machines, we have lots of problems with interlaced timeline, it seems as if the new interlaced processing workflow is broken.
I have an AAF from Avid, 25 minutes long, starting timecode is 10:00:00:00.
I have set up two projects in Resolve, one project interlace processing enabled, one interlace processing not enabled.
When importing the AAF with the option "enable interlace processing", my timeline does not match the Avid, all clips in V2 are 10h off (twice the starting timecode, 50FPS/fields vs. 25fps??)
Instead of 10:23:10:22 the clip on V2 is now on record timecode 20:23:10:22.
If I import the same AAF in my other project without "Enable interlaced processing" the timeline is correct, no clips moved 10h.
If I render out my timeline to AAF, I set my render settings to render with 10 Frames handles.
The rendered files in both projects only have 5 Frames handles. (10 fields). I guess because Resolve knows the source files are interlaced (Field Dominance shows Upper Field"). The AAF back in the Avid fails to link.
If I render out files that where shot progressive, I really get 10 frames handles.
If I set in and out in the editing timeline, resolve shows 356 Frames instead of 178. An interlaced timeline has in the FPS column 50, an interlaced source clip states 25. During grading or editing, Resolve does always seem to show deinterlaced material, never the original interlaced material on the video out. Scene cut detection seems to be broken with interlaced material. If I export a new AAF (generate new) with the enable interlaced setting and import it into the Avid, it has 50fps, and all the clips it is referencing have 50fps, no chance to relink.
So it really seems that Resolve is itself very confused with 50fields or 50 Frames. I still did not manage to deliver anything working using the method of an AAF with individual clips.
I think we need to get back to 16, at the moment any interlaced workflow seems to be fundamentally broken.
Thanks,
Flo
Since updating to DR17 (17.1 behaves the same way) on our Win10 machines, we have lots of problems with interlaced timeline, it seems as if the new interlaced processing workflow is broken.
I have an AAF from Avid, 25 minutes long, starting timecode is 10:00:00:00.
I have set up two projects in Resolve, one project interlace processing enabled, one interlace processing not enabled.
When importing the AAF with the option "enable interlace processing", my timeline does not match the Avid, all clips in V2 are 10h off (twice the starting timecode, 50FPS/fields vs. 25fps??)
Instead of 10:23:10:22 the clip on V2 is now on record timecode 20:23:10:22.
If I import the same AAF in my other project without "Enable interlaced processing" the timeline is correct, no clips moved 10h.
If I render out my timeline to AAF, I set my render settings to render with 10 Frames handles.
The rendered files in both projects only have 5 Frames handles. (10 fields). I guess because Resolve knows the source files are interlaced (Field Dominance shows Upper Field"). The AAF back in the Avid fails to link.
If I render out files that where shot progressive, I really get 10 frames handles.
If I set in and out in the editing timeline, resolve shows 356 Frames instead of 178. An interlaced timeline has in the FPS column 50, an interlaced source clip states 25. During grading or editing, Resolve does always seem to show deinterlaced material, never the original interlaced material on the video out. Scene cut detection seems to be broken with interlaced material. If I export a new AAF (generate new) with the enable interlaced setting and import it into the Avid, it has 50fps, and all the clips it is referencing have 50fps, no chance to relink.
So it really seems that Resolve is itself very confused with 50fields or 50 Frames. I still did not manage to deliver anything working using the method of an AAF with individual clips.
I think we need to get back to 16, at the moment any interlaced workflow seems to be fundamentally broken.
Thanks,
Flo