I have an issue with delay and reverb on external audio inputs: When I start a new project and I want to start with the external inputs to play with, the delay and reverb don’t work. I first have to trigger one other track once and then the effects work. Chorus works directly from the beginning, only del and rev not.
After the last firmware update 1.10a the error occurs more often now and I have to trigger another track from time to time again and not only once in the beginning.
I think I’m right in saying your 1st para is expected behaviour.
2nd para may be a new bug … athough … do you ever press double-stop to stop loops/reverb tails. If you’re doing that, I would expect that you need a new trigger again.
That is expected behavior. When opening a project, or after double pressing the stop button, the delay and reverb are silent. They require a trig from an internal audio track to start. This is because the delay can have feedback settings which result in a runaway feedback loop, potentially damaging equipment/ears.
But how can that be right? In a live situation you cant just trigger something randomly while playing just to get the del and revon the inputs to work.
That would mean you dont have the possibility to start a liveset with an input signal. If this is technicaly not possible, that would sound strange to me.
Maybe I explained it wrong: Its not only on a conplete new project, but also when loading a finished project with del and rev on the inputs.
I edited my comment to be more clear, it is anytime you load a project, switch on the device, or after double pressing stop, those are the situations where the delay and reverb are silenced.
You could work around it by using an audio track set to 0 volume, either at the amp page or the overall track volume. Triggering that will start the delay and reverb without making a sound. If I were in your situation I might just turn the device on, turn the volume on one audio track all the way down, press the trig button for that track to start the delay and reverb, then turn the volume back to where it was. That will allow you to play external things into the reverb and delay without making a sound.
Yes thats a way it would work but its not my favourite 
Yeah, it’s not ideal in a lot of ways. But then again saving a project with delay settings that quickly get out of control with no way of stopping it can actually damage things down the line, so it seems like Elektron wanted to play it safe with delay feedback loops.
If I worked at Elektron I might try to convince them to automatically start the delay and reverb any time the delay feedback is below 100. Or have it look at the amplitude of the external sends to delay and reverb and have those be able to start the delay and reverb the same way internal tracks do.
Wow I just got a pretty gnarly crash with 100% repro (at least on my current project)
I’m sending midi on channel 9 from OT to DT2.
Channel 9 on DT2 is setup as a midi track which sends midi on channel 3 on to a behringer td3.
But track 9 isn’t setup to RECEIVE midi in the midi menu, I just realized…
However
As soon as the OT sends midi note to the DT2 the DT2 crashes!
I’ve sent bug report to official elektron support but I thought I’d post here too as I can’t upload screenshot to official support.
I tried on a new project but can’t recreate. Will attempt to recreate on NEW project.
Yes, this one has been found and fix is on its way. Sending MIDI notes on the FX channel can lead to a crash. Let me know if you want to beta test the bug fixed version. In the meantime - move the FX channel out of the way and it should work fine.
Oooooh thank you! Good catch, yup turning the fx channel to another channel resolves. Then turning back to 9 causes to crash immediately, so it’s defo that!!!
Thank you 
Just to report this random bug i got tonight.
I can’t turn off Trigger 9 on my dt2 for some reason.
Keep pressing it but nothing happens. Since i bought it everything was ok, so not sure if it’s maybe user error.
If someone had something similar let me know, and if i need to provide more details.
It’s only on one track.
After reboot it is working again as normal
Sorry for the super late reply; I’m not always active on the forums. I have not specifically tested your bug conditions, but @bibenu perfectly summarized why you also got a “like” from me.
Unrelated - I have discovered a new bug related to the sample trimming screen on the 1.10A FW. An Elektron support ticket has been submitted and I have a video demonstrating the behavior.
Behavior observed when triggering the bug:
Audio playback using FUNC + YES does not execute and no sound is heard when pressing the button combo.
Triggering the bug:
When a sample is loaded and the trim editing screen is active, the bug presents when switching the playback mode in the top right to the auto one shot mode (FUNC + YES playback without needing to hold the buttons). Move the trim point from the end of the sample toward the left (cut some of the sample material) and press FUNC + YES to playback edited sample to completion. Move the end trim point towards the right (adding some of the original sample material back). Press FUNC + YES and sample playback does not occur and no sound is output (this is the bug).
Workaround to get playback functioning again:
FUNC + YES will work as intended again if the sample trim end point is moved toward the left again (sample material is removed), or if the sample playback mode in the top right is changed to something else and back to the auto one shot mode.
I have not experimented with triggering the bug by trimming the beginning of samples yet.
Buckle up. A long one to explain.
I had this great idea to exploit some kit chains I have, wavs that have 6 evenly spaced hits from different instruments in the kit. Can’t do grid machine with 6 slices, so I figured I would make a kit of 6 sounds, all pulled from consecutive slots from a single wav file. Made and saved the kit no problem.
Loaded the kit to an empty project … and surprise, the DT2 loaded 6 copies of the same sample file into sequential sample slots
Loaded an empty project, pre-loaded the one wav I knew the kit used. Result: what I wanted. All the kit tracks used the single slot with the wav already in it.
Loaded an empty project, loaded the kit to the preset pool, then sequentially loaded the 6 presets to the 6 tracks. Result: what I wanted. All the kit tracks used a single slot automatically loading the wav file the first time.
Loaded an empty project, pre-loaded the one wav I knew the kit used, then loaded the kit to the preset pool, then sequentially loaded the 6 presets to the 6 tracks. Result: what I wanted. All the kit tracks used a single slot with the wav already in it.
Why-oh-why the inconsistency in the first case ?!?!
Does this rate as a bug or am I being too picky ?
Quick update -
This bug has been reproduced and confirmed by Elektron.
I also found this problem in 1.10A. It is a bug, but you can work around this by renaming (without actually renaming them) the tracks (save the rename) and then saving the kit.
Are you sure it’s 1.10A you have? I was pretty certain this was fixed in 1.10A.
Just to check … you definitely have on the boot screen “1.10A” at bottom right? Some people have mistakenly read the whole bottom line “A 1.10” as being “1.10A”
EDIT: Noted here for future reference
Thanks bibenu, that was the problem. I thought I had 1.10A 
, but didn’t. This solved the kit saving problem 
Version 1.10B is now out, fixing the issue with potential crashes when sending MIDI notes on the FX channel.
I am experiencing a crash on 1.10B, it can be easily replicated.
First, enter the Samples menu by pressing Func + Samples.
Next, choose PROJECT RAM.
Press the right arrow key to reveal the menu, and choose SELECT UNUSED.
My unit goes into a hard lockup every time I try to select this option. Can anyone confirm that their unit freezes too?
