force incoming midi to scales
Bonjour/hi,
Slowly come from usine 4 to 5 version, need to redo a lot of patches. Grid/IB is clearer and nicer now, but crashes often when moving several time patch in grid ('access violation').
The 'user scale' module no more works in usine 5.
Is there a way to define more scales in 'midi/transform' module? (never try the sdk, if it exist a simpler way...).
Salutations, Cyrille.
Slowly come from usine 4 to 5 version, need to redo a lot of patches. Grid/IB is clearer and nicer now, but crashes often when moving several time patch in grid ('access violation').
The 'user scale' module no more works in usine 5.
Is there a way to define more scales in 'midi/transform' module? (never try the sdk, if it exist a simpler way...).
Salutations, Cyrille.
you can't add scales directly to the transform module
but maybe a good candidate for a first script..?
I'm sure some guru will help you here..
and if you have serious crash , please report to senso..
but maybe a good candidate for a first script..?
I'm sure some guru will help you here..
and if you have serious crash , please report to senso..
I have had those errors as well but i think it is related to some of the modules in the patch have been modified in the new usine. I dont get the errors anymore after rebuilding the patch in v5. for custom scales i have had great results using the mapper (values) module for each scale. just map the MIDI note number to the mapper value. it can be time consuming to input all the values by hand but it is definitely a solid solution. And with some mathematical trickery im sure there are other ways to achieve this. But, i think the script idea mentioned above would be the cleanest solution.
i'll try with 'mapper'. Do you put one module by scale, and if yes, how do you select one or another?
For a script i can try collect scales (at least those in the old 'user scale') and put them in after someone had wrote it (i can't do that).
For now when i open old patches, i carefully do 'open patch', 'save patch' and 'clear patch' instead of move them in the grid to avoid crash. It's works.
Another things, the file saver with image in the layer is very efficient to quickly organize patche interface, very helpful to me.
For a script i can try collect scales (at least those in the old 'user scale') and put them in after someone had wrote it (i can't do that).
For now when i open old patches, i carefully do 'open patch', 'save patch' and 'clear patch' instead of move them in the grid to avoid crash. It's works.
Another things, the file saver with image in the layer is very efficient to quickly organize patche interface, very helpful to me.
soundmind : can't find 'mapper' (value?) module you wrote.
the mapper(value) is a regular Usine module ( data modules )
re-bonjour/re-hi
First,
It seems that crashes that i have, no more appear since i remove a particular patche that i use to do test on midi behaviours.
Then no more trouble in moving patches through grid. The trouble involves my patch, not usine.
How can i miss it?
Still can't see a way to use 'mapper' to my purpose : there is only 31 entry in it; do i need to use (128/31=4,1) 5 'mapper', or divide data1 from 'midi get message' by 12 and without lose the octave value? i need to think it more.
Another way is to redo 'scaleMap' module that it is almost exactly that i want, i take a look on the sdk, if i can understand.
First,
It seems that crashes that i have, no more appear since i remove a particular patche that i use to do test on midi behaviours.
Then no more trouble in moving patches through grid. The trouble involves my patch, not usine.
How can i miss it?
Still can't see a way to use 'mapper' to my purpose : there is only 31 entry in it; do i need to use (128/31=4,1) 5 'mapper', or divide data1 from 'midi get message' by 12 and without lose the octave value? i need to think it more.
Another way is to redo 'scaleMap' module that it is almost exactly that i want, i take a look on the sdk, if i can understand.
no, the mapper module has array entries
so you can use 2 array ( 128 faders )
one for in values , one for out values..?
more easy to edit...?
and good news for the crash..
so you can use 2 array ( 128 faders )
one for in values , one for out values..?
more easy to edit...?
and good news for the crash..
Bonjour/Hi,
I don't understand the 'mapper' and 'array' logic (allways go without that).
Here where am i yet (nowhere).
http://cid-364811c840d86441.skydrive.li ... 0scale.JPG
The SDK solution : definitively not for me!
Script is certainly the best solution but after having a look at the 'transpose' example, well, is also not so easy to get a good logical approach.
Salutation, Cyrille.
I don't understand the 'mapper' and 'array' logic (allways go without that).
Here where am i yet (nowhere).
http://cid-364811c840d86441.skydrive.li ... 0scale.JPG
The SDK solution : definitively not for me!
Script is certainly the best solution but after having a look at the 'transpose' example, well, is also not so easy to get a good logical approach.
Salutation, Cyrille.
Who is online
Users browsing this forum: No registered users and 62 guests
