Megadrum Config Tool (comming soon!)

[dmitri]

Still the same error with the firmware update. Why did it work before?!

[elrules]

Still the same error with the firmware update. Why did it work before?!

To be honest I don't know. I have put the code the way I think it was when it worked, that is, with the open() and close() device method when starting the program and when closing it, instead of per-request open/close.

PD: by the way, I have found a very nice Javascript to tab the info in a web. See help file and version history to see what I am talking about. Hope I can write a manual soon

[elrules]

Has anybody tried again the firmware update in linux? If it works I think it is a good moment to make it public as the first release

[dmitri]

Even though I still have the same issue under Linux I think it is ready for use by most and I guess it is time to make an announcement.
The minor issues can be solved once people start using it.
Do you agree?

[elrules]

Yes

And I am now writing a manual, you will see it increasing as I update it with new tabs.

EDIT: I have decided to name the help file as index.html, as it also serves as a main descriptive web. I have uploaded the index.html to the server, and also updated the tool to point to that URL when clicking the Help button. Also updated the midi log receiver so it does not log midi notes off (it seems they were sent as midi note On with velocity 0).

[japi]

One feature request:

When you hit a pad, make the program go to that pad's settings directly ? Just like the quick access of dmitri's in the MD holding the hihat switch
Also could be nice that the program identifies the pad being hit. For example my build of md doesn't has functional buttons at this time, and I want to change the midi note of some pads but I don't know which one i'm hitting

[elrules]

Believe it or not, today I have tought about that feature! but take into account that if you set the same note for more than one pads the program will not be able to distinguish between them. I can program it so when you receive a note it jumps to the first ocurrence.

That will be in the case that the velocity hit is above a threshold. Only hits above velocity 30 for example, will make the program jump to that pad. (I also have to include that threshold for the "rim switch light" because when you hit the rim and receive a bit of xtalk, the rim light turns down due to those false low-velocity hits.)

Jumping to each pad will happen only if you have one option activated.

I think that way will be ok...

By the way, I will try to continue writting the help manual.

[Matt]

Whats the average time it should take to read / write to and from the megardrum? For me it takes about 30 seconds to get all the info from the megadrum itself and several minutes to write to it.

I don't think the changes are being saved to megadrum as after writing to it and then reading the data back from megadrum the previous changes aren't listed.

I'm running Vista, not sure if its related.

[elrules]

The time used to write one single config is a fraction of a second. For all the settings at a time, it takes a few seconds. To write the firmware it takes 20 or 25 secongs.

There must be something wrong...

By the way, can you access the menus? do you experiment graphical issues when opening the menus?

[Matt]

Thats a little un-nerving then, any ideas as to what could be causing this? Hopefuly my megadrum isn't broken. It gets detected in Windows as Megadrum Midi Trigger Device so I'm assuming that the firmware is at least working. It would be great if I could get this to work since my screen is broken right now.

Yes I do see the screen mulitplication issue that has been previously mentioned.