I am new to posting here, but have been using these forums for a long time for tutorials and general info.
I have seen a few things about the Digitone crashing or freezing up for various reasons, but haven’t seen too many solutions.
Basically, I recently got a digitone, love it, but I haven’t gotten very far yet. I have a pattern with arp mode on one track. And various locks on others. No matter what I do, whether it is copy the pattern and past to next pattern, or stop playback, copy pattern and paste it to next pattern. Whenever I switch the pattern and switch back to original pattern, the Digitone freezes and crashes. Not sending any midi to or from it either.
I have opened a ticket for this. Based on what I’ve seen so far it seems like a fairly common thing. I have it updated to latest firmware, but have not tried a factory reset yet. I have a feeling that exchanging it wont fix the problem, but that is my last resort.
Just figured I’d check to see if anyone has some ideas or at least knows the reasons why it would do this so I can avoid it.
Thank you!
Thank you for the reply. This is just with the digitone and nothing connected besides headphones and power supply. Only using the 4 tracks with an arp on one track with effects, and the other tracks with sound locks and effects as well.
I have seen variations of this possible bug in other forums, with it crashing and freezing. I can recreate this every time with the same pattern. I haven’t had this problem switching back and forth between different patterns.
Next bunch of questions to get a more complete picture of the situation and to narrow down the problem …
Does it happen with the latest OS?
Can you re-create the same issue in a new project? Maybe the one pattern you are testing with got somehow corrupted or doesn’t match exactly with what the (latest) OS expects …
Thank you, this does happen with the latest OS. But I haven’t tried it with a different project yet so I’ll try that right now and give an update.
That is one of the better scenarios with that pattern being corrupted somehow, I can’t think of any other reason this would happen. If I copy the pattern to another pattern it still works, but then switching back to the same pattern is when it happens.
Thank you again, I appreciate this a lot!
It sounds like it’s worth reporting to elektron as a bug , maybe do a backup via Sysex and include it when reporting.
It may be a problem with the pattern data or an issue with whatever is on that particular pattern number … something elektron could track down either way.
Maybe try copying to a another pattern , clear the pattern with an issue , save project , load another project , turn off / on , load up project again and copy pattern back .
Update:
Thank you for all of these replies, I appreciate it a lot.
I copied the pattern to a new project. This is what I’ve found so far: I have track 1 and track 2 layered with each other and I think this is what is causing the problem. When T2 is muted the pattern plays without crashing and can copy and paste patterns like normal. But when T2 is playing, it crashes every time I switch the pattern when it is layered with T1. When not layered with T1 and playing everything is fine. It seems like it is only when T2 and T1 are layered with each other, and both are in arp mode as well so that could have something to do with it. It will crash every time I do this with those settings in place. T1 and T2 in arp mode and layered with each other.
Thank you again for all of the replies and advice, I appreciate it a lot and I’ll update with anything else as I figure out more.
Thank you!
Thank you, that’s also a good idea. I’m going to keep trying to do that in a bunch of different ways.
So far no crashes in the new project starting from scratch, layering T1 and T2 with each other in arp mode. I’ll probably try copying various parameters between projects from the original pattern and this new one and see if the issue can be copied and pasted too.
I agree, thank you. I’ll continue to play around and see if I can recreate it. And I’ll update anything here. I’m leaning towards it being a glitch or something corrupted the file like you said, and that’s totally manageable.
It definitely doesn’t seem like a bug though at this point.
Thank you!
