u/besttype

These had beat up bass drivers which I've qualified with some THD measurements in REW using a UMIK1

But now I've discovered these tears which had gone unnoticed.
1. These are full range speakers, could they still have been overdriven, creating these tears?

2. What can/should I measure in REW to qualify this as meaningful or not for my listening?

I'm now running them with a VTV NCX252-mp pre-out'ing from a denon x4800h, paired with some SVS micro 3000s Revo's and Q1 metas for surround

They sound great, and I want to just enjoy the great deal, but I mainly like Kef for their mids and highs clarity/dispersion. So I'm anxious if this is killing quality without my ear noticing

EDIT:
KEF USA is very easy to get a hold of, great service so far. $495 shipped for a replacement UNI-Q driver. Still don't know HOW these could have over-excurted given their crossover and how little they actually move, even at reference levels. the radial nature heavily implies over-excursion. But my personal guess is that the rubber ages, stiffens, and then cracks over time. I'm guessing it's also a VERY think piece of rubber. With UV exposure, everything dies.

I will try to do some sweeps and REW work before and after replacing the driver. KEF did supply some written instructions for swapping and they were OK with me DIY'ing based on my presenting as a mech-E and EE that was comfortable with a soldering iron.

also have a VTV amp (NCX252MP) coming next week to get them off my denon and let them sing

Good news and bad news:

1. It wasn't two bricks in a box, yay!
2. they sound amazing, minus any fiddling, yay!
3. the drivers I actually care deeply about (Uni-q's) are flawless
4. They seem to be a low serial number pair. 00007. I don't know if that's special or not.

Bad News:

1. Man, one bass driver is rough. the other bass driver is ROUGHER

Questions

1. I have a Umik-1 and have fiddled with REW at least twice. any advice on qualifying the bass drivers before throwing on some grill covers? AI suggests nearfield measurements to check "distortion measurement" and 2nd/3rd/4th harmonic distortion components
2. Any recommendations on where to get the bass driver(s) replaced if the price is right? I would greatly prefer to use them without grilles. I cannot find any trace of oem driver parts, but I'm guessing that's on purpose.

Getting a pair of used reference 1s for a very good price and figure I should really give them a dedicated amp to sit alongside my denon x4800h.

The room is well treated, and I have a umik to do dirac calibration when it's all setup. But the amp feels off sized to drive these while it's also pushing four other q1 Metas and a center (TBD). Room is an open vaulted ceiling, about 700 sq ft, and I like to listen LOUD about once a day.

80% music

19% gaming

1% Bluey

I've never shopped for dedicated amp separates, only used denon avrs.

my use case would be to compare them to my Kefs and Polk R700 and build some experience between the brands. After that, I might refinish/paint them or shove them inside a shrouded cabinet so they sound good without having to look at them.

I know the dented woofer isn't meaningful.

but I'm curious if this is a good enough deal that I should follow through. Never owned a klipsch before.

Edit: They're home, safe and sound. and beat to hell. sound great though!

Updated to 4.29 yesterday. worked fine at the time. This morning both channels give me "something went wrong" messages. I can use /new commands to restart the session, that returns a valid message confirming it's a new session, but any other normal request get's "something went wrong"

Tried this fix related to Json5 dependencies. didn't work. I'm burning through $10/hr with opus 4.6 trying to fix it with no luck.

here's my OC's attempt at explaining the issue. but he's a damn idiot, clearly and can't fix it himself. so don't take this report too seriously:

_____________________________________________________

OpenClaw 2026.4.29 — Slack and Telegram return "Something went wrong" on every message

Environment: OpenClaw 2026.4.29, npm global install, WSL2 Ubuntu, Node 25.6.0

Symptoms:

Every message on Slack DM and Telegram DM gets: "Something went wrong while processing your request. Please try again, or use /new to start a fresh session." Response is fast. /new succeeds but error returns on next message. Webchat works fine. Both channels were working on 4.27.

Logs show (in order of appearance across troubleshooting):

[channels] failed to load bundled channel slack: Cannot find module '@slack/web-api'

[channels] failed to load bundled channel telegram: Cannot find module 'grammy'

lane task error: skills.entries.goplaces.apiKey: unresolved SecretRef "exec:op-google-places-api-key:value"

lane task error: channels.telegram.botToken: unresolved SecretRef "exec:op-telegram-bot-token:value"

What was tried (all failed):

Gateway restart (multiple times)

Cleaned stale/orphaned session entries from sessions.json + restart

Removed individual skill SecretRefs from config + restart

Removed ALL skill SecretRefs from config + restart

Applied GitHub #75623 workaround: npm install in plugin-runtime-deps dir + npm install --save grammy@^1.42.0 in core openclaw + restart

Combined #5 and #4 together + restart

After each fix, a new error surfaces in the logs. Latest is the channel botToken SecretRef which can't be removed without disabling the channel entirely.

What still works: Webchat, 1Password exec providers from shell, direct node module imports from the runtime-deps directory.