Even borrowing OT’s record trigs would be lovely for this purpose. It is definitely possible at least, it would just need the right button combo to be pushed to separate a normal trig or a trigless trig from a record trig
a page with 8 “macro knobs” with 4 configurable destinations each, as in the analog 4
That would be amazing. A performance page as such.
That would be amazing, and I think it’s possible to implement because doesn’t seem to need additional processing beyond what the CPU is currently doing.
Another thing that I’d love to have is live sampling directly to a track. For example, pressing [SAMPLE] and [5] it would start sampling next time the track 5 starts looping again, and would sample for as long as the length of the track and assign the sample directly to track [5] without any further user interaction. Perhaps shouldn’t normalize the sample in this case. And it could save it automatically with some default file name and open a dialog to rename it after sampling, so the user has the option to either input a better name or press [NO] to just continue with the default name.
This would open the possibility to live looping, where each track could have different lengths and scale factors, and the tracks where you assign the new samples could have sequences programmed beforehand.
A simple request that I feel would improve workflow.
On the sampling trim page, please swap the buttons for preview with trim.
A non destructive action should be one button (Yes - preview) and a destructive action should be two (Func + Yes - Trim).
It would make previewing the sample while dialing the trim knobs much easier without accidentally trimming the sample.
If you’ve ever trimmed a sample on another sampler/groovebox you can just press the pad while trimming. No double key press needed. It’s just fiddly.
As improbable as it is I’ve been dying for a proper time-stretch lately. It’s always a bummer when I find a nice loop but can’t change the speed without changing the pitch as well. If anyone knows any solid workarounds aside from using a DAW I’m all ears!
Time stretching! It should exist in any decent sampler and Digitakt is!
Choose between record samples in stereo or mono even with the limitations in record time because of the memory.
Come on Elektron, is not this features that differentiate the digitakt from OT…it is this and much more and DT with this features do not threat the OT!
Interesting! I’ll give this a try!
Hi, I wonder if kits will arrive one day to digitakt, even model: sample has it… why not digitakt? Someone knows something about it?
Thx
No-one knows.
Please Elektron, give us that time-stretch and slicing of samples !
And maybe add that lowpass/bandpass filter that we can already enjoy on the Digitone.
Definitely do! Especially with vocal samples
No it’s not a replacement for proper time stretch but it yields new and unexpected things.
I’m pretty sure it is cpu intensive to time stretch. Maybe it could be implemented as a resample type deal. That way it could be done without killing the cpu. But then people would want to do things like LFO the timestretch and then it’s back to killing cpu. Timestretch done offline works fine for me when I’m in the DAW (love the Edison editor) making things to import and I think it sounds better than anything I’ve heard on box anyways.
Anyone think slice could be done? I was thinking about how it could just stamp out 16 (or 32 or whatever) slices based on sample length and then move the cursor start to where you want the slices to be at. No real cost to cpu to try and get that perfect 0 transient and could do by ear.
Doing it per trig is time consuming and a starting point, even a rough one would definitely speed things up.
Another fill button. So, we can use fill or fill2 and if both are pushed, it enable fill3 !!! Awesome or maybe a mess in the pattern ?
I understand what u are saying @Synj00, but im talking in the performance field. Imagine that im making a live performance and im playing one pattern that is 124 bpm, and i wanna choose next pattern in a stack of 3 patterns that i’ve made, all from the stack have different bpm, when i choose the next pattern to play, for instante have 128 bpm, so I can slowly go up the bpm so as not to be noticeable until I reach 128bpm, or I can lower the pattern I chose to 126 bpm so the scaling is not too drastic. As is done in the music mix.
With timestretch this is possible.
The design level can even be easier as you are referring to as a resample genre.
Now for the question of later also want to use LFO in timestretch …
If it is not possible to implement a design that uses few resources, Elektron need to be clear in this respect, saying that the timestretch will be implemented and due to the considerable resources it can not develop the LFO in it.
There is nothing like the clarity and transparency that gives credit.
This in my opinion.
I have to admit that I am not aware of the facts in terms of machine resources.
But in that regard, I let Elektron developers analyze these factors and it’s always good to have an honest opinion of them.
I understand what u are saying Synj00, but im talking in the performance field. Imagine that im making a live performance and im playing one pattern that is 124 bpm, and i wanna choose next pattern in a stack of 3 patterns that i’ve made, all from the stack have different bpm, when i choose the next pattern to play, for instante have 128 bpm, so I can slowly go up the bpm so as not to be noticeable until I reach 128bpm, or I can lower the pattern I chose to 126 bpm so the scaling is not too drastic. As is done in the music mix.
With timestretch this is possible.
The design level can even be easier as you are referring to as a resample genre.
Now for the question of later also want to use LFO in timestretch …
If it is not possible to implement a design that uses few resources, Elektron need to be clear in this respect, saying that the timestretch will be implemented and due to the considerable resources it can not develop the LFO in it.
There is nothing like the clarity and transparency that gives credit.
This in my opinion.
I have to admit that I am not aware of the facts in terms of machine resources.
But in that regard, I let Elektron developers analyze these factors and it’s always good to have an honest opinion of them.
Then you would be better suited for the Octatrack. It’s geared towards performance and has timestretch.
Spoiler alert: OT timestretch sucks and sounds terribad even at base BPM, and hardware timestretch almost always sounds bad anyway.