"Megadrum Config Tool" released

[Ken Forgettable]

Poking around a bit I see you and your IDE have been working hard!

Is it true MACs don't like java 6?

Checked out the code with Tortoise SVN but had to use the Repo browser to save locally as the Checkout menu thing didn't like the URL for some reason. Downgraded to Suns java5+netbeans bundle as you recommend and don't see any bug fixes in v6 that apply to MIDI.

I want to hammer the firmware downloading so will not bother to sign up unless I make some progress.

You're a very nice man - thanks.

[Rubis]

The command line checkout code doesn't seem to work:

Code: Select all

svn checkout http://megadrumconfigtool.googlecode.com/svn/trunk/ megadrumconfigtool-read-only

errors with does not exist. I also tried without the space after trunk/ but still get the same error.


EDIT: I believe the correct URL should be http://megadrumconfigtool.googlecode.co ... onfigTool/

making the command:

Code: Select all

svn checkout http://megadrumconfigtool.googlecode.com/svn/MegadrumConfigTool/

[elrules]

ok, i corrected the link to the svn in the webpage that MCT shows when clicking the About dialog

the URL to do the checkup is:

Code: Select all

http://megadrumconfigtool.googlecode.com/svn/MegadrumConfigTool

I also added a "donate" button to the web just in case someone feels grateful for this tool.


Yeah, MAC does not like last java version.
Anyway, someone recommended SysexSenderX-FCM for Mac
http://members.shaw.ca/akochoi-old/blog ... dex.html#2
It accesses Core MIDI in Mac with the Objective-C language.
Would be great to have an executable or library to call from java.

[gastric]

I'm not kidding that this tool for me is major part of the MD project overall now. It makes the various settings to absolutely easy to visualize, access, modify, and manage. This tool should be "advertised" heavily when promoting the overall MD project as a huge advantage over every other module, retail or DIY.

"You get a bazillion inputs, 3-zone support on every trigger, superior hihat pedal control, and best yet - the option to control the entire module via an easy-to-use computer based software control panel. WOOT!"

[elrules]

Thanks for your comments, gastric, I really appreciate that

[dmitri]

I'm not kidding that this tool for me is major part of the MD project overall now. It makes the various settings to absolutely easy to visualize, access, modify, and manage. This tool should be "advertised" heavily when promoting the overall MD project as a huge advantage over every other module, retail or DIY.

"You get a bazillion inputs, 3-zone support on every trigger, superior hihat pedal control, and best yet - the option to control the entire module via an easy-to-use computer based software control panel. WOOT!"

What about telling it over at vdrums.com? E.g. in
http://www.vdrums.com/forum/showthread.php?t=49307
http://www.vdrums.com/forum/showthread.php?t=47569

[elrules]

VERSION 1.62 released:

- Changed the way in which the Midi Monitor shows the hihat pedal value received. Now it actually shows the REAL value. A value of 0 means open, and a value of 127 means closed. Take that into account when you configure the new hihat parameters of the latest firmware.
- Added support for the new Hihat parameters.
- Rearranged the GUI, with quick access buttons for all MD related actions (removed the from/to file buttons). Left some space (new panels) for future new features.
- Added item in the Help menu to see which firmware version is recommended for this version of MCT.
- Added "set-all" buttons for the rest of the parameters of the pads.
- Added midi note names to field boxes.
- Fixed this issue a user was having: "I have issues where when you first load the app it cannot communicate over the set MIDI. You have to open the options, change the MIDI, then change it back to what it was first set to before it will communicate with MD."
- If you set 3rd zone BNote = Disable, MCT will automatically set BThreshold = 0, to physically disable triggering of that 3rd zone in MD.
- Fixed the firmware version check. Now the default firmware version (if you have not set it) is 00000000, instead of taking the current date, what was causing MCT to think you have a version higher than last one.
- Apparently the firmware updating is fixed, at least it worked for me.
- Choke notes are now visible in the Midi Log, with a red background and a "CHOKE" label inside the bars.

I recommend deleting the MCT config files and folder before executing, to have a "clean" startup with new options. (This folder is usually located in the user profile folder, C:\Documents and settings\username for WinXP users)

[alchemicus]

i've just downloaded it!

[Rubis]

Major update on this one Elrules! The "Send to X" stuff at the top is a lot more readable than in your mock-up. I don't have my MD with me, it is at my friend's house where I am building my drums, but I will play with it more when I get it back.

From the changelog, it seems like everything really important is working with this one? Great work!

Edit: I don't know if this was there before and I just didn't notice it, but for the third zone configuration, the arrows are cut off. It gets better after changing themes, but is still cut off. A problem no matter what theme I use, but is a little better with Lipstick and Infonode. After changing to them, it shows the full arrow, but won't on a cold start. Minor gripe, as they can still be configured by the slider.

[elrules]

I don't know if this was there before and I just didn't notice it, but for the third zone configuration, the arrows are cut off.

Got it. I will fix that