Got a quick reponse from Manuel and Oh boy am I relieved! He kept the insta jump feature along with quantised launch. The setting is in the Arranger’s Launch quantization settings menu:
“Load quantization. Same as Launch quantization but in this case applies when the Arranger is OFF and the patterns are manually loaded.” P. 51
I wasn’t sure 100% but seemed weird too that it was gone for good. Config menu is getting beefier but these quality of life settings are a godsend. Usually a workflow is imposed and you either like it or work around it, OXI may be the most customisable sequencer in that aspect.
Happy for you 
No, you may use Harmonizer in 3 seqs and transpose on the lead. Not the same but it works for that case.
Don’t think so (not sure, don’t have the thing in front atm)
Ooh, a bit of a scary workflow.
Let’s say you have project 1 open – it’s empty. You build your masterpiece. Then you press Save -> Select slot 3. You select “duplicate project”.
Done, you’ve performed a save operation.
Except that you’ve duplicated the empty project to slot 3 and if you now think you’ve Saved on Slot 3, and go loading that project, your masterpiece is gone.
I know that the wording used and the workflow makes sense in the Oxi world, but pressing Save -> select slot is such a common workflow, and it works differently everywhere, that I’d hope there’s room for rethinking that one…
What alternative would you suggest?
Maybe there could simply be something like
”Save project here”?
Trying to figure out if it breaks some current workflow… I think the Oxi saving flow could be directly analogous to Save vs. Save As in computers:
Shift-Save (which saves the open project to the currently ”open” slot) on Oxi is ’Save’ on computers: with OSX, Windows et al ’Save’ saves the open file with the current filename.
Pressing Save and selecting the slot where to save on Oxi is equivalent to ’Save as’ on computers: it lets you specify the filename (or in this case, project slot) before saving.
Overall, having this structure where you can’t open a ’new project’ without choosing a project slot is slightly different from typical conventions, but yeah – I guess the main concern is avoiding loss of work.
I’m a bit stuck here between my DAW, WIDI Jacks, and the OXI, hopefully someone can tell me if what I want is possible.
I want the “Central” device in the WIDI group to be my PC MIDI interface.
I would like the OXI to receive clock from the DAW.
I have 3-4 WIDI Jack devices, currently set to peripheral.
I would need to connect the OXI One via USB or somesuch, and then would I be able to receive clock, but send notes out to the “Central” WIDI device (RME Interface MIDI ports) and then have the MIDI broadcast to the 4 peripheral WIDI Jacks?
Hi!
When applying probabilities or logic (in my case, 1|2) to longer notes, I try to press the start point of the longer note.
So, let’s say I have a green note on step 1 with a white tail extending to step 4.
If I apply 1|2 to the green “head” of the note, what happens is the note won’t sound on step 1, the second time around, but rather on step 2, the “tail end” of the note.
Am I missing something? I would expect the condition to apply to the entire note.
Thanks!
It definitely should apply to the full note, not just the ‘head’ as it were - are you on the latest firmware? Could be a bug.
Probably not implemented! I’ll tell Manu right away, seems to be an easy fix just copying the “head” value to the “tail”. That wouldn’t work well with random though, only with logic hmm…
Is it working fine for you on 3.0?
Yes exactly, missed the part of explaining on how the actual transposition has to be done in the lead sequence. However the difference with Hazmonizer is that the follower sequencers transpose with quantisation, so it’s not fixed transposition like most engines do. This is much better in my opinion, but it’s not possible to transpose all sequencers at the same time without quatisation.
Yes, latest, that is, 3.0 
Thanks for picking this up @CarlosUnch !
Just ordered yesterday! Very excited!
This sequencer will definitely need some youtubers to spread the word of it’s 3.0 update because all the older videos are very outdated.
Unfortunately for Oxi I think the video a lot of people watch is the Loopop one.
agreed, here’s hoping for more / updated tutorials soon 
Question: can you hook a midi keyboard (e.g. the op1-field) to the usb-c in of the oxi, and then send that (+clock) thru through the midi ouputs of the oxi?
So that I could control/sequence other synths from both the op-1 and oxi?
In theory, sure thing. In practice I don’t know if the OP1 is supported yet. Is it @OxiInstruments ?
I believe this can be done but it is probably worth owning an Rk006 which makes working with OP1s much easier.
I have clocking coming from USB (Ableton) into Oxi one which I then send MIDI out to other gear and that clocks/sequences everything in time with the DAW.
I had an OP-1 Field for a few days and surprisingly, MIDI Bluetooth from/to OXI was working flawlessly while MIDI USB was not.
I could, all at the same time:
This was an all wireless battery powered setup, so you still have all the physical I/O from both machines available.
Wow thanks carlos, that sounds interesting indeed! Definitely gonna try it.
Too bad there is no such thing as clock sync over BLE. Lets hope setting them on the same tempo manually will suffice.
Also, i was syncing my tx-6 to the op-1 field via BLE, so will have to make choices.
Might have to buy an additional unit such as rk-006 then, this might open up a lot of possibilities. I hope haha