@kelvfimer said in Playing X68000 games with MIDI music:

My point is how to set up that timidity.cfg and sd.cfg what's the way to tune it etc.

As I've written before: The only (uncommented) line in my timidity.cfg is:

soundfont "/usr/share/sounds/sf2/SC55.sf2"

I have no SC55.cfg of any kind. Maybe my midi output is not configured correctly, but I can hear midi music in several x68000 and pc98 games. They seem so sound correctly, but indeed I also have a slightly irregular midi output (it sometimes slows down for some notes).

The only real problem I have are buffer underrun errors in the logs. I'm not sure if that corresponds to the timing issues, but it might.
I'm not sure how to get rid of them, but I would think that the midi daemons have to run in or close to real time.

@mitu thats sad, wish I knew how to code for it, as Elan Performer software takes midi-in. Great for triggering animations. Not to mention Octamed audio tracker for making music :(

Any idea what would it take to do, is it scripting or C+ coding. etc?

Some refs I have found:
https://github.com/midwan/amiberry/wiki/Serial-Port-support
and for a PC/Ami emulator:
https://www.amigaforever.com/kb/13-107
and this for Linux/Amiga:
https://mathr.co.uk/blog/2019-12-10_midi_network_between_linux_and_amiga.html

@roslof said in Retroarch not registering MIDI Soundfont Files for DosBox-Pure:

@testudo said in Retroarch not registering MIDI Soundfont Files for DosBox-Pure:

@roslof Thanks for the suggestion. I removed all but one SoundFont file from the <system> folder and also removed the Gravis Ultrasound folder/files from the <rom> folder as an added check. Unfortunately, no change. Retroarch is still not registering the single remaining .sf2 file.

I don't want to steer you wrong, but this still sounds like the same problem I had. It was scanning other folders (not just the pc folder) and finding .sf2 files. One of which was 512MB and its mere existence prevented the pull-down from displaying properly. Are you certain there isn't a lingering .sf2 hanging out in a scummvm folder or something?

@roslof I do have other .sf2 files spread throughout usr/share/sounds/sf2 and scumm/extras folders. I'll give renaming them a go and see if that does the trick.

@mitu Awesome, this fixes it! Thanks for the help.

@Protocultor
Protocultor for President :D
Thank you very much, it works. Now the only thing left I need to know is, can you change the deadzone amount of the left analog stick somewhere? I know you can change it in the option for ingame movements but it doesen't apply for the menu navigation and when I move up and down it often register a left or right movement and messing up my settings.

UPDATE: Nevermind I found the settings in the config folder inside zdoom.ini

I've followed your tutorial (many thanks btw!) and managed to get MT-32 emulation through Munt 2.5.0 working on RetroPie v4.7.1 using a RPi4. However, I've got a little issue with switching between TiMidity and Munt.

This is what the pre-Munt device configuration looked like:

pi@retropie:~ $ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'TiMidity' [type=user,pid=577] 0 'TiMidity port 0 ' 1 'TiMidity port 1 ' 2 'TiMidity port 2 ' 3 'TiMidity port 3 '

And this is afterwards:

pi@retropie:~ $ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'MT-32' [type=user,pid=645] 0 'Standard ' 1 'GM Emulation '

As you can see, TiMidity is no longer listed.

How can I revert back to TiMidity, or even better use both at the same time on different ports? When I disable autostart in rc.local and reboot the system, TiMidity doesn't automatically shows up. How can I resolve this?

EDIT: I've managed to get it working by performing "sudo apt-get -y install timidity timidity-daemon". For some reason installing Munt resulted in the TiMidity daemon disappearing, but that has now been resolved.
EDIT2: Never mind, it was just a brain fart. It wasn't even configured as a daemon/service prior to installing Munt. I hadn't touched RetroPie for over almost a year and forgot that TiMidity is started/stopped though scripts used by the systems/emu's (i.e. PC).

Currently it looks like this:

pi@retropie:~ $ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'TiMidity' [type=user,pid=538] 0 'TiMidity port 0 ' 1 'TiMidity port 1 ' 2 'TiMidity port 2 ' 3 'TiMidity port 3 ' client 129: 'MT-32' [type=user,pid=654] 0 'Standard ' 1 'GM Emulation '

For comparison sake, I've done some testing between TiMidity and FluidSynth. I must say they're pretty on par, but as a service I prefer TiMidity, as it's less resource hungry.

pi@retropie:~ $ aconnect -o client 14: 'Midi Through' [type=kernel] 0 'Midi Through Port-0' client 128: 'TiMidity' [type=user,pid=539] 0 'TiMidity port 0 ' 1 'TiMidity port 1 ' 2 'TiMidity port 2 ' 3 'TiMidity port 3 ' client 129: 'MT-32' [type=user,pid=652] 0 'Standard ' 1 'GM Emulation ' client 130: 'FLUID Synth (4992)' [type=user,pid=4992] 0 'Synth input port (4992:0)'

The post [Tutorial] Installing Munt (MT-32 emulation) on RPi 3 might be interesting regarding this topic.