I've been working on a loudspeaker design tool for my own use for a while now. It covers enclosures, crossovers, diffraction, measurement import, and so on. I mostly started it because I was tired of moving numbers between three different programs and a spreadsheet just to answer one question.
Most of my time has gone into getting the physics right rather than polishing the interface. I've been checking the results against published anechoic measurements, instead of only comparing them with other simulators. Two programs agreeing doesn't necessarily mean either one agrees with the real speaker, and testing that has caught me out more than once.
I'm curious about the parts of your own workflow that existing software doesn't handle well.
What do you still calculate by hand or keep a spreadsheet for — not because you enjoy doing it that way, but because the software doesn't give you a better option?
Are there any results you routinely double-check because you don't completely trust them?
What did you have to learn from forum threads rather than from the program itself?
And is there any variation or "what if?" idea you regularly skip because setting it up would take more effort than it's worth?
I'm not looking to pitch anything or collect a generic feature wishlist. I'm more interested in the awkward parts of the process that people have simply learned to work around.
If this turns up anything useful, I'll come back and share what I learned — and what I ended up doing about it.
Most of my time has gone into getting the physics right rather than polishing the interface. I've been checking the results against published anechoic measurements, instead of only comparing them with other simulators. Two programs agreeing doesn't necessarily mean either one agrees with the real speaker, and testing that has caught me out more than once.
I'm curious about the parts of your own workflow that existing software doesn't handle well.
What do you still calculate by hand or keep a spreadsheet for — not because you enjoy doing it that way, but because the software doesn't give you a better option?
Are there any results you routinely double-check because you don't completely trust them?
What did you have to learn from forum threads rather than from the program itself?
And is there any variation or "what if?" idea you regularly skip because setting it up would take more effort than it's worth?
I'm not looking to pitch anything or collect a generic feature wishlist. I'm more interested in the awkward parts of the process that people have simply learned to work around.
If this turns up anything useful, I'll come back and share what I learned — and what I ended up doing about it.
