Tonverk Subtracks issue

Hi all,

I’m running into what seems like a serious issue with Subtracks on the Tonverk, and I’m trying to figure out if this is a bug or if I’m misunderstanding the workflow.

Here’s what I’m doing:
• I create a Subtracks instrument (drum kit) and load samples
• I save the instrument
• I save the project
• I power off the device
• After restarting, I load the same project

Expected behavior:
The Subtracks setup should be exactly as I left it.

Actual behavior:
The Subtracks are empty, and I have to manually reload the instrument again.

Important notes:
• This happens even when all 8 subtracks are filled
• The instrument shows as “NEW” even after loading a saved kit
• I am definitely saving the project before shutting down

This makes it very hard to rely on Subtracks in a real workflow, because the project doesn’t seem to recall the assigned instrument.

Is this a known issue?
Is there a specific step required to “bind” an instrument to a track that I might be missing?

Any clarification would be greatly appreciated, because right now this feels unreliable for actual use.

Thanks!

1 Like

Definitely not how it’s meant to work. Are you in the presets project? I seem to remember people having weird bugs only in there that went away when they created a new blank project.

The only other thing I can think of is if you accidentally hit memorize (func+D#) before you populated the samples and it is reloading that.

1 Like

Thanks for the reply, really appreciate it.

I’m definitely not in a preset project, I created a completely new one to rule that out. I also haven’t used any temp save (FUNC+YES), only proper project saves.

I did some more testing and something strange is happening:

  • When I load my saved Subtracks instrument (e.g. “PAKDRUMKIT3”), it briefly shows as loaded
  • But shortly after, the instrument name reverts back to “NEW”
  • From that point on, it seems like the track is no longer actually linked to the saved instrument

After saving the project and rebooting, the Subtracks are empty again.

So it looks like the instrument isn’t being “bound” to the track properly, even though it appears to load at first.

Have you (or anyone else) seen the instrument name reverting back to “NEW” like this? That seems to be the moment where things go wrong.

At this point it feels less like user error and more like a bug, but I’d love to hear if I’m missing something.

Is this happening on all tracks or just one of them?

A few including myself have had this happening on track 1 since the 1.3.0 update. Elektron are aware and a fix is coming on the next update.

Was happening to me when switching in and out of Perform Mode.

3 Likes

Good to know. I always use tracks 1-4 for tonal stuff and 5-8 for rhythmic stuff.

1 Like

AFAIK the bug im talking about only affects track 1 (but don’t quote me) so maybe log a support ticket?

1 Like

I’ve hardly used subtracks, so I haven’t experienced this problem. I find it really tedious to have to press the track number, then the subtrack number, and go to a page just to change one parameter. But I hope they fix it soon.

1 Like

It is a known issue, I’ve only used subtrack on one track and it disappers. I use it on Track 3.

1 Like

It happened to me on track 8 today.

2 Likes

It’s just one extra button press on changing any other track sound. Give them another go they’re a great tool.

Hi. I don’t deny that it can be powerful. I initially used them for percussion parts based on the frequency of the sounds, but there are several things I don’t like about them.
I can’t use a multimode filter to sweep a high-pass filter across an entire track with a single turn, for example.

There would be alternatives if I could choose multimode filters for effects tracks or buses. I haven’t tried linking the subtrack filters to a macro, but that would require an external controller.

Same problem here…subtrack not loading kit on track one…I have only 15% of the ram of the project free and it only happen on the 2 last patterns on 25 pattern total…midi is fine tho…