it loads as well.
Btw while testing this, menaged to delete all my kits 
Well⌠need to start all over again. Luckily i wasnât happy with them
2 Likes
Same problem with kits
I can save them, but they load with sample slots messed up, usually the way init kit is configured (1st track - sample slot A2, 2nd track - sample slot A3, e.t.c.)
Other sound parameters (filter, effects sends) are fine
Factory kits are fine too
Reformatted +Drive, factory reseted, no luck
3 Likes
So, when you save on firmware 1.10 you get a working kit, but samples arenât in the slots you expected ?
EDIT: OIC. There is a bug. It doesnât save the samples you created in tracks 1-16, instead it treats sample slots A01-A16 as the kit and saves that instead
Yes, exactly the sample. Kit Save has a bug.
Have either of you emailed support yet ?
3 Likes
Yes, I did report to them.
Moreover, I reported an another bug I found after too, I recognized after this update is that when you go to sample pool and press func+yes which supposed to take you to the location of the sample on which you pressed the mentioned shortcut, it takes you to the location of the last sample uploaded to the pool but not to the location of the sample on which you pressed the shortcut. Which is quite annoying and time wasting.
6 Likes
Hm, i just checked this and it takes me to right location.
Maybe i am doing something different then you. In SRC i would open sample pool and hit Func+Yes and it would drop me exactly to that sample in proper folder.
Tryed few different samples in different folders and each time it did it right
1 Like
Itâs not even that ⌠seems like âkit saveâ is hardwired to save the samples you get when you initialize a project, no matter what.
2 Likes
Yup you are right, now it doesnât work. Confused
1 Like
It worked when i turned it on, with samples already there. As soon as i imported new ones stopped working.
Thatâs a bummer, probably one of shortcuts i use the most
2 Likes
I donât know if itâs a new bug from 1.10 but today I encountered a really strange behaviour while sampling.
When you tap stop multiple times while recording, the recorder head jumps to random places and even overrides recorded parts
Digitak 2 nrpn values acting as on /off intead of smooth interpolation after upgrading to 1.10
Has anyone noticed the nrpn parameters acting as on / off switches after the upgrade?
I use nrpn to control the ecluidean sequencer, before upgrading my midi controller (Firefox ec4) work perfect to select the number of pulses, now it just goes from zero pulses to full page. I tried my midi setup on a blank project and it acts the same way. Any help is really appreciated.
Luis
2 Likes
Yes I encountered it today, I have edited one of the 16 tracks sample slot saved then reloaded and that one edited track reverted to the previous saved state that I had before the update to 1.10.
Edit: the reverted itâs sample to the previously saved state I had saved before the upgrade to 1.10 but all the Amp,Filter, FX etc saved and reloaded correctly.
2 Likes
the new feature âadd parameter locks to all active trigsâ doesnât work on midi tracks
4 Likes
Parameter lock all trigs does not work on MIDI Track? just want to confirm if this is the case . I couldnât get the new parameter lock for all trigs on page or track feature to work on a midi track.
I can confirm the following bugs (reported by users above) on Digitakt II OS 1.10. A fix version is in the works!
- Save Kit doesnât save the correct slots (@bibenu)
- FUNC+YES when browsing sample slots doesnât always go to the correct sample location (@axiombreaker)
- Add p-lock to active trigs, doesnât work on MIDI tracks (@gm)
28 Likes
Sample files uniqueness/hashing bug, but its transfer not DT2
I think Iâve found a bug related to file hashes (detecting file duplication in other words). I create a project with sample file from a mix of folders (mine, not factory). Back up the project with transfer. Reorganise and delete some of the files used, then restore the project with transfer, restoring missing files, and opting not to restore identical files.
Then I know that I have all the files needed by the project, no duplicates on the plusdrive. This worked fine on firmware 1.02. I even recommended the process to someone a few days ago.
On firmware 1.10, it kind of works, but itâs not always detecting duplicates, so I sometimes end up with duplicated files, one in my project folder (because transfer thought it was missing) and one in the original folder location.
Did the hashing method change between firmware releases, I wonder ? Even then, Iâm not sure that accounts for what Iâm seeing.
EDIT: I will dig into this some more, try to reduce it to a simple case I can reproduce and report.
Anyone else seen anything like this ?
EDIT: Now noted in transfer bugs thread with simpler explainer
EDIT2: Now emailed to support
1 Like
not sure if this is a bug, but with Overbridge mode ON , analog outputs will create loud static noiseâŚ
Trying to wrap my head around the 1.10 ânot saving new samples in kitsâ bug because just about to go on a two week holiday. Planning to bring the DT2 with me but this bug seems, if I understand correctly, make it impossible to correctly reload any new kits created on the device?
If you created the kit did a âkit saveâ on 1.10, yes, those kits appear to be broken. If you created the kit prior to 1.10 then those appear to load and work fine.
1 Like
Yes, but only with kits created after 1.10 update
Also thereâs a workaround
Just save a kit via âManage kitsâ, it will load just fine
5 Likes
Nice, I didnât know that. 
2 Likes