Can you recreate this after rebooting the device? It’s an old bug that’s proved hard to track down. If you have a way to recreate it please post the steps.
A reboot of my PC seems to have fixed this, super weird. I’ll leave that post up there in case someone encounters the same issues.
I have a 128 step sample (sampled on the machine) which, although routed out of the ctrl all, is still affected by it. Subbed to elektron already.
Spoke too soon, it’s doing it again! The number of requests never goes down.
there seems to be a really annoying bug when copying patterns around, it’s like you copy a pattern and it says “copy pattern” and the Bank/pattern light at the top left corner blinks but when I move to the pattern where I want to paste over, then it doesn’t paste it
1 Like
Hi, just updated my DT2, and LFO destination sample slot still doesn’t work when loading my DT1 project… and the track is using ONESHOT machine.
1 Like
The currently selected track will be affected by ctrl all even if it’s routed in your settings to not be
If you select another track (preferably one that is routed to be affected by ctrl all), everything should work as intended
Hopefully this makes sense
2 Likes
Just got the double trig problem again. Reboot fixes it but it returns after a bit (experience so far)
3 Likes
I believe this is intended. Because you are actually just controlling the selected unit, the track button then applies that to other tracks selected in the routing. Routing from the active track to others.
1 Like
Are you pasting the pattern to a new place before moving to the new pattern? You didn’t mention that step.
You hold PAT+TRIG of the pattern you want to move to and then press the paste button, then you can switch to it as normal.
I have experienced a few times this bug where the external input FX routing gets stuck and won’t update with any change on the mixer page. This goes back to normal after power cycling, or what seems like a few different scenarios. I’ve fixed it by changing pattern, triggering a sample track that is routed to FX (sequence was also paused at this time) and some others but can’t remember, whenever it‘s happened I just fiddle with stuff til it goes away.
May be related to this other bug where certain tracks or sounds seem to gate the delay/reverb or some sounds miss their routing to it and also like mute previous notes that are already in that delay.
Thanks, good to know!
1 Like
That’s been confirmed to be deliberate.
3 Likes
As probably mentioned above already, here are my issues:
Just upgraded my DT2 to firmware 1.02. Transfer software is also upgraded to 1.8.1.
With some samples send to DT2 I get the error “Device failed with operation”, highlighted in red
If I try to remove a folder containing one of these failed transfers, I get the same error.
I tried rebooting both my DT and my pc several times, as well as reinstalling the transfer software.
Shortly after:
Transfer software is going bonkers, crashing more often now. I need to reboot my pc every time now after a crash in order to even open the program.
When browsing my sample folders on the software, it often indicates that there are only a few empty folders on the +Drive, containing not a single sample, whilst still showing that there is over 5 GB of storage used in the upper right corner.
Digitakt also occasionally freezes whilst connected to my computer, and needs a reboot in order to react to any incoming commands again.
The software is making duplicate folders on the Digitakt. I have 2 different “incoming” files on my +Drive now, and the transfer software just shoves new incoming sample folders into one of the duplicate folders with apparently a mind of its own.
I now also have 2 identical *write protected" factory folders on my +Drive.
1 Like
Hello,
i just had a bug where the project bank i was working on reset itself???
I was recording loops and building guide tracks for porting projects from a DAW to the Digitakt II.
Somehow the bank i was working on reset itself in its entirety???
…
I don’t know how to replicate this issue, sorry…:
1 Like
I just did a reset of the +Drive and downgraded to firmware 1.01.
Whenever I try to acces the +Drive on Digitakt the entire device freezes completely, requiring a reboot. This happens every time I want to acces the +Drive.
Edit Did another +Drive format and now it’s working again. Also firmware 1.01 is running quite well giving me no issues anymore with any transfers.
I encountered a bug, and I wonder if anyone can confirm the same behavior before I submit: when external signal (ST) is routed in and you activate EXT L+R in the compressor routing page, the EXT signal does not activate the compressor metering on the comp page. Only when you push an internal DT track, the metering activates and then the EXT starts to activate it as well.
Hey all putting good vibes out there for all of these requests!
Here’s one: wondering if anyone has issues with Song Mode, where the conditions of a trigger are overriden?
For example if I restart a pattern in song mode, say, to bring in a new sound (in a separate row), the conditions of trigs do not restart.
In contrast if you were to restart a pattern outside of song mode (manually), the conditions for trigs (like 1:4 or 2:4) also restart.
Does anyone else notice this or am I crazy?
Thanks!
JWJ
Is th
Pretty sure this is how song mode is intended to work on all Digi boxes. X:Y condition counts do not reset from row to row, track master length (like, for lining up polyrhythmic sequences) does.
1 Like
Windows 11 Pro
Firmware 1.02
USB Audio/MIDI enabled
Latest Transfer (and I believe OB) installed, but unrelated to the issue
I’m using the Digitakt II as audio interface, previewing samples with VLC causes a crash that does not occur when I am just using my laptop sound card.
I’ve tried changing the VLC audio output settings from auto to specify DirectX, doesn’t work.
Windows Audio waveout/soundmapper as the setting seems to not crash, is this to be expected for a USB (class compliant) audio endpoint?
Edit: Ah, this seems interesting-
Faulting application name: vlc.exe, version: 3.0.21.0, time stamp: 0x31bc319a
Faulting module name: ExplorerPatcher.IA-32.dll, version: 22621.3527.65.2, time stamp: 0x6630647b
Exception code: 0xc0000005
Fault offset: 0x00001281
Faulting process id: 0x0x3E4C
Faulting application start time: 0x0x1DACD63B691B06E
Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe
Faulting module path: C:\Program Files\ExplorerPatcher\ExplorerPatcher.IA-32.dll
Report Id: b1bb6c55-39af-4282-a383-538306f084b8
Faulting package full name:
Faulting package-relative application ID:
Ok, so this might just be a Windows Explorer modification on my end glitching out, updating ExplorerPatcher seems to have resolved it.
Weird, but I’ll take a self-serve fix anyday.