I have the exact same annoying behavior on my DTII : )
Please report to Elektron support if you haven’t already!
Ooof … sounds like something that should be added to automated testing … it’s not like that’s an obscure combination or sequence.
Thanks for confirming, I have reported to Elektron support!
This morning I added two lock trigs to activate retrig for a track. While the lock is saved, and shows up on the Trig page when I hold down the trig as well as producing the intended effect, it does not flash to show that there is a lock.
Wanna report one, maybe someone can alao reproduce.
Whenever i connect Dt2 to my Daw(ableton live) Track #2 Note Velocity and Length get messed up.
Note goes one octave down, Velocity goes to 0, and Lenght shoot up to max
Here is the discussion for checking what you find is really a bug
If you’re sure, report to Elektron support (you can still leave a note here for others to confirm or just know)
If someone can try to reproduce these before I send a bug report to support:
- Select a track with a sample
- Change Machine to Slice
- Press YES from the SRC page to open the Slicing menu
- Select Edit Slice Points (do not create multiple slices, keep just one)
- Play a bit with FUNC+POS
- Digitakt II freezes, can’t do anything more → Restart the machine.
Sometime I even got this:
Yes, this has been reproduced and is already fixed internally. Will come in a future bug fix release. In the meantime, avoid doing this
Good news, yeah, I already avoid it
My sequences data in my pattern I’m working on just keep randomly deleting! Is this happening to anyone else? It happened to me twice in like 2 hours now.
have reinstalled transfer and reinstalled the update still cant upload any new samples on transfer
Signed up to report an issue, then I saw up thread that this has been fixed.
I have a project that still exhibits the behavior. Sending any midi data on 9 reliably causes the unit to hard lock and display an error, latest 1.15 “slice” firmware, setting Receive FX to off fixes that project.
It’s the only project I’ve tested (so far) with the issue happening reliably. I did have another hard lock happen on one of my other projects I was just testing (again sending midi on channel9 with it set to effects) but I can’t get it to replicate on that project now.
All crashes happened on the 1.15 firmware.
Thanks for reporting this, will be taken care of straight away.
For readers of this, it was not an error. Max file size is 64MB, and upload of an MP3 file which are larger than that when uncompressed will thereby be rejected.
I didn’t know in which thread I should ask this question and I didn’t want to create another topic.
Since I’ve bought the DN II, my DT II is no longer the Master, it’s now receiving Clock, PC and Transport from the DN II. The other day, I tried to record an internal Loop with no success. The Loop wasn’t tied to the DN II BPM. I tried to start the recording from the DT and also from the DN, same results.
Does the DT need to operate with its own internal clock to record perfect loops?
It does feel like an overlooked thing, and I would report this to Elektron support, were I you.
Done.
Just tried it here, recording perfect loops on DT2 works as expected when synced/clocked from to the DN2. You can see the Recorder’s R.LEN fluctuate slightly, just as the tempo does, but it’s not affecting the recording here. Maybe it’s failing at certain tempo though?