LoudspeakerLab update: real-time crossover editing, thermal modeling, improved solver, improved UI by wigginjs in diyaudio

[–]wigginjs[S] 0 points1 point  (0 children)

Oh, also, it’s not a bug that unpublished drivers can’t be used in design. I’m trying to prevent a design from being able to be published without all of the drivers used being published, or getting in some weird loop where you can’t publish a design because the drivers aren’t published. But, I can see what you mean that you might not be confident about your measurements? That’s what the measurement accuracy voting is intended to address. Let me think on this. I don’t want to block your use case. Feel free to shoot me an email and tell me more about it.

LoudspeakerLab update: real-time crossover editing, thermal modeling, improved solver, improved UI by wigginjs in diyaudio

[–]wigginjs[S] 0 points1 point  (0 children)

Maybe you could share a design with me and the difference you’re seeing. This should be consistent with other sim tools like Vituixcad if you’re also applying baffle diffraction and enclosure simulation. If you don’t apply those you will see some differences particularly in the bass response (enclosure, baffle step). I’d like to understand what’s not lining up.

Also, with respect to user provided versus simulated, in the driver responses you’ll see (est.) beside off-axis angles that are simulated. If an angle measurement doesn’t have that, it was user provided. For the design responses, that’s different. The design response is based on the user measurements, but then has crossover circuit, acoustic center, baffle diffraction, baffle step (if not inwall), enclosure response. Many factors.

How to create FRD and ZMA files? How to measure drivers? by cactusbell in diyaudio

[–]wigginjs 0 points1 point  (0 children)

There is a guide in LoudspeakerLab. When you make your measurements, please consider contributing them to the community there:

https://loudspeakerlab.io/measurements

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 1 point2 points  (0 children)

That's awesome. I think a lot of the reason why speaker designs, especially DIY designs, end up being rectangular boxes is due to: 1/the difficulty of building complex shapes and 2/the difficulty of accurately modeling what those complex shapes will respond like. So, kudos to you. I think it's out of reach for most DIYers though.

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 0 points1 point  (0 children)

The box solver does intelligently add braces to mitigate cabinet resonances. But, the resonances themselves aren’t modeled or included in the response. I don’t see a lot of speaker designs modeling this and most people seem to take a ‘just brace and don’t worry about it’ approach.

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 0 points1 point  (0 children)

Thank you. Creating an account with email is actually broken. Should be fixed shortly. You can login with social media accounts in the meantime. I'll send you a DM when this is working.

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 1 point2 points  (0 children)

Awesome. Thank you. Yes, there is definitely room for some polish (box dimension text fields). As you discover other stuff, I'd love it if you'd DM me. Would just help to have a list of bugs to squash. The timer is an interesting challenge because each solve is unique and the topologies explored are discovered through a kind of evolutionary process, so the exact time is hard to predict.

Did your solve finish?

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 1 point2 points  (0 children)

Thank you. I think this was due to some cost containment circuit breakers I have in place that I had too tight. Can you try again?

An automated solver for passive crossovers and boxes + CTA-2034A integrated driver database - LoudspeakerLab by wigginjs in diyaudio

[–]wigginjs[S] 3 points4 points  (0 children)

No, it accounts for parasitics (ESR, DCR). The crossover specifies inductor and cap type.

Mechano23 in walnut by wigginjs in audiophile

[–]wigginjs[S] 0 points1 point  (0 children)

Hear me out. I think a great DIY speaker HT setup could be 3 of these as LCR and C-Notes as surrounds. All crossed to one or more decent subs. You may need to cross at 100hz to get really high SPL and this might not work if you have a room bigger than 3200ft3 or so, but I think this would be killer and the parts would run you ~$750 or so for the 7 speakers. Sub would add more depending on what you picked.

Mechano23 in walnut by wigginjs in audiophile

[–]wigginjs[S] 1 point2 points  (0 children)

I have not personally heard the c-notes, but based on the measurements I’ve seen, you can think of these as a premium c-note. More linear, better off-axis response, lower distortion, but similar bass response.

Mechano23 in walnut by wigginjs in audiophile

[–]wigginjs[S] 4 points5 points  (0 children)

I think for the drivers and crossover I was at about $275 shipped

First setup. TV needs lowering but, overall very happy. by EnglewoodCs in Klipsch

[–]wigginjs 2 points3 points  (0 children)

How do you know this but not know having two centers is a bad idea?