they just at some point need to be held together at the same time for 5 seconds.
no gymnastics or special timing required 
5 seconds is also longer than many ‘expect’ , you can actually change this in the sidekick.json file.
but i wanted it ‘long enough’ that its not done accidentally…
I played it pretty conservatively, you probably could reduce it to 3 seconds and it would feel more responsive - and highly unlikely you’d trigger it by accident.
as i said, Im happy to implement other key combos, that could be switched in the config file.
again, I was pretty conservative, as I’m not that familiar with norns patches, so was not sure what combos are in use - possibly 2 buttons for 3 seconds.
the ‘requirement’ is…
a) it cannot be a combination of something that is used in norns patches (or orac/pd patches)
b) it has to be simple and memorable.
c) you don’t want something that can be trigged accidentally.
d) has to work on both fates and factory norns
e) we do not know the ‘state’ of norns (this would required a change to norns) which I dont want to do (*)
f) I don’t want to present a UI (e.g. bring up an ‘are you sure message’) as i cannot guarantee norns patches will redisplay the screen over it… or not overwrite it.
apart from that i can do whatever…even something complex. press enc 1, turn enc 1, enc 2 , enc 3, press but 3 , within 5 seconds (though this probably falls foul of both a, b and c )
(*) there is a another potential solution, and that is I fork Norns, and put an ‘exit’ option on the menu,
but I quite like the fact that the norns software is ‘untouched’ currently.
forking for such a small change does not seem work ith.
the intention of PolyPd was to see how easy it was to convert a ‘standard’ organelle patch,
which meant making the minimum number of changes possible.
this has some ‘limitations’… what would be resolved if I was ‘doing it properly’
these are:
a) mother.pd
I did not ship routeOSC as its not needed, but left parts of mother.pd unchanged where it used it BUT would make no difference to functionality.
b) defaults and /tmp/patch/knobs.txt
this i probably should have shipped as i forgot this is how organelle gives reasonable ‘default’ values to the patch. this means currently you have to twist each encoder to start off at a reasonable default.
c) encoder 4
so to make the implementation simple, I matched the 4 fates encoders to the 4 pots on the organelle,
to support 3 encoders, would mean changing the patch much more, and so defeat the purpose.
AND given we only have 4 encoders i use but 3+ enc 4 as a volume control.
so your issue is a combination of b) and c)
it defaulting to a very low pitch, so you need to twist enc 1 but worst, is i think its default to zero volume, which you cannot change as you dont have encoder 4
SO…
what I need to do for this ‘demo’, is simply default the values to something reasonable, and move the volume to but 3+ enc1 - its still won’t be perfect for the norns, since you wont be able to change the 4th parameter but thats not really the point of this patch
Im still think about if this ‘mother.pd’ will just be an example of how it might be patched, or something I’ll actually make a bit more ‘thorough’, and so remove the bits not needed.
this is part of thinking about how compatible to i want to make fates/norns with organelle patches… which I’m still not 100% decided on.
in terms of ‘fixing properly’ , or converting real patches
this is patch is only a starting point
if you want to use 3 encoders, dealing with multiple parameters would have to be done in a different way.
given the UI of the organelle is different to the factory norns - that comes as ‘no surprise’, and I think revisiting the UI is no bad thing.
(obviously a fates with 4 encoders, could quite easily use an organelle patch largely unmodified as demo’d in polypd - this is why I asked @okyeron to add the 4th encoder option )
anyway, i think you’ll find if you open up in VNC theres no fundamental issue, just this demo patch is not really currently ‘designed’ for a 3 encoder norns.
