i tried all of them, it made no difference, still just playing two slices.
Is the LFO synced to BPM? Do you have it set to restart on each new trig?
no itās free running. have you tried to replicate this? i was using just a simple drum break sample with a few trigs over 32 steps and it just kept playing 2 slices that were not even next to each other in the sample.
Iām pretty sure Iāve successfully put an LFO on slices, but I havenāt used the slice machine much, apart from some initial exploration when it was released. If you can reproduce this in a minimal setting, dump the project and post it here, and we can try loading it and see what we can determine.
You need to be very specific about the settings otherwise the LFO will play back either the slice number or the NOTE mode, which will just machinegun the first slice. Probably what youre hearing. Try these settings:
Slice Grid: 16
Slice Select: 9 (so the LFO depth of -8.0 doesnāt reach the NOTE mode)
LFO Wave: Saw
LFO Dest: Slice Select
LFO Depth: -8.0
8 Likes
Ooh, thanks. It wasnāt working the way I hoped when I tried it a while back and this probably explains why.
Cheers
well that makes sense, will try later, thanks!
Another reason for hearing 2 repeating slices could be due to the depth setting. If you crank the depth too high, it just goes outside of the addressable range of slices. The LFO depth is handled a bit unique for the Slice Select setting. Each whole number is a jump of a slice. So 1 will move 1 slice, 8 will move 8 - however it also matters which waveform youāre using. A Unipolar waveform (eg Envelope) is only positive so a setting of 8 (or -8) will move 8 slices left or right from the default slice, but a Bipolar wave (eg Random) oscillates between positive and negative, so this means the Depth is the amount of movement on either side of the default slice. (Think of the values as literal, thereās no interpolation going on). By default slice I mean the slice that is selected on the SRC page.
So if you change the number of slices you need to adjust the depth to match (half of the total for a bipolar wave, or the same number as the total for a unipolar wave) if you want to sweep the entire range.
3 Likes
Hey all!
Do we have a separate thread for OS 1.51A reports, or I should post them here?
Thanks in advance.
I encountered with MIDI messages bug. When you reload pattern (Func + No) sometimes digitakt sends CC, PB, BC, MW values as 0. I tried to debug it over MIDI Monitor tools and discovered that sometimes digitakt send data incorrectly - it separates cc codes with zeros and 0-cc codes with actual values. As a result device connected to the digitakt receives wrong settings and it ruins the preset. It was awful in live performance situation. It was midi data via usb, I donāt know if it happens with midi output.
5 Likes
My DT (currently on firmware 1.20) is not showing up inside of Transfer and when I connect via my Clarett8Pre, the SysEx transfer gets stuck 50% of the way through. Anyone know why this may be and how to get around it?
Thanks!
Welcome aboard.
Check Transfer version: latest is 1.8
Try another USB cable (I have had better results with a quality one)
Plug the USB cable directly in your computer, with no intermediate accessory.
(I think on new firmware it doesnāt matter much but I donāt know on 1.20) Check that in your MIDI settings both MIDI IN and MIDI OUT are set to USB.
Report back here
Hey, thanks!
My version of transfer was out of date, but with those changes made and a fresh USB cable (the last one was the Elektron cable shipped with the DT), itās still not showing up in Transfer.
EDIT: the SysEx transfer via midi also still doesnāt work
The DT also isnāt showing up inside of Overbridge. It worked great when I used it around the time of the 1.20 firmware update (my Overbridge version is out of date, but the current version doesnāt work with firmware versions before 1.5, the version of OB Iām using did used to work fine with DT on 1.20).
Well, youāre good for an OB update I suppose.
Youāre plugging your DT directly in the computer USB port?
Latest OB update doesnāt support DT firmware prior to 1.50 and Iām on 1.20 so canāt update it.
Yes, plugged directly into computer via USB.
Sorry, I donāt actually know - is Elektronauts an official Elektron support channel or should I contact them direct? If it wonāt take the update Iām wondering if Elektron - or an approved engineer or something - can help?
Thanks again
Harry
From memory, you canāt get to update to 1.40 or more without getting 1.21
So you need to get this intermediate firmware. Some users might have still this older version, maybe look for the relevant topics, otherwise yeah, contact the support
No, as stated in the first post (I should maybe make this clearer).
1 Like
I had something weird happen yesterday whilst building a pattern, I had a kick on track 1 and felt the need for some extra meat so went to track 3 and put another kick in the same place but once played the second kick was 1 step early, tried live recording it and as soon as the pattern was stopped and restarted it was 1 step out again. Everything was matching in terms of track lengths and when I did the same in another spare track it worked as expected, first time I have experienced anything like that and wondered if anyone else had come across similar?.
1 Like
I assume this was never addressed by Elektron?
This has happened to me on the DT1 (and 2) with pitch bend, for example. The result was a detuned synth for the remainder of my performance, and until I figured out what was happening it was extremely disorienting.
2 Likes