- Posts: 6
- Joined: Fri Jun 10, 2016 3:21 pm
Tue Apr 17, 2018 12:30 pm
We shot 29.97p HD footage in XAVC-I with Sony FS 7, log, generated MXF rushes in Resolve for Avid. I accidentally created files that were 1080i instead of 1080p.
Editing in Avid you get a motion adapter on each clip but it edited fine, so didn't realize my error until trying to export an AAF and bring it back to Resolve for grading. All the other sequences from progressive rushes work fine, but when this AAF comes into Resolve it can't find EITHER the original camera files or the transcodes. I've tried all variations of assist using ... and turning off assisting.
I've also tried relinking individual clips on the timeline in Resolve to source media. no luck.
I'm assuming its because of the interlace issue. Though, the AAF and edited sequence are in interlace, as are the transcoded rushes, so I would think that would work.
Five other sequences have worked fine; all with normal progressive footage; and progressive clips on this same timeline have worked too. Just not the interlace ones.
Any suggestions much appreciated!
Editing in Avid you get a motion adapter on each clip but it edited fine, so didn't realize my error until trying to export an AAF and bring it back to Resolve for grading. All the other sequences from progressive rushes work fine, but when this AAF comes into Resolve it can't find EITHER the original camera files or the transcodes. I've tried all variations of assist using ... and turning off assisting.
I've also tried relinking individual clips on the timeline in Resolve to source media. no luck.
I'm assuming its because of the interlace issue. Though, the AAF and edited sequence are in interlace, as are the transcoded rushes, so I would think that would work.
Five other sequences have worked fine; all with normal progressive footage; and progressive clips on this same timeline have worked too. Just not the interlace ones.
Any suggestions much appreciated!