As I have been using the Digitakt DT1 stand-alone more frequently that before, I’ve had some weird glitches that have required me to reload my project or reboot entirely.
It could well be me (!) but some silly stuff like midiclock out starting late, sudden track volume drops, effects sends decreasing in input. I haven’t catalogued any of them, as I didn’t think there was any point. It’s very stable so I’m just wondering…
Can I ask those who have done the journey I’m on how stable they think the last firmware was?
Will Elektron roll out more bug fixes after 1.50A or is that the end?
The latest firmware is 1.51A as opposed to the stated 1.50A so if you’re on 1.50 you could back up your projects and then update to see if you get any improvement?
Seems stable to me but, as with you, I haven’t spent any time documenting issues or adding them to the official thread.
Particularly with midiclock out, I’d test this with a variety of gear on both sides (ie digitakt to different gear than what seems late starting, and different clock to that same late starting gear) as I find elektron gear and digitakt specifically to be pretty steadfast in this capacity.
Where are you hearing the track volume drops? Right out of your headphones when using the machine standalone? Is it possible you’re pattern chaining and then manipulating parameters in real time so that the altered parameter is still impacted when returning back to that pattern?
Not positive what you mean about effects sends decreasing in input, are you saying the amount of the effect (example delay) that you dialed in, is reduced? If it was applied per pattern then it could be similar to what I described before, but in single patterns unless reloading, I don’t think it would be a problem.
No I didnt. I have been working away of late. I was using a simple DT1 midi out to Microfreak setup just before I left, which is where the issues seemed to occur, but the testing stopped as work began!
The DT1 seems to do some other weird stuff, like pushing all its controller data values out when the sequencer is stopped and restarted. I was recently using it with a Nord 3P and every time the sequencer was stopped and started, it resent all its controller data to the 3P which totally messed up the sound I was working on. I am going to start using the 3P with a midi controller to see the difference as I am certain it wont push anything to midi.
That’s pretty weird behavior, does it do that with any other devices or just the 3P? I know you can’t do it now, but will you have access to a midi monitor either in software or can you get an app? We’d want to see what DT is sending that’s causing that to occur. If it can’t be disabled, maybe there’s a way to filter out whatever it’s sending.
Anyways, bummer that it’s not working yet but something might be going on that’s just not right in front of your face, might be able to figure it out given some time and a little more info. Just wanted to check back with you and see if it was still wonky.
No I’ve not tested it with any other form of controller yet, but I’m going to do that when I’m back. DT pushes the current controller values when you press play, which means if you’ve been editing the 3P and not saved it, the sound is gone.
I’ve got a Bitstream 3x I’m going to try it with next week.