to those not familiar with developing modules on orac.
Iād like to point out its very easy for end-users to move pages around, or add parameters onto different pages - you simply need to edit the modules.json file of the module.
(orac doesnāt even care if you place the same parameter on two or more pages!)
@oweno im not sure id put it on the first page, as this means all the module pages are now offset. - thatās the reason the id had them in this order, so they match the module keys used for activationā¦ i think this is very important.
what you could do, is place this straight after the modules - this would mean its still on a āknownā key, so quick to access.
generally what i do for gain staging isā¦
a) turn up/down individual modules that i know are quiet/loud
b) use the chains gain to balance āthe tracksā
c) use P2 as main output gain.
so i could see if we had a page with gain for ch1, ch2,ch3,final out ā¦ that would cover most of my use-casesā¦
its 1 page for the chain and final out on a known key, and then individual gains are on the respective module key.
Orac uses its own mother.pd , so there is nothing stopping me adding parameters to control the master compressor if thatās desirable.
(just let me know what parameters and what there ranges should beā¦ id use current values as the default
alternatively (perhaps preferable?) i could remove compressor from mother.pd, and
- have a compressor in new module slot (out)
- move compressor into the router
yeah Iām still grappling with the best way to give access to gain of modules.
currently its done in the most āmodular/flexibleā way possible, as its under complete control of the router module - but that does limit the UI mechanism available.
however, I do recognise gain is a very important aspect, so perhaps it needs to be handled separatelyā¦ e.g. i could imagine something āfancyā where i could switch the vu-meters to present the input output of the āselected moduleā when in mixer mode
of course, im still limited by UI ,
the main goal of orac, was that patches were easy to convert ā¦ so therefore ive not made any assumptions about the use of the keys, and in particular about the AUX key.
this mean most orac functionality end up in the menu - but this is not appropriate for something like a mixer which we need fast access too.
however, now that Orac is maturing, iām thinking about āreconsideringā this, and focus on allowing Orac to have a UI which is coherent, rather than just being compatible 
in particular, I think @oweno and @chrisk have shown on recent patches some really creative use of the AUX key to form a āfunctionā key ā¦ and I like the way its consistent across patches.
I could see something similar in Orac, where AUX is used to:
- toggle things (arm/play)
- be a shortcut into other functionality, like a specialised mixer.
this would mean changes to some modules, but Ive some ideas on how to minimise that.
it seems like a good way forward for Orac, as the aux key/aux line and status have been a bit of misnomer in Aux, which means its tending to be under-utilised (imo)
) 
