Thanks so much!
I will definitely monitor the updates page more frequently so I don’t post anymore stupid questions!
1 Like
Not fixed, from what you said.
Did you write to support ?
No I didn’t. Maybe I should. I suppose someone from elektron’s team is monitoring threads on the forum especially threads about bugs and feature requests. One way or another they will know about the problems.
1 Like
I’m not sure you can necessarily rely on that. The information recorded in threads here is generally going to be much less detailed by comparison to a dialog with Elektron support.
3 Likes
Oh no, the DT2 just did this again in a new & different project.
Sampling then saving the sample to a track, results in the device going silent on all tracks - until you switch it on/off.
It’s not a huge thing, but along with the lack of mono support it’s starting to put me off sampling
I seem to have intermittent issues where send fx on external inputs do not work. Can’t replicate though…
Is it saving back to the same track that triggers it ? And which firmware ?
The delay, reverb and compressor (but not chorus) need to be triggered by an internal track to stay ‘awake’, so if you’re only sending the ext inputs through them, they can stop sounding. It’s a weird shortcoming that’s currently expected. You can use a spare track with sends enabled and a trig firing and just turn its volume all the way down. Should keep the effects active.
5 Likes
Also any time you double stop the sequencer(all the time for me) midi tracks will loose fx on restart unless one of the 8 audio tracks are pressed.
2 Likes
Cheers guys. Will look into those scenarios.
1 Like
Has anyone had this issue : I saved a kit with multiple tracks using the same sample in the sample pool. When loading the kit to another project, the sample is loaded multiple times into the pool, occupying as many slots as there are tracks using this sample.
So in essence, the kit doesn’t seem able to point multiple tracks to a single sample in the pool. This generates unnecessary clutter in the pool (and ressource usage)?
2 Likes
I’m having this exact same problem and it’s driving me nuts. I have to power cycle every time I record a sample.
1 Like
I have 1.03A and I still have this problem
same here
For some reason conditional trig [1st] just straight up isn’t functioning. It is triggering the first time round the master sequence length but that’s not how this trig has ever worked. Tried restarting but still works the same. Any other trig type will act how it should. Have linked a video. 1.03A
Hard to tell from your video.
At least plock pitch +12 on that trig…
So it triggers all the time, not once ?
I don’t know if this has been reported already but I’ve been having an issue since the update to 1.03 where my digitak 2 looses all audio and sampling capability.
Sequencer lights up and rolls arround when I hit play, but no sound plays, and the sampler screen goes black, I have to do an on and off to fix it…
Any reason why?
I’ve lost track of the definitive thread on this, but there was a bug where saving a sample caused the sound-engine to fail and require a restart. Bug was introduced by firmware 1.03, and fixed by 1.03A, although it seems that 1.03A (re-)introduced other problems.
Is that what you’ve got ?
Sounds like what I’ve been seeing, and a couple of others.
Cause unsure, but saving a sample & assigning to a track often causes it - but it’s not 100% reproducible
This is the main place that bug was discussed …
… and the fix notified.