Thanks for reply!
I bought my DT2 in May last year and can’t believe that this is what we are dealing with, almost one year in! How is such a major bug even able to slip through?
FFS
Thanks for reply!
I bought my DT2 in May last year and can’t believe that this is what we are dealing with, almost one year in! How is such a major bug even able to slip through?
FFS
To be fair to Elektron this bug has only existed since firmware 1.10, not for a whole year.
But, yes, it’s a bit of a disappointing QA failure, TBH.
I was wondering the same. It’s possible a last minute change caused it to sneak under the radar but I don’t really know, just guessing.
Somehow this one got by me. I have a lot of praise for the team after fixing up some longstanding bugs, but I really wish the MIDI features were treated better than a second class citizen on the DT2. I’ll be testing this release more thoroughly.
I had no choice but to take my sound pack offline for the time being. After the 1.10 update, sounds (that were not already on the digitakt) seem to be transferred properly (including samples), but when you try to load the sound into a project, the corresponding sample is not loaded. As I said, this only applies to sounds/samples that were not already present. I tested this by creating a sound … transferring it to the computer … +drive formatted … sound back to the digitakt. Behavior as described above … 2 customers can confirm this behavior.
For you to test:
ELMYSTRA.dt2pst (5.6 MB)
Sounds quite like the ‘kit save’ problem above. Because ‘kit load’ worked for old (saved pre 1.10) kits, it easy to figure out that the if the kit load worked, the problem was with ‘kit save’ … I can’t figure from your description if the problem is really with preset save or preset load.
Looks like it failed to load into the project on 1.10, in that the preset ‘BassDrone E01’ did not load the expected sample. However the sample was there on my plusdrive,
and could be then used with that preset.
EDIT: I’ve discovered that presets I made on 1.02 work fine when loaded on to 1.10, so it may be that this is a preset save problem like the kit one. Paging @ThomasJ
As more of a SAAS developer I’d love to have a internal view of how these embedded platforms automate any of their workflows/overlapping scenarios or fuzz their interfaces.
I know a lot of it does come down to necessary manual testers, and they’re always going to be slammed with working out matrices.
The above functionality does not work correctly for me on 1.10.
I have pages 1 and 2 filled and when I extend to 4 or 8 I only get page 1 on all pages. I created the project on 1.10 as well.
Does anyone else see the same behaviour?
For me, it works like the manual says. Same page setup across all tracks.
It doesn’t work if it was a longer pattern and you recorded steps on later pages then shorten it then lengthen it again. If you get what I mean!
When switching the euclidean sequence into a permanent sequence by holding function and turning euclidean off, the unit bugs out and kinda freezes, a couple seconds pass before it locks the sequence in, and the metronome stops flickering during this time.
I haven’t seen this happen yet - what I did notice is that the freeze confirmation disappears behind the more generic “Euclidean mode off” message too quickly to be meaningful. Is this behavior you describe during playback or when stopped?
Further investigation suggest that all the trigs are copied to all the pages on some tracks. Maybe connected to the machine type (grid machine in my case). If I create a new pattern (stock sounds) it works as intended. Must be something with this pattern I am working on that messes things up. All my copies of this pattern reacts this way.
Do you mean that if you lenghten and then shorten the pattern the intendend functionality breaks/introduces the bug?
It means it’s a one time thing upon its setting. So in your example, the reason it is only copying page 1 is because that is the one you initially mirrored to 2. If you start a new project with 2 pages filled (manually), then extend, it will mirror 1 & 2 to 3 & 4 respectively. If you start a project with 1 page filled, then extend to 4, it will mirror 1 to 2, 3, & 4.
Yes exactly. Sorry was in a bit of a rush before.
But yes I think its not a bug.
So if you extend a track it will copy steps but only if you haven’t already added steps on later pages.
It actually remembers the full track sequence even if you shorten it.
If you do want to overwrite every page then you have to use page and copy then to overwrite later pages if that’s what you want to do.
Or set auto-copy (or whatever its called) to ‘off’ in settings. Which is what i do, as the auto copy when i extend a pattern’s length is usually unhelpful to me
Do you copy each track from the pages you want to the new page? It’s not possible to copy a page with all the tracks data at once as I understand it, right?
PAGE + COPY (then PAGE + PASTE) if you want to do that