So cool
I see op-xy on the back, did you also map it and using together with m8? Or separate?
Would you be at all willing to share the file? ![]()
Sharing my Tonverk indef files here too in case its helpful.
Danke!
ok here it is @josker Still has to be mapped in M8 but I can also send the M8 song template file if you want?
M8.oxie16 (93.2 KB)
OXIE16.m8s (109.7 KB)
I havenāt yet but OXI already has an instrument definition for it so it will fun to do so!
Thanks so much! ![]()
![]()
Is anyone whoās using this controller in 14-bit mode shocked by how aggressive the acceleration is, even on Acc0 which is supposed to be linear? Like, I can go from 0-16383 within 1.5 turns, tops. It kind of defeats the purpose of 14-bit mode. I seem to remember that the curve of Acc1 on the EC4 was a sweet spot for me.
If Iām not really mindful of the speed with which Iām turning I get jumps of several hundred values at a crack.
What Iād really love to see is a ācurveā adjustment where you can actually set the acceleration curve of value-to-turn-speed instead of choosing from 4 presets.
The device itself is really beautiful and the build quality is very confidence-inspiring. Iām hoping someone sees this or maybe itās on the to-do list to fine-tune this feature!
Ive been reading and hearing that they are very responsive and considerate to requests.
Its been 6 yrs since you posted wow!
Itās definitely been some time⦠I got sucked into max/msp and offloaded my Digitakt, which I still miss sometimes. Itās funny, when I look at my last post itās about basically the same thing, only on the Digitakt. I really just want to be able to adjust the response curves of ALL the knobs!
Yes. My biggest problem with it though is the 2 cc (+push) per knob limit.
Having 4 cc per knob at least would REALLY open this thing up.
The function where you use one knob to control others is pretty pointless once its setup as the master knob makes the others redundant.
Just give us more CC per knob so we can make proper macros.
E16 owners: how do you deal with the collision between Elektronās pattern-stored track levels and the last states of your E16 encoders before you switch patterns?
apart from the Octatrack which can send a MIDI state dump on command, does this basically mean you can only have an E16 smoothly controlling, say, a Digitakt or Digitone across multiple patterns if you opt for Perform Kit mode (i.e. no cross-pattern variation in kits) ?
trying to wrap my head around the tradeoffs before I commit to buying one
I donāt think you can, unless you can send CC on pattern change (I believe you can on the Neuzeit Drop). If Elektron re-instate the global level functionality then it would work nicely. The E16 would drive and the levels would reflect that as you change pattern. Something I desperately want them to add back (Its in the Mk1 boxes)
I see. thatās a shame. so it sounds like:
(a) stick with Perform Kit mode
(b) after changing patterns, gently wiggle essential encoders on each track you intend to control from the E16, so the Elektron sends CCs to the E16 and update it on their new current values
Whats everyoneās experience with the build quality? The device is really quite expensive where I live (for me personally ) and I donāt really want to pay for postage if I had to replace a faulty unit.
Like the OXI One sequencer, itās bomber fucking solid. Zero complaints in that department.
Awesome. I think it will suit my use case and I like the space vs feature set.
Does anyone here use an Oxi One and E16 to create automated ādropsā like the Neuzeit Drop? Can I fire the drops from the sequencer and sync to the BPM? Apparently the āsnapshotā drops are not synced and run free. Thanks!