Free Tools for Tonverk: Multisample & Subtrack Building (new links)

I think it has something to do with the fact that it’s a mono sample. So far, MS Architect can only handle stereo files. I’ll have to see when I can get around to integrating support for that. As a workaround, you could try converting it to stereo in the meantime. But in this case I have no clue if this really works…

1 Like

@metropolis_border thank you so much for these cool tools been having a blast with them!

I might have found a bug;

-velocity+ mode does not load on the tv with 127 samples per slot, only loads upto 126. If 127 samples are loaded in a slot it exports fine but gives some sample error on tv. If this is the case maybe you could reduce the limit to 126

Thanks again for these tools! \m/

1 Like

Thanks for the synth ideas, food for thought. Love the idea of Cascadia!

1 Like

Good catch. I guess it has something to do with the counting? maybe tv counts v0-126?
I Try to fix this and the (not loading mono files with loop points) this weekend.

1 Like

Seems so, slots 0 and 1 play the same sample

1 Like

You can do this with eldrum or elmulti format.

I have 2 eldrum kits I made that 8 sounds (1 for each subtrack), and for each sound there are 4 velocity layers and for each velocity layer 4 round robins roughly. It’s around 120 samples for the kit. With the velocity layers you can actually nest different sounds, so on 1 subtrack you could have a velocity layer containing your open hats and a different one containing your closed hats. This is the most effective way to do a choke group on the tonverk but it’s a pain to set up with new kits/sounds. But it also allows you to have more than 8 sounds on a subtrack.

Elmulti is great for drums too and you can do all the same stuff.

2 Likes

I‘ve since done it with eldrum and described the process for those who are interested and haven’t done it yet:

It didn’t work with the elmulti tool because that one always tried to map the samples to notes and pitched them. The interface also wasn’t built to do what I found immediately in eldrum creator.

v0.78 – Multisample Architect: Mono samples are now detected as well, but they are written as stereo during export.

v0.73 – Kit Constructor: 126 samples per slot instead of 127, as 126 appears to be the maximum supported.

9 Likes

Question: After adding multis sampled wav files onto the tool, how do I upload this into the Tonverk and have it selectable as an Instrument in the Multi Sample Menu? I’ve tried creating a zip file and copying and unziping it into the User/Multisample directory.

There needs to be a folder in the „user“ folder that contains the .elmulti file and the .wav file. Just drag and drop the unzipped folder. Then wait for a while after booting up TV until the symbol in the upper left corner stops spinning. Now you‘ll find the instrument in the „multisampler“ menu at the bottom.

Edit: if it still doesn’t work, try putting it into the „multisampled instruments“ sub folder. That’s where everything I sampled onboard landed.

1 Like

I’d recommend saving multis in the User/Multi-sampled instruments folder from the start. That’s the official location, and who knows what side effects there might be if you don’t save them there.

I discovered by chance that the TV actually finds user multis even when they’re in the Elektron folder. Perhaps that’s one of the reasons why it takes so long to index the sample list: It scans the entire SD card.

1 Like

I can now see it under intruments however, I’m getting the error “Failed to load instruments Multi Player Sampler Error”. Does it need to be converted into any particular audio format? I’ve tried 44.1 khz/16 bit and 48 khz/24bit. For reference, I’m attempting to load the free multi sample from Samples from Mars and in particular the SEM Sync Multisamples from here.

Example for sample filename “SEM Sync A#1.wav” which looks a little different from the factory multisample name, i.e. “Rubber Bass-000-042-f#1.wav”

That shouldn’t matter. I have many multisamples in this format and they work fine (e.g. name f#1.wav).

My best advice would be to check the files in the free app Endless Wave. If you open one sample from the folder, it will show all samples in that folder, so you can verify whether they have loop points, correct root notes, and so on.

I’ve had multisamples from Samples From Mars where only half of the files contained loop points, while the others didn’t. MS Architect just works with wav files with embedded Loop points. Otherwise you have to choose the one shot mode.

1 Like

Thanks @metropolis_border that worked, there were no loop points in the samples

1 Like

Blockquote

Does your tool also export just one single sample file? Would it be possible to add that as a feature, like creating a tonverk native style long chained multisample single file?

I’d like to create a clean “master project” with all of my favorite multisamples loaded in and I’m worried about maxing out the sample slot limit of 1073. It also would just look way cleaner and be way easier to navigate the project pool if multis aren’t occupying dozens or hundreds of slots.

Or maybe I misunderstand and there are some drawbacks to doing this like it prevents round robins or something.

I tried vibe coding a tool today that consolidates existing elmultis + folder of associated samples into a single autosampler style wav+elmulti. Didn’t with the first time but these things rarely do. Will try to troubleshoot. But I figure this is a better feature built into your tool than as a separate utility

I’m not sure what the .elmulti file is supposed to look like in this case. The format and Tonverk are extremely picky — even one blank line too many or too few can break the file.

Maybe I can find a way, but this will take some time.

Since i’m probably not knowledgeable enough to triage exactly why an elmulti file has broken / why TV wont read it properly, I’m not sure how to iterate other than with brute force via claude code - TV doesnt export logs of why it cant read a file, and I dont have the willpower to investigate and understand these files line by line manually (major appreciation to those of you who do!)

If i happen to crack it with vibecoding I’m happy to try and export something useful either as requirements documentation or code, that you can build off of / integrate into yours.

Looks like this :

Auto sampler - 16 x 4s notes

ELEKTRON MULTI-SAMPLE MAPPING FORMAT

version = 0
name = ‘CHROMACOMB3’

[[key-zones]]
pitch = 60
key-center = 60.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 988
trim-end = 192988

[[key-zones]]
pitch = 63
key-center = 63.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 192988
trim-end = 385500

[[key-zones]]
pitch = 66
key-center = 66.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 385500
trim-end = 578012

[[key-zones]]
pitch = 69
key-center = 69.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 578012
trim-end = 770524

[[key-zones]]
pitch = 72
key-center = 72.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 770524
trim-end = 963036

[[key-zones]]
pitch = 75
key-center = 75.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 963036
trim-end = 1155548

[[key-zones]]
pitch = 78
key-center = 78.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 1155548
trim-end = 1348060

[[key-zones]]
pitch = 81
key-center = 81.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 1348060
trim-end = 1540572

[[key-zones]]
pitch = 84
key-center = 84.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 1540572
trim-end = 1733084

[[key-zones]]
pitch = 87
key-center = 87.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 1733084
trim-end = 1925596

[[key-zones]]
pitch = 90
key-center = 90.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 1925596
trim-end = 2118108

[[key-zones]]
pitch = 93
key-center = 93.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 2118108
trim-end = 2310620

[[key-zones]]
pitch = 96
key-center = 96.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 2310620
trim-end = 2503132

[[key-zones]]
pitch = 99
key-center = 99.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 2503132
trim-end = 2695644

[[key-zones]]
pitch = 102
key-center = 102.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 2695644
trim-end = 2888156

[[key-zones]]
pitch = 105
key-center = 105.0

[[key-zones.velocity-layers]]
velocity = 0.9960785
strategy = ‘Forward’

[[key-zones.velocity-layers.sample-slots]]
sample = ‘CHROMACOMB3.wav’
trim-start = 2888156

IIRC I didn’t use latency compensation nor release time. Silces don’t last 4s but 512 or something samples are added…

Yes, I know the format from the auto sampler itself. But I think the main issue is figuring out where things like loop points and velocity layers need to be placed in this trim .elmulti — unless I’m missing something.

Or @fffiiissshhh you just talking about one-shots? In that case, it shouldn’t be that difficult (at least in theory).

2 Likes