Tonverk: bug reports

Yep. I said press the encoder (before turning it) to get senitones. ; )

In SRC page, when you turn encoder A, you can see the value. Set the value you want, then lock it to the trig with Trig + Encoder press.

1 Like

Picked up my Tonverk today, updated to 1.3.3, having lots of fun!

Hit my first crash!

While sampling, I cancelled the sampling process and then a second or so later I got the ā€œOops!ā€
Is there a way I can get more details to send Elektron? No screen full of numbers anymore!

In settings>system you can generate a diagnostics file to send them

2 Likes

just had one of these 5mins ago :upside_down_face: someone mentioned that when you don’t hear the short ā€œwhooshā€ in the TV’s output at startup → no sound. possibly true, pretty sure i noticed that happen once before. this bug happens to me on cca 1:20 boots.

1 Like

Alright I was adding some multisampled instruments with multiple layers and the Tonverk started to act out, at some point as I play the scale something happens and suddenly the Tonverk stops producing any sound at all.

No sound from wave tables or other patterns. Need to reboot it to get the sound back.

Looks like some kind of memory crash.

I see people talking about booting into no sound, but this is not the case, there is sound on boot, it ā€œbreaksā€ when playing a multisample.

Has other people experienced and -more importantly - reported this?

send the project/multisample to elektron to debug it.

i just noticed that the warble effect is only available on the master, when did this change or was it always like this?

The shape machine will randomly stop working, starts working again once turned on and off. When I bring the env back down to the middle the sound will come through again but the chops don’t register.

Yeah I reported something similar here

Glad I’m not alone! I can try to remember to report this later

Day 2! More bugs found in 1.3.3!

Can I join the beta testers?

Grainer in Sync mode:
load any sample, most easy to see with a long one, like a song length or a beat or something.
Set SPRD to 0.01
Set POS to 60
Set Density low, ~4-8
Size doesn’t matter but easiest to see with a longer size so you can see the grain stick around on screen, but short enough that it doesn’t move too far from its start point (turning down pitch really low helps with this).

With SPRD set to 0 it should play from a single position (60)
With SPRD set to 127 it should play from any random position in the file
With SPRD set to ~10-16 you should start to see the start point move by 1 pixel.

The problem is:
With SPRD set to 0.01 around 50% of the grains are emitted a long way before POS, with the distance determined by Density. (it never jumps forward, only backwards)

This only happens in Sync mode, Random gives you expected results (actually I didn’t test OSC mode).

Example video (no audio, just watch the grain positions, how they jump backwards depending on the density):

When spread is set very low I’d expect the grain spawn location to be very close to POS, but due to this behaviour it’s somewhat unusable if you want to spawn location to be in a small region.

2 Likes

It’s a buss and mix effect. It was always like this. There’s a list in the manual to show which are insert, send, buss and mix effects.

It might’ve always been like this but maybe it’s always been a bug ? Tracks losing their samples has always happened too .
Ideally it’s available on all tracks . ( though there is vibrato on audio channels )
Or maybe put a subtle lfo on delay time , that’ll do some weird pitch warbling

1 Like

It’s not a bug, it’s in the manual as a buss or mix effect.

Here:

So, I just tried loading 70 gigs of multi-instrument samples from Mars onto the Tonverk, thanks to the Convert with MOSS update. The Tonverk just can’t handle that much (and i have a really good sd card). It becomes completely unusable after 5 minutes. It lags like never before, there’s latency between hitting a key and hearing the note, and it can’t even switch sounds or machines anymore! No matter which sample or machine I select, it’s the same sound that keeps playing.

I sincerely hope Elektron isn’t pouring all its resources into the Overbridge update for the Tonverk just to release (and selling us) the Outbox 8. This machine needs to be stabilized, and above all, WE NEED INDEXES TO SORT MULTI-INSTRUMENTS BY MACHINE OR CATEGORY.

I still have 3 weeks to return the Tonverk to Thomann. I got it as B-stock for only €1000, which puts me in an uncomfortable spot, because I’m more in love with the idea of what the machine could be than with what it actually is.

6 Likes

its only got 8gig ram i think, so its never going to load 70gig.
a lot of multi’s in one list isnt good though, ive added a fair amount and its all in a weird order (not even alphabetical) … its a mess … so i agree, index/organisation does need to improve
i’m guessing if i move it all to my mac, then back again it might be displayed in alphabetical order… but i havent tried.
all this is before doing any preset / instrument saving , this is just dealing with multi’s that ive copied off max to sd card.
i think presets have a basic filter (drums / instruments?) … stil not ideal .

Agree 100% on indexing — that’s the real problem.

Small correction though: it’s 4GB RAM, and it’s a 4GB sample-memory limit per project, totally separate from SD storage. So the 70GB isn’t a RAM issue — you could have 1TB on the card and it shouldn’t lag, because unloaded samples don’t touch RAM or CPU. Storage ≠ playback.

The lag is the browsing/indexing choking on a huge library with no proper sorting — that’s software, so fixable. And the ā€œstuck sound, can’t switch machineā€ bug sounds like a software hang (Elektron’s release notes mention loading certain presets making the device unresponsive), not a RAM ceiling.

Either way we agree: proper category/machine indexes are badly needed.

6 Likes

Well , at least we can specify the names we want things to be … that wasn’t possible a while ago , on an actual piece of released hardware !! …

So I expect it’ll get better .

I’m tempted to delete all of the multisampled instruments in the factory content folder and just create my own from scratch with a consistent naming system so specific patches are easier to find in the single long list that’s the only option under the current OS. (I know there are tags for ā€œinstrumentsā€ and ā€œdrumsā€ in the current multisampled patch browser but that’s not much use TBH).

The lack of multisampled instrument tagging and sorting is a real weak spot right now.

4 Likes

please make sure to email this to elektron in case they dont see it here

1 Like