i understand that they are but there’s no word on when or how this will be resolved - that bus may have passed until the next one, it’s hard to know when updates may come, unless something is considered critical
Just tested with a powered USB Hub (see link below). Audio stopped within 5 minutes. Tested with the steady drone and with a synth being sequenced by the Digitone.
This is the hub.
I have another powered hub I can try but the one above I’ve used with a 2nd Gen. Focusrite 2i4. No issues. Same with a Steinberg UR44. I haven’t tried with the Analog Heat MKII.
I found a behavior that before the update didn’t exist
With the new update it’s like the enconders are ultrasensitive, and example would be, if you push down the encoder really fast to reduce the entire reverb send instead of keeping the value of 0, it jumps around to a different value. It’s like the machine has more room to detect the moves of an enconder when you are releasing it, I don’t really know how explain it. It doesn’t happen all the time but enough to annoy me.
I only tested on the DT, i don’t know if the DN it’s working like that too
it is and it has been mentioned - it seems to affect value display and on occasion the value when the encoder is still rotating when the press is released - it can be disconcerting to turn the value down to 0 and see it temporarily appear to raise back up a 1/3 of the way - i think it is undesired/unexpected behaviour
Anyway - this is a DN bugs thread, but presumably this will be mentioned in the latest os DT bugs thread
1 Like
Wow sorry, I had a lapse, and i thought this was the Digitatk - Bug Report Thread.
Anyway I hope this will be resolve
2 Likes
I think I have the same issue as you: I’m using a few modulators in Bitwig on the OB DN plugin and it just takes two, maybe three of them (LFO, ADSR) to basically make the DN unrespsonive. It will either crash out entirely, or lock up. If I remove the modulators it will sometimes recover, but mostly it needs a full restart. Very frustring: I’d love to control as many parameters as I see fit, and having it lock up after even just 1 or 2 seems…terrible.
2 Likes
Found some issues with the “Poly (Mono-LFO)” voice mode that seem quite buggy.
With the LFO in “Free” mode, it works as expected, all the voices use the same LFO modulation which is great. However, all of the other LFO modes (which are triggered) seem to be buggy, seemingly because the “LFO Trigs” are only having an impact when a certain voice is triggered. It seems like “Poly (Mono LFO)” mode is only utilizing the LFO from a single voice (which is as it should be), but it is not routing all the LFO trigs to that LFO, so many of the LFO Trigger events have no impact.
Take, for example, “Hold” mode: My expectation, as a user, is that in “Hold” mode the same LFO should be sampled with each new LFO Trig, so that the same modulation signal affects all the voices equally, while the sampling occurs with each new trigger. What ACTUALLY happens, though, is that the LFO valued is not sampled on every trig - it’s only sampled when a certain voice (I assume the one the LFO is originating from) is triggered. So if you have a sound with “Poly (Mono LFO)” voice mode, and a “Hold” LFO, and you play a melody in, it’s pretty random when the LFO will sample a new value since the trigs are not happening on each keypress, but only on keypresses which trigger a certain voice.
The same issue goes for the other triggered LFO Mode - with “One” , and “Half” , modes, I would expect that all voices share a modulation signal from one LFO, but that the LFO/envelope will be triggered with each new trig, not just when one of the voices is triggered. I’ve not thoroughly tested “Trig” mode yet so I’m note sure if it also behaves this way but assume it does based on other mode’s behavior.
Hopefully this makes sense, it’s a bit of a let down since I was quite excited about this mode but it doesn’t seem to be working intuitively 
1 Like
i’m not entirely sure why you suggest it’s a bug when you measure it against intuition - having said that, it’s my estimation based on intuition that it’s working as i expected it to - the modulation phase is set by the first voice, say the first note in a triad - i don’t see any other way to anticipate what happens when you add to that note than to imagine the next notes take on the same phase - there is no trigging of the LFO, that would be potentially messy
you want the LFOs with a trigged phase component to adjust for every successive note, whereas the LFO die is cast when the first note is held
maybe you could ask for an additional mono with reset mode, but it doesn’t seem buggy or a bug to me - this is evidently what was intended - whether it follows convention or not (or each user’s expectation) is another thing
a resetting mono mode option would still be welcome but i think they went the right way, it’s more akin to a legato mode - it all happens on the first note down, that’s when the LFO is set, feels quite musical to me and it avoids obvious/jarring lfo phase jumps when notes are added - ymmv
1 Like
Ya, I’ve noticed this one too. It’s a little disconcerting.
Running into an issue with midi tracks. Example, if I am editing trigs on page 2/4 on midi track 1 and switch to midi track 2, it resets the page to 1/4. I believe in the past it would stay on the same page when switching between tracks. Can anybody else test this?
I’ve also experienced the audio drop outs using class compliant mode.
I tried using it with Ableton Live on my 2011 MBP. It’s a fairly light project - Digitone Keys stereo in, a few effects and Drumracks returning, using the DK as monitor outs.
The audio just stopped after 15-20 minutes playing. Restarting Ableton got the audio back for another 10 minutes or so.
I’ve repeated it a few more times, the audio always stops eventually.
The same project plays fine using the DK as sound card in Overbridge mode. (I’ve not tried using the plugin).
Thanks for this response! You’re right, I didn’t make the connection that the poly mono lfo mode was working like legato, based on when notes were overlapping sharing the same lfo! It’s a really good implementation actually, wasnt able to grok it because I was using a track with lots of overlapping trigs so the lfo trigs seemed to be happening randomly. A mode which does a lfo trig every note event could still be interesting as an alternate mode, but as it is the implementation is fine actually. Thanks for clearing that up!
1 Like
Experiencing the audio drop outs in class compliant mode as well. Using an iPhone SE with AUM, everything works perfectly until audio stops streaming to the Digitone after a while.
Note, Digitone is still streaming audio correctly to the phone in the meantime (I got a usable recording). Unplugging/replugging the USB cable fixes it.
1 Like
Soundlocks don‘t play past another soundlock - sometimes!
Also will sometimes the track filter change a soundlock’s filter.
My DN just died on me… hopefully it just has a flu and only needs some rest and is okay tomorrow.
2 Likes
Don’t know if this has been mentioned but, when recording notes whether it be on the trig keys or on a midi keyboard, it’s not saving the length for how long you hold then down. Instead they all default to whatever you have the length set on the trig page. It’s a pain in the ass and makes it tedious to be locking each step length instead of just recording it on the fly.
3 Likes
it works for me, it works on the internal mini keys and it will only work like those (for all recording modes) on an external MIDI keyboard if that keyboard is set up to transmit on the Auto Channel of the Digitone - using the Track channel is creating your issue - quite why it isn’t working for you directly on the device i can’t comment, check again
1 Like
I haven’t had much time with the Digitone recently, but I believe this is related to the behaviour mentioned higher up in the thread, where if you don’t release the key before a new trig (or a pattern end?), it’ll just use the default length.
If I find the time to test this I’ll update this post, but I’d appreciate more eyes on this!
The combination of these two behaviours really makes DN a lot less valuable to me. Add to that its idiotic filtering out of MW/AT etc on the thru, and my setup just doesn’t work as I’d imagined it would.
I filed a ticket with Elektron on friday and gave them the repro steps and they wrote back yesterday that they might have found the issue and hope to have a fix soon.
2 Likes
I submitted a report with Elektron already, but I figured it wouldnt hurt to see if anyone else encountered this with the current Digitone firmware:
When modulating a CC parameter on a MIDI track with the LFO, changing patterns effectively breaks the LFO and functionality of the CC control on that track. After that the only way for the LFO and CC parameter to work again is by restarting the machine. It makes using a MIDI LFO too unreliable to be worth using at the moment.
2 Likes
Did you switch the power to on but not get past the tip point in the rocker switch, so it was very briefly switched on, and then have to flip the switch back to on after it returned to the off position?