Teenage Engineering EP-133 K.O. II

Interesting. On my device I can copy sounds from Group A to Group B and it works fine as I stated, but when I try and do it from Project X Group A to Project Y Group A, it loses the clipboard contents. So won’t let a paste happen afterwards.

1 Like

same here

Hey I got that Temu bag finally. It’s nice and fits the fanboy case. Pic should be a few posts above

Just make sure you are in the SOUND mode when pasting. I did the same thing as when you switch projects, it starts in MAIN, so I though it wouldn’t copy over.

8 Likes

Well I’ll be damned. Great catch and excellent find. Nice, now there’s kits if you’re ok losing a project to it.

4 Likes

I have now read many previous posts. But I haven’t actually found out whether the problem with the fader or the packaging has been solved. Can anyone help briefly? Is it safe to order a KOII now.
Thank you!

Its solved. The faders where never the problem. it was the weight on top of the faders when shipped. they now have a plastic cylinder covering the fader.

5 Likes

Any UK retailers got stock of the fixed package version?

i wouldnt say its solved. i think part of the problem was with the fader cap. its such a tight fit you have to push pretty hard to get it on which was causing failures. i got a KO from the “fixed” batch and didnt even bother putting the fader cap on.

2 Likes

Right, but that was back when they didn’t protect the fader. I think the pressure on the boxes with the addition of the fader cap are the reason when the cap issue was happening.

1 Like

Looking at getting a midi controller for the KO. Would something like the Novation Launchpad Pro be overkill for it?

The best solution for MIDI type A/B - TRS to RCA x2 adapter:

I use LPP with KO2 but I wouldn’t buy it just for that. If you have other uses for it I do recommend it as a great all around controller.

1 Like

The cause of the (mechanical) speaker connection issue isn’t the same as those that lead to so-called “fadergate.” Those were caused by packaging design oversight and/or incompatibility between the fader stem and cap cavity.

The (mechanical) speaker problem arises where a conductive pad on the PCB isn’t sufficiently pressed onto an equivalent pad component that is connected to the speaker (by a pair of wires), effectively leaving the speaker disconnected. Removing the back of the device and carefully tightening the screws around that area of the PCB seems to fix it (personally verified), though that’s a warranty-voiding act.

I understand the use of a pad-based PCB-to-speaker connection for automated assembly purposes but this particular design appears to have problematically fine tolerance. I’m thinking of soldering some tiny blobs on the PCB pads to be sure of a connection.

4 Likes

There is no seal on the screws and it leaves no marks on the unit. Also - it would not be legal to void the warranty just by tightening the screws - at least in the EU. I’ve done it myself and although it’s not legal advice, I firmly believe it’s safe to do.

1 Like

Just trying to go places:

4 Likes

Two more days to return my EP-133, so I will ask here one last time…
Anyone notice noise/static/fuzziness on the delays as they fade out?
I have also noticed this same type of noise present using chorus.

Need to decide if I’m keeping or sending back. Wondering if it’s just a firmware fixable issue. I would expect everyone to have this issue, but have
not heard much said about it.

i have not noticed this. is the noise blatantly apparent at all times?

It’s ever-present on chorus. More obvious with more compression applied.

On delays, it’s just at the tail end as the sound fades out completely. Again, more noticeable with compression and more feedback.

Reverb sounds nice and clean. Sure seems like firmware, rather than the hardware.

I have a solid fader, so I’d prefer to keep this one. If this is actually hardware related, I’d want to send it back.