I don't think I've ever used the wizard thingy!
Fair price to pay.
It's ok for me!
Maybe not ok for anyone else though...
It's a great tool if you are designing to a required goal. As an example you generate a perfect horn via Hornresp and you want to make a multiple segment approximation as compact as possible. Some Intelligent sliding in the hands of the determined can get you a rather interesting smaller horn. If you have enough experience as to where to start on a volume reduction it can be rather quick to generate a design that is very optimized for volume efficiency.
Since we all requesting difficult features, I like to add one simple request which is annoying me like crazy, it's basically my own fault of having short memory but it makes using HR such more user friendly. I will represent my case/workflow below:
1) I have a big driver collection database, like we all do I presume. And sometimes you just want to check a dozen drivers in one design. So you go to Files > paste driver from database and check parameters, hit calculate. etc.
2) Now you come back to input screen and I can't remember which driver I selected from the database.
3) So you go to Files > paste driver from database and browse through the list again and check which driver you have added.
Do note that i sometimes have the 'brilliant insight' to write the driver type/name inside the little comment section on the input screen.
So it would be immensely helpful when pasting a driver from the driver database, the name of the driver (or name you have given for the driver) would be displayed somewhere inside the T/S overview on the input screen.
1) I have a big driver collection database, like we all do I presume. And sometimes you just want to check a dozen drivers in one design. So you go to Files > paste driver from database and check parameters, hit calculate. etc.
2) Now you come back to input screen and I can't remember which driver I selected from the database.
3) So you go to Files > paste driver from database and browse through the list again and check which driver you have added.
Do note that i sometimes have the 'brilliant insight' to write the driver type/name inside the little comment section on the input screen.
So it would be immensely helpful when pasting a driver from the driver database, the name of the driver (or name you have given for the driver) would be displayed somewhere inside the T/S overview on the input screen.
Cone midrange design process with HR?
I have searched through this thread and haven't found what I am looking for so forgive me if I missed it.
I am interested in the design process for a horn loaded cone midrange. I have a pretty good handle on bass horns I think but this seems a bit trickier. What I think I know is that one has to use the directivity feature to get a representation of the actual high end response (say 5-10 degrees off axis) and that the throat and front chamber are critical in getting smooth high end response.
In particular I am looking to come up with a horn and driver combination to give about 105 to 110 dB/W/m from 500Hz to at least 5K (7K would be even better). Max output would not need to be more than 115dB for sure as this is for domestic use.
So what I need is an outline of the design and modeling process using HR. If there is a pointer to an already existing write up that would be fine.
I have searched through this thread and haven't found what I am looking for so forgive me if I missed it.
I am interested in the design process for a horn loaded cone midrange. I have a pretty good handle on bass horns I think but this seems a bit trickier. What I think I know is that one has to use the directivity feature to get a representation of the actual high end response (say 5-10 degrees off axis) and that the throat and front chamber are critical in getting smooth high end response.
In particular I am looking to come up with a horn and driver combination to give about 105 to 110 dB/W/m from 500Hz to at least 5K (7K would be even better). Max output would not need to be more than 115dB for sure as this is for domestic use.
So what I need is an outline of the design and modeling process using HR. If there is a pointer to an already existing write up that would be fine.
Also I don't quite understand the front chamber area specification. In this simulation of an Eminence Beta-6A the schematic makes it look like the diameter (and thus area) of the front chamber is almost the same as that of the driver cone but to get that I had to specify the chamber area as almost five times the cone area. What am I missing.
For interest the on axis and 5 degree off axis response predictions...
For interest the on axis and 5 degree off axis response predictions...
Attachments
Also I don't quite understand the front chamber area specification. In this simulation of an Eminence Beta-6A the schematic makes it look like the diameter (and thus area) of the front chamber is almost the same as that of the driver cone but to get that I had to specify the chamber area as almost five times the cone area. What am I missing.
I think it's because you've got 4 speakers (2P 2S) so it's 4 times Sd
I think it's because you've got 4 speakers (2P 2S) so it's 4 times Sd
OOPs.
I installed the new HR in a new directory Renamed the included Hornresp.dat and copied my old one to the new directory. When launching hornresp it just hung but will start fine with the included (empty) Hornresp.dat
That's from 2016, you might need help with that.
Just for kicks, you could try to make a copy your old Hornresp folder and then install the new Hornresp into it.
When you are in the length field you can use the [T] key to select tractrix and [L] key to select the LeCleac'h.
Help file updated for Multiple Drivers
Thanks David for the input.
Apparently my math skills need some attention.
I have updated the Hornresp Help File with Multiple Driver information.
Jim.
Hi Jim,
Apart from the driver parameter values not being the same, it seems that you have some difficulty in multiplying by two
In your second record:
Sd should be 532.00
Bl should be 10.56
Nd should be 2P
Vrc should be 50.00
Atc should be 1090.00
Kind regards,
David
Thanks David for the input.
Apparently my math skills need some attention.
I have updated the Hornresp Help File with Multiple Driver information.
Jim.
FE206 is Wizzer/Cone Driver
It gets its high frequency response by avoiding mass roll-off by decoupling the larger cone diaphragm from the whizzer by a compliance between them. The low Q here has more to do with driving the whizzer. To get any decent bass response requires a long air column presented by a back loading horn [1]. This driver is not suitable for a front load horn design. For drivers suitable for that type of application see the JBL CMCD Article [2]. A low driver qts and high BL product may deliver superior results in some cases, particularly were cost is not a major design consideration. WHG
It gets its high frequency response by avoiding mass roll-off by decoupling the larger cone diaphragm from the whizzer by a compliance between them. The low Q here has more to do with driving the whizzer. To get any decent bass response requires a long air column presented by a back loading horn [1]. This driver is not suitable for a front load horn design. For drivers suitable for that type of application see the JBL CMCD Article [2]. A low driver qts and high BL product may deliver superior results in some cases, particularly were cost is not a major design consideration. WHG
Last edited: