So, I know that is currently no way of setting loop points on Multi-Player instruments from TV. But, I have noticed that some of the factory Multi-Player instruments have a looping stage. I also remember seeing a story from Cuckoo in which he is showing some way of editing .elmulti files in order to set loop points.
Has anyone experimented with this?
I have a lot of multi-sampled instruments that are screaming for loop points 
I never had automated multisamplers before bento and Tonverk and was somewhat rudely surprised by the management overhead. The following steps are much more seamless when you generate multisamples from a DAW environment like Logic to be used in the DAW’s sampler but until TV implements a way to detect and set the loop points on device after you collect the sample data (MPC and Maschine give you this so there’s a reason to think it might come), this is the process. It kind of sucks honestly.
Here is an example of what loop data gets added to your .elmulti for each note. I rendered this one using the Multisample Architect tool with an already existing set of SFM multisamples that had the loop data (start/stop) already set in the .wav metadata. The TV autosampler doesn’t generate loop data or have that in its .wav file metadata so presently you would have to export the folder of .wav for that multisample instrument, process it with a DAW or Endless Wave or some other software/script to detect and add loop zones to the wav metadata, then generate an .elmulti file where those loop zones are listed alongside each note. I don’t know for a fact that TV needs the loop data in the multisample .wav or if it’s sufficient to have it in the .elmulti only but most multi samplers use a SMPL chunk of metadata that has sections for loop start and stop and loop mode.
The fastest way I could currently think of is if you have a solid algorithm to autodetect the loop points and crossfade data non-interactively, writing a script to do that directly on the TV multisamples in SD reader mode and update the elmulti file per note there could be a somewhat fast and painless way to go but might result in clicky loops. I’ve experimented with a python algorithm for this but haven’t had the time to get it right.
[[key-zones]]
pitch = 31
key-center = 31.0
[[key-zones.velocity-layers]]
velocity = 0.49411765
strategy = 'Forward'
[[key-zones.velocity-layers.sample-slots]]
sample = 'Dirty and Sick Micromoog G0.wav'
# add the below loop data
loop-mode = 'Forward'
loop-start = 53479
loop-end = 120483
loop-crossfade = 32
keep-looping-on-release = true
[[key-zones]]
pitch = 32
key-center = 32.0
[[key-zones.velocity-layers]]
velocity = 0.49411765
strategy = 'Forward'
[[key-zones.velocity-layers.sample-slots]]
sample = 'Dirty and Sick Micromoog G#0.wav'
# add the below loop data
loop-mode = 'Forward'
loop-start = 82514
loop-end = 131575
loop-crossfade = 32
keep-looping-on-release = true
2 Likes
Thank you for the very detailed answer!
I think I will try with the fast way first, making per-note edits in .elmulti file.
But I imagine that this way will require a lot of trial and error until getting those loop values right for the specific samples.
Maybe this will be an easier process with future FWs, considering that the TV auto-sampler already lets you specify the release time for the samples.
as a proof of concept make a multisample instrument with only like 5 notes of 3 second samples, then pick the same 1 second interval of sample numbers to set on all of them. You can take these numbers and it should work.
loop-mode = ‘Forward’
loop-start = 48001
loop-end = 96002
loop-crossfade = 32
keep-looping-on-release = true
See if adding that to each note works and if so, you know that just updating the elmulti works.
Otherwise, you can just batch-process the folders in the logic autosampler and use its loop point detector and update the metadata that way and see if TV respects the loop points without editing the elmulti.
2 Likes
I had a look at this before and came to the conclusion, for now, that it’s better to have loop points in the WAV files rather than in the .elmulti file. There’s no way of finding good-sounding loop points in Tonverk itself, even with crossfade, and editing the file by hand is more miss than hit. So I’m starting to play with free external tools like Endless WAV, and not bothering with specifying loop points in the .elmulti file.
4 Likes
Yes I returned my Tonverk to Sweetwater as soon as I discovered there was no way on board to set multi sample instrument loop points on the device itself … I wouldn’t even mind doing it manually, like on an old school sampler.
But absolutely no loop editing on multi samples was a hard pass for me…. Straight back to the Elektron dealer.
Try to DiscoDSP Bliss, sample as you wish, export to *.sfz copy all files on a tonverk and voilà, all multisamples on loop for infinite…its very simple and easy to do, One more think (reedited) use Convertwithmoss to change format form sfz to emulti, thats all