In this topic, we’ll post all Tonverk Upgrades (major updates with new features added) and Updates (minor - major updates where the focus is generally on improvements, corrections, and implementation), as they arrive.
Tonverk 1.2.0 - December 17, 2025
We know Grainer, and the 1.1.0 OS that fixed the sync issues, are still fresh on the block, but we had some pretty neat dishes in the oven that didn’t quite make that release. So here is OS 1.2.0, a chance to put a few more little festive additions under the Tonverk tree. We’ve got new effects, even more options with the existing effects, a random mode for the arpeggiator, and some other little additions alongside further fixes and improvements.
Tonverk 1.0.2 is now available to download. This update addresses several bugs, including solving MIDI jitter issues over DIN, improving the audio/MIDI latency, and ensuring perform mode is activated correctly. The second part of correcting the MIDI jitter - tightening MIDI over USB - as well as further improvements, will arrive soon via a new OS.
Good to hear audio latency is finally acknowledged and seemingly improved. Looking forward to installing the update and trying TV out as part of a setup! Also encouraging to see there’s a thread now and a next update on the horizon, makes me optimistic.
Is there a target date for the ‘second part’? We’re all very excited to use our TV’s and I want to have mine be USB MIDI master for my setup so I’ll be looking forward very much to that update.
I’m also having hard time understanding that. At first it should have been in the 1.0.1 then 1.0.2 and now they are saying “next update”
It feels like there is not enough developers. There is no other updates for other devices AFAIK. Why is the development is so slow. It’s been few months already and we still don’t have the proper stable version. I would not call this version v1 even but here wr are.
I can’t believe that fundamental features such as copying patterns from project to project, naming multisamples, or the ability to save a project with all samples are still not possible. These aren’t quality of life features. Without these capabilities, it’s impossible to work with the device in a reasonable manner. Disappointing for me. We really need a statement here about what we can expect in the near future.
It seems the new behavior is that TV remembers if PERFORM mode was on or off when it was last shut down. It booted with it on the first time, which worried me, but then I turned it off, shut down, then booted again, and it stayed off.
It’s a new platform, dealing with latency is a complex task. I wouldn’t be surprised if they had every TV dev available working on the latency issue just to get this out. I imagine now the other outstanding bugs/quality of life improvements will come at a faster pace at this point.
@Elektron it would be super handy if you posted the release notes, instead of relying of users to do so. There is always room for improvement. Other than that - great news - still waiting for a Wavetable and Slice engine.