Would you like a complete redesign of MCT?

[elrules]

I have been thinking on the possibility of redesigning MCT.

There are some features I was going to add to version 1.9, which are aftertouch mapping for using Addictive drums, easy tweakable drummaps, presets, etc...

THe thing is that from the user point of view, it would be easier to have different screens for each thing so he can focus on any of them without getting lost. Currently, in the main screen you have all the configuration panels, and part of a midi monitor, but you can open a more detailed monitor in other window, and then the drummaps, and so on... I think that maybe the application, as it´s growing, it´s getting messier.

My idea is to have a tabbed panel, in which each tab represents a different logical part of the application: Monitor, Configuration, Drummaps, Curve Editor, Firmware updating, Tools & Options, Log

In the monitor tab I will put a good monitor, with individual bars for each input, log of hits, xtalk spotting, etc. This is the only screen that the user would like to see when playing or when trying to find configuration problems.

In the configuration I will put all the configuration panels (misc, hihat and inputs) but removing midi channel, midi note and curve from the hihat and the inputs

In the Drummaps tab, I will put all the inputs with midi channel, midi note and curve parameters, with options to map their corresponding aftertouch notes to other notes. Also here you can select which VST you are using so instead of midi note numbers you can select the name of the element to trigger (for example, I say I am using Superior 2 and the midi note box gives me a list of all the elements of the Superior 2 drumkit, that internally will be converted to midi notes)

In the Curve editor the current curve editor

In the firmware updating a nice interface to change input names, update firmware, with instructions step by step (all in the same panel, without popups)

In the Tools and Options tab, the options of the application and other things I still haven´t thought about

In the Log tab, the application log


I want to know if you people like this new approach and if you have any suggestions to do for this new design. What do you think?

PD: I will update soon MCT to 1.83 including the new option dmitri included: Inputs priority. And then I will stop any development of that version of the program to work on this new one. It may take me some time, but the result I think would be nicer

[davem]

elrules,

I think that would be great. It would be really nice if we could use native widgets also for each operating system. I'm more than happy to help in this effort.

Dave

[jman 31]

Elrules, I think what you have done already is awesome! If you have the time and the desire, I say go for it. I'm sure people would love it. But, I think that what you have already offered to this community with it the way it is, is huge!

By the way, thanks for a great program!

Jman

[davem]

I have to echo JMan by the way. MCT makes setting all these pads up sooo much easier. Doing the odd tweak directly to the MD is alright, but it's far simpler to use the computer

[cortinerocañero]

Hello, I'm confused about the above but I think I understand very well, about everything from being able to be configured for various programas.Ya it be great to have it in Spanish
a greeting and encouragement are doing a good job

[elrules]

Yeah, a feature to be added is the possibility of internationalization, that is, making it possible to show the application in several languages

[Ken Forgettable]

+ Maccas graphs still need doing
+ change 'live' editing to only send updates on change of focus or lengthen delay to allow for fine adjustments.
+ Have Pads name highlighted on note reception to compliment the MIDI monitor and Quick access - would also highlight cross talk and related issues.
+ Be able to read/save any slot not just the default startup slot 1

[alchemicus]

yeaah great ideas!
I hope there will be a good compatibilty with mac os!
And for italian traslation, i'm here!!

[Ken Forgettable]

elrules did ask for help - anyone with time to sign up?

[elrules]

I will answer your private message here, Ken, so everybody can join and help.

And many of your would have realized. I don't have much time for developing this new version of MCT.

I have moved this week from Amsterdam to Barcelona. I got a brand new job here. iPhone development this time so I am pretty busy doing Objective-C programming (sounds like I will get some practice to help Dave finishing those drivers for being able to connect MCT and Megadrum in a Mac computer).

The thing is that Ken asked me through PM how do we have to proceed to continue the development of MCT. I have been looking in google code how to make a branch of the project to continue developing in that branch but couldn't find how to do it. The idea is that, as this new proposed version is going to be a completely different approach, it would be better to leave the current MCT 1.82 untouched, and start with the new one either in another branch (how?) or in a new project under google code.

What do you guys think? Who is in?