Megadrum Config Tool (comming soon!)

[elrules]

Try installing this:
http://www.mandolane.co.uk/dlPlumstone.html
For installing (in Tiger OS, which has java 1.5) you only need to copy plumstoneserv.jar to /Library/Java/Extensions

For more info please read this:
http://lists.apple.com/archives/coreaud ... 00214.html

Please report your results

[kimouette]

Try installing this:
http://www.mandolane.co.uk/dlPlumstone.html
For installing (in Tiger OS, which has java 1.5) you only need to copy plumstoneserv.jar to /Library/Java/Extensions

For more info please read this:
http://lists.apple.com/archives/coreaud ... 00214.html

Please report your results

Image 1.png

Thanks so much... it works!

[elrules]

Well, one problem solved. Now you have to tell me if the actions work well. And I also would like to know if clicking Help->Help takes you to the help.html in a browser and if the app saves your user settings from one run of the app to another. If all that works, and after seing that the GUI looks good, then the Mac test will be finished

I would want to complete this table:

Tested and everything working on:
OK - Windows XP
## - Windows Vista
## - Mac (10.4+)
## - Linux

[kimouette]

I also would like to know if clicking Help->Help takes you to the help.html in a browser

Yes, it brings me to this URL : http://www.serfin.eu/configtool/help.html
And this is what I see :

Image 1.png

For the rest, I promise to do every single thing you asked for, but right now I'm stuck with the very first thing I tried to do : updating the firmware using the .sys file.

Could you tell me exactly how to do it... I'm pretty sure it starts with the "Actions window"

Image 2.png

but I cant do it.

I tried "Actions/All Megadrum setting/Load from File/
then navigate to "megadrum32_16_20081020.syx"
but I get the following window

Image 3.png

[elrules]

Updating firmware is disabled for Mac users as I the default Midi implementation of Java fragments sysex messages longer than 512 bytes. That is why I included a windows DLL file for windows, which has native methods to send big sysex messages.

The action to update firmware should appear in the menu Firmware -> UPDATE FIRMWARE, but as I said, it is only enabled in windows systems.

Anyway, we can make together a test. I can re-enable the Firmware menu for Mac, and you can try to update megadrum with that. Maybe the plumstone library has no restrictions on sysex size. If it fragments the sysex firmware don't be afraid, the megadrum will ignore those sysex packets.

When I arrive to my home (in 10 minutes) I'll recompile it and reupload. At 3 o'clock you can try it again, ok?

[dmitri]

Updating firmware is disabled for Mac users as I the default Midi implementation of Java fragments sysex messages longer than 512 bytes. That is why I included a windows DLL file for windows, which has native methods to send big sysex messages.

Can Java implementation send raw MIDI data? If yes, then you don't need to use Java sysex handling, just send everything from a .syx file as raw data.

[kimouette]

The firmware update you just added might just work. But I cant test it right away since I might have to change the crystal I currently have on my board.
Here's what I see when I choose "Firmware/Update firmware" and navigate to the right .sys file...

Image 9.png

Like I said it might work, I'll tell you as soon as I can

If I change some pad's parameters and simply quit the application, I am not asked to save my setting. The app simply closes and when I come back, all my parameters are set back to default.

But loading previously saved files using either the "Actions for all setting", "Hihat pedal setting" or the "Actions for selected pad", all work perfectly!!

Actions from MD and to MD dont work. The app seem to be thinking for couple of seconds, but no confirmation can be found : neither with the MD LCD screen nor the Config tool.
The only way to find out it didn't work is to send a specific setting to the MD, quit the app, re-open it and import the setting from the MD: no parameter changes are takin into account, it doesn't work.

Drum maps: I know I can save a .mdm file using the "Actions" window, but since I'm still not sure what drum maps are supposed to look like, I cant confirm that the right drum map is opened when I load one!

One last thing...just a suggestion.
Look at the following picture.

Image 7.png

It shows the "/Users/User name" directory.
Normally we dont put anything directly into this folder. Everything has to be located in one of the sub-folder you can see. So if you could maybe put that default directory (containing "MegadrumConfigTool.ini" and "SubpadNamesConversionTable.ini") directly into "/Applications" or "/Users/User name/Documents" it would be "cleaner" !!

[elrules]

The firmware update you just added might just work. But I cant test it right away since I might have to change the crystal I currently have on my board.
Here's what I see when I choose "Firmware/Update firmware" and navigate to the right .sys file... Like I said it might work, I'll tell you as soon as I can

That is not sure, as the secret for being able to update the firmware is that the OS must not fragment the sysex firmware file. Testint it is the only way to find it out. One remark: if your bootloader (on the LCD) does not show the clock, then the bootloader is the first version so you don't need to press Up to change the clock, just press down and then press Yes in the app.

If I change some pad's parameters and simply quit the application, I am not asked to save my setting. The app simply closes and when I come back, all my parameters are set back to default.

But loading previously saved files using either the "Actions for all setting", "Hihat pedal setting" or the "Actions for selected pad", all work perfectly!!

This feature was not included. When you open the app you get all the default values and you have to load all from megadrum to have them shown. ...But it is a good idea to let the user save its current settings when closing the app, and then reloading them when running the app. I will program that.

Actions from MD and to MD dont work. The app seem to be thinking for couple of seconds, but no confirmation can be found : neither with the MD LCD screen nor the Config tool.
The only way to find out it didn't work is to send a specific setting to the MD, quit the app, re-open it and import the setting from the MD: no parameter changes are takin into account, it doesn't work.

I see... Maybe the library I linked you is not the best library for Mac. I have been searching again for a java library and I have found what seems to be the most accepted implementation of midi in mac. Click here:
http://www.humatic.de/htools/mmj.htm
Then delete the plumstoneserv.jar, download the "mmj" and copy both mmj.jar and libmmj.jnilib into /Library/Java/Extensions.
Let's see if this midi implementation is better than the other.
In the mmj website it claims that copying mmj.jar and libmmj.jnilib is enough to make an standard clossplatform-programmed app (as my app) work with Mac. Let's see if that is true...

Drum maps: I know I can save a .mdm file using the "Actions" window, but since I'm still not sure what drum maps are supposed to look like, I cant confirm that the right drum map is opened when I load one!

Drum maps are a set of parameters only containing what refers to midi settings, that is: midi notes for all inputs and hihat pedal, and midi channels for all inputs. You can load a "Drummap" so those parameters will be set in the GUI. Then you need to send them to megadrum to make them effective.

One last thing...just a suggestion.
Look at the following picture.
It shows the "/Users/User name" directory.
Normally we dont put anything directly into this folder. Everything has to be located in one of the sub-folder you can see. So if you could maybe put that default directory (containing "MegadrumConfigTool.ini" and "SubpadNamesConversionTable.ini") directly into "/Applications" or "/Users/User name/Documents" it would be "cleaner" !!

I also would prefer to save those files to one of the folders you mention, but Java does not provide a good way to access those folders (only the user.home variable, that in Mac seems to point to "/Users/User name"), and I don't know if in other languages of the OS, the folder is going to be called Applications or Aplicaciones or something else. The user.home is a sure shot

[kimouette]

I see... Maybe the library I linked you is not the best library for Mac. I have been searching again for a java library and I have found what seems to be the most accepted implementation of midi in mac. Click here:
http://www.humatic.de/htools/mmj.htm
Then delete the plumstoneserv.jar, download the "mmj" and copy both mmj.jar and libmmj.jnilib into /Library/Java/Extensions.
Let's see if this midi implementation is better than the other.
In the mmj website it claims that copying mmj.jar and libmmj.jnilib is enough to make an standard clossplatform-programmed app (as my app) work with Mac. Let's see if that is true...

I followed your procedure and tried changing the hihat pedal setting and send it to Megadrum... same thing, nothing happens, and when I quit and re-open the Config Tool and try to Load the setting from MD, nothing changes

Drum maps are a set of parameters only containing what refers to midi settings, that is: midi notes for all inputs and hihat pedal, and midi channels for all inputs. You can load a "Drummap" so those parameters will be set in the GUI. Then you need to send them to megadrum to make them effective.

I did the test and it works: I changed Midi note number and and midi chanel of different pads and could easily save and load the drum map I created.

[elrules]

I followed your procedure and tried changing the hihat pedal setting and send it to Megadrum... same thing, nothing happens, and when I quit and re-open the Config Tool and try to Load the setting from MD, nothing changes

It would e interesting to connect the app to a virtual midi port and then to a monitoring tool. Is there any virtual midi device like Midi Yoke in windows, but for Mac? Is there any monitoring tool like MIDI-OX?