V1.1.0 I’ve tried to change the TV pattern via midi by sending bank and program change messages. This is not working, I tried sending from DAW and from a hardware sequencer. This also did not work in last firmware.
My current setup includes a lot of devices: 8 devices from Elektron, 1010music bluebox, Faderfox pc 12. The MIDI connections are wild—logical to me, but when I explain how everything is connected, everyone rolls their eyes…
There is NO audible latency, except for the Tonverk. The sound from the Tonverk reliably and confidently arrives 10 ms later than everything else.
I haven’t noticed any fluctuations lately, but I haven’t had much time over the last few days – it would be a bigger topic here in the forum if there were still a problem.
A latency of 5ms is usually negligible—most people won’t notice it.
From ~9ms onwards, it becomes annoying.
Let’s have a little lesson 
-It’s best to listen loudly and sit in the stereo triangle. At 230 km/h on the highway, it doesn’t matter.
0ms:
2ms:
5ms:
10ms:
20ms:
You’ll notice that with claps, it’s relatively unimportant. With two kicks on top of each other, it becomes problematic.
If you’re a (vinyl) DJ, you always want to push one after the other with two devices.
If you’re not, it just sounds very messy.
And the groove can quickly be ruined.
Seen this way:
It is a problem. It shouldn’t be. Elektron will fix it.
5 Likes
Thanks for the examples. Yes, that is quite noticable.
Likewise, only the Tonverk has latency and therefore cannot be synchronized as a slave in my setup 
It’s been three months and I’m going to have to wait another 30 days.
2 Likes
I came here just to see where they are with the sync issues.
I was anticipating a Torso S-4 competitor from this device and we can confidently say, it’s here.
But the sync and crash issues on launch were intolerable.
They have to solve for this, man. I think a lot of artist are on the fence of re-purchasing or becoming first-time owners over this recurring issue alone.
Elektron makes it super clear what the situation is and how things will move forward. They also explained how this error occurred, apologised for it, and presented a roadmap.
It’s a shame that it gets lost among all the other repetitive complaints. But, let’s be honest, massive complaining won’t change anything or make things happen any quicker.
I’m sure the developers at Elektron put a lot of time into making sure we can make music.
No one has to buy the Tonverk and then be annoyed that it doesn’t work perfectly yet. There are other great devices for making music too.
Most of the bugs have already been fixed, and it’s only a matter of time before the current ones are sorted too.
If, for some unlikely reason, we can’t get rid of the latency:
The machine runs smoothly otherwise, so a MIDI shifter is a good idea.
It’s a great device on its own.
And the best thing is that we can be sure that lots more great improvements are on their way. Elektron doesn’t usually just abandoned a device that’s almost finished, and launch a new product on the market instead.
The only failure in the company’s history was the battery handle. It was a pretty cool idea, but honestly, who really needs a handle with a battery?
1 Like
It seems that PROB + COND logic is still broken. Although I didn’t test it in a fresh project. Let’s hope it gets addressed in the next patch. 
1 Like
Still seems to be issues with clearing lock and note trigs on sub tracks. I’m trying to clear out a sub track for reuse as I have resampled it, but locks and notes are still happening.
I also have a weird blue trig. A note is playing here but I can’t make it light red or not light at all.
2 Likes
I still wonder who approved this machine (Tonverk) before releasing it and putting it on sale with so many bugs. It took me two minutes to realize there were bugs and three minutes to understand that it was a problem. Why release a machine with so many bugs?
1 Like
Further to my blue trig issue above. Trig 1 now lights up a different shade of blue when it should be white, green when it should be yellow and not at all when it should be red. This is on a new project. I have logged a ticket with Elektron support.
2 Likes
see:
https://www.elektronauts.com/t/introducing-tonverk/237997/3861
…
Despite extensive pre-launch testing that we conduct for all products, sometimes critical bugs only surface at or just after release. In Tonverk’s case, a late-stage optimisation introduced side effects that caused the jitter and some other unexpected issues. Tonverk is unlike anything we’ve built before, and launching on a completely new platform means treading new ground in many ways. As a result, solutions to problems are rarely straightforward.
Nevertheless, we want to say sorry for the rough edges some of you have encountered early on. We’ve navigated one or two of these moments before - stress dreams from the Octatrack and Digitakt launches spring to mind - but it’s very much an Elektron trait to turn such challenges into epic journeys not defined by their beginning. We’re confident the issues on Tonverk will be fully resolved very soon, and that its own adventure is only just beginning.
…
3 Likes
I also have the red LED channel not working on step 7, so I’m not sure if it’s a hardware fault or a software bug.
Minor bug with track 6 level.
I have the Tonverk paired with a faderfox pc4 controller. Track 6 level (cc95) suddenly became unresponsive to both the controller and to the Tonverk’s knobs. I had to restart.
looks like your red led died because yellow = green + red. hopefully it’s a software glitch
1 Like
I hope so for those affected. Since Elektron tweaked the LED control in the last update, there is at least a small chance that it is just a bug.
1 Like
I tried recording unquantised, with a fast keyboard riff. The resolution recorded turned out low & steppy that it did not capture the notes properly, Is this a feature (read: limitation), a bug or I don’t know the procedure for this.