An ‘unlearn’ option so you could just tweak the param you want to clear all mappings if you don’t remember what it’s being modulated by would also be great!Ī couple possible issues with specific modules:
I think I’d prefer if you could explicitly pick which bus was being mapped when turning on mod learn.
It seems like since the learning happens when modulation is produced, and they only send when they are being tweaked, there is no way to map macros to other parameters of other modules because they end up being mapped to themselves or other parameters of the macro module (though you could use an LFO source on the same bus to do the mapping). I think this especially an issue with macros. I’m finding it a bit error prone as there’s no easy way to tell what’s currently sending or the value, and I seem to keep ending up with unexpected mappings, or modulation sources modulating their own parameters etc. I am finding modulation mapping a bit tricky, maybe I’m missing something though. It will also be great to be able to include example presets with modules. Looking forward to incorporating modulation and the sample management into my modules. The new routing structure is really intuitive and navigating the module menu and router makes the workflow much faster. Really incredible work! Enjoying it a lot so far. 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 The idea behind the beta, is that I get to hear whats working, whats not, what can be improved… Then simply change the chain midi parameters on So active/auto means the input is taken to a track that is ‘selected’ on the device.īut for sure, if your driving with a sequencer its not that useful, so just turn if off, or move to a different channel The reason is simple, not everyone has controllers that can send on different channels (or do it quickly), I should point out this idea of an active input, is pretty common,Įlectron have it (auto channel) and so do squarp … its often the default. (this is mentioned in the Orac 2.0 overview video … around 14:54 ( ) … thanks to Antonio, there are timings in the YT description ) Now you will get no midi thru the main/active input If you don’t want to use midi for the active input, just go to the routers parametersĪ) put main midi channel to something you dont want to use (e.g. (and as you’ve seen on my Orac 2.0 for Organelle video - I often use a ‘proper’ keyboard with the Organelle )īUT as with many things in Orac, this is configurable!
What your missing is there are two ways to get midi in!Ĭhain input and ‘active input’ (also called Main Ctrl!)Īctive input, you usually associate with the organelle keys, but now Orac runs on other platform we need this possibility for midi as well. What I want to do is to have one or more chains in orac and trigger them individually from the midi tracks on my Digitone, preferably with the use of the Digitones parameter locking different CC values. What is the actual functionality of the Chain Midi page? As I understand I can make more chains and give them individual channels, yes? But why does my current chain 1 receive midi from my Keystep even with “In Midi” set to off? (0 = keep alive time (seconds), if > 0 server will drop connection if next ping is not recieved in 2 x keep alive time) TheTechnobear/MEC/blob/master/docs/OscMessages.md # Kontrol This protocol is described basically here: Then there is the underlying protocol between Orac, which is a proper protocol that not only distributes data but also meta data, this is how the Push2 is implemented in MEC - so it can have a completely different look n feel.
people ask about android, but I dont have a android box to develop on, so the community could easily write this themselves This is deliberate, since I wanted it to be write for another platformĮ.g.
The one you see in the PD/Lemur clients I call ‘OSC display protocol’, this is just rendering a display to the patch - if you open up the PD patch you will see its trivial.