I just made a rapid fire follow-up video to address a couple questions I got from the first loop pad video.
tl;dw:
Can you use the EP-40 as a live looper or loop station?
a. Probably, but it sounds really tough to do.
Why did you time stretch every loop?
a. Loops play start-to-end repeatedly and stretching it to a bar duration makes sure it doesn’t fall out of time.
How does Live mode work with loop pads?
a. In Live mode, changing tempo changes the pitch of all pads. This makes sure there’s no stutter-y sound in the sample, but affects the key you’re in. When Live mode is off, changing tempo does not change pitch.
Is there a fast way to resample?
a. Yes, go to Sample, press +, and select RSP (mono or stereo). Hold shift and press the pad you want to sample to, then play the pad you want to resample and hit Sample to end recording.
I think most of what you want to do should be possible.
When you set the EP’s default MIDI channel (SYSTEM > MIDI > CHN, usually channel 1), you can trigger all 48 pads starting from C1. If you assign a MIDI channel to a pad, incoming MIDI notes on that channel will play that pad chromatically.
Sidechain compression should also work with external MIDI input, just like it does normally.
That’s brilliant news, thanks for taking the time. Seems like a best of both worlds situation where you get the EP grit with full arrangement mode view for precise midi edits
That might be possible, but you’d really be fighting the device’s intended workflow (not that there’s necessarily anything wrong with that). It might be easier to use something like Amigo sampler or effects if the sound is what you’re after.
Yes doesn’t seem that straightforward. Looking at YT seems like using a keyboard to play pads is plug and play via midi but for some reason can’t get ableton to work - should be similar.
I can get the ep to sync to ableton but not sequence.
I was able to sequence KO2 with Digitakt, but when I tried to sequence e.g. drums and a sample in keys mode, it only played to sample that was in the keys mode.
Hello,
Basically I would like an Ableton midi track to control the EP pads.
I have set up midi out to EP in Ableton and midi channel in on the EP.
Not sure what I’m doing wrong
Very happy to hear!
I think I also got it to work. Realised I was using a drum rack as a midi channel instead or a proper midi channel.
I set midi channel in the EP to “all” and basically start from bottom of Group A which corresponds to C1 in the midi track
Thanks for your support!
thank you sooo much for the samplebuilder!!
have been messing with some kits and it is really fun.
here’s one:
one question: did you (or anyone?) try to timestretch multisamples? when i go into TIM menu and set the BPM accordingly, the first sample streches fine but the other seven are just glitches. is there a solution for this? would be amazing to change the tempo for the whole kit at once…
it’s probably an oversight in the builder. maybe metadata is required for each multi sample for bpm and its only wired in the first? @Instant_Fidelity come across this?
thanks for flagging. i’ll check it out when i get the chance.
Based on my analysis of the 471 stock EP-40 Riddim samples, timestretching multisamples may not be supported. All 5 official multisamples (clavinet, hammond, melodica, muted guitar, opti organ) have BPM disabled (“time.mode”: “off”). The 99 samples that do have BPM enabled are all single-sample loops (drum loops, bass loops), not multisamples. The TNGE metadata format seems to only support a global “sound.bpm” field at the root level and there’s no way to set BPM per-region.
The glitching behavior @kostianix described (first sample works, others glitch) happens because the EP-40 applies timestretching to the entire concatenated audio file. The first region starts at position 0 so it stretches correctly, but regions 2-8 start at different positions and get mangled by the global timestretch algorithm. It might be worth testing out adding the “sound.bpm” to each region to see what happens and if it fixes this issue, but given none of the stock samples have that field in the regions I doubt it will fix this issue.
I’d say officially timestretching isn’t supported for multisamples and if you need tempo sync, use single-sample loops instead of multi-region mappings, or pre-timestretch your source audio before building the multisample.
Nice. Not in riddim land currently. But I wonder if the multisamples were all the same length (like a breakbeat cut at 1/8ths) would it apply the same bpm for all. And the glitches are due to varying sample lengths in a kit.
Something to test.
Quick tip: Timing can be very helpful when dialing in the start point of a sample.
If 32nd note repeats are silent or barely have a sound, I’ll move the start point a little later. For fine adjustments, hold shift and press + in Sound Edit → TRM mode.
For extra resolution hold Tempo and type 399 (i.e., set the project tempo to 399bpm).
Alternately, enter Keys mode and go down a few octaves.
