MegaDrumManger is now ...

[Kabonfaiba]

MidiLogBug.png

There is a MDMFX bug whereby if I go to options (don't change anything) and click OK.

I get +1 extra note added to the Midi Log.

In the attached picture, I've gone to options window three times - so now I get a groups of 4 notes or groups of 8 aftertouch notes in the log.

[Rovalo]

During my firmware 20181031 upgrade issue I noticed that depending on MIDI open/closed the upgrade instructions screens are different.

In my case update is only successful when MD is manually forced in update mode as per first screen step 4. Otherwise I get an error message.

With MIDI closed:

MDMFX20181028-firmware-upgrade-screen-midi-closed.JPG

With MIDI open:

MDMFX20181028-firmware-upgrade-screen-midi-opened.JPG

With MIDI open after Start update MD automatically enters update mode followed by this error, timing issue?

MDMFX20181028-firmware-upgrade-error screen-midi-opened.JPG

[daniele99]

Hi dmitri, i noticed that MDM and MD don't exchange some parameters like "Hihat input" number. I use Ch26 for Hat to avoid crosstalk inside the first mux and when I click "get all" in MDM it doesn't change from ch2. The same if i click "send all". The same issue with "AltEncoders" parameter. This happens clicking "Save to slot" from MDM to MD too. I will check for others non-exchanging params.
Another problem: did MDM starts with 100 slot by default? This setting makes Atmega644-MD behave like crazy.

[dmitri]

1. I will check the HiHat input number. AltEncoders is not a parameter which can be changed externally with a sysex or MDMFX.
2. It doesn't start with config 100. If no config was saved before, MegaDrum just displays a non-existent slot number which I chose to be 100. It doesn't load from or saves to slot 100.

[dmitri]

Hm, just tested HiHat input number and it works as expected. Changed it in MegaDrum and did 'Get' in MDMFX and it sees the setting changed. Changed it in MDMFX and sent it to MegaDrum and MegaDrum shows the setting changed.

[daniele99]

So i believe it's my fault. I'll check one more time. Thank you!

[paulritik_09]

I'm trying to help here, to make the MDM-app a bit more robust, user-friendly and easier to use with less questions for the end user and improved usability. It's not that I do not respect or appreciate the work you do, or have done, It's just that I know it could be better and way more user-friendly.
It's my work to make things easier to use, I'm not just talking without any knowledge

[Rovalo]

I have issues with midi communication with MD.

It is my idea to use the first MD midi port 'MegaDrum USB MIDI' for communication with the DAW/VST.
To change setting of MD I wanted to use the second MD port 'MIDIIN2 (MegaDrum USB MIDI)' , but I cannot get it to work.

When I select in MDMFX Main\Options the second port then they cannot connect.
MDMFX will show in red 'MIDI Init Error'.

Is it not possible what I described?
What do I misunderstand?
How is the use of the second port supposed to work?

Please advice, thank you.

[dmitri]

In terms of Sysex control from MDMFX both pairs (In/Out) of USB MIDI ports are equal.
You configure MDMFX to either use the first pair or the second pair of USB MIDI ports. Then you use only the other pair in your MIDI app.
You can also restrict the second USB MIDI port for Sysex only (MIDI2 for Sysex only checkbox in MDMFX Global settings).
Make sure MDMFX and your MIDI app use different MegaDrum MIDI ports, otherwise it may lead to errors/problems in MDMFX and/or MIDI app.

[Rovalo]

So I think you confirm that what I want is possible and normal.

I tried to select MDMFX to communicate with MD through MIDI2 port (without another MIDI app active).
The behaviour is not consistent but I found that selecting the in/out ports pair manually (not clicking Same MIDI in/out) makes a difference.
Now it is sometime possible to get it set.

And if I select MIDI2 for MDMFX, should I select MIDI2 for Sysex only?