check your DM
1 Like
Round robin is the last thing missing, I can help with files if needed. LMK
It seems like it is possible since bruce released this exclusively for drums:
https://boorch.github.io/eldrum-builder/
Thank you again 
1 Like
In Multisample Architect - Round Robin was already implemented, and I’ve added it to Drum Constructor as well.
4 Likes
Thank you so much for this app… It’s added so much fun to the already very fun Tonverk
1 Like
More of a general question in regards to the TV and multisamples:
-
How much does a multisample instrument take up in terms of Mb space?
-
Are these samples compressed somehow into a proprietary format or just saved like wav.'s?
-
If I sample with the TV, are they saved on the SC card or is there internal memory on the machine where used samples are loaded?
Your welcome. I am glad you like it.
It depends on the multisample. If you load a multisample with just two notes at one second each, it’s only a few kilobytes. If you sample every second note, add velocity layers and round-robins, it can easily reach hundreds of megabytes. But even with a 64 GB SD card you’ll still have plenty of space.
Normal wav files - 48khz/24 is recommend.
It’s on the SD card. But when sampling on the Tonverk, you only get one single sample file that contains the start and end frame for each zone.
2 Likes
Alright, I see. Thanks for the explanation.
@metropolis_border - hey, it looks like the site is down and there is an error message saying that you have reached your usage limit. Happy to throw some dollars in for the fees if that would help! I imagine lots of folks would.
1 Like
Hi,
yes — the new links are above. I had to switch to GitHub Pages because Netlify has a very strange pricing policy. Now the apps are on GitHub Pages:
6 Likes
@metropolis_border First… thanks a ton for your hard work on these tools, they’re really useful and we all appreciate it a lot.
I was wondering if it would be possible to toggle a mode at least for the Multisample Architect that would generate both .preset and .elmulti files to the same folder to quickly deploy multisample sets that are ready to use on both the OP-XY and on Tonverk? Even if it means keeping 48k samples at 48k (I know space considerations matter on XY more than on TV) it is easier than managing separate trunks of the same multisample collections. Since you obviously use both devices, is there a problem that you’ve found with that approach to motivate having the 44k default rate in XY .preset generation and 48k when making Tonverk presets with .elmulti?
If nothing else, I guess it would mean users like me could just run it once per set instead of twice and save you some upstream compute costs.
Regarding 44.1 kHz on the OP-XY: this is actually a RAM limitation. The OP-XY only has 64 MB of RAM, and with 48khz multisamples you hit the limit very quickly. I know from other sound pack creators that packs made at 48 kHz caused a lot of problems, because once the RAM is full, multisamples either play back only partially or not at all. For this reason, I’ve kept my packs below 7 MB per preset from the very beginning.
Have you tested whether Tonverk and OP-XY are fine when the other device’s file format is also present in the same folder (i.e. .elmulti files on OP-XY or patch.json files on Tonverk)? If both devices simply ignore the unsupported format, this could work in principle — although I think using 48 kHz on the OP-XY is not a great long-term choice and every folder is then “.preset”
Regarding upstream compute: there is none. Everything runs locally in the browser / on the user’s machine — no data is uploaded.
Thanks for doing this! What do I have to do to make multisamples out of the Samples from Mars collection? When I load the samples everything looks fine, Tonverk recognizes the multisample but I get a “sample error” when I try to load. I tried restarting.
It’s hard to diagnose this without seeing the actual samples, so from a distance it’s basically guesswork.
In general, Multisample Architect expects clean, consistent material:
stereo samples, with embedded root note information and proper loop points.
With Samples from Mars it can get sometimes a bit tricky, because their packs are often mixed. I’ve seen collections where:
• some files have loop points and others don’t (inside the Multisample)
• metadata is inconsistent or missing
That can easily lead to a “sample error”, even if Tonverk recognizes the multisample structure itself.
As a quick test, I would suggest trying to load just a Multisample as a one-shot multisample. If that works, then the issue is almost certainly with the format or metadata of the Samples from Mars files.
You can also inspect your multisamples with a tool like “Endless Wav”.
When you open one WAV file from a multisample there, it will show you the entire multisample set: whether it has any embedded metadata at all, and if so, all the other WAV files that belong to it, including their root notes and loop information.
2 Likes
I can confirm that. When it comes to drum samples from TR machines, Samples from Mars are hard to beat, but most of their multisamples are a bit chaotic in terms of metadata. It’s not the best source for creating own multis for TV.
1 Like
Thank you!
I’ve just come up with the perfect way for me personally to build drum kits with multi sampler. Can I do that with this tool?
Idea is:
- I choose say eight favorite hat sounds. And record 16 variations of each of these.
- I then assign one of these hat sounds to each of the eight white keys in a multi sample preset (choosing the 0 octave).
- Each of these eight sounds has 16 variations that are velocity layers.
- I can then perform with the variations by using the velocitx knob or assigning random velocities
- I would choose another octave and assign eight of the variations to the keys there, so I have the option to live drum the variations instead of having to program/perform them with velocity
3 Likes
In theory, that could work if you export them as multisamples in one-shot mode.
1 Like
Thanks, that’s good news! I assume it will be obvious how to do this once I start using the tool?
I think it mainly comes down to preparation (root note naming for hi-hats, kicks, and so on). In your case, I’d start with a small selection and test whether it works the way you expect, before doing a lot of prep work. That way you avoid investing a ton of time only to find out that something doesn’t behave as expected — especially since features like velocity layers are still in an alpha/beta state.
1 Like
A common (incorrect) msg is:
No loop points found in any sample. One-shot mode will be used.
Here’s the file. It has clear loop points (confirmed with Adobe Audition and Endless WAV). maybe it helps troubleshooting.