Digitakt 1.04 : Bug reports

[Buska]

Mine does the same thing in test mode

[Padevil]

Random freeze while using audio and midi. Couldnt reproduce the error =(
So underwhelmed by the lack of stability

[Olle]

Random freeze while using audio and midi. Couldnt reproduce the error =(

Report to support. Almost all reported freezes using MIDI has been MIDI feedback. Check that you don’t have a MIDI loop.

[Olle]

Still get freezes when sending midi to self.

This is most likley MIDI feedback.

[Geir]

It seems I only get this freeze when I double tap stop. It doesn’t freeze when I single tap.

[void]

it’s due to midi cc 120 being sent and received in an endless loop:

Could the DT be a "studio hub" without song mode?

note: you can use the midi thru port as midi out port when you do loopback like this. there is an issue right now, where if you have active midi tracks, and you press double-stop on the DT, it will send out special midi cc 120 (all sounds off) from the active channels. It will then also receive this message, and this will trigger the message to be sent out the midi channels again >>> endless loop, hang.

[Geir]

Aha. Thanks. Nice to know the reason as to why this happens. I noticed that I can get out of this loop by flipping the «Input From» to disabled and back to midi (Port Config). No need to reboot.

[patilon]

anyone else having problems with automation changing the notes?
started a new project… installed the firmware again… still the same

[Padevil]

Thank you, will send to support.

I don’t have midi loop, however I have quite a bit of midi information entering the Digitakt.
I had two other freezes:

• One right after clicking real-time record.
• One while playing a midi track with an external keyboard

[kwamensah]

woke up this morning to a bricked device after it was working with this update the night prior.

[avantronica]

That’s rotten luck. It’s not obviously a bug though (this topic), and you’ve cross-posted this point in another thread, so I suggest replies to your issue go there.

If you have a voltmeter or another device which uses a similar PSU to the DT one you could test the psu on that device. In any case, it sounds like an issue to take up with support asap

[kwamensah]

It now has turned itself back on out of the blue. So I guess it is a bug where it hangs or locks at startup intermittently.

edit: I have an open support ticket.

[re5et]

i read about a 30 second wait before turning it back on (has to empty charge or something).

[brisket]

The sequencer sometimes stops playing back after I’ve recorded MIDI input from an external keyboard. ie, I’ve been recording MIDI into the sequencer with a keyboard, cool, but after a while it stops playing back any sequences at all, even those recorded with the DT itself. Changing project fixes it for a while, but then it happens again.

[thegiantarm]

Knobs in MIDI channels take multiple pushes to enable channel & program functions. Have experienced this numerous times in different MIDI tracks.

[digiwut]

Yeah mine has done that from the beginning. Thought I was the only one. Are we the only two?

[brisket]

me too. Was wondering if it might be a HW issue with new encoders? seems to have improved slightly.

[AdamJay]

Sounds repeatable.
File support tickets!

[provoda]

Same encoder behavior here

[Olaf_Wolkenhauer]

I had the same problem (multiple tries required to get midi channel and prog changes activated) in 1.03 and it remains in 1.04. I first thought I do something wrong and did not worry since it always eventually works and is only required occasionally. This has also been discussed previously, but no harm mentioning it again until someone has an explanation/solution The 1.04 update made a huge difference to my DT experience… hardly trouble now ( o chrashes so far) and I am starting to enjoy the machine now.