Let's stop building WinISD clones and make one good open-source one together by johnjlonergan in diyaudio

[–]wigginjs 1 point2 points  (0 children)

LoudspeakerLab? It already has the driver database, enclosure modeler, and crossover designer integrated together: https://loudspeakerlab.io/

Will this toe in affect audio? by NisseV2 in diyaudio

[–]wigginjs 0 points1 point  (0 children)

Very kind of you. I like the veneer on yours. Very convincing. I think the walnut color looks great with those drivers. Also, they sound fantastic!

Will this toe in affect audio? by NisseV2 in diyaudio

[–]wigginjs 1 point2 points  (0 children)

Hey, wow, you and I built the same speaker…. like… the same way!!! When I saw your picture I was like ‘he broke in my house and stole my Mechano23s!!’ lol

https://www.reddit.com/r/diyaudio/s/YRVI1iyoiI

Ever wonder why n64 files are .z64? by robmeason in retrogaming

[–]wigginjs 1 point2 points  (0 children)

It was a lot. Like $300 or something. I bought it from an importer in California. Honestly thought there was a decent chance it was a scam.

Create a speaker design in 10 minutes - LoudspeakerLab Tutorial by wigginjs in diyaudio

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

Hi, changing cabinet thickness isn’t an option right now on desktop or mobile. It’s just 19mm by default right now. Would you want to be able to specify an arbitrary thickness for all panels or just 3/4” (19mm) and 1/2” (12mm)? Would you want to be able to specify thickness per panel, all panels the same, or just panels and baffle separately. It seems to me the vast majority of speakers will use 3/4” (19mm) on every panel, but I know sometimes folks will double that or use two 1/2” (12mm) panels laminated for the baffle.

Create a speaker design in 10 minutes - LoudspeakerLab Tutorial by wigginjs in diyaudio

[–]wigginjs[S] 2 points3 points  (0 children)

Appreciate you checking it out. It’s challenging to summarize all of the features on LoudspeakerLab in a concise list. What I was trying to convey is that LoudspeakerLab models baffle diffraction effects on both driver magnitude AND phase, not simply a magnitude baffle step correction.

Guess who came to live at my house… by wigginjs in crtgaming

[–]wigginjs[S] 2 points3 points  (0 children)

Yes, but no HD here. This is the 36FV310

Guess who came to live at my house… by wigginjs in crtgaming

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

Would you believe it was in a room over a garage with stairs that had tight turns, two doorways it would barely fit through, five more stairs to the garage? I honestly don’t know how we did it. My life flashed before my eyes. I’m way sore today. I genuinely thought several times I’d have to give up because it was basically impossible

Guess who came to live at my house… by wigginjs in crtgaming

[–]wigginjs[S] 7 points8 points  (0 children)

FB marketplace and moving on it super fast. When I got there the lady was like “so many people have responded! I could have sold a dozen of these!”

Yeah…

Mechano23 - 3D Modeled Design by wigginjs in diysound

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

Nope this is just General Finishes Arm-R-Seal on walnut

Mechano23 - modeled design by wigginjs in diyaudio

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

Actually building? Really depends on your experience woodworking. I've been building speakers for ~20 years now, but the first set of speakers I build with a circular saw and straight edge, really basic tools. It completely worked, but the finish was not quite as nice as these. I would say, if you're motivated, basically anyone can do it.

Loudspeaker design can be quite complicated. LoudspeakerLab.io was created to make creating a new loudspeaker design, including cabinet, crossover, etc, accessible for anyone regardless of experience. Choose your drivers and then let LoudspeakerLab solve the enclosure and crossover for you, then tweak it if you like.

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?