Vulture Culture Calls Out Behringer: The JN-80 Poly Aftertouch Fiasco

Vulture Culture wastes no time dropping the bomb: Behringer’s JN-80, trumpeted as a polyphonic aftertouch beast, is actually just another channel aftertouch pretender. The video starts with a side-eye at Behringer’s marketing, which has been very clear—polyphonic aftertouch is supposed to be here. Spoiler: it isn’t.

Instead of individual pressure per key, what you get is the same tired channel aftertouch signal, no matter how you press those keys. Hold a big chord, lean on a single note, and the JN-80 responds like it’s stuck in 1985. If you wanted independent expression in your pads or leads, you’ll have to look elsewhere—or plug in a proper controller.

Here’s the kicker: the JN-80’s sound engine happily eats polyphonic aftertouch if you feed it from a DAW or external controller. Vulture Culture demonstrates this with the clinical precision of a rave scientist—send in real poly aftertouch data, and the JN-80’s voices respond independently, just as advertised.

But the built-in keybed? It’s a dead end. No matter how you prod, poke, or bash the keys, the internal hardware just spits out a single aftertouch value for the whole channel. It’s like buying a sports car and finding out the accelerator is just a brick with a sticker on it.

Not content to just rant, Vulture Culture rallies the troops. Viewers are encouraged to grab a free MIDI monitor and put their own JN-80s to the test. It’s open-source accountability: if you’ve got the synth, you can confirm or debunk the claims yourself. This is how you turn a gear review into a community investigation—no corporate smoke and mirrors required.

So, can Behringer fix this in firmware? Vulture Culture isn’t holding their breath. The video points out that the sound engine can already do polyphonic aftertouch—it’s the hardware that’s lagging. Unless Behringer has some magic up their sleeve, this probably isn’t a fixable bug; it’s a design choice baked into the keybed itself.

The final word? Behringer’s support has been silent so far, with a ticket opened and no answer in sight. Vulture Culture leaves it hanging: will the company own up to the spec sheet blunder, or will this just be another ghost in the update logs? Until there’s an official response, users are left in limbo, waiting for either a miracle or an admission of guilt.