u/CobbyCode

Exactly. AI can write Rust, C, OpenGL or whatever else you need. HTML is often used because it makes distribution and remote control easy.

In FXRoute the time critical DSP parts are native C, while Python and the web UI handle control and orchestration. That split is intentional and works very well. The system is quite performant now and has been optimized a lot.

And AI can absolutely produce clean C code too. It still needs review and testing like any other code, but there is nothing inherently preventing it from writing efficient, memory safe code.

You're right that AI was used heavily in the development. I'm not trying to hide that, and honestly I probably wouldn't have built something of this scope without it.

That said, I'm a certified audio engineer and I do have some programming background, so the overall design and audio architecture weren't just generated blindly.

I also don't agree that the architecture is wrong. Python is used for the control and service layer, which is a good fit for a browser controlled appliance. The actual realtime DSP runs natively in C inside the PipeWire audio path, so Python and the web API aren't processing audio samples.

An LV2 plugin would make sense if this were just a crossover/EQ plugin. FXRoute has become more of a complete audio appliance with routing, streaming, measurement, device management and DSP, so the split between a web UI, Python control layer and native DSP is quite deliberate.

Yeah, you're right. I posted about FXRoute before and this was just an update, so I skipped the basic explanation. Bit of tunnel vision on my part.

no worries, not in love with OpenAI either.

maybe keep your biz registred in your home country in that case.

not anymore, at least for me and many others.

I really wonder why all hype Opus 5.5 now. Bought a plan for that reason... still fixing the bugs it introduced, yes Frontend, 3D, great, Backend......omg... inventing a lot broken senseless stuff, ignoring exisitng logic, too much handholding needed to fix it afterwards. Goodbye Claude, you suck.

i just know Opus 5.5 and it´s not for me.

instruction following as a reason to still use Astra maybe? i mean Opus is.... really bad at it.

I don´t get the Opus 5.5 hype, sry. Bought a plan yesterday and canceled today, it did a lot things, yes, mostly things i didn´t asked for nor wanted, nor they made any sense, took me almost a day to get back to normal.

Complete other way around for me, Opus 5.5 sucked badly, while Bunny did well. Canceled Claude right away, it was so anoying, yes good at frontend, but it´s clear, it suck´s.

it´s trash, need a lot hand holding to not invent too much stupid stuff.

Opus 5.5 had been horrible to me today, honestly dam stupid, ignoring the exisitng logic completly, takin me hours now to sort his invented sh... sucks. Switched to Claude for the hype... learned a lesson today, i hate Claude.

first time Opus user here, seems to be usable on the 20$ plan. if they would have some unlimited chat with better voice recog., i would skip my openai plan.

maybe one can keep it more neutral? influenced by each other? i mean, the language thing is older then our nations.

maybe related to the switch to Sol 6 ? I feel the same btw.

funny, as it´s the other way around for me atm.

PipeWire does not necessarily resample. It can switch the device to the source sample rate, so 44.1 kHz can stay 44.1 kHz, 96 kHz can stay 96 kHz, etc.

Digital volume control means the stream is technically no longer “bit-perfect” below 100%. In practice, though, this is essentially irrelevant with modern high-bit-depth processing. A physical potentiometer also changes the signal and can introduce channel imbalance, noise, etc.

16i16 and UMC204HD doing well for me.

good explanation, i still like them cause they are not pure evil, boring party, but not many scandals compared.

at some point it have to come down, let´s wait till the market crash.

tryin my best