I hope this meant they sent you one to try out in advance. 3rd party Digitakt II support on day one is nothing short of a miracle!
It’s gotten a bit quiet in hear, but know that your efforts in sharing this with the rest of us is truly appreciated!
3 Likes
Unfortunately not, would have been nice!
Elektron have never replied to any of my requests for details on file formats and such, I assume that’s due to it being open source and supporting manufacturers other than just Elektron.
Digitakt II looks to be a nice refresh though 
(and if Elektron wanted to send me one, I could cancel my order with Alto and save myself a few beans! I’m sure I can find room for a ‘Sponsored by Elektron’ badge on DigiChain 
).
5 Likes
hey @brian3kb, for the last couple of days, every time i use “trim right” the results are completely silent for all files. any idea?
Looks like a regression on the trimming - just pushed a fix to resolve, sorry about that!
Holding Shift while clicking trim-right will trim both left and right - there was a bug in this where I forgot to put the default 0 offset when not trimming right 
v.1.4.13 is live on the main, just give it a couple of refreshes to auto-update.
Two changes:
- Option to skip rendering of the mini waveform display in the sample list.
- Fix regression bug on trim-right selected action.
Previous versions are always accessible by just adding the version number to the end of the url, e.g. https://digichain.brianbar.net/1.4.11
3 Likes
Hi, I can’t get DigiChain to work in my system, 4-core iMac / OS 10.13.6 / 24 GB RAM / Chromium. I prepared 60 short 48kHz/16-bit wav samples (tot. time 1 minute) and successfully loaded them but when I click on the Spaced Chain button it gets stuck on “processing” for hours. I managed to chain 4 samples, nothing else.
Any hint?
Try doing 30 samples twice ?
15 samples … you get the idea
You can always join those together.
Thanks but anything more than 4 samples make the thing stall. It simply stays thinking forever, CPUs get busy too.
I was looking for an easy method for chaining 60 or 120 samples, equally spaced in time, to use in my Model:Samples.
Try another browser ?
Could you let me know the version of Chromium you are using, and if you wouldn’t mind sending me a DM with a zip of the samples your are trying to chain and I’ll take a look at them and try to reproduce the error with debugging enabled, try and figure out what’s causing the issue.
Are you simply importing the samples then clicking the spaced chain button?
Thanks!
Edit: actually, looking at your config, 10.13 is High Sierra, Chrome/Chromium v114+ isn’t supported on that OS version, Safari 16.3 also isn’t supported 
DigiChain uses some fairly recent Web Browser API’s/features that are not available in older versions. I will add some messaging on app launch to check for this so it’s clearer for those unable to upgrade that things aren’t going to work out.
If you happen to be running a patched Chromium version (e.g. GitHub - blueboxd/chromium-legacy: Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+ ) and still having issues, then please do still send me the files to test with to rule out a bad wav header/format.
3 Likes
Hi brian3kb,
thanks for the quick reply! Yes I imported the samples, adjusted samplerate settings (only the first time really) and pressed Spaced Chain. After 1 hour waiting I reloaded the page and tried other combinations, thankfully the samples survived the refresh.
I am running Chromium 122.0.6177.0, don’t know if higher versions can run on my system.
I have sent you a DM with zipped samples, just in case.
best regards
Max
1 Like
Chromium 122.0.xxx is the best of my browsers, last chance to see DigiChain run.
Thanks got them, and those load without issue for me (Chromium 124.0.6367.91), and I can edit crop build chains - I’m going to see if I can get the exact version of Chromium you have up and test with that, I have used 114.x.x previously, so odd that a later release has issues. Will let you know how I get on, apologies it’s not working for you 
Great! I will test the latest Chromium build 126.0.6460.0 to see if it runs smoothly.
1 Like
I couldn’t get the binary (or the source) for 122.x.x, but I was able to test with 120.0.6099.224 and everything worked as expected.
I will also look at adding additional error message surfacing from the processing screen, see if we can get an error message to work with. Thanks for helping out with debugging!
Happy to know you were successfull, unfortunately Chromium 126.0.6460.0 didn’t do the magic and DigiChain was caught in Guru meditation. 
edit: I found the link to Chromium 122.0.6177.0 Release 1235488 · blueboxd/chromium-legacy · GitHub
If you hold down the Shift key while clicking the Spaced Chains button, do you get the chain rendered to the top of the list, or do you get the same processing hang issue?
Unfortunately, I don’t have an Intel mac available to test that binary on, only Linux VM’s.
I’ve added some version checks and error surfacing on the latest url - if you could give that a go and let me know if you see an error?
Thanks again for helping!
It “hangs” also with Shift+Spaced Chain. Let me explain better: chaining more than 4 samples (total length less than 4 seconds) takes a long time to process, much longer than it would require me to do the same job manually in Sound Forge or Audacity (or Audition, FWIW).
This morning I investigated more methodically and found that what I described as “hang” is actually an “extremely slow processing”. I managed to chain and resample-to-the-list 5 samples (less than 6 seconds tot. length) in about 5 minutes, more than I expected but it succeeded. I’ll investigate furthermore in this direction and report my findings, if it’s of any interest
- note: as a reference I am using “latest” edition of DigiChain
The files sent build into chains in under 3 seconds on my Android phone, and about the same on my 2015 iPad.
I wonder if this is a video card driver issue, as rendering the waveforms is probably the most taxing thing being done (and Chrome should offload that to a GPU when it can), could you try disabling the waveform rendering in the settings and see if that makes any difference?
Toggle this setting to ‘YES’, then refresh.
(This brings my processing time down to less than 2 seconds on my phone).