https://github.com/dwhinham/mt32-pi/wik ... 2-pi-setup
The mt32-pi OSD settings are only visible if:
- You have enabled MiSTer support in mt32-pi
- I2C comms are working (the MiSTer core has received a message from mt32-pi)
If you mean you can't see the MT32-PI option in the ao486 (or AMIGA/ATARI ST) then you need to update the Cores and MAIN.
Either you haven't configured mt32-pi correctly (see previous post) or you're not using the custom user port->Raspberry Pi wiring scheme. You can't do this just with plain MIDI; there needs to be an I2C connection between the Pi and the MiSTer.shimian wrote: ↑Mon Jan 11, 2021 12:14 am Are any of the the Show Info - No, Yes, LCD-On (FB), LCD-Auto (non-FB) for MT32-Pi intended to provide an OSD over the HDMI output of Mister? I don't have the OLED display as indicated but at times would like to see the information on screen to validate it's working. None of the options I have tried work. LCD-On shows a dark gray box, but nothing inside of it.
I have full control over the mt32-pi via the OSD, I wired it myself to the arduino header with some jumper wires. I can change modes/etc of the mt-32pi from mister GUI, but when I toggle Show Info, I get nothing. Which is the correct Show Info mode to use with no LCD attached to the pi directly?d0pefish wrote: ↑Mon Jan 11, 2021 12:27 amEither you haven't configured mt32-pi correctly (see previous post) or you're not using the custom user port->Raspberry Pi wiring scheme. You can't do this just with plain MIDI; there needs to be an I2C connection between the Pi and the MiSTer.shimian wrote: ↑Mon Jan 11, 2021 12:14 am Are any of the the Show Info - No, Yes, LCD-On (FB), LCD-Auto (non-FB) for MT32-Pi intended to provide an OSD over the HDMI output of Mister? I don't have the OLED display as indicated but at times would like to see the information on screen to validate it's working. None of the options I have tried work. LCD-On shows a dark gray box, but nothing inside of it.
So this is odd. When I enable ssd1306_i2c, I lose mister control and the mt32 submenu disappears from my Mister OSD. Thought? I have everything wired to the schematic.
Thanks for the update. I’d double checked my config and wiring but still couldn’t get it to work. Now I’m thinking my issue is the same as this. I’m using short breadboard wires connected to a short USB 3 cable. I’ll try disabling the display output and, if that works, shortening my cables further.d0pefish wrote: ↑Mon Jan 11, 2021 4:10 am Just for the benefit of those following along, this was resolved after some chat outside the forum and looks like it turned out to be an electrical signalling issue.
If you're rolling your own wiring, bear in mind that I2C is extremely sensitive and can be broken by noisy signalling - keep wires short and use shielded cabling if possible.
Enjoy
Code: Select all
MIDILINK_PRIORITY = -20
MUNT_OPTIONS =
MP3_VOLUME = -1
MUNT_VOLUME = -1
MODEM_VOLUME = -1
FSYNTH_VOLUME = -1
MIXER_CONTROL = Master
MUNT_ROM_PATH = /media/fat/linux/mt32-rom-data
FSYNTH_SOUNDFONT = /media/fat/linux/soundfonts/SC-55.sf2
UDP_SERVER = 192.168.1.130
UDP_SERVER_PORT = 1999
UDP_SERVER_FILTER = FALSE
UDP_FLOW = 0
TCP_SERVER_PORT = 23
TCP_TERM_UPLOAD = /media/fat/UPLOAD
TCP_TERM_DOWNLOAD = /media/fat
TCP_TERM_MP3 = /media/fat/MP3
TCP_TERM_MIDI = /media/fat/MIDI
TCP_TERM_SYNTH = FluidSynth
TCP_TERM_ROWS = 23
TCP_FLOW = 3
TCP_SOUND = TRUE
DELAYSYSEX = FALSE
#USB_SERIAL_MODULE = /media/fat/pl2303.ko
[AO486]
MIDI_BAUD = 31250
UDP_BAUD = 38400
#TCP_SOUND_CONNECT = /media/fat/SOUNDS/connect_sav.wav