On Thu Feb 8 13:23:22 2024 +0000, Nikolay Sivov wrote:
There is still a bug which is already in the tests, where the topology
id of the resolved topology will not match the original topology (when not using the no resolve flag), this is because of a bug with the topo loader where it creates a new topology object with a different ID, in Windows apparently it creates a new topology object but it contains the same ID as the not resolved topology. Is that Load() functionality to preserve IDs? We should probably test that with Load() as well. However, since one case use a custom loader, maybe this is implemented in both places.
I wrote the test for IMFTopoLoader::Load, as you can see the topology ID of the full topology doesn't change and the topology object address does change.