Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hanging notes/data corruption on GPIO input with certain MIDI sources #21

Closed
thorr2 opened this issue Aug 16, 2020 · 97 comments
Closed
Assignees

Comments

@thorr2
Copy link

thorr2 commented Aug 16, 2020

Hello, I just installed this for the first time and made my own MIDI adapter for the GPIO pins using your schematic. I hooked up an OLED display and it works properly. Munt is missing some note-off's and it is consistent (always happens in the same places in the same songs). I am using Monkey Island 2 for example on my MiSTer and the music always has hanging notes in the same places that should not be there. The display shows these notes hanging. I have tried different chunk sizes (32 and 2048) and set my frequency to 32000 and the scaler to none. Nothing so far seems to help. Any ideas what could be causing this? I have also played Doom on my MiSTer with my Roland SC-55 mk2 and it works fine with no hanging notes, so that is not the cause. I also tried playing to the mt32-pi from my PC and it also has hanging notes. Thanks for your help.

@dwhinham
Copy link
Owner

Hi!

Which model of Raspberry Pi are you using?
Is there any chance you can get me a recording of the hanging notes or tell me a specific song/time to look for so I can try to recreate the problem?

@thorr2
Copy link
Author

thorr2 commented Aug 16, 2020 via email

@thorr2
Copy link
Author

thorr2 commented Aug 16, 2020 via email

@dwhinham
Copy link
Owner

dwhinham commented Aug 17, 2020

Thanks for sending me the MIDI.

I've just tested playing this song from Windows on mt32-pi v0.3.1, using my GPIO midi interface - it worked just fine with no hanging notes.

I'm guessing there is an electrical issue with the GPIO circuit.

  • Can you measure the resistors to make sure they're the correct values and in-spec?
  • Do you have another optocoupler you could try?
  • Is your PSU and USB power cable good enough for the Pi? If you test with Raspberry Pi OS/Raspbian, you should not be getting any 'lightning bolt' symbols on the screen or undervoltage warnings in dmesg when the Pi is under stress if your PSU is good.

@nswaldman
Copy link

I'm experiencing something similar with the PI-MIDI board I've just received: the onboard MIDI interface is doing drunk renditions of the MIDI data while USB is fine. Here's some listening material: https://www.dropbox.com/s/5kcjc7rlauv0scf/recordings-mt32pi.zip?dl=0

It's not identical, but there's a slim chance we're both having the same problem. I'm still in the process of ruling out the usual suspects (cables, power adapters, different Pi units).

@thorr2
Copy link
Author

thorr2 commented Aug 17, 2020 via email

@thorr2
Copy link
Author

thorr2 commented Aug 17, 2020 via email

@thorr2
Copy link
Author

thorr2 commented Aug 18, 2020

Hello, I completely built a new MIDI interface with all new parts and I used a different set of resistors from a different manufacturer and measured each one before soldering it in to get the closest I could to the recommended values (and they were very close), and after everything was in place, I tried it and I still have the exact same problem. I had this problem before and after installing a PCM5122 hat. Are you testing on a Raspberry Pi 4 when you are having no issues? Any further help would be appreciated.

@thorr2
Copy link
Author

thorr2 commented Aug 18, 2020

I noticed this diagram uses different resistor values (220, 470 and 1K). I am not sure if trying that would help. https://www.instructables.com/id/PiMiDi-A-Raspberry-Pi-Midi-Box-or-How-I-Learned-to/

@dwhinham
Copy link
Owner

dwhinham commented Aug 18, 2020

I'd use that circuit diagram with caution, it has a pull up going to the +5V and the UART on the Pi is only capable of 3.3V, so there is risk of damage. Someone in the comments on that page also noticed this.

Sorry you're still having trouble, I'm really not sure what to suggest 😥

Can you provide hi-res photos of your circuit and how it's connected to the Pi?

The circuit in the README is the same as on this page: https://www.samplerbox.org/article/midiinwithrpi
I've tested it successfully on Pi 3, Pi 4, both constructed on a breadboard and on an assembled PCB.

Was your SD card 100% clean when you installed mt32-pi? (i.e. not just copied over an old Linux installation)

Can you try to test the interface in a clean install of Raspbian to try and rule out mt32-pi? You'll need to do the config dtoverlay changes and use ttymidi with something like MUNT or FluidSynth as suggested in this page: https://zuzebox.wordpress.com/tag/midi/

@thorr2
Copy link
Author

thorr2 commented Aug 18, 2020

Thanks. It is really late, so I will provide the pictures and work on this more tomorrow. The SD card was clean formatted before installing the MT-32 Pi. I noticed the Diode is different in the link you provided. I am not sure if that makes a difference or not. Also, I have a Pi 3 that I can try it on, but it will take some work to get to it (it's in a NesPi case acting as my Pi-hole).

@dwhinham
Copy link
Owner

Uh oh - yes, you're absolutely right, it's meant to be a 1N4148.

Please try with one of those if you can!

@thorr2
Copy link
Author

thorr2 commented Aug 18, 2020

I will have to order some. Hopefully that will fix it! Thanks!

@dwhinham
Copy link
Owner

I hope so! 🤞🤞

If this was the reason, I apologise for the mistake - you're the first person to actually attempt to build the circuit from the schematic listed here and report back.

I'll fix the schematic ASAP.
Thanks!

@nswaldman
Copy link

nswaldman commented Aug 18, 2020

@thorr2 to answer your questions:

I've tested on a Pi3 and Pi4, the dropped/stuck notes are different for each Pi tested, but they seem consistent for each.

@thorr2
Copy link
Author

thorr2 commented Aug 18, 2020 via email

@thorr2
Copy link
Author

thorr2 commented Aug 19, 2020

I installed the new diode and it did not change anything unfortunately. I guess I will try your suggestion of installing Raspian and trying to make that work. I tried once before but didn't get very far. Hopefully the link you provided will provide all the necessary information. I also have a Pi 3 I can try, so I may try that first.

@thorr2
Copy link
Author

thorr2 commented Aug 19, 2020

I tried the Pi 3 and it also had the issues, but less so.

@thorr2
Copy link
Author

thorr2 commented Aug 19, 2020

This is the spec sheet for the 6N138 I used: https://media.digikey.com/pdf/Data%20Sheets/Lite-On%20PDFs/6N138-39%20Series.pdf
Is it possible this requires 5V and I need to buy a different one that works at 3.3V?

@thorr2
Copy link
Author

thorr2 commented Aug 19, 2020

This is interesting (see the answer talking about 5V): https://electronics.stackexchange.com/questions/165255/midi-in-many-circuits

@dwhinham
Copy link
Owner

dwhinham commented Aug 19, 2020

Sorry the diode didn't change anything 😢

  • You should still try Raspbian.
  • You could try powering the opto via 5V as per the circuit in that StackOverflow answer, but you must add a voltage divider so that the signal is brought down to 3.3V before going into the Pi's Rx pin or you'll permanently damage the Pi.
  • Try other manufacturers of opto aswell. I'm assuming you've ruled out the opto being faulty by replacing it with another unit?

@thorr2
Copy link
Author

thorr2 commented Aug 19, 2020

Thanks. I soldered in the 0.1 uF capacitor and changed the circuit to wire it up to the 5V on pin 8 with pin 6 going to 3.3V through the resistor per the diagram I linked. It unfortunately did not change anything. I used a different 6N138 when I made my second MIDI board but they were both from the same manufacturer. I want to try Raspian, but it sounds like I will need to figure out all the steps from different sources. I have a Pi 4, and that post was 2017. Getting Munt to work with the GPIO MIDI IN is the challenge. If I can't figure it out, maybe you can tell me all the steps in a list of what to do from scratch. I can install Raspian from the imager tool and I am very familiar with Linux.
Thanks again,
Michael

@dwhinham
Copy link
Owner

No problem, I'll do a quick write-up of how to test it in Raspbian shortly.

I've noticed another mistake - in my breadboard diagram, the connections from the MIDI DIN plug are reversed, and it's because the tool I used to draw it (Fritzing) has an incorrect pin mapping for the DIN plug pins - the schematic is OK though.

I doubt this will be affect you though, as you mentioned soldering and I guess you followed the schematic and not the breadboard. I'm still interested in seeing how you've built your interface!

@thorr2
Copy link
Author

thorr2 commented Aug 20, 2020

Thank you very much. I would really appreciate the write-up for what all to do in Raspian (including setting up Munt and using it with the GPIO midi port). For the MIDI DIN, I went by the numbers on the schematic and the numbers embedded in the plastic on the MIDI connector. I have uploaded pictures, so maybe you can check if it is right. Here are the pictures:
https://www.sendspace.com/file/7kcr3i

Those are from my first midi interface that I made before changing it to 5V and changing the diode. My second interface is soldered to the pins on the Pi Hat because I am trying to make it fit into a case and there is not enough room for the push-on connectors. They are basically the same though.

Thanks again!
Michael

@dwhinham
Copy link
Owner

dwhinham commented Aug 22, 2020

Hi Michael,

Thanks for the pictures - it looks like a nice neat construction. I can't see anything obviously wrong but it's quite hard for me to tell with prototype board.

Sorry for the wait on the Raspberry Pi OS setup steps, it took me quite a long time, but here's a new wiki page where I'm going to be putting troubleshooting info from now on: https://github.com/dwhinham/mt32-pi/wiki/Troubleshooting

I can play your Pink Panther MIDI without any hanging notes on this setup with my breadboard GPIO interface and an Arananet Pi-MIDI hat. Let me know how you get on!

@thorr2
Copy link
Author

thorr2 commented Aug 23, 2020

Thank you very much! Your instructions worked perfectly, but I had to restart mt32emu-qt after rebooting (this was obvious but thought I would mention it). The results are exactly the same with the same hanging notes. If I play the MIDI file directly in Munt, it sounds fine. So, I guess the next step is to order a new 6n138 chip or try an alternative chip like the H11L1. I may also try putting the 0.1 uF capacitor on the midi pin 2 to ground before I do anything else. Edit: I tried adding the capacitor and it did not help.

Thank you so much for all of your efforts.

https://www.reddit.com/r/AskElectronics/comments/ci4b8e/6n_137_vs_6n_138_vs_6n_139/
https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/584083

@dwhinham
Copy link
Owner

dwhinham commented Aug 25, 2020

No worries, I'm glad you were able to follow them!

Unfortunately I don't know what else to suggest; my electronics knowledge only goes so far and I've just been using circuit designs that others have shared. But at least we know for certain that it's a hardware issue in your case.

Hoping someone might chime in with a suggestion or feed back their own experiences, or maybe it's worth asking in that subreddit - I'd love to hear if you get any further!

@thorr2
Copy link
Author

thorr2 commented Aug 26, 2020 via email

@icb-
Copy link

icb- commented Aug 26, 2020

So, I guess the next step is to order a new 6n138 chip or try an alternative chip like the H11L1.

I would strongly suggest using the H11L1 (e.g. the ON Semi H11L1M) over the 6N138. It has an open-collector schmitt trigger output, so still needs the pull-up resistor, but unlike the 6N138, the detector side is specified for a 3v to 15v supply voltage, so you can power it from the 3.3v supply without having to use a resistor divider to get the output to acceptable voltages. If you do change to the H11L1M, keep in mind that it's not pin compatible with the 6N138. Cost is a little higher, 91¢ for the On Semi H11L1M at Digi-Key at qty. 1 compared to 81¢ for the Lite-On 6N138 at Digi-Key, but negligible if you're only buying one.

The -0.5v to 7v for the 6N138 quoted above is misleading. That's from the "absolute maximum" section of the data sheet, that lists the voltages that can be applied without damaging the chip, not the voltages it works at. A traditional 6N138 is specified to work with a 4.5v to 5.5v supply. Some chips may work from a 3.3v supply, but it's working outside its intended voltage range.

@dwhinham
Copy link
Owner

Thanks for this info and clarification on my misleading interpretation of the datasheet. I couldn't find any better information to help @thorr2 on my own - sometimes, the only way to get the right answer on the Internet is to say the wrong answer so that someone will come along and correct you. 😄

I guess 6N138s that work at 3.3v are just from blind luck. It'd be great to have a better example schematic up here based on the H11L1, so I'll order one too shortly and maybe we can improve the design.

@dwhinham
Copy link
Owner

dwhinham commented Aug 29, 2020

@Braincell1973 I've just noticed your nice MIDI I/O board has an output DIN - this is very useful and should give you what @icb- described above.

It would be very interesting if you were able to use the above build, put the "not working" USB MIDI interface into the Pi's input, and use a second interface on the Pi's output. Then you could use Munt on the PC to receive from the 2nd interface and compare the sound to what the Pi is outputting.

If what's received from the Pi is good, then mt32-pi has a MIDI parsing bug.
If it's the same (broken), mt32-pi is probably fine.

Hope this makes sense!

@glaucon1984
Copy link

glaucon1984 commented Aug 29, 2020

Just tried the new kernels, there are still hanging notes and similar behaviours with MI1 and MI2 intros. Still no messages on the OLED display of my PI-MIDI besides "Lucasfilms Games" and the instrument indicators.

About logging the MIDI out, I'm afraid I would be useless with a soldering iron if I had one, but MiSTer solution is based on open source code running on Linux, so I wonder if it's possible to log the MIDI data at a software level (and if that would require involvement from the MiSTer dev)

EDIT: One detail, not sure if it's of any help, when I disable "delaysysex" on MiSTer midilink.ini, things get much worse, even when using CM-32L ROMs, just saying because this is supposed to be needed only for Rev. 0 of the MT-32, which could not keep up with... the speed of the sysex messages? so my feeling is that if I could delay the sysex (whatever this means) even more, it would get fixed. Without delaysysex is like there is a random "ding" or a sustained "wowowow" every few seconds, with it I can definitely recognise the music, but there are issues on it.

@icb-
Copy link

icb- commented Aug 29, 2020

As an alternative to building a MIDI OUT DIN circuit on the TX pin, what I did was get a spare FTDI FT232R USB serial adaptor, and connect it to the Pi's TX pin and ground. The FT232R can be configured to run at MIDI baud with setserial -v /dev/ttyUSB0 spd_cust divisor 768, which sets the clock such that using 38400 baud is really 31250 (see this page for how this is calculated/how to adapt for other USB serial adaptors). I then used ttymidi -b 38400 and Munt in the same way as in my troubleshooting wiki page (but on my PC and not a Pi), and was able to successfully hear the music from both the mt32-pi and from my machine running Munt receiving from the Pi's serial output.

If you have a second Raspberry Pi, you can use the midi-uart0 overlay to reconfigure the first UART so 38400 baud is really 31250 baud, and use ttymidi to inspect what's coming. If it's a Raspberry Pi 4, you can also use the midi-uart1 overlay to reconfigure the second UART the same way, to run a second ttymidi to capture two MIDI streams. Check the help for ttymidi for the flag to attach to a different serial device.

You can connect the TX pin of one Raspberry Pi to the RX pin of a second Raspberry Pi, or the output of the optoisolator circuit to the RX pin of two Raspberry Pis. You just have to make sure you're not creating ground loops, by using isolated power supplies or connecting both Raspberry Pis to the same power supply.

@Braincell1973
Copy link

@dwhinham yea I can try anything but I only have the 1 midi cable....... .

From my perspective, my setup had major latency issues going from a keyboard to serial midi and as soon as I went from the midisport 2x2 everything worked fine , so as far as I can reason the hardware and mt32pi is fine , the only difference was the drive to the opto and the change of rom.......

I'm going to see if I have a 2nd cable in the loft and use the midi in out and thru on the midisport to see if it enables the 2 keyboards I tried to work.........

@dwhinham
Copy link
Owner

@icb-

If you have a second Raspberry Pi, you can use the midi-uart0 overlay to reconfigure the first UART so 38400 baud is really 31250 baud, and use ttymidi to inspect what's coming. If it's a Raspberry Pi 4, you can also use the midi-uart1 overlay to reconfigure the second UART the same way, to run a second ttymidi to capture two MIDI streams. Check the help for ttymidi for the flag to attach to a different serial device.

Thanks, I've got most of this documented over on the troubleshooting page (thought not the midi-uart1 info!).

@Braincell1973 Cool, thanks - any more test results will be very useful.

Cheers both.

@Higgy69
Copy link

Higgy69 commented Aug 30, 2020

@dwhinham - I did hot plug HDMI before, so this time I did it correct ;) and got an output.

Ok this might be something you always do, but we are not (or not all of us) - Turning on Pi power when music/midi/scummvm is playing. I have noticed that things sound very different in a good way, many more notes etc, if I power on when Monkey Island 1 is running and not before. I still get hanging notes, but the sound is very different.
I was playing Monkey Island 2 and doing the powering on during music playing, it sounded good but you can see on the OLED that after a short while there is a Hanging Note on 5. It says on for a good while.

Picture on left is MT32-pi running before starting ScummVM. Picture on right is when I power on while music is playing
https://pichost.net/img/2JSk0
If powering on before (left hand picture) the Top Info on OLED does not change.
Here are my HDMI screen grabs. Same again left is initial Pi power on in Windows, Right is when music is already playing.
https://pichost.net/img/2JVDx

Thanks

@dwhinham
Copy link
Owner

dwhinham commented Aug 31, 2020

@dwhinham - I did hot plug HDMI before, so this time I did it correct ;) and got an output.

Great 😃

I have noticed that things sound very different in a good way, many more notes etc, if I power on when Monkey Island 1 is running and not before. I still get hanging notes, but the sound is very different.

That's because the synth won't have received any of the SysEx or program changes to set instrument parameters and assign instruments to parts, so you'll hear music, but all the instruments will be wrong. This setup data is often sent out just once at the start of the song.

Your logs look fine, although you should set i2c_dac_init to none to avoid the "I2C write error". Your DAC doesn't need initializing and it's not connected to the I2C bus. This is completely unrelated though and won't have any effect on the problems you're having.

I'm guessing that when you switched-on while the music playing, an incomplete message got interpreted as an Active Sensing command, hence the "Active sense timeout".

@olliraa
Copy link

olliraa commented Sep 2, 2020

As advised by @dwhinham I'll report in this thread. Also experiencing these weird "notes not playing" problems. Here's a more detailed info regarding the setup:

Rpi 3b+
mt32-pi 0.3.1
PI-MIDI by Araranet

Tested with the following controllers:

Kawai K1-II (ch 2)
Roland RD-64 (ch 2)
Midi cable tested working just fine with both of the controllers and Behringer USB/midi interface + Arturia software synths.

Sample rate and buffer size don't affect the problem.

@dwhinham
Copy link
Owner

dwhinham commented Sep 2, 2020

I've just had an absolutely shocking idea while reading MIDI specs.
Running Status. We don't do Running Status.

How on earth have I never heard of this?!
http://midi.teragonaudio.com/tech/midispec/run.htm

An account of similar experiences here: http://blog.cornbeast.com/2012/12/beware-of-midi-running-status/

If the firmware of some USB interfaces "optimise" outgoing packets by using the Running Status feature, it would explain everything.

I will try to implement this as soon as possible. Please stand by. 🤞 🤞 🤞

@dwhinham
Copy link
Owner

dwhinham commented Sep 2, 2020

Testers with hanging notes:

Please try this build:
https://github.com/dwhinham/mt32-pi/actions/runs/236578640

As usual, unzip the kernels and try as much gear as possible.

Anxiously awaiting your test results! 🤞😄

@Higgy69
Copy link

Higgy69 commented Sep 2, 2020

Applies virtual pat on back :)
Just tried Monkey 1 & 2 and no hanging notes ;)

Rpi3 1.2GHz
Win10 ScummVM
USB-MIDI UM-1EX

Over the next few days I will try again my AMIGA and see if the last note hangs when exiting the game, and even when AMIGA is powered on/off needing the RPi to be power cycled to stop.

@nswaldman
Copy link

nswaldman commented Sep 2, 2020

Hopping on the party boat, can verify this works.

Raspi3 1.2GHz + PI-MIDI board
MacOS ScummvM, Pink Panther MID
USB UM ONE MK2, M-Audio Midisport 1x1

@dwhinham
Copy link
Owner

dwhinham commented Sep 2, 2020

I think we can call this resolved. What a ride!

First of all, many thanks to all of you for your patience and for taking the time to test, report, and brainstorm ideas for the underlying cause.

I sincerely apologise for being suspicious of hardware when such a critical MIDI feature was missing from the software. I was so convinced of it being hardware that I couldn't see the forest for the trees. 😞 I'm still quite shocked that I'd never heard of MIDI Running Status, and a lot of sample code out there seems to lack it. But it was right there all along in the specification.

Still, it's good that popular hardware schematics have been scrutinised here, big thanks to @icb- especially for that. I will update the example schematic soon with the H11L1 alternative as it allows a simpler, safer design and avoids the possibility of underpowering the optoisolator.

You've all been given credit in the release notes for v0.4.0, which is now available. I hope that's the end of this issue! 😄

@Higgy69 If you still get a final hanging note in your Amiga game, please feel free to open a new issue. I think it'll be a different problem (maybe we need to implement a reset command or something), but I have Amigas over here too for testing so we can talk about it and test.

Thanks again all, and I hope you can now enjoy mt32-pi properly. 😄

@dwhinham dwhinham closed this as completed Sep 2, 2020
@dwhinham dwhinham unpinned this issue Sep 2, 2020
@dwhinham dwhinham self-assigned this Sep 2, 2020
@dwhinham dwhinham added the bug label Sep 2, 2020
@olliraa
Copy link

olliraa commented Sep 3, 2020

Works like a charm :D Thank you soo much @dwhinham for this lovely piece of software 🥇

@glaucon1984
Copy link

Thanks for not giving up, it's hard is to troubleshoot an issue one cannot reproduce, MT32-PI is now running perfectly for me!

@dwhinham
Copy link
Owner

dwhinham commented Sep 3, 2020

My pleasure! 😄 Thanks again for your patience.

@thorr2
Copy link
Author

thorr2 commented Sep 3, 2020 via email

@thorr2
Copy link
Author

thorr2 commented Sep 3, 2020 via email

@Braincell1973
Copy link

Tested on my 2 keyboards and things much improved....

Yamaha pss680 works perfectly
Mk449 works mostly but cuts some notes short...... ( unsure if its keyboard ??? )

No change from scumm on pc , works very well.

But , As I have never owned a mt32 I cant verify this next thing , on the pc, whilst scumm seems to work properly, playing regular midi files to the mt32pi results in musical oddities , rather like its missing a track, if that makes any sense.

I can compare the output to the mt32 and Windows wave table and its like there's details missing ?? I read somewhere that the mt32 has a reserved track 0/1 ?????

Anyway , thank you for this fantastic device

@thorr2
Copy link
Author

thorr2 commented Sep 3, 2020 via email

@dwhinham
Copy link
Owner

dwhinham commented Sep 3, 2020

@thorr2
Great to hear!

The Pink Panther MIDI has a cymbal and an open hi-hat at the end. Here are the final bars:

image

The open hi-hat sound on the MT-32 goes on for quite some time, almost 5 seconds! The cymbal has a pretty slow decay too. It sounds identical to me on both desktop Munt and mt32-pi, so I don't think it's anything to worry about, it's just how the MT-32's drum kit sounds.

I did some testing (both Munt and mt32-pi, no difference) - editing the MIDI file to add a CC 120 or 123 (All Sound Off/All Notes Off) message to the drum channel has no effect on a playing cymbal. But adding these during a long piano note cuts off the sound as expected. So these CCs, if present, do get through to the synth and work just fine, but even if they were present in the song file, it would have no effect on the drums, and this is probably just by design of the MT-32.

@Braincell1973

Sounds good - can you check the behaviour of the Mk449 on desktop Munt when you get a chance? You can get the latest Windows version here.

Playing regular General MIDI files will rarely sound correct on an MT-32 (or an emulation of one) - the MT-32 pre-dates the General MIDI standard, so most of the instrument mappings will be wrong, and as you've noticed, channel 1 is reserved.

It's possible to get somewhat close though. On a real MT-32, holding some buttons down on startup will change the default channels from 2-9 and 10 to 1-8 and 10 (10 is always for drums). Additionally, Roland published some .MID files full of SysEx that try to remap the MT-32 instruments to resemble General MIDI. It's nowhere near perfect, but it's fun to try.

If you grab the MT2GM archive from here and play the MTGM.MID file to mt32-pi, it will remap the instruments and set the receive channels to 1-8 and 10. You won't hear anything when you play the MIDI, and it lasts around 30 seconds. After that, try playing some GM songs.

But this isn't really the intended purpose of the MT-32 - you want to find some songs composed for the MT-32 such as the ones @thorr2 has suggested. 😃

@loskaa
Copy link

loskaa commented Sep 28, 2020

@dwhinham Just wanted to let you know that after these latest updates, mt32-pi is working perfectly also with the pc-midi card (http://pcmidi.eu/). There were all sorts of strange hiccups which are completely gone with 0.5.0. Nice work!

@dwhinham
Copy link
Owner

That's what I like to hear - excellent! 🎉

Thanks for the feedback 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants