odd that you should have to reinstall orac… cannot think why that would be
oh, well main thing is its working!
and thank you for noticing
(theres quite a lot of subtle changes, that won’t even make an change list)
you can do all this already…
what your missing is there are two ways to get midi in!
chain input and ‘active input’ (also called Main Ctrl!)
active input, you usually associate with the organelle keys, but now Orac runs on other platform we need this possibility for midi as well.
(and as you’ve seen on my Orac 2.0 for Organelle video - I often use a ‘proper’ keyboard with the Organelle )
BUT as with many things in Orac, this is configurable!
if you don’t want to use midi for the active input, just go to the routers parameters
a) put main midi channel to something you dont want to use (e.g. 16)
b) set note to OFF
now you will get no midi thru the main/active input
(this is mentioned in the Orac 2.0 overview video … around 14:54 (https://www.youtube.com/watch?v=mywEOeth40Y&t=894s) … thanks to Antonio, there are timings in the YT description )
I should point out this idea of an active input, is pretty common,
electron have it (auto channel) and so do squarp … its often the default.
the reason is simple, not everyone has controllers that can send on different channels (or do it quickly),
so active/auto means the input is taken to a track that is ‘selected’ on the device.
(this is exactly what Orac is doing)
but for sure, if your driving with a sequencer its not that useful, so just turn if off, or move to a different channel
then simply change the chain midi parameters on
Chain 1 Midi In = ON, In midi ch = 1,
Chain 2 Midi In = ON, In midi ch = 2,
Chain 3 Midi In = ON, In midi ch = 3,
its be really useful if you tried this…
the idea behind the beta, is that I get to hear whats working , whats not, what can be improved…
if everyone just ‘waits for it to be finished’ , then nothing will get improved, since the only inputs is mine… and excluding bugs, I’m fairly happy with it as it is