OS Update: Tonverk 1.0.1

I still have the bug on loading certain samples in wav format. Some samples do not want to load even though they work perfectly on the digitakt 2.

1 Like

Works fine here in a couple of patterns, which machine / trig type you using?

I updated, and
MIDI SYNC still isn’t working.
The Tonverk as MIDI IN slave has a slight latency with my Digiton II.
The Tonverk as MIDI OUT master causes the bpm of my Digitone II and Octatrack MKII, which are slaves, to go off-kilter; it varies between 100 and 300 bpm.
I just restarted the machines; the bpm is stable, but there’s a slight latency with my Digiton II and Octatrack MKII.
So there’s a latency in MIDI IN and now a latency in MIDI OUT that wasn’t there before.

1 Like

Transfer dynamically converts the audio files to the correct format that the Digitakt / Digitakt II expects.

As Tonverk is dealing with the sample as it is, it likely is in an unsupported format, or has unusual wav chunk sections present that it doesn’t understand - have you tried converting the non-working files to 48kHz 16/24/32 bit?

1 Like

It says in the notes and the posts that this update does NOT fix the midi issue, that will be in the next update in October.

2 Likes

Did you read the release notes or announcement details ?

I guess not

6 Likes

Soon October, in a few days…

No, I haven’t tried converting because there are thousands of them; it would take too long.
It’s still strange not to be able to recognize a wave file. My computer does it just fine…

Yes but obviously it will not be at the start of October, they literally just put out an update today… Expect the end of October if they make it.

2 Likes

the large amount of bugs they have fixed is concerning…they really rushed to get TV out…

pressure from Roland and Akai of course…

1 Like

meh i dont care for conspiracy theories but glad they’re squashing stuff
unfortunately market timing is a thing, i think strategically they timed it well

remember the a4 mk1 came out and the +drive wasn’t even enabled. take that in for a second. they have come a long way and will continue to improve, and eventually i bet the price of the TV goes up, like most other boxes as more $ and dev is poured into it so i wouldn’t mind getting it now at these prices

2 Likes

Or they only work on MIDI for a few days and send us a new OS at the end of the week so we can synchronize and integrate the Tonverk into the setup :))))

I have definitely got 1st trigs working on a single sample machine.

Optimistic, but unlikely!

Just want to say thanks for the update guys. Really enjoying the new machine. It’s really amazing.

Thanks for all your hard work.

5 Likes

Yes, I don’t think that we got to wait latency like on DT2, or DN2.

I’ve played a lot with RT kernel + jackd(as more stable audio framework) on RPi5(ARM platform too) for different purposes, with own builded RT kernel and optimised Linux env, but I never got audio loop better than 8ms(with overwitch or or some jackd clients like usb audio emulated device to connect to iPad as host), in fact 8ms was a best result without xruns.

But it’s acceptable for me.

5 Likes

You’re right, deleted my post.

1 Like

a good list of updates there and nice to know the midi timing fixes are in the works, thanks Elektron.

I think TV is going to turn into something special thru its course of updates.

The latency of the MPC is also about 8 ms. I dont know which kernel they did use.

2 Likes

same, can confirm. very surprising.

That´s the stuff i´d expected to be solved first bevore anything else.