Digitakt audio input issues

[pthm]

I recently picked up a Digitone to use with my Digitakt and have discovered an issue with the audio inputs.

I haven’t previously used the Digitakt audio inputs so not sure if this is a new problem or one that has existed for the duration of my ownership. Basically the audio inputs on the Digitakt aren’t functioning correctly, its as if there is a really loud signal present even with nothing plugged in.

I’ve exhausted all the troubleshooting steps I can think of.

I have tried factory resetting the Digitakt, i’ve tried different cables, different input sources. But the problem is present without any input connected at all. It’s present in headphones, main out and via Overbridge. It’s present using the external mixer and using the sampler monitor.

Also tried different power supplies, no difference

Here is a video I recorded showing the problem:

Digitakt audio input issues

[davestasiuk]

I would say open a ticket with Elektron.

Edit: And while you wait, maybe try the reverse routing setup? Try passing your DT audio through your DN

[shigginpit]

I’m just curious if you’ve tried hard panning the inputs (respectively) left and right yet and what the results were? When you show the mixer section it appears left and right input panning are both dead center.

Also, can you show what your compressor settings are on the Digitakt? I agree, something strange is going on but there may be something we’re overlooking so probably best to keep poking around before deciding it’s broken.

I’d verify the audio routing in the pattern menu and see what it shows under “route to main” as well as “send to fx”, and then in global audio routing if “int to main” is set to “auto”, it will kill output to the main when overbridge is available, so as far as when you connected to overbridge and the monitor cut off, that’s what I assume happened. If you change it to On then it will send audio through the monitor outs even when plugged into to OB. You can verify the same settings for route to main and send to FX for the global parameter here. Also see if anything is checked under the global fx mix and make sure nothing is checked as a global fx parameter just to cover our bases.

If you need a reference try page 68 and then 72-73 in the manual and it will lay some of it out a little more clearly. I can’t say yet if any of this will impact your current situation, but perhaps something is going undetected. Also, I didn’t see you mention how the digitone works by itself (or if it doesn’t work at all) so digitone by itself, without the digitakt, does it function as expected and the problem is only when input into DT? Sorry if I somehow missed that part, but it looked like the focus was on digitakt being the problem so I didn’t catch whether or not DN behaves normally outside of this audio routing?

Anyways, I can’t promise that I’ll figure it out, but someone probably will, so the more information that you put out there, the easier the puzzle becomes to solve.

[pthm]

Thanks for taking the time to write such a detailed reply, really appreciate it!

Compressor settings

Route to Main and Send to FX are all enabled.

Global FX Mix, all disabled

I have tried messing with the panning, doesn’t improve the situation, if the input is hard panned then the distortion / cutout is only present on the stereo channel its panned to. ie. if I pan left and increase the gain only the left channel cuts out / distorts. This seems somewhat intuitive though, at least it means the panning is working I guess? but my assumption is that is later in the chain and this issue seems to be inserting itself much earlier.

Digitone is working as expected, no troubles there. You’re correct with the int to main setting, that was the cause for the audio cutout when connected to Overbridge.

The Digitone is probably somewhat of a distraction to this troubleshooting process, the issue is present with it completely disconnected and remains the same when an alternative audio source is connected to the inputs.

[shigginpit]

Yeah, cheers sorry it didn’t turn out to be more helpful, looks like everything is good on your end so it certainly sounds like a hardware issue with no further digging but just to explore a few more small points here, when was your Digitakt manufactured, can you check the sticker date on the bottom? So, if I’m clear, you have not yet used the inputs to sample a line-in signal directly. You’ve moved samples through Transfer from your computer or used onboard samples, and audio out works normally with those items, but there was no other opportunity before now to determine whether the inputs worked at any point since the digitakt has been in your possession.

I see you did a factory reset, did you run a self test while you were at it? I assume no errors were found?

If your build date (showing the week number and year) is within the last 36 months, you’re still covered under factory warranty and it may be wise to follow up on that. A trouble ticket won’t hurt anything. When you got the DT did it already have the 1.50 firmware installed or did you have to upgrade from 1.40 or a prior OS in order to get 1.50 onto it? Did you do the recent minor update to 1.51 or whatever it is? (I haven’t done that one yet myself).

I see you did a factory reset, so I’m assuming any projects are backed up, with that in mind I can give you something that may amount to no more than busywork but it’s always worth a shot. I’ve seen some instances where (when the issue is related to the firmware) reloading the OS via DIN midi sysex (as opposed to using usb firmware update) can clear up some weird problems, mostly it has to do with corrupt files and not things that appear as hardware issues. The only reason I’m mentioning it, is that it’s something you can try since you’re attempting to confirm the issue is hardware related (quite strange how the l/r independent are blazing hot and the sum l/r gets no feed at all).

So that is to say, if you want to reload the 1.50 OS using sysex through the transfer software (over din midi, disconnect usb and hook a midi cable through your interface to the computer). This is the short version of how to accomplish that but it’s really pretty simple:

How to update your device via sysex transfer : Knowledge Base (Beta) (elektron.se)

I would not expect this to solve anything, but I would perhaps use it to reaffirm that the issue is hardware related and not something in the firmware caused by some weird remnant of a prior OS glitching out.

I apologize but aside from this, I can’t really think of any more specific advice. I think checking the build date to confirm if you’re in the 36 month window is a good start, and if your receipt (if it was a new purchase) is newer than the build date, the 36 months will go from there.

Sorry for the long-winded response but hopefully this comes across as coherent and not just rambling

[pthm]

Manufacture date is W21 2021 so still within warranty.

Test mode shows no errors and I have upgraded to the latest OS update, when purchased it was running 1.4 I believe, I have upgraded it incrementally.

Previously have used transfer and USB input to sample, never the analog inputs. I will try the sysex update, need to figure out how to get a DIN output from my mac though, perhaps via the digitone? that seems risky

[shigginpit]

The Motu doesn’t have a din in/out on it?

[pthm]

You are right, it does! that completely slipped my mind

[shigginpit]

no worries, I know digitone won’t work as a midi interface but the motu should be golden for this. I use my UA interface for this purpose and works fine.

[pthm]

Did the restore via DIN cable, no change.

I have noticed that if I try and sample the L or R channel individually, the phantom signal / noise / distortion presents as a strange waveform that doesn’t cross 0 db

This is the same no matter if I choose input L, R or L+R

[shigginpit]

I don’t think the video is loading, I see the black box but no data has come up. Is it formatted the same as before?

My instinct is that somewhere there is a broken or loose solder joint which is grounding something that shouldn’t be grounded and thus there is both noise, and no input signal, but it could really be anything at this point. My honest advice is if you’re patient enough to do the factory service, I’d have them do it at zero cost, otherwise you may invoke the wrath of a major headache using a multimeter looking for a short or paying someone at a third party shop.

[pthm]

With my limited knowledge, this looks like a short to ground on the inputs. It’s pinned at -1

I did try testing the inputs by probing the other end of the input cables whilst they were plugged into the Digitakt (whilst powered off) with a multimeter to see if there was a short between the ground sleeve and the tip of the jacks, but there wasn’t any.

Not sure if this would even detect a short somewhere else in the signal chain

[shigginpit]

That’s basically what I was implying I just hadn’t yet updated the post when your reply came through but I also feel there’s likely a short to ground somewhere in the input path.

[pthm]

Looks like its the end of the road for now, I have submitted a ticket with Elektron, will wait and see what they say. I really appreciate you taking the time to try and help out, thank you.

[shigginpit]

No worries, even without a resolution I think that it’s better we got here then to leave a bunch of ground uncovered and have you later chasing your tail over the same things.

Good luck with it, try and update this when it gets fixed or if there’s a firm diagnosis, so that we solve the mystery (for posterity).