As far as I have been able to use it, the existing transform MIDI module simply spans the correct notes over a set of keys (neighboring MIDI note values will generate the same corrected note value). I suppose this works well for pianos (I will play with it today
midi transforming for a grid
For the Push project, I want to make a simple way to map the grid to different scales. I would prefer to do this by writing a script that outputs an array of velocities and then be able to take the changed index of the array and have that correspond directly to the "correct" note in the scale.
As far as I have been able to use it, the existing transform MIDI module simply spans the correct notes over a set of keys (neighboring MIDI note values will generate the same corrected note value). I suppose this works well for pianos (I will play with it today
), but for using a grid/matrix I think there must be a way to do it based on sequential numbers, or we need to script/patch one.
As far as I have been able to use it, the existing transform MIDI module simply spans the correct notes over a set of keys (neighboring MIDI note values will generate the same corrected note value). I suppose this works well for pianos (I will play with it today
So no one else has had any issues with grids (or anything else) + midi transforming? 
senso, is it difficult to add an integer based input pin combined with a "notes in scale" pin output?
senso, is it difficult to add an integer based input pin combined with a "notes in scale" pin output?
Can't help for scripts, but can you provide an example of the way you use matrix + midi transformer , cause there's different ways to patch this .
About the transformation of the module, i'll transmit to senso (generally it's better to use the Suggestions & improvements forum for this )
About the transformation of the module, i'll transmit to senso (generally it's better to use the Suggestions & improvements forum for this )
Are you looking for a diatonic transposition?
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp
Sorry, I should have been more specific.
There is a "scale" listbox which will make sure all notes will be in a specified key. When you play a C or C#, it will play C# for both if you are in the key of C. It's not always two notes mapping into one note, sometimes it is three notes and sometimes one.
I'd like to use it from the perspective of a grid -- so 0 is the first note of the selected scale, 1 is the next note, etc. I guess we would also need an output from the transformer that says how many notes the current scale has in an octave. Then I could indicate scales properly on the grid by highlighting every root note. Say it is D Minor, then every 8th pad will be highlighted in a different color than the rest of the pads. The transformer module doesn't really care much though, it just takes whatever MIDI note number (ie grid index) and sends out the right note.
Should I post this again in the suggestions section?
There is a "scale" listbox which will make sure all notes will be in a specified key. When you play a C or C#, it will play C# for both if you are in the key of C. It's not always two notes mapping into one note, sometimes it is three notes and sometimes one.
I'd like to use it from the perspective of a grid -- so 0 is the first note of the selected scale, 1 is the next note, etc. I guess we would also need an output from the transformer that says how many notes the current scale has in an octave. Then I could indicate scales properly on the grid by highlighting every root note. Say it is D Minor, then every 8th pad will be highlighted in a different color than the rest of the pads. The transformer module doesn't really care much though, it just takes whatever MIDI note number (ie grid index) and sends out the right note.
Should I post this again in the suggestions section?
yes, pleaseShould I post this again in the suggestions section?
Who is online
Users browsing this forum: No registered users and 29 guests
