clairerobot

I'm stuck with a hack i'm trying to do on M4Live Granulator II - basically intersecting the midi to freq conversions to input lists of my own microtonal scales and thus trying to use midi notes in Ableton clips only as placeholders for my own scales... i managed to do this easy with other basic M4L synths, but for some reason i can't grasp, when i do this to Granulator it also pitches everything 4 octaves higher... can anyone clue me in on why this is happening?

I attach 3 screenshots, first of the overview and then the 'ml.poly.granulator' and then 'p fm pitch' patches (ALL EDITS MARKED PINK). I suspect the most important part is the FM/PITCH subpatch but I may be wrong. I also noticed that the mtof object in it's original form/function in the original patch gives really small values - and not at all the frequencies that i am hearing, so perhaps this is actually controlling something else that I am missing.

I'm stuck with a hack i'm trying to do on M4Live Granulator II - basically intersecting the midi to freq conversions to input lists of my own microtonal scales and thus trying to use midi notes in Ableton clips only as placeholders for my own scales... i managed to do this easy with other basic M4L synths, but for some reason i can't grasp, when i do this to Granulator it also pitches everything 4 octaves higher... can anyone clue me in on why this is happening?  

I attach 3 screenshots, first of the overview and then the 'ml.poly.granulator' and then 'p fm pitch' patches (ALL EDITS MARKED PINK).  I suspect the most important part is the FM/PITCH subpatch but I may be wrong.  I also noticed that the mtof object in it's original form/function in the original patch gives really small values - and not at all the frequencies that i am hearing, so perhaps this is actually controlling something else that I am missing.

trying-to-hack-granulator-ii-in-order-to-enable-special-scales

[mtof 0.] has a base of 0. hz set. As standard (ie if you just create a new mtof, no argument) it is set to 440hz, hence the pitch difference. Look in the inspector and it should make sense.

What would be the reason/motivation to set the mtof to 0. hz in the original?

Not sure without poking round the patch, but I guess so that you can get to the lower octaves. Perhaps it's necessary because of the transpose system used late in the chain? does it solve your problem though?

how would we know if that represents 0. Hz output or note number 0. input? mtof does not allow to connect a bang. :D

the reason why it is set to 0. is that people are used to set object to floating point mode this way.

of course for [mtof] this is not needed as is can only output float anyway (there is no use for truncated Hz values), but it is required for objects like [ftom], for example.

the reason why it is set to 0. is that people are used to set object to floating point mode this way. 

True enough... seemed to fit the problem so well... but I didn't test it!

even compressed the patch is pretty big and each time i try to paste it here the post won't complete - is there another way to share it with you? i'd be happy to e-mail it

even compressed the patch is pretty big and each time i try to paste it here the post won't complete - is there another way to share it with you?  i'd be happy to e-mail it


Success! In the FM+PITCH sub patcher: that tiny decimal that the mtof gets multiplied with (division) - dividing by 10 each time moves it an octave down :)

i'm sure i probably need to apply the same principle to other parts of the patcher for correct finer nuances but for now i can continue with the piece..

Success!  In the FM+PITCH sub patcher: that tiny decimal that the mtof gets multiplied with (division) - dividing by 10 each time moves it an octave down :)

i'm sure i probably need to apply the same principle to other parts of the patcher for correct finer nuances but for now i can continue with the piece..


Trying to hack Granulator II in order to enable special scales