VOGONS

Common searches


First post, by rcblanke

User metadata
Rank Oldbie
Rank
Oldbie

Hi all,

Since it gets more and more problematic to have any influence on the midi device numbering in Windows, and adding and removing midi devices can alter the ordering of the devices in unpredictable ways, I thought it might be handy to also allow mididevice selection with DOSBox by using its name (or part of its name) in addition to its number/id. Please see the attached patch and compiled Windows executable. It works like in this example:

Z:\mixer /listmidi
0 "Microsoft GS Wavetable Synth"
1 "E-MU XMidi1X1 Tab"
2 "UM-1G"

Z:\midiconfig=1
(Status window shows: MIDI:win32 selected E-MU XMidi1X1 Tab MIDI:Opened device:win32)

Z:\midiconfig=um
(Status window shows: MIDI:win32 selected UM-1G MIDI:Opened device:win32)

Z:\midiconfig=xmidi
(Status window shows: MIDI:win32 selected E-MU XMidi1X1 Tab MIDI:Opened device:win32)

I hope someone will find this useful.

Regards,
Ronald

Attachments

  • Filename
    win32r3931.zip
    File size
    1.53 MiB
    Downloads
    13 downloads
    File comment
    Win32 executable based on [r3931] with patch
    File license
    Fair use/fair dealing exception
  • Filename
    midi_win32.patch
    File size
    1.04 KiB
    Downloads
    36 downloads
    File comment
    The patch file
    File license
    Fair use/fair dealing exception

Reply 2 of 30, by Yesterplay80

User metadata
Rank Member
Rank
Member

I'd also like to thank you for your patch! I have implemented it in my DOSBox ECE build.

My full-featured DOSBox SVN builds (without debugger) for Windows: Vanilla DOSBox and DOSBox ECE (Enhanced Community Edition)

Reply 8 of 30, by KainXVIII

User metadata
Rank Member
Rank
Member
Dominus wrote:

Screenshot or it didn't happen 😀

Sorry!

Attachments

  • midi.png
    Filename
    midi.png
    File size
    48.45 KiB
    Views
    379 views
    File license
    Fair use/fair dealing exception

Reply 9 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

hmm, for me neither... with svn on OS X

Edit: well, it's not supposed to work on Linux/OS X 😀

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox

Reply 12 of 30, by KainXVIII

User metadata
Rank Member
Rank
Member
Dominus wrote:

and it's the same when you are not in the NC shell?

Yes, i specially checked it without NC.

Last edited by KainXVIII on 2017-02-01, 21:56. Edited 1 time in total.

Reply 14 of 30, by KainXVIII

User metadata
Rank Member
Rank
Member
Dominus wrote:

And of course: does it work with lock stock DOSBox 0.74?

Proof 😀

Attachments

  • mix.png
    Filename
    mix.png
    File size
    6.37 KiB
    Views
    370 views
    File license
    Fair use/fair dealing exception

Reply 16 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Does it work if you use the new build without any autoexec commands or other commands? Asking to make sure you haven't accidentally another mixer program interfering

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox

Reply 17 of 30, by KainXVIII

User metadata
Rank Member
Rank
Member

Holy cow! I finally found the cause of why this patch is not working for me - i need to delete mt-32 roms from dosbox folder (and i even don't use builtin MT-32 emulation, only external MUNT)

Reply 19 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Yes, probably something like "if roms in folder x -> midi=mt32emu" to have less config settings but screwing up everything else. Or mt32 emu is enabled by default and failing without the roms and thus enabling normal midi again.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox