Login

u/besttype

▲ 2 r/KEF

Q1 Meta Foam Plugs get blown out by bass

I have a 4.2 system with 4x Q1 Metas in a workshop crossed over at 80hz with 2x SVS Micro 3000s Revo subs. I put the foam plugs into to fully seal the speakers and smooth the crossover to the subs. It's a big 24x36 space so I am driving them loudly enough to fill the room.

BUT the damn plugs won't stay in. The woofer is blowing them out and im finding them on the floor the next day. I am pushing them in as far as possible while still having a reliable chance of pulling them back out (don't want to lose them inside the port or enclosure)

I could 3d print something but im assuming foam is the right solution for absorbing resonance. Should I put them in loosely and cap them with a 3d printed cap? or would the cap introduce resonance by acting as a hard reflective surface? Is there some other recommended solution here?

EDIT:
To be fair, I've been hitting that KEXP recording of Angine De Poitrine pretty hard over the past week. on reflection, that can't be helping.

reddit.com
u/besttype — 5 days ago
▲ 1 r/openclaw

Agent SDK vs Claude CLI

I don't get what the practical difference is between the new Agent SDK for Claude vs what I've been using for a couple weeks: Claude CLI. Openclaw is just using a local install of Claude Code via its CLI to wire in Opus 4.7 as an agent.

I don't even think openclaw via Claude CLI is disapproved as a mode of interface (but maybe now it is?). I'm hardly a power user so maybe i haven't tripped up any usage limits that would get my harness red flagged.

reddit.com
u/besttype — 8 days ago
▲ 2 r/openclaw

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.

u/besttype — 19 days ago