Pro Tools cannot open the aaf exported by converter

[drunkenQCat]

Before opening a bug report, please search open and closed issues to see if the problem has already been addressed. If there is such a report, and your issue is not adequately addressed there, please reference the issues in your new report.

Bug Report

Please pick one of the following categories:

Incorrect Functionality and General Questions

Pro Tools 12.6 cannot open the aaf, neither the otio capable to davinci resolve I wrote, or the no_metadata.otio in test sources. The report is just like:

(translation: cannot open project because errors occur in the process)

To Reproduce

1. Operating System: windows
2. Python version: 3.12.8
3. Example snippet that demonstrates the issue - if it's a build issue,

import opentimelineio as otio

mytimeline = otio.adapters.read_from_file(r"no_metadata.otio")
otio.adapters.write_to_file(mytimeline, "test1.aaf", use_empty_mob_ids=True)

4. OpenTimelineIO release version or commit hash：0.17.0

Additional Context

What's more, davinci resolve cannot find the path of all sources when import the aaf tranfered by converter.

[timlehr]

@markreidvfx are AAFs without some MobID even valid for import?

[drunkenQCat]

after 2.0, the exported aaf still cannot be opened, reports the same error.

[rogernelson]

Discussed at OTIO TSC. AAF without MOB id are not valid. Is there a historical reason why we can generate them this way? @jminor @markreidvfx have any idea?

[drunkenQCat]

I tried use _generate_empty_mobid function in aaf_writer.py, finally exported an AAF file, but still cannot be opened. I used InfoDump.exe get the dumped data for debug:

test_dump.txt
and also, I used Davinci Resolve to export another correct aaf and got the dump info:

correct_dump.txt

Hope these info can help for debugging.