Great tool!
Any chance of a volume control? I like to use the live play feature before export, with my hardware playing, and Loopseek is waaaaay louder than the hardware. Thanks.
1 Like
Thanks a lot. Sure, I can add that in one of the upcoming updates.
I’m not entirely sure what you mean by “louder than the hardware” though—could you clarify which hardware you’re referring to?
1 Like
I have my Elektron boxes, etc being monitored through Bitwig.
1 Like
Looking forward to picking this up! Looks perfect for tonal Multis.
Any plans for eldrum-friendly drum kit creation support/UI? Or tips on how to use it for that? Eg your UI is based aroudn sampling every x notes, but for drum machines one must pre define and sample specific midi notes corresponding to the connected vst/hardware midi mapping.
Simple use case would be round robin + a couple velocity layers (think a matrix of drum machine one shots) into the 8 subtracks, like is possible on MESET or Eldrum Creator web tool. Getting a straightforward 909 or Jomox or cr78 kit or whatever, or a velocity responsive Nord Drum kit.
Extended features would include fitting more than 8 sounds into 8 subtracks, so defining which notes when sampled should fit into which subtrack at which velocity level. For example lets say Low Tom, Mid Tom, and Hi Tom should fit into a single subtrack, spread evenly by velocity (0-42, 42-84, 84-127), or Closed Hat and Open Hat. (Also with RR, of course!) So maybe Subtrack 1 is just BD so simply hitting C1 8 times, but Subtrack 2 is Toms, so hitting C#1 (LT), D1 (MT), D#1 (HT) each 8 times and putting those into velocity layers.
Edge case extending the above logic would be building a „master“ drum kit where every velocity level within a subtrack is a different set of round robin samples. So, 127x8 RR kicks (subtrack 1 vel 1=909 kick x 8 RRs, subtrack 1 vel 2=808 kick x 8 RRs, …vel 3 = Jomox kick… and so on). Then subtrack 2 is 127x8 RR toms, subtrack 3 is 127x8 RR snares, etc. Would probably not be as many MB as one thinks as these oneshots are short.
3 Likes
thanks for the detailed input — really interesting use case.
The current workflow does work for drums, but there are two limitations at the moment: it samples contiguous notes (so skipping specific MIDI notes isn’t supported yet), and there’s no dedicated Eldrum export.
From a technical side this should be doable, it’s mainly a question of how to design it cleanly from a workflow/UX perspective. Predefined profiles could be a good way to handle this, but I’ll need to think a bit more about the best approach.
Appreciate the ideas — very helpful.
4 Likes
Not a bad thing by any means, but is this built with AI?
The website looks very much like the typical AI design patterns, which leads me to wonder if the plugin is too?
fair question.
First of all, it’s not a plugin — it’s a standalone desktop application.
It’s not “AI-generated software”, but AI was definitely part of the development process — like it is for most developers today.
I’ve used it quite a bit in certain areas, for example:
- helping with GUI work of the App (not my strongest area)
- a large part of the EXS reverse engineering
- and some implementation tasks and iterations
And yes — the website itself is largely AI-assisted. That’s just the most efficient way to do it today.
4 Likes
Visually, I do recognise some claude in there yeah. Indeed I don’t think it’s a bad thing per se. For paid software however, I do believe that at some point it should be transparent how much AI influenced or contributed to the build.
Don’t get time wrong it’s a skills to prompt and get the result you have in mind. But at the same time everyone is dropping html tools and for paid software it’s hard to know what it is you’re specifically paying for.
Any chance of some options re file name?
For example, the format preferred by the 1010 samplers is:
SampleName-Note-Vel
i.e. MoogBass-36-96.wav
You can try the Bento export, but you’ll need to delete the patch.xml, since I’m not sure if it’s identical between Bento and Blackbox.
Instead of something like name-c1-v110.wav, it switches to a format like name-36-110.wav when you select Bento export.
1 Like
Great, thanks 
This tool can do that part without any quirks.
https://www.bjoernbojahr.de/endlesswav.html
What that tool does not is the auto-find loop points 
Bento / Blackbox / Tangerine do not make any assumptions based on file names when the wav metadata are there. AFAIR that the first place that these devices’ firmware looks at.
Yup, well aware of Endless, I’ve been using it for years and it’s great.
This app however looks like a great solution for multi-sampling and I was simply looking to avoid an extra step in naming the files, and it turns out i didn’t need worry as the Bento output is fine, I’d just not thought to check that
Aware of that too, I was simply looking to maintain consistent filenames with my existing multisamples, which I now realise I can with the Bento output so we’re all good!
From my initial testing it looks like something I’ll definitely make use of so @metropolis_border will have another sale today…
2 Likes
Played around with the demo a little last night, and I think I’m going to buy it as it was very easy to take something I’d already multisampled with the Tonverk and add loop points to it.
Would a VST version in the future be possible? I use a lot of soft effects I’d like to sample as well, which I can do by sampling into the the Tonverk and then dropping the Tonverk folder into the program, but it would be nice to cut out the middle man.
1 Like
I haven’t tried but — you can add layers of vst’s
Maybe a synth and fx vst selected in loopseek will capture everything you want
1 Like
Bought it this morning. It’s brilliant for my needs and going to save me a LOAD of time prepping multis for my 1010 boxes (I have both Bitbox micro & V2 in my rack and a BlackBox on my desk).
Well done Jens, this is a very welcome addition to the tool chain!
3 Likes
I’m glad you find it useful — that was exactly the idea.
And yes, I can totally understand wanting to keep consistent file naming.
Great to hear.
Regarding a VST version: that’s not really planned at the moment, as it would require a pretty fundamental redesign of the app.
That said, there is a workaround depending on your setup. On macOS for example, you can use something like BlackHole and route your DAW’s output into LoopSeek via the hardware input. That way you can autosample the full signal — including VST instruments and any effects in the chain — though it would be in real time.
As for the dual layer feature in LoopSeek: the internal host is designed for instruments, not effects. If FX plugins show up in the list, that’s usually because they aren’t properly declared as effects in their plugin metadata.
2 Likes
Thanks a lot.
If you get a chance at some point, you could send me a zip folder of a few basic Blackbox multisamples — ideally one with loops, one with velocity layers, and one with simple one-shots. Just load them on the Blackbox and save them as-is so they include the default .xml.
Since Bento and Blackbox don’t differ that much, this could help me potentially add a proper Blackbox export in a future update. As I don’t own a Blackbox myself, it would probably involve a bit of back-and-forth testing.
Or does the Bento .xml Export works with the Blackbox?
2 Likes
xml is not guaranteed to be cross-compatible on 1010 devices. Not that it would not make any sense.
2 Likes
Yeah, it’s a bit unfortunate — it could be so much simpler.
But I guess it shows how difficult it is even within a single company to maintain a consistent format. So it’s not too surprising that there’s no real standard across different samplers.
The whole multisampling landscape is pretty fragmented. Historically that made sense, since a lot of it was early pioneering work and everyone built their own systems. But looking at it today, it does feel a bit outdated.