www.megadrum.info

Is it possible?

No, it is not possible. To do this, the application must decrypt and later encrypt a portion of the firmware thus exposing the encryption method.

I'll ask Dmitri to think of a solution if it's possible (I hope he'll read this when he'll be back). If not, a very useful workaround could be to include an input mapping window in MCT, where the inputs could be renamed and the new names could be seen at least in MCT. The mapping window would help to match the names with the LCD on MD (which we don't really use when working in MCT anyway).

Renaming inputs in MegaDrum itself is not possible as Firelord pointed out. Reasons:
1. Encrypted firmware format.
2. Too little EEPROM space to implement renaming using it.

So the renaming can only be done in MCT if implemented.

dmitri wrote:So the renaming can only be done in MCT if implemented.

So I'm wondering to whom I should pray to hear the humble request of a poor MDmer with over 40 pads arranged completely differently from what the default names suggest (Will that be a prayer to the Lord, perhaps a Firelord?)

You can rename them in MCT by clicking 'Firmware→Edit pad and input names' menu item (or by pressing CTRL+I). The pads will be renamed and stay that way in MCT, the only difference is that they will not be sent with the firmware when you update via bootloader v5.

Firelord wrote:You can rename them in MCT by clicking 'Firmware→Edit pad and input names' menu item (or by pressing CTRL+I). The pads will be renamed and stay that way in MCT, the only difference is that they will not be sent with the firmware when you update via bootloader v5.

That's just exactly what I wanted. I've just noticed that I already used this in a second WinXp partition on my laptop. Being senile makes life filled with great new experiences every day.

dmitri wrote:Renaming inputs in MegaDrum itself is not possible as Firelord pointed out.
2. Too little EEPROM space to implement renaming using it.

Eh?