Oxi Instruments E16 MIDI-Controller

Don’t have an Oxi so sorry if not helpful but have a couple questions.

Is the idea that you leave filter cut at 127 and then switch to another page and then back, at which point the filter resets to 0?

Or, does the filter cutoff lose its value as soon as you switch the page?

If it’s the second scenario, I’m guessing it’s possible that your second (or other page) shares a CC value with the first page. Even if it’s not the same CC# it could be a modwheel message or something.

If it’s the first scenario, I would reach out to Oxi because I’m guessing there’s something you can set in the software. *edit I see you reached out in discord

1 Like

Thank you for troubleshooting with me @Jacob

When e16 boots up, it goes to a main screen that shows the “home” screen. From there, there are scenes displayed, generally each scene set up for different instruments. Mine is m8, tx-6, opxy and the others are as of yet unused.

Once i select “opxy” is when it kicks off. The scene then shows 12 presets, which in my case correspond with tracks 1-8 and 4 unused slots.

Anyways, i will hit up support!

1 Like

I think you need to config the option that doesn’t send the values when you load a scene.

1 Like

Ive triedby using the “confirm” option but its not working but thank you for the ideas.

if I understand you right: turn on the E16, go the CONF page, go to System, and then Transmit Params. Turn this off. This way the E16 won’t send all the CC values when you load a scene.

3 Likes

Yesssss @ozias_leduc thank you! I should not have assumed all settings were on the oxi app. Phew this makes life so much better.

1 Like

To be honest it was @alespardo’s post that made me realised that option existed!

It has been annoying me too - every time I’d switch scene, whatever synth it was connected to would totally shit itself lol

On a separate note, I must say the Oxi App could be lot better. Not a fan.

3 Likes

I try to rely on Mod Macros (sending MW/BC from the e16) for a lot of my controls. It requires more setup, but if saved into sound patches, they are ready to go when loaded. They work additively from where any parameter happens to be set. When changing patterns, it can be beneficial to reload the e16 page defaults where I have all those mods set to 0. That way they don’t jump from being higher values from the previous pattern. Replace 0 with 64 for parameters you want bipolar control over.

It’s not perfect, but there’s less jumping.

4 Likes

Looper is coming

6 Likes

very nice! I just bought a B-Stock E16 at a good price. Great to see such a useful update already!

2 Likes


5 Likes

Absolutely nuts that is :flushed:

1 Like

I’m completely brain dead when it comes to scripting. What cool things can you do with Lua? What could this addition add? I’m really sold on the looping so might order one tomorrow .

Sky’s the limit :stuck_out_tongue:
Mostly depends on what you get as script-accessible API ofc, there’s a link on the discord server to an API PDF

Can react to encoder events, send sysex etc, so seems geared towards making custom performance controls/macros

2 Likes

4 Likes

I’ve had a read through the Lua scripting doc.
At the end is an example “Yamaha TX81Z complete editor for OXI E16” which is pretty cool

Overall it looks like it can do most things you would hope/expect, respond to any changes on the device and send out whichever message you like, I’m not clear if it can listen to general messages from midi in (e.g. program changes or cc messages sent from other controllers) and respond to those, which would be cool. Currently I have a script running on a raspberry pi and it would be nice not to have to use that anymore

2 Likes

Anyone using this with Tonverk? Im failing to get any sort of response on TV.

Sending messages from TRS1 output. TV is set to receive Midi CC. Pretty sure ive set the encoder up properly on E16 but maybe not.

Any insights greatly appreciated!

EDIT: Then it worked, sort of, but now my track one is permanently silent and after a reboot of TV the controller no longer affects anything…

Yes, I posted my instdef above here

Works well, but there’s so many params you have to pick and choose to make it fit one definition!

2 Likes

Thanks!

I have a setup where MIDI notes (=drum triggers) plus tempo from my Stolperbeats go into the E16, and from there to my Syntakt. This works fine for say an hour, but then the tempo is no longer tight, and some notes are out of sync. Only remedy then is to restart the E16. This is really a bug problem in a live situation of course. Perhaps there is some kind of memory leak? I tested by unplugging the midi from the E16 and connecting the Stolperbeats to the Syntakt directly, all while still running. The sync problem was gone immediately, and returned as soon as I connected the m idi to the E16 again. Anybody else seen something like this?