Sure, that’s your prerogative, but it doesn’t change my position.
Let me fix that for you:
To say otherwise is to deny the validity of what’s reported daily in the bug reports thread, and rarely are the complaints duplicates.
This isn’t about prerogatives; this can be objectively established.
What are some of the bugs you encounter most often yourself, ones that hinder your workflow?
Here’s a slightly different take. You should start with the ST. And upgrade the TV later. If you start with the TV, you might get spoiled.
The routing and FX on the TV are incredible. The possibilities feel endless.
So going from the TV to the ST could be a little bit of a disappointment in the future.
The ST is not disappointing. It’s awesome. But you might set your expectations a little high if you start with the TV.
And I don’t experience a lot of bugs with the TV
Cute, still doesn’t change my experience, and my use case.
Keep fixing!
about Tonverk bugs : there are bugs but nothing that prevent making music. I’m 100% confident Elektron team will fix everything as soon as possible and add features and machines.
Starting with Tonverk now is the best move because :
- The price won’t go down
- You start with the almost 1.0 feature set, you can consolidate the knowledge of actual features before they add more
- Bugs will tends to be fixed
- Better hardware in Tonverk, better layout of buttons.
Just curious : how long do you own a Tonverk?
Around 3 months, regardless my opinion, is based on the current state; anything else would be pointless.
With all due respect this is not true at all!
It’s incredibly buggy.
Just this evening I have had:
-
Loaded my project to get it sounding driven and distorted at twice the volume it should be (restart unit)
-
Had hanging retrigs that sustain for ages and ages
-
Been locked in a project creation screen I didn’t initiate and can’t get out of (restart unit)
Not saying it’s unusable but stating it’s stable just… wow. It’s the most unstable thing I’ve ever used! Not stable in the slightest???. ![]()
That may be your experience, but it hasn’t been mine. I haven’t encountered any of the issues you’re referring to.
In general, we all form our opinions based on our own experiences and points of reference — that’s simply human nature.
From my experience, and from what others report as well, we’re not seeing the level of bugs you describe. That’s why we consider the TV to be quite stable rather than buggy.
Of course, your experience appears to be different, and that naturally leads to a different opinion.
Can you send your unit to Elektron to extract it’s DNA?
No word of a lie I’ve had to restart mine one more time since my comment 12 minutes ago. It randomly started outputting no sounds whatsoever.
oof! that sounds bad. I assume you’re on latest firmware. can I ask how long you’ve had it and whether you’ve tried any specific trouble shooting like replacing the sd card or anything?
Had it since December time.
These are well known to be very buggy and temperamental units mate.
Not unusable but more bugs than you can count at present. There’s nothing wrong with mine, it’s just how these are. Buggiest thing I’ve ever seen.
It sounds amazing though!!!
As I mentioned, that hasn’t been my experience, and clearly not everyone else’s either. If the TVs were randomly restarting (or need of) for everyone, they would of course be returned.
You might want to try replacing the SD card and also make sure the power supply is stable.
I have also not really encounted any show stopping bugs. The only things that I have noticed are related to Super/Subtracks trigs.
I also had one occurence of a Subtrack not making any sound after a pattern copy, which a restart fixed.
Otherwise, it’s definitely never frozen on me.
I wonder if the new storage/file system is causing some people’s unit to freeze. Almost as if Tonverk could use a Copy All and Save function, like in Ableton. Although, that would fill up the SD pretty quick.
If my Tonverk was freezing, the first thing I’d do is format the SD Card.
My literal point was to underscore the highly subjective frame your position was being positioned from, and strike a more objective accord between your experience, and those being reported.
It’s fine you have no issues, but to say the Tonverk isn’t buggy is just factually incorrect. Rather, you aren’t experiencing the bugs, which again is fine, but when speaking to prospective purchasers trying to assess the current state of the machine such statements are… misleading at best.
If you disagree then…
A) Your version of the software is somehow magically different than the same firmware being run by those reporting issues,
B) They’re lying.
C) The issues come from hardware defects your machine hasn’t succumbed to, or
D) You have a workflow that precludes hitting, or minimizes notice of, the bugs.
A and B seem implausible, and C would be just as bad for a prospective purchaser. Since C would be a nightmare, I’m left to conclude D.
It look like very buggy in comparison of mine and other. I think you have something went wrong, maybe corrupted samples or bad format or buggy project from 1.0 ?
I think for most people, the thing just work as excepted, encountering some minor bug from time to time, nothing that can transform it in ‘the buggiest thing’
But everything I’ve reported has been corroborated by many many other people on this very forum every time I’ve mentioned anything.
I’d genuinely love to know how many people on this forum think their Tonverks are working as expected.
I find your position perplexing.
Let me give you an analogy:
We both go to the store and purchase a copy of Italo Calvino’s new novel If On A Winters Night, A Traveler, and proceed to skim through. I read every third page, you read every tenth. I say “hey, there’s a great bit with a dog,” but you retort “there is no dog in that book, I think you’re wrong.”
We have the same book. Your experience does not trump the reality of another, so if somebody says they experienced X then accept that X is in there since, by nature, we have the same book (and workflow differences amount to us not reading every page).
This of course cuts both ways, something anyone with experience in systematic troubleshooting understands.
Unless a bug can be consistently reproduced and external variables have been ruled out, there’s no solid evidence that it’s a system-wide issue affecting all machines.
Very few people on this forum seem able to provide meaningful data points when reporting problems. Just recently, in another thread, several users repeated claims of 10 ms MIDI latency, yet without offering any details about their system, signal chain, or even how the latency was measured.
I don’t have a magical machine, and I’m not suggesting that none of the reported bugs/issues are not real. However, I’m also not convinced that every issue mentioned here represents a genuine system-wide bug. In many cases, the problems are likely dependent on external factors and specific use cases.