Free Tools for Tonverk: Multisample & Subtrack Building (Beta)

As @krunchr wrote. Logic or MainStage are great for creating multisamples with loop points and root notes from scratch.

If you’re on Mac, MainStage is a cheap option. On Windows, there’s SampleRobot — but it’s more expensive.

I also use Endless WAV quite a bit, though not for finding loops — more to double-check whether my app is writing the correct loop points.

By the way, the Multisample Architect also writes loop points and root notes into the WAV files — but of course, it can’t create them itself.

1 Like

Thanks for all the tips. I’m a Bitwig user and it comes with a great multisampler, but no autosampler (you can do something similar with some midi notes :stuck_out_tongue_closed_eyes:). I hope that the autosampler of the Tonverk gets better over time and that you can edit the multisamples on the TV itself. That’s why we buy this hardware to not mess about with software tools. I’ll keep using your very handy tool for all the old multi stuff that’s roaming about my internal memory on my Mac. Cheers.

Sure, no problem! I also have an older version of Bitwig, but when I used to make music on the computer, I mostly went for soft synths rather than multisamplers.

I also hope that the autosampler on the Tonverk will improve over time, but since it always creates just a single WAV file with trim points—no matter how many notes you record—I’m honestly not sure if the foundation is really there for much deeper editing in the future.

Maybe we’ll be able to fine-tune the start and end points of the samples, but I doubt there will be much more beyond that.

Finally had a chance to make a bunch of multisamples and this tool/thread has been a massive help to figure things out as I have never made multisamples before. I donated a few bucks for your efforts, thank you!

One thing that I noticed after making all of these multisamples is that the pitch/key center is off for each sample. For instance, I have a Bass Guitar multisample where the first note is F1, which should correspond to Pitch value 29 (assuming Middle C / C4 is 60) but the app generated it as 41 and then obviously went sequential after that. Maybe I should have uploaded a config file to make sure the values are correct but I figured it would just detect the pitch / octave # based on the naming convention. My naming convention is basically EB_SampleName_F1.wav (EB = Electric Bass).

What do you think of adding a Pitch field to the right of Note? So:
Original File / Note / Pitch / Prefix

Seems like there’s enough space in the UI for it.

Anyway, I adjusted the elmulti manually as I had to remove the loop info as well as change the pitch and everything worked wonderfully. I’ll figure out the loop info soon enough. :slight_smile:

Really wish Elektron would have made a guide for this from the get go. Mutlisamples are essential to this device and it really baffles me they didn’t give us any guidance for making our own from the start. Maybe they’ll have something with this next release.

Also, if anyone needs to quickly / easily rename stuff I can suggest Bulk Rename Utility (Windows). Makes things so much easier, especially if you need to use Regex to fine tune things. I’ve also attached a quick xlsx file of Key / Pitch Values and Velocity / Decimals that chatgpt graciously created for me.

Key Pitch Velo Deci.xlsx (11.9 KB)

Thanks!

1 Like

Thanks for your feedback and donation.
You mean it is 1 octave off for you?

This is because there are different middle c counting Systems.

For example:
Yamaha, Logic Pro, Elektron the middle c is c3
Roland, Ableton and Protools the middle c is c4

But I can add a manual note definition in one of the next updates.

2 Likes

Ahh hell, yup, 1 octave off. I didn’t realize Elektron middle c was c3. Shoulda looked for that from the get go. Thanks for the clarification!

No Problem at all. I will add the manual Note definition in one of the next Updates.

2 Likes

Awesome, maybe also a +/- next to Pitch to shift the numbers incrementally or by octave would be cool too.

I’ve updated the Multisample Architect — you can now switch between C3 = 60 and C4 = 60 MIDI note reference systems.

Using octave +/– would have been the wrong logic, since it’s really just the MIDI note assignment in the .elmulti file that adapts to the other system.

Manual note entry is also implemented now.

4 Likes

hi there, could you explain naming scheme for each sample pitch ?

1 Like

There is this ( i ) Button. in the header besides the App Name+version number:

If your samples don’t provide root notes in the smpl or inst chunks - each sample filename must include note information with a separator (dash, underscore, or space) — such as -C3- , _G#4_ , F5 , or C#4.wav (just one separator is needed before the file extension).

1 Like

hey thanks, i figured ! great tool :slight_smile:

1 Like

If i’m sampling a vst instrument , i just use my daw of choice Reaper and render the midi notes with the name to individual wave files, drop them into Multisample Architect and its done. Super fast, upload on to Tonverk. super fast, takes 50% less time then direct sampling.

1 Like

I’m glad to hear it’s helping you and saving time — that’s exactly the purpose of the app :slight_smile:

For me, the part that used to take the longest — getting normalized, trimmed, and seamlessly looped samples into Tonverk or OP-XY — has now become by far the quickest of all three steps:

  1. Sampling an instrument in Logic – depending on the synth and sound tweaking, about 10–15 minutes
  2. Multisample Architectless than 30 seconds
  3. Shaping the sound, fx and creating the preset in tonverk – around 10–15 minutes
3 Likes

Thank you for making this! I haven’t used it yet but I’m planning to try soon.

Does this part mean your software sets loop points or is that Logic’s job in the steps you listed?

No, Logic’s Auto Sampler takes care of the looping

1 Like

Does anyone know if Tonverk will reconize markers written in the smpl as loop points?

Logic’s Auto sampler is nice, but the rendering will take ages as it does not allow offline rendering.

https://www.bjoernbojahr.de/endlesswav.html

found this one for marking loop points, seems promising .

1 Like