At least we found what cause this problem, maybe it will be useful for someone.

Just tested and the presence of the ROMs does prevent the listing for me as well.

@collector: can you check whether it is because mt32emu is always enabled or by default and when you disable it, the roma don't matter?

Dominus wrote:

@collector: can you check whether it is because mt32emu is always enabled or by default and when you disable it, the roma don't matter?

Does not matter, roms cause issues even if mt32 emulations is set to off.

Thanks for checking! This is bad coding then 😉

The command "mixer /listmidi" works with the win32 midi device only!

What I think is happening here is: The MT32 patch makes MT32 emu the new default midi device (which I don't like really). So if you start up DOSBox with "mididevice=default", it tries to load the MT32 emulator. If you set up your config pointing to the roms in the DOSBox directory and you start up, MT32 emu will successfully be loaded, but "mixer /listmidi" won't show nothing. Now if you remove the roms from the directory, the MT32 emu won't load and DOSBox does a fallback to the win32 midi device. And, as we now know, "mixer /listmidi" works with that one and will list the midi devices successfully again. Please have a look at your DOSBox status windows, I bet it looks like this:

As you can see here, DOSbox doesn't care if the roms are in the same directory:

So, we should tell Sergm to change his patch that it doesn't set mt32emu as default 😉

Dominus wrote:

So, we should tell Sergm to change his patch that it doesn't set mt32emu as default 😉

I asked him how to change it, maybe it's no big deal.

UPDATE: Changed! Win32 is now default again.

I added something based of this to r4015-4017.
Thanks rcblanke!

Awesome, thank you qbix!

Qbix wrote:

I added something based of this to r4015-4017.
Thanks rcblanke!

Work same way?