-First. I have two different audio input set in R and L mono mode. FX apply intermittently on audio in. They begin working but after a while they stop being sent to the FX block. Only a reboot fixes it. Notice it works slightly better if only one input is been used.
-Second. Related to this, there CC control for send FX on Audio In only for the Left channel but not for the right channel when used in modo mode.
If anyone is having the same problem, which reddit suggests they are, the solution is to change Param Output from CC to NRPN in the midi port config. Apparently they ran out of CC addresses on Digitone so external pattern mutes on it are only accessible through NRPN or whatever. It works now.
I noticed the same issue about inputs not being send to fx.
An other issue I had with inputs is when itâs set in stereo and I change pattern, itâs sometimes send all the sound to the left. To get back the stereo, I have just to put it again on mono and then on stereo again, and it works.
It the inputs settings change from a pattern to an other, it sometimes need a trig from en audio track to let the external sound go to the master. Maybe not a bug (this is similar to the thrumachines on OT) but not logical to me.
In step rec mode, the green step is often stuck at the same place after recording data. The only solution to repair it is to reboot the device.
I sent a ticket already, but wanted to share here to see if it happens to everyone:
On track 2, if there is a sound with arp, when I switch patterns it stays there. Same sound and arp. It doesnt load the sound of the new pattern that is running. I had to restart the unit many times during live gigs to solve this. Completely unprofessional.
Still unsolved, the issue of transposing without showing the semitones on the screen. Happens with track and pattern transposition. I had to abandon this trick in my live sets, which is sad because it is an amazing musical effect to transpose 2 semitones the whole pattern and then back.
Very easy, just transpose a track or the whole pattern and look at the top of the screen. The semitones donât show (this started a couple OSs back, it was fine before that)
Has happened a lot of times during live gigs, itâs difficult to replicate in the studio, but for sure the people from R&D must have a clue on why this is can happen.
The semitones not showing up thing was fixed for me in the most recent firmware. It always shows correctly for me now.
I did have a hard crash (weird behavior for a few seconds, then high pitched squeal) yesterday that occurred when I had an arp on track 1, and track one was also set to trigger track 2. I turned the arp on on track 2 and thatâs when it got weird and crashed.
It is still not working ok, the semitones thing, see attached video. The numbers dissapear when you transpose and have a small lag to appearing again. This didnt happen in older OSs. It is impossible to quickly reach the transposition you need without knowing where you are.
Thatâs not right, in previous OSs you could ALWAYS see the number of transposition. Just like you see any other parameter you modify. There are no blank moments.
Okay i was incorrect. Just updated to 1.40B from 1.40 to test this.
Flashing seems to be normal and is there while you hold track button after you transposed up/down.
I assume its there to indicate that you havent changed to that value yet, while the track button is held.
I have the same behaviour on the device as shown on your video, and there is no lag in changing the pitch. Even if i transpose while the number is gone, it still goes to the desired transpose value instantly.
I can see why its confusing tho, number is offscreen 50% of the time, and it can be difficult to do fast transpose in the middle of the show.
I think its a valid observation and that we should create support tickets to have it changed to something more readable.
This crash is a bug that Elektron acknowledges and hasnât been able to fix (there are Elektonauts threads describing why/when it happens). It would be really helpful if people who experience this crash submit a bug report, to help get it fixed.
Exactly!! You are right, I hadnât realized it was -intentional-. But it was a bad idea, it is very confusing, i need to see all the time where the semitones are going before releasing the button. Thanks for the insight!
It could be that there is no trig on track 2, so the sound of the new pattern is not loaded.
Try to do your pattern change with a trig set on step 1. And report.
This kind of comment is best avoided.
People here are helpful and friendly, but they also know that a lot of bugs are user error, so disdain gets in the way. And makes the place less comfortable for everyone.
I understand the frustration though, weâve all been there.
Best attitude is to look for a clear understanding of how the gear works and using it for what it can do.
Of course you can always reach Elektron support to declare a bug, or even ask for some change once you know the machine pretty well at feature-request@elektron.se
Hi,
can anyone try it please:
My Digitone does not responds to midi cc 77 (filter envelope depth) - it does not show the tweaking in the interface nor is it audible.
Other ccâs like filter, resonance, amp lvl, drive, panning & co seem to work for me.
It happens with trigs anyways, Iâll try to replicate and send a video.
The âcompletely unprofessionalâ was referring to the live performance not to the Digitone. The audience might think that if they see you having to turn a unit off and on again and doing weird things with stop and play all over your rig since the DN is the clock source. The artist looks unprofessional. Sorry if this sounded too harsh for the forum, my apologies.
Iâm having some issues with HLD mode and negative values for Fade (fade-in) on the LFOs. Hold isnât latching, same as a free-running oscillator. Except sometimes it doesnât run at all. Once in a while, it will work correctly, but usually it wonât.
Fade-ins arenât working. I noticed this in conjunction with the HLD mode. Iâm not sure if there is some relation between the two. Again, sometimes it works, usually not.
Im currently playing the arp into a track with Live Rec mode set to unquantized. The arp latches onto the beat nicely as I play the notes slightly ahead of time to âcatch the gridâ and it all sounds cool as I record. But playback is a total mess. It turns out that although the arp latches onto the beat during live recording and live playing, playback of the recorded arp seq doesnât latch to the beat, so the arps start immediately at their off-grid location. Is this a bug or just a âthatâs how it isâ thing?