4 posts were merged into an existing topic: Digitakt out now!
- when you turn the level/data encoder while holding a trig button, like trying to dial in a p-lock, the unit says lock-memory full. (???)
Forgive the repetition but I just need to voice my frustration about the encoders. Some settings, notably sample play mode, are just ridiculously hard to dial in the setting. Sample play mode the encoder travels with no response before skipping far too quickly past the options. Also sample selection menu scrolls far too quickly through the list.
I noticed this when I played with the demo unit at Superbooth and I just assumed that maybe that unit had taken a battering or something.
I know itās due to be fixed in next OS but I am slightly concerned it might be a lack of consistency in hardware issue, as I donāt see how anyone involved in testing can have thought this was how the encoders should feel.
EDIT: all this said, I must say Iām very happy with the Digitakt and I much prefer the simplified workflow vs Octatrack which I owned previously.
^ this is definitely a software thingā¦ just couldnāt get it done in time I guess
Hope so. The same encoder does seem to work fine for different menu items. Just needs some more thoughtful calibration of the responsiveness when scrolling through menu with 4 options vs menu with 127 options.
It sounds strange that they could mess the encoder behavior in software. As it happens when samples are involved, could it be that somehow Digitakt CPU canāt keep up with the changes the encoder is trying to do to the samples? If that is the case, it could be difficult to fix in software.
Weird about these encoder issues is that Cenk mentioned in several of the Superbooth marketing videos that the new encoders are better and more precise than the old ones. Kinda weird to be marketing the unit with that claim when the encoders seem to act far worse at the moment (I have never had issues with the encoders in my A4, they feel very precise to me).
yea I can see how it gives the impression of computery lagā¦ but really Iām 100% sure itās just how the software uses the information from the encoders. It seems to be a more complicated implementation than before.
For example, sample playback mode:
You need to turn the encoder with a certain speed above a threshold until it selects the next mode. Usually, you will end up turning so fast that you will skip a few modesā¦ this of course doesnāt feel right.
With the older encoders it was probably simpler, you could just advance one step on each tick received from the encoder, or something.
It just needs fine tuning.
If you power into test mode, you can move a little bar around the screen with the encoders and itās perfectly fine there.
5 Likes
same here
they confirmed already they are working on it until itās perfect ā¦ there will already be some improvement in 1.02
This has all been posted already. We need a list of bugsā¦
1 Like
I try to wrap my head around this buggy product.
Yes, it is lurkingā¦ definitely, butā¦
This is your third post with the same sentiment in this thread, itās better off in one of the other few general threads on perceptions of DT and its release
Letās leave this thread primarily for owners who are helping get the bugs fixed by reporting and discussing 1.01 bugs here, everything beyond that, especially when itās not even constructive, only adds to the noise and serves nobody
6 Likes
So we now have 1.02
Anyone try to upgrade yet? Release notes look encouraging.
Promising
Sweet 
and my DT arrived today, just in time for 1.02
1 Like
Just had a catastrophic failure with my DT for the first time. Running 1.01
Spend a half hour making a pattern in a new project with new samples. I was happy with it, stopped it and walked away. Came back 10 mins later to play it again and nothing, no sound. I look samples are still loadedā¦ did I erase the pattern, maybe, I try to make it again, no sound from the sequencerā¦ Is the volume off? Nope the tracks trigger just fine when I tigger them manuallyā¦ Some setting? Nope, no tracks will NOT trigger from the sequencerā¦ Did I mute the tracks? Nopeā¦I select several other patterns, and banks on the project, same issue, sequencer lights up, steps are selected, no sound.
I went back to the preset project and it works just fine. Another bank in that project works fineā¦maybe a bug? I went back to the new project, SAME problem. Project is broken.
All other operations are fine besides this broken projectā¦ What is the deal? Anyone else experience this?
UPDATE: just updated to 1.02 and the problem went away on all tracks of the pattern I was using EXCEPT track 1. Iām going to just delete the whole project and start over and see if it happens again.
1 Like
OS 1.02 is now available with many bug fixes.
For bug reports on OS 1.02, please post in the following topic:
1 Like
I contacted support and currently this is intended behaviour. Gah!
1 Like
Same, also in 1.02