has anyone else had a play with this evaluation tool??
if i was Celestion or the guy behind it i would be looking for a good place to hide...or fix it...it's totally buggy when it comes to making changes in the already limited parameters, it keeps reverting to the previously entered value which becomes frustrating quick.
as something that seems to be intended as a marketing tool to help consumers select the appropriate product it's a dismal failure....but that's just my opinion.
if i was Celestion or the guy behind it i would be looking for a good place to hide...or fix it...it's totally buggy when it comes to making changes in the already limited parameters, it keeps reverting to the previously entered value which becomes frustrating quick.
as something that seems to be intended as a marketing tool to help consumers select the appropriate product it's a dismal failure....but that's just my opinion.
I had a look yesterday. I accepted no limitation on the size and it recommended the biggest possible. Not sure where I'd be going with that. With hornresp instead one can learn where the sweet spot is and what the compromises will do.
If you are referring to the HornWizard portal at https://celestion-horn.netlify.app/ then yes.
Development of the application was led by Bjørn Kolbrek, co-author of the highly acclaimed "High Quality Horn Loudspeaker Systems - History, Theory & Design" book. The HornWizard portal worked perfectly for me and did precisely what it was supposed to. No bugs, no reverting to previously entered values.
I have a somewhat more positive opinion as to the usefulness of the HornWizard tool... 🙂.
I think I see what I did wrong. Maybe I wasn't the only one, and maybe this can help. This may be a simple language/semantics issue, and the instructions do not make it clear. To me a 'wizard' is a one shot sweet spot calculator. This is actually a simulator which you use iteratively and is more powerful than I was imagining.
The input box labels marked 'Max' falsely confirmed for me that this wizard was looking for bounds. That's not the case at all, it is looking for your wanted mouth size, dependent on it fitting in with the length. It may be a simple interface matter to select the mouth size limit or the length limit at a time, rather than to simply indicate their interdependence by using the word Max.
The unopened 'Parameters' box didn't make it clear this is meant to be used progressively, I found that out by accident when I went to review the input and found it could be recalculated... and when I did, the power of the app opened up for me.
So after I worked out these minor issues I found it to be quite interesting and useful.
The input box labels marked 'Max' falsely confirmed for me that this wizard was looking for bounds. That's not the case at all, it is looking for your wanted mouth size, dependent on it fitting in with the length. It may be a simple interface matter to select the mouth size limit or the length limit at a time, rather than to simply indicate their interdependence by using the word Max.
The unopened 'Parameters' box didn't make it clear this is meant to be used progressively, I found that out by accident when I went to review the input and found it could be recalculated... and when I did, the power of the app opened up for me.
So after I worked out these minor issues I found it to be quite interesting and useful.
Seems useful, I think it's just helped highlight to me that I've probably been simulating designs that would beam too much at HF due to being a bit long. It'd be good if you could export horn profiles, but maybe you can do that by registering I haven't checked.
Which web browser are you using turk 182?
Which web browser are you using turk 182?