famusvictim
2013-05-19 09:03:23
TWO FEATURES I WANT THE MOST
FIRST FEATURE - MULT. MIDI OUT
A single MIDI message output per translator is perhaps the most cumbersome thing about MT, and limits the program from every being a useful compositional mnemonic tool, for those who want to create custom single button 4-part harmony controller set-ups, for example. If someone wanted to set up 8 4-note chords each designated to a specific controller pad, then it takes them 32 translators instead of what could be just 8 translators.
This is the one feature that I think could most increase one's efficiency with MT.
A program called Nodal does this (but only for note data, and is designed for organizing temporal and tonal algorithms, instead of MIDI translation and MIDI translation algorithmic control) - but seeing this made me think that this really should be a feature of MT... especially from a musician's standpoint, and also from the standpoint of having a simpler project file.
In general it would make an MT project file look like, feel and behave in a much more efficient and uncluttered manner, in my opinion. It could reduce bugs, unclutter the sometimes massive number of translators, and be more cognitively efficient.
Perhaps it could even lead to new functionality that might appeal to musicians, especially those used to sequencing, in future versions, like drop down menus for chords, or even custom arpeggios (see below).
A SECOND SUGGESTION:
I would REALLY like MT to autodetect BPM information from software inputs, and then have a drop down feature where you can link timers to the BPM via note types (1/64th to whole note, etc...) This could REALLY turn MT into a custom effects powerhouse...
FIRST FEATURE - MULT. MIDI OUT
A single MIDI message output per translator is perhaps the most cumbersome thing about MT, and limits the program from every being a useful compositional mnemonic tool, for those who want to create custom single button 4-part harmony controller set-ups, for example. If someone wanted to set up 8 4-note chords each designated to a specific controller pad, then it takes them 32 translators instead of what could be just 8 translators.
This is the one feature that I think could most increase one's efficiency with MT.
A program called Nodal does this (but only for note data, and is designed for organizing temporal and tonal algorithms, instead of MIDI translation and MIDI translation algorithmic control) - but seeing this made me think that this really should be a feature of MT... especially from a musician's standpoint, and also from the standpoint of having a simpler project file.
In general it would make an MT project file look like, feel and behave in a much more efficient and uncluttered manner, in my opinion. It could reduce bugs, unclutter the sometimes massive number of translators, and be more cognitively efficient.
Perhaps it could even lead to new functionality that might appeal to musicians, especially those used to sequencing, in future versions, like drop down menus for chords, or even custom arpeggios (see below).
A SECOND SUGGESTION:
I would REALLY like MT to autodetect BPM information from software inputs, and then have a drop down feature where you can link timers to the BPM via note types (1/64th to whole note, etc...) This could REALLY turn MT into a custom effects powerhouse...