Digitone 1.2_ bugs discussion

The muting combo itself isn’t sending anything. Watching a midi monitor when muting, the OT isn’t leaving any hanging note ons. Everything has a corresponding note off. Looks more likely that the OT isn’t the problem here.

1 Like

I isolated the issue. It has to do with the order in which steps 4 and 5 of the original post are executed. To summarize, if the DN record button is pushed to stop recording after the first recording pass, and BEFORE the external midi sequence is paused/stopped, then you get the deletion/yellow trigs on the next DN recording pass. If the DN record button is pushed to stop recording AFTER the external midi sequence is paused/stopped, then no bug.

1 Like

I think I found a bug.

Someone has experienced probles when removing several trigs at the same time? I can create them but when I want to remove them I have to do it one by one…

A possible bug involving the new arrangement for sending Bank Select messages in OS 1.20 is under discussion here:

1 Like

Not completely sure but I think now when, for example, I create 4 triggers at once it´s ok, and when I try to remove them, maybe only 2 or 3 are removed.

There seems to be a conflict with the new Reload Track Sound (NO + T1-4)…as during live record that is already used to clear trigs as the sequence is playing. I tend to use this a lot so it’s pretty annoying to keep accidentally reverting a sound I’ve been tweaking.

1 Like

Yes this seems indeed to be a bug. I will notify our firmware developers about this. I tested, and if you press T1-4 + NO (In that order) then it will only remove the trigs (in live record mode) and not reload the track sound. Still, that NO + T1-4 does two things at the same time is obviously not the way it should be.
Thanks for the heads up.

6 Likes

The mod wheel, pitch wheel and aftertouch doesn’t work after I updated. I don’t know if it’s only in overbridge mode or in the other mode as well. I can’t check it because I’m not home for the moment. Is this bug reported to elektron?

I’m using Digitone together with an Arturia Keylab 49.

2 Likes

The new control all revert feature only reverts the current page and not every control-all tweaks on several pages. If you keep holding the MIDI button and go back to the different pages you had been tweaking and press NO they will revert to their default state but actually not fully on some tracks. I have experienced a few times where some tracks did not revert fully.

It would be great to have this fixed and have this new function revert all Control-all action.

(Func+No reloads the pattern fully and tracks may be muted so it’s not the same)

This. Saving project with FUNC+SETTINGS turn on the mute mode, then you need to press FUNC again to exit.

Noticing a velocity bug when using aftertouch.

Doesn’t happen all the time but I’ve been able to recreate it sporadically using a specific work flow. Soft velocity note on and apply aftertouch. Sometimes after releasing key, the velocity will be stuck around that level. Meaning hard or soft hits will be noticeably quieter. To fix hit any key hard and apply after touch. Volume will spike back up…

Some Plocked steps don’t flash, while others do. Seems totally random.

Aren’t sound locks flashing?

Yes, but not parameter locks. That’s not normal is it?

Just a wild guess: can you set a lock trig (yellow) which doesn’t actually contain any locked parameter?

Because:

The [TRIG] key of the locked trig blinks red (for note trigs) or yellow (for lock trigs) to indicate the trig now contains a parameter lock.

… sound like it’s blinking yellow when there is an actual parameter locked (compared to a lock trig without a parameter locked).

Erm, not that I know of?

Is that a line from Inception? Haha.

It’s from the manual section where it gets explained how to set parameter locks.

  1. Press [RECORD] to enter GRID RECORDING mode.
  2. Press [TRIG] to add a Note trig or [FUNC] + [TRIG] key to add a Lock trig and to where you want to perform a parameter lock.
  3. Press and hold the [TRIG] key of a previously placed trig (note trig or a lock trig).
  4. Turn the DATA ENTRY knobs that control the parameter you want to lock, and set it to the desired value. The graphics become inverted for the locked parameter, and the locked parameter value is displayed. The [TRIG] key of the locked trig blinks red (for note trigs) or yellow (for lock trigs) to indicate the trig now contains a parameter lock

So it seems you set first a lock trig (2) and afterwards lock a parameter there (3 + 4).

But when you stop after (2) then you have a lock trig (yellow) without a locked parameter which will not blink.

Hi all. Not a bug from 1.2, but a bug from earlier versions that ive noticed is still in 1.2:
I have a arturia keystep going into my digitakt, whos midi out then goes to my digitone. I then use a midi track to forward the midi output from the keystep, through the digitakt, to the digitone.
So here is the bug: sometimes when I play a note on the keystep, the adsr of the currently displayed page, for the currently selected track on the DN all go to 0.
For example: I select track one, and go to the filter page. Upon playing a note on the keystep, the filter envelope a, d, s, and r all go to 0.
Few notes:
-i have not figured out how to get this to happen reproducibly, but it happens frequently. I am ~90% sure it only happens upon switching tracks on the DN, and then it seems to happen maybe 10-20% of the time.
-ive only notice it happening to the adsr of the filter page, and the ads- of operator A on the synth2 page. I havent had it happen to the adsr on the amp page.

  • i have not tried with another midi controller, although im not sure if this would make a difference, since i am assuming only the note data is being forwarded from the DT to the DN.
    Anybody else notice this issue.?

Make sure you have set ENCODER DEST to INT (and not INT+EXT) on the Digitakt.

Otherwise it will send CCs when you operate the knobs which will modify parameters on the DN).

After updating the Digitone all arps are being set to off and a speed of 1/1. This may have been caused by Overbridge, it’s been acting very strange with arps in general.