Hello friends! here I have an ish with the brilliant create
random locks feature we all love so much. my ish seems to be that my ‘random’ isnt working, no matter how many times i try, the slices stay the same. Ive gone under the hood as far as the manual goes, and watched people online, but havent seen this one yet. has anyone else experieinced a non randomizing create random locks?
Hi, can you show a picture of your settings page for the slice machine? Is this Digitakt 1 or Digitakt 2 which has the problem?
Have you had success doing this in the past or is this the first time you’ve tried?
Thanks
Also to make sure, have you already filled the sequencer trigs? You need to do that part manually, just in case you didn’t know.
its worked in the past! im all up to date and rocking the DG2. photo is a minute
Ok, I’ll look at your photo. Should hopefully become evident where the problem is.
It’s fine, you don’t need to try the video yet. So you have the trigs filled already? You put some in while in recording mode?
yes i put a few in, strange that sometimes i DO hear the slice change, but then i create rando locks again, and it seems to get ‘stuck’ - which makes no sense. my LEN of trig tab is full, as well as my AMP page.
So on the trig page, the trig length is INF?
And the exact problem now, is that you laid some trigs on the sequencer and on the GRID machine page you press the YES button and go down to create random locks, but when you press YES one more time, nothing happens? Or you don’t hear it happen, I guess I should say
thats exactly it = seems to stay stuck, often on the very beginning of the sample.
but annoying eratic, sometimes seems to behave as it should
Does your sample have a lot of repetition? I just mean, would it be easy to tell all the slices apart from each other?
How many pages is your pattern? When you go here
can you play all slices manually with the trigs?
I think that the best thing we can do test this will be for you to make a new test project, something totally empty. Load this same sample to a track and fill all the trigs for 1 whole page, then use the grid to slice the sample and let’s see if it has the same problem in a new project or not.
for example, i just put down 3 trigs on a single page pattern, and the first slice is on slice 10, but when it plays, it doesnt play slice 10, it plays the beginning of the sample
i will give this a shot = thanks for the help!
ok no problen, let’s figure it out.
try the randomize on the new pattern. with all trigs full it should be easy to tell if it’s randomized or not.
its working!
niiiiicccee. ok so the first project, we need to figure out what’s different.
yet the LEN is not at INF,
your 16 slice grid must have sufficient length in context of the sample at this bpm.
length determines how long the sample can play for, but I think that if you have some slices set, that the length only needs to be sufficient for the length the trig will actually play for before the next trig hits.
so, if you had a trig on each of the 1, 5, 9, 13, then the length needs to be at least the distance between 1 and 5 otherwise it will cut off early. If it’s still playing when the next trig hits, it should choke the first slice out (because it’s monophonic).
pretty sure that’s how it works, so in this case maybe it doesn’t matter if it’s inf as long as the slice is sufficient to play for the distance in between trigs.
on the original project, try this same setting and see if it changes anything for you. start with all trigs in the sequencer grid full and then, if it’s successful, change it to only the trigs you want and test again to see if random is hitting correctly.
okay, back to the original project, again, behaving weirdly. i tried creating linear locks and it didnt., next tried grid at 8, and [pput down 1,3,5,7,9,11,13,15.
heres another clue = you know how usually you can have the sequence running and when you change the locks, it will happen in real time? this doesnt occur here. theres no change Unless i stop and start the seuqence, and even thenm, its a 50/50 whether the locks have changed or stayed the same