Bit of good news, elektron support responded to my ticket about the perform mode bug and said they have a fix for it, so that should be good in the next update 
9 Likes
Anyone else tried recording a sequence into their daw for a few minutes - straight audio in, no midi in/out involved - and notice that it slowly goes out of time?
For example. Bpm is 120, I record it into the daw that is also 120. I line up the first hit (kick for example) and then once you get a few minutes into the recording, it is now off grid and everything is hitting to early. It’s like the internal tempo has sped up slightly.
I have reported this to support with audio examples and screenshots. Not heard back for a while now. But just wanted to see if anyone else noticed this while I wait to hear back.
In amp settings on a Single Player machine, I can’t select a release time of 72. The value skips from 71 to 73.
Same here.
I just had my first experience with p-locks (on trigless trigs) not saving correctly. The trigs were there, just without p-locks. On a single player track. I tried various workarounds:
- copy pasting to new pattern
- saving to new project
- deleting the trigs and p-locking them again
The last one saved correctly.
Buzz kill, spent my time doing that and now I have to go to my day job. Will report through the formal channels
1 Like
Two findings regarding sampling:
1.) When creating a long sample (1 or 2 minutes minimum) using resampling, it sometimes happens that audio data in the saved file is missing from a certain point onwards and only silence remains. In this case you have to reboot the TV and try again.
2.) Normalization sometimes does not work after sampling or resampling. In this case, the level of the sample is not increased or left unchanged, but reduced to a barely audible audio signal.
They need to get the issue of projects losing elements, p-locks, trigs (the whole lot) at what seems to be purely random from my experience at least sorted. Nearly every power cycle or save is missing components on my unit and it’s hit the point of it being unusable until it’s fixed. I get the argument of making do without on a product that’s a straight synth like pre-preset era, but this is a product built around a sequencer. When that core component can’t reliably hold onto the information it’s been fed what is genuinely a great workflow experience is quickly a nightmare. At least some comms from them addressing it would be helpful so we know how long we might be sticking our TV’s on ice for, anyone had any updates from them on their support tickets?
3 Likes
Removing parameter locks by clicking the knob for the lock isn’t working
1 Like
P-lock for LFO Mode = TRIG not triggering LFO on a step 1 trig. Digitakt 2 for comparison
1 Like
Anybody know when the midi sync fix firmmare update is coming? Loving it but looking to really start putting this thing to verk
Have you set the Play Mode to POLY M.LFO or MONO in Setup? If you don’t do that, the LFO will only reset 1 voice of an 8-voice cycle.
1 Like
Yes, play mode was set to Mono
There was a post somewhere that mentioned they were trying for October
Found a bug, if you copy and past a pattern it pushing back the HP.MON parameter from 0 to the maximum. Also If you recall the pattern it also pushing back to the maximum. Doesnt make any sense
1 Like
Im using Tonverk all outputs (3 stereo) connected into an Audiofuse 16rig. Kinda a problem that previewing Subtrack kits and Multi samples, you only hear them thru Mix AB output. For me it would be logical to hear it on the output its assigned to
1 Like
Just tried it here, seeing the same as you.
When I send program changes from TV to DT2, the change occurs one pattern after the TV changes
Has anyone else noticed the encoders randomly jump around by one or two degrees? idk if it’s a software issue or my encoders are faulty
yes, did notice this before I returned.
mine was very obvious because the main volume encoder would turn itself and pop the big pop-over on top of the UI while I wasn’t touching the machine
2 Likes