Hornresp

Happy Holidazes and all that jive! ;)

Installed latest rev the other day; saved a DBR just now, clicked to 'add' and got a 94 error, so closed/reopened and it was in FIND and both opened OK, accepts changes!
 

Attachments

  • runtime error 94 11.25.22.PNG
    runtime error 94 11.25.22.PNG
    27.7 KB · Views: 66
  • DD506D2DBR.txt
    2.7 KB · Views: 52
  • DD506D2DBRv2.txt
    2.7 KB · Views: 46
I was planning to horn load an AMT driver, but I can't find in the help file how to calculate for rectangular drivers.
A non-circular diaphragm in an electro-mechanical driver (such as in the oval-shaped KEF B139 woofer shown in Attachment 2) is modelled as a rigid plane circular piston having the same Sd area as the non-circular diaphragm.

Insufficient parameter values are provided by manufacturers for Hornresp to model Heil type air motion transformer (AMT) drivers.
 

Attachments

  • Attach_1.png
    Attach_1.png
    26.4 KB · Views: 64
  • Attach_2.jpg
    Attach_2.jpg
    4.3 KB · Views: 63
  • Like
Reactions: 1 user
Installed latest rev the other day; saved a DBR just now, clicked to 'add' and got a 94 error, so closed/reopened and it was in FIND and both opened OK, accepts changes!
Hi GM,

Thanks for the feedback. I imported both your records and then added a new one of each with no problems. It is interesting that your screenprint shows the record field as blank, which would indicate that for some reason the record displayed was not correctly stored in the Hornresp.dat data file. This used to be an issue when multiple sessions accessing the same data file were run simultaneously, but that should no longer be possible so I am mystified as to what could have caused the run-time error you experienced. Hopefully everything is back to normal for you now though.

Kind regards,

David
 
  • Thank You
Reactions: 1 user
Feature request : Dummy tweeter/signal

Hello David,

Horns are generally used and are practicable for tweeter frequencies. But most tweeters can't be modeled using T/S parameters, as either the design is not amenable to it (AMT/compression driver/ planar) or because the data is not provided by the manufacturer. Also, when simulating a synergy horn, the tweeter response curve will always be the missing link in the chain.

It would be extremely helpful if we have a feature to create a dummy tweeter whose response can be set using data like sensitivity, fs , Sd, Qts, Xmax etc., so that user can approximate the frequency response data manufacturer usually provides.

Regards,
Giri
 
It would be extremely helpful if we have a feature to create a dummy tweeter so that user can approximate the frequency response data manufacturer usually provides.
Hi Giri,

This can already be done by adjusting the driver slider controls in the Loudspeaker Wizard until the desired response is achieved, and then saving the final set of parameter values as a driver in the Driver Database.

Alternatively, if the parameters of a driver are unknown then a reasonable indication of how the driver will perform in a given horn, some way either side of the cutoff frequency, can be obtained by specifying a constant diaphragm velocity (double-click on the Eg label in Edit mode to select Vel).

Kind regards,

David
 
  • Like
  • Thank You
Reactions: 4 users
I guess they're corresponding to Dickason's SBB4, SC4 and QB3 tables. Is that right?

Correct.

MJK 2021 A uses Dickason's Table 2.3 (SBB4 and BB4, QL =15)
MJK 2021 B uses Dickason's Table 2.6 (QB3 and SQB3, QL = 15)
MJK 2021 C uses Dickason's Table 2.9 (SC4 and C4, QL = 15)

Linear interpolation is used where necessary to calculate intermediate values not in the charts.

(I checked with Martin and he indicated that the QL = 15 charts were the ones to use).
 

Attachments

  • Attach_1.png
    Attach_1.png
    22.4 KB · Views: 66
  • Thank You
  • Like
Reactions: 1 users
Exploring Port Sizes vs particle velocity, once again longing for an option to force a Flat output FR :cry:

It is possible to obtain a flat frequency response in Hornresp by using an iterative process to automatically adjust the value of Eg at each frequency, as shown in the attachment. This is not the same as having a flat transfer function however, where the output would be constant for a fixed Eg. WinISD uses a relatively simple model which makes it possible to specify a flat transfer function. This cannot be done in Hornresp, which uses a more complex model.

I must be missing something, but I cannot see how being able to specify a flat transfer function would be of much use in designing a practical loudspeaker system anyway :).
 

Attachments

  • Attach_1.png
    Attach_1.png
    14.4 KB · Views: 60
  • Like
Reactions: 1 user
Maybe?

—->A ‘double’ (ie: parallel) offset driver mode (like PH1 allows so fantastically and was an EYE opener!) but without the (L45) element that attaches them?


—->Ch(no offset) ch1 (one side gets offset) ch2?(both sides are ‘offsetable’) and increasing with ‘path’
 

Attachments

  • 2529CB62-A6FD-46BC-A34C-004E257D0262.jpeg
    2529CB62-A6FD-46BC-A34C-004E257D0262.jpeg
    302.9 KB · Views: 69
  • 12FE279A-D32A-44FC-8DA1-2A2262EF6DDE.jpeg
    12FE279A-D32A-44FC-8DA1-2A2262EF6DDE.jpeg
    419.8 KB · Views: 72
  • Like
Reactions: 1 user
—->A ‘double’ (ie: parallel) offset driver mode (like PH1 allows so fantastically and was an EYE opener!) but without the (L45) element that attaches them?
—->Ch(no offset) ch1 (one side gets offset) ch2?(both sides are ‘offsetable’) and increasing with ‘path’

Not sure if you are asking for two different things or if you are suggesting two potential ways of doing the same thing :). Either way, the best that Hornresp can offer is as shown in the attachment. Hopefully this gets you close to what you are looking for.
 

Attachments

  • Attach_1.png
    Attach_1.png
    13.9 KB · Views: 74
  • Like
Reactions: 1 users