Implementing support for MFPlat.dll and MFReadWrite.dll

[André Hentschel]

Am 25.12.2013 01:48, schrieb Alexandre Bique:
> 
> I'm trying to make Ableton Live works better with wine, and as stated
> in this bug: https://bugs.winehq.org/show_bug.cgi?id=35105 setting
> wine version to win8 will make Ableton Live crash.
> 
> I first though that it was an issue with the OpenFileDialog being
> replaced by IFileDialog because it was something that changed and it
> was visible, but after second thought, I'm thinking about something
> else.
> 
> I noticed that ableton tries to load these libraries:
> 
> err:module:import_dll Library MFReadWrite.dll (which is needed by
> L"C:\\users\\Public\\Application Data\\Ableton\\Live 9
> Suite\\Program\\VideoExportMMF.dll") not found
> err:module:import_dll Library MFPlat.DLL (which is needed by
> L"C:\\users\\Public\\Application Data\\Ableton\\Live 9
> Suite\\Program\\VideoExportMMF.dll") not found
> 
> and they're part of Microsoft Media Foundation ...
> 
> And just after IFileDialog returns with valid data, the application
> crash and we can see on the output:
> 

How do you guess by that output that it's about some MF*.dll?
is e07010ec-bc17-44c0-97b0-46c7c95b9edc related?
I don't know how things behave with missing interfaces, but i guess the app get's a NULL pointer back and tries to call a function from that object.
(so an easy test hack would be to stub an interface like that somewhere else and see what happens)

> 
> So what do you think? Is MFPlat.dll and MFReadWrite.dll a good
> candidate? If so, how to implement the library? What are the
> guidelines?

Guidelines can be found in the documentation.
You can also use git to see how new dlls are built up. e.g. b03d07dff4d710d9176602a7d939c94bf7dd89ff