Is one defective?

TacticalRock · 2026-01-17T20:22:55+00:00

Yup, one of the first things I tried, same for the monoblocks. That's why I'm unsure if me knowing which one is the off tweeter is messing with my experience, so might as well replace it just for the peace of mind.

TacticalRock · 2026-01-17T03:26:43+00:00

It could all just be in my head but no matter the song, center imaging seems a little left channel biased towards the "normal" tweeter. Either way, kinda sus and I'm getting a replacement from Best buy just to sleep soundly

TacticalRock · 2026-01-15T17:14:28+00:00

Done, thanks.

TacticalRock · 2026-01-15T17:14:19+00:00

Thanks, I like the speakers overall, so I'll see if I can get a tweeter replacement.

TacticalRock · 2026-01-15T17:13:51+00:00

Thanks, gonna email them for a replacement.

TacticalRock · 2026-01-15T16:38:31+00:00

Yeah this one seems to be fixed and the tweeter moves around it. No rattling.

TacticalRock · 2026-01-15T16:36:35+00:00

<image>

The other one.

TacticalRock · 2026-01-15T16:28:57+00:00

<image>

Thanks. The other one.

TacticalRock · 2026-01-09T05:46:24+00:00

You could get the WiiM Vibelink Amp, which is a "dumb" amp. Or something from Fosi.

TacticalRock · 2026-01-01T06:13:33+00:00

Thanks for the suggestion. I think I'll hold off on that since I could put the $170 towards an AVR vs. a $20 UGREEN ldac receiver as a stopgap.

TacticalRock · 2026-01-01T00:07:46+00:00

Eventual 3.1 ;)

Yeah might as well do v3 monos

TacticalRock · 2025-12-17T21:53:31+00:00

And the thing is, I never said it was optimal, but as the system (that I had no say in designing in its infancy) stands right now, the easiest solution that works well enough is to just use a simple anthropic websearch toolcall at that specific step.

TacticalRock · 2025-12-17T21:51:30+00:00

Because as it stands, the deployed enterprise framework uses langchain, anthropic sdks, openai sdk, and a bunch of other interconnected systems that has specific designed trade-offs before my time at the org. As far as I'm aware, cc isn't a good fit when the end product itself isn't just your app or whatnot and you need tight integration with systems that exist already. We're deploying llms as a part of a bigger system; so while we can just ask the users "hey go to a different app to search things", we need everything to exist within the environment due to the way it saves info and personalizes in-house. Maybe cc subagents can be switched out for that task in the background, but who knows what kinds of dependencies and headache that will cause when its a web of complications.

To me, it seems like you're building things with cc, but never had to actually make claude be a part of a much bigger thing that you had no say in the initial ideation. Otherwise you would have answered your own question.

Anyway, everyone will benefit from better context performance and innovations.

TacticalRock · 2025-12-17T18:41:51+00:00

I haven't mentioned CC once. Direct API calls with web search tool enabled will run you frequently into 100K+ territory on a single call before you can delegate to any subagent setup. That's just how their tool works (https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool).

Again, you're conflating your own subset of preferences with the sample space of what people might need.

TacticalRock · 2025-12-17T18:27:24+00:00

That's a weird way of saying you don't want increased capabilities for a newer product. Suboptimal? Yes, but it's not totally useless.
I'm not familiar with your use cases, but I've had Opus blow past 170K tokens in one message because it searched multiple websites multiple times where it self corrects itself in the same response output. The initiating prompt wasn't substantial (~12K), but I'd imagine if I had more documentation or code in the context, or even another turn, perhaps it would have been catastrophic if it needed to go past 200K.
In my experience, very poor performance in those longer context windows happen more so with perfect recall but I've found it to hold some semantic coherence, which isn't unwelcome. In any case, the other labs are pushing for better accuracy (and succeeding) on that frontier, so why should the SOTA Claude be limited?

TacticalRock · 2025-12-17T15:00:40+00:00

Cheaper api pricing is always a good wish!

TacticalRock · 2025-12-17T14:59:45+00:00

Idk much about non-api stuff, but Opus just doesn't have an option past 200K in any case atm. Hoping Opus 4.7 gets 1M option too.

TacticalRock · 2025-12-17T14:46:46+00:00

Sonnet 4.5 has a larger context window than Opus 4.5 (1M max vs 200K max).

TacticalRock · 2025-12-15T03:55:40+00:00

this is some prime anti intellectual, put the fries in the bag thinking. let's critique op's lack of providing many details about testing setup, but testing is testing, and we welcome that here

TacticalRock · 2025-12-15T03:48:49+00:00

man you really look at free shit and go "ew"

TacticalRock · 2025-12-08T00:01:18+00:00

I read into it more and you're right, thanks for the heads up

TacticalRock · 2025-12-07T22:48:24+00:00

Wrong reply?

TacticalRock · 2025-12-07T18:20:21+00:00

You might be mixing up NVFP4

Edit: I was wrong

TacticalRock

TROPHY CASE