nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 15, 2019 10:46:53 GMT
Following on from this post I have created a random panner module for MidiFire as requested by janosax. There are two blocks in this scene (attached) which you can merge into your canvas. The first, 'Note Blocker' is a simple Stream Byter script for filtering in just the notes you wish to allow to trigger the panner. It is configured to only allow the F4, G4, A4 and B4 though to trigger the panner. The second block is the panner which has some configurable variables at the top as follows: ASS K0 = B0 0A - you can specify the CC to be sent if you don't want the MIDI pan CC ASS K2 = 10 20 2 - specifies the minimum and maximum pans (actual value will be randomised between these two (16 and 32) and also the delay between pan CCs as the panner gradually pans from L to R (or R to L) and you can change that pan speed (or disable entirely by setting to 0) The panner will only output the pan CC and nothing else so should be used in parallel. Regards, Nic.
|
|
|
Post by janosax on Jan 15, 2019 13:02:54 GMT
Thanks Nic for your quick work on this new module :-)
I had to change notes as they needed to be F3-G3-A3-B3, my mistake, and I had to add Protocol Filter to filter all notes at the end of the scene, just allowing CC to pass though, as Janosax Custom already allows those notes, to avoid doublons.
On this new pan Randomizer, limits work as intended. I’ve set delay to 0 as it’s supposed to send a fixed value with fast note on/off trigger. Could be interesting with hold/toggle CC trigger.
However, # determine final value IF L1 ... pan right or pan left, don’t work, as I suppose it should alternate left and right trigger? There are often multiple trigger to the same side: pan right pan right pan right pan left pan right pan right, just an example.
Also, triggered values are often too much close from each other, like CC value 85 then 89, so there is no real difference (can’t even see AUM’s knob moving), so there is still a potential phasing issue here, or at least lack of loops spacialisation.
Hope my feedback helps, thanks again.
|
|
nic
Soapbox Supremo
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Jan 16, 2019 14:31:08 GMT
Hi janosax , I'm not sure why you needed to add the Protocol Filter at the end as the panner only produces that CC and blocks all incoming events. It should alternate between L and R for each trigger note. I have just tested this and I cannot make it stay on the same side. :-) Also, pan centre is 64 so the panner generates values < 64 for Left and > 64 for Right. You should see what side it goes to and by how many CC value units in the two block labels. I'm thinking if two notes were received then this would keep it on the same side. Could that be the issue? You can change the random limits (in scene I sent you was set to min:16, max:32 (I think)) to expand the range that the random numbers will fall to make the pan more apparent. Do you wish to email me your Scene and I can check over it? It may not be a problem with the panner itself but how everything is hooked up. Regards, Nic.
|
|
|
Post by janosax on Jan 16, 2019 23:30:06 GMT
I’ve just sent you a mail with the scene :-)
Many thanks.
|
|
|
Post by janosax on Jan 17, 2019 23:35:27 GMT
Works perfectly in my setup now after Nic has fixed my mistakes!!
Very very nice feature for my looping stuff.
MidiFire and Nic just rocks :-)
|
|