if the tonverk is just a ‘better’ digitakt 2, people will get mad. and I don’t believe it will be that.
the digitakt 2 will get some cool updates in the future. im shure it will happen. but shit takes time.
if the tonverk is just a ‘better’ digitakt 2, people will get mad. and I don’t believe it will be that.
the digitakt 2 will get some cool updates in the future. im shure it will happen. but shit takes time.
The Octatrack has FIN and FOUT (fade in and out) parameters for buffer recording, which helps to minimise perceived popping of recorded loops (though there is a thing where you have to set FOUT to 0 if you want a continuously running loop to remain in time, for reasons).
Does the DT2 not have something like that? Does it seem to have a fixed “FIN/FOUT” setting or none at all? Just curious.
No. Amp envelope, start/len, trig length.
I am not fond of OT FIN/FOUT, fixed curves, changing duration values only add silence !
And yes FOUT add extra recording time.
FOUT can be used with Pickups.
FIN for short recordings granular stuff, otherwise I prefer ATK.
Blackbox seems better for seemless loops recording.
Maybe we can have an update for xmas

🫣 ??!
Well….I didnt get on w mine tbh (bb) and touchscreen was smaller than my phone’s. Anyway maybe Elektron will fix it…
I didn’t gel with 1010 UI (BBox, Tangerine, Lemondrop, Fireball), but some features are great.
They’d had to rethink it totally imo, more than a fix.
Any improvement welcome !
I could be wrong about this, but doesn’t granular/stretch mode use crossfade? It’s a while since I read the manual but I remember seeing something about it there…
Anyway, to those who are frustrated, have patience and a little trust still. I believe that the new DT2 and DN2 are based on a new hardware platform so there might be more going on behind the scenes than usual.
This is pure guesswork from me of course, but I still remember then hiring someone with experience in the Rust programming language a while back. This tells me that they could be facing unforseen setbacks or something like that. I feel for you all and hope it won’t be too long before it gets sorted.
Two or three things give hope here
All of that gives me some hope that it was, and still is, an intended feature of DT2.
Dunno what is used but it doesn’t work properly. Clicky.
Using lfo on start as timestretch has almost the same quality, and it doesn’t use crossfade.
OK that clarifies things a lot, thank you. Perhaps they can optimise the engine a bit to get more juice out of it, but currently it is essentially max 32 (16 tracks of stereo) voices. To do a crossfade you need to add a voice to overlap with the one playing, which means doubling the voice count. That takes processing, so either they have enough unused processing cycles to spare or they have to come up with a dynamic solution somehow - meaning allocating voices from unused tracks or other compromises.
The only thing I can say is; sit tight and let it play out - but that’s me talking to myself more than anyone here…
I hope that turns out not to be the case because they told me directly that they are aware of the sample slicing needs, however they did not say they are working on it… but they did not tell me to get an octatrack… they just said they are aware of the needs.
I agree with you, no developers of samplers should need it but that hasn’t prevented me from living in a world where developers of samplers need it all the time
such is the bane of my life
Which could mean either they are not working on it or they have been instructed to say they are not working on it ![]()
Depends on what you think of as a voice. Usually voices include triggers, envelopes, filters, FX, etc. For crossfades really all you’re doing is reading from the same audio data using two playheads. It’s not very computationally expensive but might constitute a sizeable amount of work.
Yes true, I guess I simplified it too much but the point still stands - it takes processing to do even if it’s far less than a full voice in the normal sense. Anyway I’m a couch engineer and I know hardly anything so disregard my highly suspect opinions and carry on. 
Not at all good sir, you’re mostly right on the money. I’m just trying to inspire even more hope that change will come, butt probably failing in the nerdiest of ways.
I’m aware I’d like to find £20m in my sock draw tomorrow, just don’t know how to make it happen. (Sorry! I know you’re just trying to give people a ray of hope
)
I think solving the clicking problem is possible for looping samples without crossfades, if they added an OT like zero crossing finder (which you dial in yourself). For grid/slice mode they’d need a way to automatically snap, but there’s no guarantee that’s possible for every sample, but there could be an algorithm that made an attempt to do this.
What I’m saying is, I don’t think crossfade is the only way to fix this, which is good as I can’t see crossfade being implementable
yep… I’m just staying positive about it because the DT is a sampler after all, and they are a business, and hopefully continuing to improve the sampling capabilities will fit nicely in between those two notions… if someone had just told me to go get an octatrack instead as a response I would have immediately returned the DT 2, whether it’s god or not lol… cause i can’t go for that no I , no can do, i can’t go for that can’t go for that can’t go for that…
Zero crossing snapping, with short fades IN/OUT if snapping isn’t possible, would be a great improvement.