- Posts: 44
- Joined: Mon Oct 15, 2012 4:52 pm
We are having a strange problem using MXF mix downs and edls. In avid, we do a mixdown of just the video, so that it just one MXF file, and export an edl of all the cuts. We then add the mixdown with the edl and color in Resolve 9. Once the color is done, we render a single MXF, not using the AVID AAF ROUNDTRIP (we made our own settings). We then take the MXF put it in the Avid MediaFiles folder, let it scan the databases and then use media tool to bring that file in.
The problem we are running into is that Avid thinks that the original mixdown out of the avid and the rendered file from Resolve are the same file and the avid gets confused and thinks the Resolve render is the original and vice versa. We also noticed that this doesn't happen when AVID AAF Roundtrip is selected (we don't use this option because sometimes we have multiple MXF mix downs in the sequence and using AVID AAF Roundtrip won't let you Render out a single file).
We have done a lot of testing and realized that it appears that Resolve is appending some kind of data from the first clip in the timeline to the rendered file and not making it unique from the original AVID MXF Mixdown. When we add blank filler to the beginning of the file in the timeline in the Resolve, this problem goes away. As a second workaround, we have been doing the export as normal as a single file (without the AVID AAF Roundtrip... which creates a file that we know gets confused in Avid) and then reimporting that single file back into Resolve and then using Avid AAF Roundtrip to export a unique single file.
Anybody else experiencing this?
Kenny
The problem we are running into is that Avid thinks that the original mixdown out of the avid and the rendered file from Resolve are the same file and the avid gets confused and thinks the Resolve render is the original and vice versa. We also noticed that this doesn't happen when AVID AAF Roundtrip is selected (we don't use this option because sometimes we have multiple MXF mix downs in the sequence and using AVID AAF Roundtrip won't let you Render out a single file).
We have done a lot of testing and realized that it appears that Resolve is appending some kind of data from the first clip in the timeline to the rendered file and not making it unique from the original AVID MXF Mixdown. When we add blank filler to the beginning of the file in the timeline in the Resolve, this problem goes away. As a second workaround, we have been doing the export as normal as a single file (without the AVID AAF Roundtrip... which creates a file that we know gets confused in Avid) and then reimporting that single file back into Resolve and then using Avid AAF Roundtrip to export a unique single file.
Anybody else experiencing this?
Kenny