Pulling my hair out trying to get the OXI 16 to control the Tonverk

Elektron Gear Tonverk
1

Pulling my hair out trying to get the OXI 16 to control the Tonverk.

Can anyone help or share any tips with me. Or any obvious road block s they faced?

Currently outputting from trs1 on the oxi 16 to the midi in of the TV.

Channel one, auto channel off. Looking just to get a track level working… But every thing I’ve tried won’t work.

Fader fox pc4 (which I use for my octatrack) tested with same cables confirmed working with the same cc’s etc…

I’m running out of ideas!

The Oxi e16 with 1010 bento and Ableton both with usb and trs work perfectly…

Am I being a bafoon?

2

I think the pc4 uses trs type B cables and the Oxi uses type A, could that be it?

3

Ive tried three different cables, and the USBC. Not sure if thery’re a or b… gonna keep at it.

4

Also, the cable which i use for the faderfox worked, with the pc4 to the TV. so must be comatible with b if it is b…

1 Like
5

It’s type a, check e16 thread. Or new manual on oxi website

1 Like
6

My Neuzeit Drop works with type A cable (no luck connecting it via usb so far but it works via din so all good).

Some of the Cc destinations don’t work properly at this time. Track level does respond though.

Have you got the receive CC box checked on TV?

7

I’ve managed to get my Faderfox PC4 which was configured to work with my octatrack to work with the Tonverk. I just added a second page and entered the TV cc’s and all is good for levels, a filter and a send per track (8 tracks)

The strange thing was, I have two Fader fox PC4’s. One works flawlessly with the TV, the other doesn’t. I’ve copied the settings from the octatrack to the other, changed the midi merge - usb -midi-midi etc. But cant get the second Faderfox to work.

I even downgraded the firmware on the second faderfox as it was newer. The original faderfox was never updated or had any settings changed, it just worked out the box with the octa.

Factory reset of the second faderfox didn’t seem to do anything ether. I wish there was a way to check the merge / global midi settings.

I don’t want to mess with the first one’s global/midi as it’s essential for my octatrack.

The E16,… I think I’m going to have to buy a dedicated a to b cable or vise versa… My brain is so fried now I can’t remember. (and have a refresher look at the OXI forum as suggested.)

Fresh day tomorrow with a clear head after a good sleep should clear things up.

Massively confusing and all over the place, but I have a working set up for now, and the TV is excellent.

Thank’s for all the comments and support so far. Please let me know if anyone has any more ideas from the fragmented and demented info I’ve given so far :joy:

1 Like
8

Yes.

9

Here’s a video if anyone want’s to take a look. More focus on getting the faderfox configured now, as I’ve ordered the correct cable for the E16.

10

Hi,
I am running into the same problems,
Did you find a solution yet?
All the best … marian

11

I was just having the same issue but it looks like it’s a Tonverk E16 USB issue.

I don’t think the Tonverk acts as a USB host so it’s likely not designed to work with the E16 like this, which is a shame. A single cable setup would be fantastic.

Din works fine for me, But make sure you have a type A adaptor. (first time I was using the wrong adaptor and thought it wasn’t working at all)

The page settings slipped me up with my first attempts. Theres also a setting to turn off that was silencing everything on scene opening (transmit params).

12

Be aware there are some known bugs. I was having trouble with my E16 and Elektron support confirmed that at least the new Wavefinder machine type wasn’t processing MIDI correctly.

13

CCs just not implemented for Wavefinder on 1.30.
This is not a bug.

14

in 1.31 :raised_hands:

The Wavefinder SRC machine’s parameters did not have any MIDI CC mappings.

1 Like
15

No offense @sezare56, but even Elektron called it a bug.

Release notes for 1.3.1 (which just came out today):
" Bug fixes

The Wavefinder SRC machine’s parameters did not have any MIDI CC mappings."

1 Like
16

Ok ! :content:
But I’d rather consider it just like something missing, not buggy.
An improvement.

(Btw in the beta release notes it was presented as an improvement, not a bug.)