mat1jaczyyy

how would i know

uhh i don't write directly to any memory regions here, i just sysex send the update to the mk2 and the bootloader does all the writing and checksums if something...

if it is a real brick you can fix using an st-link and full flash (bootloader+firmware) dump of MK2 (i can provide over discord) https://github.com/mat1jaczyyy/lpp-performance-cfw/blob/master/unbrick.md (the images are dead because...

weird, dunno

Here are a few screenshots to help better describe the problem:    I can only differentiate by name, but the names are the same.

@micdah ?

RtMidi adds port number on Windows to "ensure uniqueness". While it does succeed in ensuring it, disconnecting/reconnecting devices will change other devices' port numbers, so now it's impossible to tell...

the Port isn't unique either, since it merely represents the "index" of a connected midi port. say there are 3 devices 0,1,2 and device 1 disconnects, device 2 will now...

@micdah haven't you already modified rtmidi to fit RtMidi.Core's needs? is there anything available in each platform's native API that we could expose to rtmidi, subsequently to RtMidi.Core?

Sounds like firmware update got interrupted midway and left you with just the bootloader, should be fine if you just re-update properly. MIDI sucks and it can be difficult to...