And where we can get this older 1.25E OS ?
Any link ?
Contact support and theyāll get it to you, or try the link in this thread:
Pre-sliced recorder buffer issue 1.25H
please fix this!
this issue is more than a year old⦠![]()
Clearly they know about it, so it would perhaps be of no benefit to report, but itās still probably more beneficial than posting here ⦠perhaps support could give an indication on when an update may be forthcoming ⦠clearly there are a few more distractions for Elektron these days and bug fix roll outs donāt seem to be as frequent as weād all like
ps - creating threads pointing to threads isnāt recommended ⦠itās not a given Elektron would see it anyway, but in this case itās clearly a known issue and I am sure itāll be fixed in the next os
thanks!
Why donāt you downgrade to 1.25E ?
is there a 1.25E? canāt find it on the support pageā¦
Just above your first post here ! 
Hi. I was thinking about pre-sliced buffers. I canāt test the issue because Iām on 1.25E. Wondering if it would be really useful for me, and go for TRC without any regret.
Apparently it doesnāt work properly if you change tempo.
As @Clancy mentioned, you can assign a saved silence sample. Itās not a big deal. You use start points now ? Whatās really interesting with pre-sliced buffers. Tell us more ! 
Is there a big advantage to using pre-sliced buffers over shortly spaced recorder trigs?
Just wondering as Iāve never used them 
Iāll write something up about sliced recorder buffers and also start points when I have more time, unless someone beats me to it⦠
Anyway your point of view will be interesting.
I was almost ready to answer 1 hour ago, but I made other tests before. And now Iām not sure anymore. Short records or plocked start/slice points ?
Some thoughtsā¦
It can sound the same, with trigs corresponding to rec trigs for short recs, or slices with correct linear locks (or lfo on start). Played real-time, some limits like pitch up or rate reverse seems to be in common.
But you can also use slices for short recs, play with Length and go up to 1 octave up depending on Length, and slice duration.
Many things to explore. Realtime pitch shift, lfos on pitchā¦Realtime granular stuff ?
For tests you can rec track 1 with track 2 (rec trigs > SRC3=T1). - 1 microtiming for rec trigs.
If you record inputs, normally no need for microtiming, maybe timestretch off.
(Settings for realtime playing)
Hmm, thanks for the info! i should just try it and see! Iāve gotten into the habit of using lots of rec trigs on flex tracks for glitchy fun with the inputs. I know you mention some uses but most of these are things that I already do with flex tracks. The OT cannot predict what will be recorded so before slice 16 can be played, it must be recorded, so doesnāt that make it the equivalent of 16 rec trigs? Although I guess you can have much smaller chunks of audio with slices, and also you get multiple chunks of audio. Rec trigs just give you one piece of audio that is constantly overwritten
Iāll have to check it out properly tomorrow 
Is this bug still not fixed?
Iām on the latest OS and it seems to be still there
Stil on 1.25H here, so your telling me⦠
Itās weird, it wonāt even revert to start points if slic is on as if there were no slices, it leaves one zero length āghost sliceā that ruins it⦠Is that still there?
Anyway start points work great for even length slices for buffers and work better after changing tempo then re recording. But slices should stick, they did on 1.25E and beforeā¦