Same here! It’s like what people say about the OT - it does so much, but you don’t need to learn it all at once, or ever really. I’m wanting to learn the pattern-baaed stuff now, and it’s a blast! One day I’ll dig into Matriceal.
Only had mine for a day but absolutely love it. Having come from a dark place (Kordbot) and then a halfway house of after thoughts (Deluge) I can fully appreciate the class of this device. For a start it worked off the bat with Logic. Setting up the bluetooth connection was a breeze and Logic is very responsive. The basics clicked soon enough - done a drum pattern, changed the pattern lengths, added some chords, set the bass to harmonise to follow any chord changes, got a few VSTS on the go - lovely stuff! The build quality is something else - very classy, sturdy, Apple’esque. I love they included a midi cable, usb connection and an actual carrier case. I have a list of stuff im planning to go deeper on today and determined to make it do what i want and not get all loopy! But so far so good!
The shortcuts and operation of this I find generally pretty intuitive, and I’m blown away by it frankly. However one thing I’m finding odd is copy & pasting patterns.
Is the only way to copy a pattern diving into the menus and using the encoders?
The much more intuitive approach of using the copy & paste buttons seems a strange omission. It’s a small thing, but thought I’d ask
Hmm, true! I haven’t used the pattern part of it too much, but this is a surprising omission, given that the copy/paste features are generally pretty good.
Besides this, I hope we could modify the trig probability for multiple steps at a time.
There are some ways to copy a pattern. What exactly you’re trying to accomplish?
Simply copy the whole pattern for a sequencer to another pattern, the most basic thing.
Still not 100% clear So for instance you are in sequencer 1 and you want to copy the pattern stored in slot 1 to slot 2 in the same sequencer? In this case you can just press (or hold) the save button and double-tap pattern slot 2 to copy it there.
That’s effectively what I’m after, thanks! - it’s much easier than the menu diving. It’s still takes a bit of a mental leap (for me at least) as the row you save into isn’t related to the active sequencer
Waiting on an OXI One from the lovely guys at Signal Sounds. I’m wondering about midi thru possibilities and the experience people have.
I will be using the OXI to sequence my elektron devices but I would love to be able to use my Stolperbeats module to take over pattern modulation once in a while.
Can the OXI take in midi and pass it through to other devices or even use it to modulate one of its own sequences on the fly?
What’s the state of the instrument definition?
The manual don’t say much about it.
I would love to be able to load a definition for the multi track midi mapping depending on the iOS synth I use. Is this already possible?
no. only predefined instruments.
this is a feature request on the Oxi forums tho
however you can map CCs easily enough you just can’t save them as an instrument def.
Thanks @drxcm.
Where can I find those predefined instruments?
There isn’t a published list
When i get a chance i could list them here.
I can’t get the OXI One to send bank change messages, at least not to my Hydrasynth. The prog change messages work just fine, but the bank option does nothing. So all I can set is patches in the first bank ‘A’ which isn’t much use.
I’m setting this on the OXI on the third page of settings for a sequencer, I’m not using the arranger
Is there something I’m missing?
TL;DR: It’s a known issue, try to annoy Manu enough to implement the workaround
A Bank Select consists of two parts (bytes) because in the MIDI standard it’s specified to address up to 16.129 banks. But some synths messes up with how to read the two bytes. They read the MSB (most significant byte) as the bank number and ignore the LSB (least significant byte) completely. Technically the LSB and MSB are send in two parts but the device just stops reading after the first part.
The OXI (still ) can’t be configured whether the LSB or MSB should be send first in order to control this kinda devices properly. This should be a per sequencer setting. It was brought up a couple of times in the past but it hasn’t been resolved yet. My workaround with the Hydrasynth and others is to keep the presets I use in production on bank 1.
I think it’s on the Discord, and if I recall correctly the the feature request has been closed since there are other features being prioritized now.
It would be nice to get back to custom defs once it hits whatever milestones.
Thanks
I’m pretty familiar with MIDI and the whole LSB & MSB stuff, as I’ve written several bits of MIDI software and spent plenty of time in the bytes and nibbles of MIDI messages.
I don’t really know who is at fault here, I tested the Hydrasynth sending both the LSB + MSB over CC 0 & 32 and it worked fine, but the OXI doesn’t seem to work. But good to know it’s not me doing anything wrong
I’m not putting my Hydra presets in bank A, I’ll simply give up on the OXI for program/bank changes
Interesting, thanks for sharing. Gonna have a deeper look into the MIDI packets. Maybe my explanation was wrong. Another factor which comes to my mind is the timing. Lets see…
Very surprised that Bluetooth is working so well in combo with a Mac M2 and Ableton with a very low buffer size. Hardly any latency and rock solid connection.
Hadn’t thought I could do this without cables.
I created a Tips and Tricks thread for the Oxi One. Thought it would be easier to follow vs the full discussion here.