This is the first time I’m writing here and I want to report some bug I had these last days. By the way, my Digitakt is in 1.11
Ok, so
1 - Samples :
I spent hours to work on a project, I sample and resample what I made to free some tracks. As everyone use to do. Then I select a sample I just recorded, save and add in my ram. For exemple this is the number 29 (I have samples before and after). I trig this one on my track 4. I do all my stuff save pattern and project then continue to work. Next day, I start my digitakt and “BIM” the magic trick happen, my sample disappeared. In my RAM on my sample 29 I have now ----- instead of his name. Also, my sample 29 disappeared from my record folder. It happened 5 times in 3 weeks.
2 - Trigs :
In this project I use samples (that I resampled from de Digitakt) that are 32 step long for some. So on my track 1 for exemple I put a Trig on step 1 that will be play the sample for 32 step long. It work correctly. I saved etc… I played with all my patterns, everything works. Then with a new magical trick my Digitakt doesn’t play the trig I add on step 1 (even if I put a trig on an other step). When I press on my track 1, it lunch my sample doesn’t play any of my trigs on this track. All my track are unmuted. And it doesn’t work.
3 - LFO :
I want to use my LFO as a randomizer on my samples. So on track 2, I put a sample and define his start and stop point. On my LFO I selected sample start destination, define depth, speed, wave as random and trig start lfo. I put 32 trigs on 32 step. I don’t understand why it doesn’t change the start point on each step, or it works but stay on the beginning of my sample.
4 - Midi IN/OUT LFO :
To have more LFO I use the cable trick. So I put a midi cable on my Digitakt IN that I connect on my Digitakt OUT. I use the midi map and add a Midi LFO on a track that have a LFO already. It work well, but after some minutes or hours my Digitakt start to freeze and I have to reboot every 2 min. =/ It works perfectly before the new update.
I reinstalled my Digitakt OS, but nothing changed.
Does anyone have this kind of issues with his Digitakt ?
About point 4, I can say that it actually happens to me if I press the bottom Stop twice fast. As far as I remember, it is normal for this to happen. Some people learn to play stop only once, others like me, stop using the midi loop trick. But I think I read that you are not supposed to do that, if one does it, is under their own risk.
3 and 1, no idea. but for point 1, how long is your sample? less than 33 seconds?
2, are both mute modes unmuted (purlple and green)? i would also check the quantization, maybe putting it a little bit later. sometimes trigs in 1st step dont trigger because of that.
In general, it seems that many of your problems have something to do with memory and saving? which way are you saving? Func+yes, or also saving project?
i had something similar going on a couple of days ago:i had an overbridge session with 3 Elektrons in Logic Pro X (one was DT) and then i closed Logic and left for lunch.Computer went into standby (overbridge engine was still running) and when i came back and started Logic i saw a"synchronizing overbridge" message in the DT display and BAM…after that all samples from my sample pool got wiped.Even"better":i did reload the saved project but still,the samples were gone! Super annoying and a bug file under “absolute NO GO”.The (empty) sounds and trigs were still there so i could reproduce it after spendung a little time.And i was lucky,the project was still quite empty.If this happened with a project containing lots of different patterns…i would have thrown this thing out of the window thats for sure!
conclusion:always backup your project (make a copy) like you are working with a win 95/98 computer!
I tried to throw it through my windows ahaha. . . Kidding
It was after long time of work on it. I haven’t my old samples to recreate the one that was missing.
Yep you’re right like we are in 1998, but in 2020 ahaha
make adjustments to lfo speed/depth. you may have your lfo at a speed/depth where it doesn’t change the start point enough or doesn’t cycle to a new random value on each step. i use this technique often and it works as expected.
Can you maybe list your LFO settings? It’s weird that it’s not showing any effect from the way you described it. You can also check on the second source page, here you can see where the sample starts when a trigger hits.
When I want to have a randomized start point – I want that a lot of times, haha – I typically take a blank LFO page and only adjust DEST to Sample: Start, WAVE to RND, MODE to HLD and DEP to taste. Seems to work everytime.
