Hornresp

diyAudio Moderator
Joined 2008
Paid Member
David, lately I've been interested in capturing say, the main screens plus beamwidth and efficiency. It looks as if it's possible to capture the efficiency screen from a different calculation to the others, and this/beamwidth won't be included in the capture if not looked at before doing so.

Is it best to do the calculation, ctrl-B, look at the efficiency then capture from that screen?

Also, if you don't mind is beamwidth not available with vented rear chamber? I've been checking with closed and adding the chamber in a separate operation.
 
Hi AllenB,

David, lately I've been interested in capturing say, the main screens plus beamwidth and efficiency. It looks as if it's possible to capture the efficiency screen from a different calculation to the others, and this/beamwidth won't be included in the capture if not looked at before doing so.

Pressing Ctrl+C with one of the default charts or the beam width chart displayed will capture the results for all the default charts, and for the beam width chart if generated.

Pressing Ctrl+C with the efficiency chart displayed will capture the results for the efficiency chart only.

Is it best to do the calculation, ctrl-B, look at the efficiency then capture from that screen?

Because capturing the default and beam width charts does not capture the efficiency chart, and capturing the efficiency chart does not capture the default and beam width charts, the order in which the charts are captured should not matter.

Also, if you don't mind is beamwidth not available with vented rear chamber? I've been checking with closed and adding the chamber in a separate operation.

The directivity tools can be used with either the horn output or the port output, but not with the combined output. To accurately calculate the directivity characteristics of the combined output would require more information on the relative positions of the two sound sources.

Incidentally - your post has resulted in me finding yet another bug :).

Capturing or releasing the default and beam width chart results causes the form title to show "Hornresp - Acoustical Power" or "Hornresp - Acoustical Pressure" regardless of the actual chart being displayed.

I will investigate and hopefully fix in the next few days.

Kind regards,

David
 

Attachments

  • Attach_1.png
    Attach_1.png
    62.5 KB · Views: 275
  • Attach_2.png
    Attach_2.png
    64.5 KB · Views: 268
It was in the excursion under different power levels. I had a difference in the setting from the input screen and the setting in the maximum SPL screen.

Hi Mark,

For the first case, diaphragm displacement is calculated assuming a constant input voltage Eg. For the second case, displacement is calculated assuming a constant input power Pmax. In the attachment, the black trace shows the displacement for a constant input power of 1 watt, and the grey trace shows the displacement for a constant input voltage of 2.83 volts (1 watt into 8 ohms).

Kind regards,

David
 

Attachments

  • Attach_1.png
    Attach_1.png
    63.6 KB · Views: 226
Well Done Bjørn!

Congratulations to Bjørn (Kolbrek) on receiving the award for the Best Peer-Reviewed Paper of the 139th International AES Convention. The award was presented to Bjørn on the first day of the Convention (Thursday, October 29) during the opening ceremony. A remarkable achievement when you consider the calibre of the people presenting papers at the Convention. Bjørn is in illustrious company indeed. His award-winning paper is entitled "Horns Near Reflecting Boundaries".

AES New York 2015 139th AES Convention / AES New York 2015

AES New York 2015 Paper Session P9: Transducers—Part 3: Loudspeakers
 
Hornresp Update 3940-151112

Hi Everyone,

CHANGE

When the Horn Segment Wizard is used with either a hyperbolic-exponential flare or a Le Cléac'h flare, the maximum allowable S2 value is 999999.9 sq cm.

S2 values greater than 99999.99 were being stored to two decimal places, which exceeded the eight-character field width limit - see Attachment 1.

S2 values greater than 99999.99 are now stored to one decimal place - see Attachment 2.

Kind regards,

David
 

Attachments

  • Attach_1.png
    Attach_1.png
    32.1 KB · Views: 166
  • Attach_2.png
    Attach_2.png
    32.2 KB · Views: 163