Megadrum Config Tool FEATURE REQUESTS

Discussions of any related software

Moderator: Related software moderators

Re: Megadrum Config Tool FEATURE REQUESTS

Postby macca2004 » Sat May 16, 2009 11:06 am

elrules wrote:I like your graphic, macca ;)


Thanks...left side of the text was clipped somehow...The lower line is Threshold and the higher line is Dynamic Level.
macca2004
 
Posts: 80
Joined: Wed Dec 10, 2008 6:54 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby acspike » Sat May 16, 2009 11:37 am

elrules wrote:Don't worry for netbeans, i will explain how to set it up to have the same working environment i have.

About the SVN import, can I do it with Tortoise or netbeans clients? how can i know the URL of the google code server? i have to learn how to do all of this... :lol:


All of the information you need to do a checkout is listed on the Source tab of the google code site that was setup when you created the project. You will need to use the special password that google generates for you in the google code interface to gain commit access to the repository.

userfriendly wrote:Usually you would do an svn import into the empty repository, then move the directory to a backup location and check out a working copy from the repository to a new directory (which can of course have the same name, so when you open netbeans again it won't notice anything has changed).


I guess you might also want to consider using the traditional SVN trunk,branches,tags directory structure. I don't remember if google sets this up for you or not. I've also never worked on a project that didn't use it so I don't know what the negative effects would be. I do know that some auxiliary tools assume that it is there.
acspike
 
Posts: 17
Joined: Mon May 12, 2008 12:58 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby Ken Forgettable » Sat May 16, 2009 1:28 pm

elrules wrote:
Ken Forgettable wrote:+ If Dmitri implemented a 'Quick Access' SysEx message to be sent from the firmware then MCT could auto-select the pad parameter screen (maybe with an image of the physical LCD screen too).
There is already something like that implemented. You can enable Quick Access in the Options of MCT, and set the threshold for that effect
My Megadrum is locked in a dark room away from java. Can someone confirm this behavior for me:

+ Quick Access is enabled and working on the Megadrum and MCT is currently on the Kick pad.

+ I press HiHat pedal down and hit Aux2

Does MCT now show Aux2 as the selected pad?

Thanks in advance.
Ken Forgettable
 
Posts: 402
Joined: Tue Jan 06, 2009 5:04 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby gabriel1712 » Sat May 16, 2009 6:08 pm

Ken Forgettable wrote:Can someone confirm this behavior for me:

+ Quick Access is enabled and working on the Megadrum and MCT is currently on the Kick pad.

+ I press HiHat pedal down and hit Aux2

Does MCT now show Aux2 as the selected pad?

Thanks in advance.


You need to activate MD setting (not showing the meter, but push random left or right button on MD to wake the settings) and strike a hit above the quick access velocity threshold. Then yes, Aux2 and any other pad hit will get chosen in MCT as well.
"the woods are lovely, dark and deep
but I have promises to keep
and miles to go before I sleep..."
gabriel1712
 
Posts: 195
Joined: Thu Mar 19, 2009 10:16 pm
Location: Denmark

Re: Megadrum Config Tool FEATURE REQUESTS

Postby Ken Forgettable » Sat May 16, 2009 9:27 pm

macca2004 wrote:...left side of the text was clipped somehow...
I'd like to follow this up. Will you repost a non clipped version in View-O-matic please?
Ken Forgettable
 
Posts: 402
Joined: Tue Jan 06, 2009 5:04 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby dmitri » Tue May 19, 2009 2:58 pm

I've posted a new version of the bootloader. See http://www.megadrum.info/forums/viewtop ... 8678#p8678
Changes may be useful for the firmware update procedure.
dmitri
Site Admin
 
Posts: 8709
Joined: Fri Aug 03, 2007 8:05 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby elrules » Thu May 21, 2009 8:59 pm

Just to let you know, the implementation of the requested features is going well ;)
Version 1.7 will come soon
elrules
 
Posts: 629
Joined: Thu Nov 29, 2007 4:51 pm
Location: Murcia, Spain, Europe, The World

Re: Megadrum Config Tool FEATURE REQUESTS

Postby dmitri » Thu May 21, 2009 9:05 pm

I had to remove "Once you pressed the key DOWN to start the update, it sends back everything it received over MIDI including all bytes of incoming SysEx messages." option from the bootloader
dmitri
Site Admin
 
Posts: 8709
Joined: Fri Aug 03, 2007 8:05 pm

Re: Megadrum Config Tool FEATURE REQUESTS

Postby elrules » Thu May 21, 2009 9:07 pm

That means the only difference now is the clock selection sysex messages?

I have a doubt, which is the start note name in megadrum?

0 = Disabled
1 = D#0 ?¿?¿?¿ I don´t know in which note name megadrum starts the note scale
2 = ...
elrules
 
Posts: 629
Joined: Thu Nov 29, 2007 4:51 pm
Location: Murcia, Spain, Europe, The World

Re: Megadrum Config Tool FEATURE REQUESTS

Postby dmitri » Thu May 21, 2009 9:14 pm

1. C# -1
2. D -1

And so on
dmitri
Site Admin
 
Posts: 8709
Joined: Fri Aug 03, 2007 8:05 pm

PreviousNext

Return to Related Software

Who is online

Users browsing this forum: No registered users and 74 guests