LoudspeakerLab 10-Minute Speaker Design Tutorial

[technodanvan]

Its SBA 761 from Troels.

That is an interesting design. I don't think LoudspeakerLab can do it all at once in its current form, though you might be able to do it in parts.

 

[wigginjs]

Auto-solver now optionally takes your direction for crossover points, slopes, and what topology features to consider.

 

[technodanvan]

Is there an intent for it to suggest 'extra components' if you first just ask for a simple crossover that needs cleaned up?

 

[wigginjs]

@technodanvan I'm not sure that would make sense, or maybe I don't fully understand your question. If you want the solver to have the breadth to do whatever it wants, just run it without 'Advanced' options. If you want to narrow the search scope because you already know the ideal points, that you don't want certain patterns (zobel, etc) then you can uncheck them and narrow the solver's search space. I think having the solver re-suggest options you've already eliminated would be kind of like just putting it back on full-auto mode. It would have to search those other spaces to know that. Does that makes sense or did I misunderstand?

 

[technodanvan]

Apologies, I was on my phone and abbreviated that comment somewhat. My thought process here was one that would teach or guide a user through the things that could help them with a better speaker by making suggestions for not only the 'blocks' that could benefit the frequency response, but perhaps even allow a user to adjust the frequencies at which those blocks are centered. Perhaps this is present already, I have not been in there for several days now.

Random aside, will drivers from Beyma be added to the database at some point?

 

[wigginjs]

LoudspeakerLab now supports passive radiators, multiple ports, and pre-built cabinets. Also, @technodanvan, you should find some Beyma drivers in the catalog too

 

[technodanvan]

Big update! I still need to get in there sometime to check out the last update. Got some time off upcoming so I'll see about getting in there.

Edit: Is there a place to add a second PR?

 

[wigginjs]

Big update! I still need to get in there sometime to check out the last update. Got some time off upcoming so I'll see about getting in there.

Edit: Is there a place to add a second PR?

One PR for right now. I’m thinking about making it possible to add PRs to the sides and opposing sides. This starts to creep into territory that is much more niche in terms of design and adds a fair amount of simulation complexity, like open baffle, bi/di-pole speakers. I’m not sure the juice is worth the squeeze because this represents such a small % of designs overall. Curious to hear feedback from others about their ‘must have ‘ features.

 

[rokr]

Wanted to do a test to check what will happen if change the position of drivers.
Before i made the change, i tried to do a remix without making any changed at all. Used the Mechano23.
While very close, the results were not the same...

 

[wigginjs]

@rokr This is really interesting and confused me at first. I was able to replicate. This happens because I created the Mechano23 design's crossover with a netlist import which specified the same ESR / DCR values for the crossover components that XMechanik specified in his original design. But, when you remix it, those crossover component ESR/DCR values get replaced with generic estimates that don't quite match what was in the original netlist. So, that's why they don't match up. I'm not sure if I should carry forward the DCR/ESR values from a netlist when someone remixes a design because the author could supply some strange DCR/ESR values for very specific crossover components that the author of the remix may not intend....

 

[Bryguy]

Not sure if this is the right thread to post this, but I am having a hard time uploading a driver. I fill in every required field, but when I click to save changes, I get the error message "Stored measurement data is missing: Object not found in S3: drivers/d4724f72-448b-46da-8afb-eb7b75a732a8/on_axis.frdStored measurement data is missing: Object not found in S3: drivers/d4724f72-448b-46da-8afb-eb7b75a732a8/on_axis.frd"

 

[wigginjs]

@Bryguy Hi, yes, thanks so much for reporting this. Emailing [email protected] is a more reliable way to get a hold of me, but I just appreciate you taking the time to let me know about this.

Your report revealed a bug that can occur which causes driver profiles to get 'stuck'. I patched the bug and your driver profile should be on your account now in 'draft' state. I did notice that the frame/cutout diameter fields don't have realistic values, so you'll need to update those and save, then you'll be able to publish the driver.

 

[Bryguy]

@Bryguy Hi, yes, thanks so much for reporting this. Emailing [email protected] is a more reliable way to get a hold of me, but I just appreciate you taking the time to let me know about this.

Your report revealed a bug that can occur which causes driver profiles to get 'stuck'. I patched the bug and your driver profile should be on your account now in 'draft' state. I did notice that the frame/cutout diameter fields don't have realistic values, so you'll need to update those and save, then you'll be able to publish the driver.

Thanks!