Digitakt II: bug reports

My mistake for specifying the wrong bank for the PTN slots I will make sure to double check in future.

Glad the issue is being looked into. Just to clarify my understanding of how this should work

There is a list/enum with 4 entries “REV”,“REV.L”,“FWD.L”,“FWD”

a MOD depth of 1.0 on a Square LFO means the output is cycling between 0.0 and 1.0 this value is then added to the parameter specified in the MOD destination.

Starting on “REV.L” [1] with a MOD depth of 1.0 the expected behavior is it should cycle between “REV.L” and “FWD.L” indexes [1] and [2] respectively. (this with the assumption that lists are zero indexed)

Pretty sure all shapes are bipolar in the digis lfos. Meaning you’ll oscillate between +1.0 and -1.0 not 1.0 and 0.00

3 Likes

If the LFO is bipolar and the destination is a list you are restricted to selecting values either side of the one initially set. Lets test this with another destination that has a list of values.

Grid machine.
Slices: 4
Selected slice: 3
Mod Destination: Slice Select
Mod Trig Mode: Hold
Mod Waveform: SQR

tapping the track button to fire a trig and sample from the current LFO position, lets see what that gives:

Mod Depth: 0.01-0.99 , selects either slice 2 or slice 3
Mod Depth: 1.00-1.99 , selects either slice 1 or slice 4

Lets see if it works the same way for play mode. keep everything else the same set MOD destination to play mode instead of slice select.

with FWD.L selected, and the depth of the LFO in the range of 0.01-1.00

tapping the track button to sample the current LFO selection always gives FWD

Interestingly this is also true if the depth is set to -0.01-1.00 Edit: that’s not interesting the LFO is bipolar,

Edit: setting the depth to 0.01 and the initial condition to REV cycles between REV and FWD

Conclusion. The way the slice select is setup as a modulation destination differs from how play mode is set up as a modulation destination.

Yep, and this is not correct. The intention is to use the MOD depth on PLAY MODE just like it works on SLICE etc. And good thing is - we have fixed it and already have a 1.15A-BETA for it. So if you want to try it, let me know!

7 Likes

Any chance of DT1 beta? I reported it 2 years ago when it broke my beloved ping pong :smiley:

3 Likes

Anyone experience some crackle when cutting up a sample in the slice machine? Never had this before. Don’t know if i can reproduce.

sure, I’d be up for some beta testing :smiley:

Hi there,

not sure if bug, or just feature not yet implemented?

When in SLICE TRIG MODE and JUMP or STEP RECORDING MODE at the same time, the recorded trigs don’t take into account the slices at all.

Also fixed in the upcoming release :slight_smile:

9 Likes

clicks and pops at the start and end of slices? If that is the case you need to slice at zero crossings.

From the manual:

[FUNC] + DATA ENTRY knob E, H, and D snaps the start, end, and loop points to zero crossings.

No, it is definitely different. Sounds like the sample is not being read correctly.

at a guess, how are you getting audio out of the unit? listening directly on headphones/out L+R or are you using overbridge.

Headphones. I use the dt 2 a lot, never had this until the slice machine. But it seems that i am the only one. If it happens again, ill post about it again.

You guys are the best! <3

3 Likes

Yes, this will be released in a DT1 update too.

8 Likes

Thank you confirming, awesome news! :fire::fire::raised_hands:t2::raised_hands:t2:

4 Likes

NGL after hearing MOD>Play Mode in action I’m glad I didn’t listen to those who tried to steer the conversation towards feature requests and work arounds for what was a bug.

To be fair, I don’t expect anyone thought a 2 year old bug would be fixed.

What other long standing bugs are there that people assume are not going to be fixed?

I thought the point of this thread was:

The ‘pattern change one bar late’ issue.

EDIT: Here’s the most pertinent post

Maybe @ThomasJ can work his magic here too ? :wink:

EDIT 2: Also

2 Likes