I recently upgraded to the Digitakt MK2. When loading samples there is a significant lag when loading certain ones. I never experienced this with MK1. Samples would load instantly. I’m adjusting, but it messes with my workflow when scrolling through.
Has anyone else experience this?
I assume mono samples are the same as digitakt 1
Stereo samples … well it’s too obvious to point out why they might take twice as long to load.
3 Likes
How long are those samples?
My DT2 live sets take about 60-90 seconds before all the samples are loaded.
I can’t really tell what’s going on in your video so apologies for that but if it seems like the longer load times on certain samples is not the expected behavior, then something you can do is make a list of the samples that are taking longer to load, then look at them on your computer and write down the specific file sizes. Once you have a list, load those same samples onto the digitakt II in a new batch (to make sure there wasn’t anything wrong with the original batch upload) and load them internally into a new test project. I would also create a second, lower quality version of the same samples while you’re on your computer which you can include in the same batch upload as well. This will serve as your test group so make sure you name them all accordingly and that way you can keep track of them (eg TEST1, TEST1B, TEST2, TEST2B, etc).
Within the project, load the smaller sized file back-to-back with the larger sized duplicate file and if they load at the same speed, then there might be a problem with the original project or files that are currently on your DTII. However, if in the new test project with the reloaded files and duplicate “lite” files for the same samples you see a behavior pattern which confirms that the larger files take longer to load, then the answer is that nothing is wrong, larger files just take longer to load.
Generally speaking, digitakt or no digitakt, larger files with more data just take longer to load on most devices, but it doesn’t hurt to confirm the behavior, so that you aren’t simply guessing about whether this is expected or an exception.
It doesn’t mean that you have to like the answer you get, but if it means you can stop worrying about it then that’s probably as good of a resolution as one can expect, and beyond that if you do notice something is inconsistent then it can be reported to elektron more coherently so that it can be validated as an issue and added to the fix list.
Thank you so much for that well written advice. I’m going to play around more
These are all Factory samples
1 Like
I’ll have to check each one.
These are Factory samples that came with the machine