āAnyone encountered a bug where the DN freezes with a continuous high pitch note?ā
Many times unfortunately, usually connected (I think) to using arps but not always.
I love the Digitone but this problem makes me nervous to ever use it live. Maybe Elektron could at least make it crash quieter (though obv would rather it didnāt crash at all)?
This arp bug can consistently and reproducibly crash the digitone into that high pitch noise and this has been confirmed by elektron. Youāre definitely not the only ones reporting it 
I havenāt experienced any other crashes when not using overbridge, but I havenāt played around with midi input. There is a good chance that the voice allocation thing you ran into is related to the arp bug since something goes haywire with the allocation even when it doesnāt end up crashing.
Interesting, I usually end up with patterns similar to how you describe, basically trying to get the most out of the 4 tracks, as well as running independent track scale etc. Iāve never been able to consistently reproduce the crash though, that must have taken a lot of patience for you to figure out!
Iām pretty sure Iāve had crashes with simpler patterns too though, something made me eventually get fed up of using it a while back.
Sorry but I donāt understand this sentence. Is there any relationship between Arp and Voice allocation?
Iāve encountered arp-related crashing bug a few times. Thankfully not onstage, but I am nervous about that happening. I think Iāve found a way to avoid it, which is to not have more than one track using an arp. You could give that a try until they fix the bug.
It took some investigation yes 
and yes, it can happen with simpler patterns as well, although usually this doesnāt crash the machine it just plays the programmed sequence wrong. I havenāt been able to pinpoint exactly what the cause is but it al revolves around the arp, voice allocation and sound locks (that have the arp enabled).
Some are easier to replicate than others, but for instance bug 3 is easy to replicate, and clearly not the intended behavior. I was kinda surprised that nobody (including myself) had noticed/reported it before.
@Blasted_pingin
Yes for instance if you soundlock sounds with the arp activated on T1, this will affect the arp on T2 while voice stealing is off. This shouldnāt happen. See bug 2
@Kraus @Looper Iām 98% sure your safe as long as you donāt combine it with massive sound locking. I donāt recall ever having a problem with every track running an arp while not sound locking the arp as well. Might want to confirm that before you rely on it live though 
itās been almost a year since I looked into this.
Thanks, yeah, I try and only use 2 max arps now and it mostly doesnāt happen - still a bit hairy though.
Ah, interesting, thanks for this info and all your effort looking into this.
I usually use the Digitone as a standalone groovebox and use sound locked arps nearly all the time to help make up for the lack of tracks. Iāve had this crash happen when just using two tracks, one with a sound locked arp and the other standard arp. Didnāt occur to me that the sound-locked one could be causing the issue. Have Elektron confirmed this bug?
Think Iām going to stop using sound-locked arps until a fix happens - maybe investigate using midi-loopback instead but have found that a bit glitchy when Iāve tried it before.
When I am controlling a midi channel via Logic through the DT that isnāt 1-4 it will definitely bug out! I am using it as an audio interface as well as a midi interface.
Also the LFO DEST menu can be pretty wonky under certain circumstances, it seems to do it the most when Iām trying to make changes during playback.
From Elektron support:
I also suspect that the freeze could be related to the arpeggiator. As mentioned earlier, we have for a while been hunting a known bug that can cause a freeze, that we know is related to the arpeggiator. We have unfortunately not yet found the culprit, even though our developers have spent a lot of time investigating. We have not received many reports so it seems rare that users experience this bug, but we take it very seriously and I hope we can find a solution soon.
It goes to show not many people report the bugs.
But the problem is broader than the freezing, there is quite a few scenarios (which most user will find themselves in at least at some point) in which it simply doesnāt play back the proper sequence, itās just that that is easier to not notice, or to falsely attribute to user-error, than a high pitched freezing buzz-kill.
Totally understandable btw I blamed it on user-error (myself) as well when I first noticed it. 
Ugh I always assume plenty of people submit bug reports, so I havenāt botheredā¦ I really should send one for this arp bug
We all do
Maybe a good practice would be to report at Elektron then complain here with the satisfaction of the duty being done. We should actually call the thread bug complaints instead of bug reports.
Good practice imo is to complain here, see if other people can reproduce/identify it as user error, then report to support.
So it has a lot of high end on that sound because you added a lot of err? (har har har)
Hope a power cycle can fix it.
Since I upgraded to 1.32 (then 1.32A), Iāve had two instances of entire projects being corrupted. In the first case, a different project ended up overriding an existing project. No idea how that happened. Then, today, using 1.32A, a backup of the same project became corrupted. The sound pool disappeared, there were suddenly only about 50 of the original 128 patterns.
Prior to 1.32 and 1.32A, I never had anything of this seriousness happen. Sorry I canāt provide any other information.
People, backup your work!!!
Yep only since 1.32A but consistenly, on different patches. If i turn the knob a value appears but after a while it goes back to Error.
Are you using MIDI or overbridge to control the Digitone?
Iāve seen this before when the messages sent are out of range; the 'tone shows ERR, mainly on the B operator, if I recall.
