Tonverk: bug reports

Thanks for the infos :blush:!

1 Like

Thanks also for your response, I made a search in the manual and I found this Short cut:
[TRK] + [+]/[-] to transpose the current track up/down in semitones. So, no more complain on my side :slight_smile:

2 Likes

I noticed you can only seem to copy and paste modulation pages to the same page, i.e LFO one settings can’t be copied to LFO 2, only to itself.

Has this been raised here?

1 Like

I guess it should be better to precise it is possible to copy / paste to other tracks…but yes, should be possible to copy lfo1 to lfo2, and fx lfo1 to fx lfo2.

Maybe not enough…

1 Like

Didn’t know if I should post here or in tips and tricks. Both finally.

Velocity resolution is higher than 1/128, probably 1/256.

So theoretically you can use 256 velocity layers with subtracks and multi player. That’s the tip.

But it makes more complicated to set the layers because depending on eldrum or elmulti files you can have 2 layers with the same value.

I reported it…

Not yet! I’d love to be able to use them. It was removed from the manual though…

1 Like

yes exactly, that’s what I was trying to do, copy LFO 1 settings over to LFO 2 to make a subtle variation.

I think this was possible on DTII iirc.

1 Like

has anyone else had one of the bus sequences just kind of stop working (where most or all of the triggers seem to not trigger?)

  • I have a sequence on track 1 routed to track 9
  • track 9 has a bunch of trigs with +env for a gated rythm sort of thing, sounds cool when it works
  • occasionally after hitting stop (or double stop) the next time I play again the sequence does not play as programmed
  • restarting the Tonverk seems to restore the expected behaviour

Not sure if it’s LFO related or something else… quite a complicated pattern and not easy to reproduce

Is external MIDI velocity still broken? I have a MIDI keyboard connected, and no matter which velocity curve I pick the velocity is always fixed. With version 1.3.3.

When was it brocken ? Any link ?

Isn’t your midi kb velocity fixed ?

Midi velocity works fine… Check your keyboard or there is also a setting to ignore midi velocity in tonverk.

1 Like

In step edit mode, while I’m editing a trig with a chord containing D# note, pressing FUNC + Memorize also deletes D# note from the trig. Can anyone confirm?

Yes. @LyingDalai reported a few weeks ago.
Same with RECALL, not others.

1 Like

I’ve not read the full thread, as Tonverk has been pretty stable for the most part for me, but has anyone else had the issue of no sound upon boot? Reboot fixes it, but it’s happened a few times now. I’m on 1.3.something

1 Like

I use mine almost daily. It happened once maybe 4-5 months ago

2 Likes

Interesting.
Yes, I’ve had mine since launch and am happy with it, but it’s also fair to say I’m not a power user and don’t seem to have encountered half the issues other folk have.
It’s the first Elektron box I’ve been entirely happy with, and that is in spite of not producing anything that has wowed me with either grainer nor wavefinder

1.3.3 ? Several reports of no sound after boot before that OS…didn’t happen to me since iirc…

1 Like

I just fired it up to check, 1.3.2, I’ll get it upgraded and cross my fingers, thanks for the info.

1 Like

Thanks for verifying, it looks like at some point I set fixed velocity in firmware of the midi controller and I forgot about it. Cheers!

Thanks for these suggestions!
When I adjust ā€œtuneā€ knob + Function I can only get it to snap to different octaves and not semitones.

Not sure I get your workaround with parameters.

1 Like