Acoustic Horn Design – The Easy Way (Ath4)

Member
Joined 2004
Paid Member
Regarding the profile curvatures, I found an old picture of an isolated SE extension (SE = superellipse):

se_curvature.png


As the graph shows, the curvature increases smoothly (almost linearly as a clothoid) to a point of a maximum, and then it decreases again to a point where the contour connects to a baffle (which has zero curvature). Note that in this graph it's not along the curve but as a function of x, i.e. the decrease is actually more gradual along the profile (it's similar to the initial increase, only the other way around).

I claim that for a baffle-mounted shape it just can't be better :)
 
Last edited:
  • Like
Reactions: 1 user
As for the backward compatibility, also some might have noticed that it's now possible to define an OSSE horn simply like this:

Code:
OSSE = {
  r0 = 19    ; Throat.Diameter/2
  a0 = 41.0  ; Throat.Angle
  a = 71.25  ; Coverage.Angle
  k = 1.3    ; OS.k
  L = 19     ; Length
  s = 1.12   ; Term.s
  n = 2.467  ; Term.n
  q = 0.999  ; Term.q
}

So there are the OSSE and R-OSSE profiles now (as described on my website), both using a similar notation.
(The parameter 'q' meaning different things in both but I won't change that...)

I see no need for the old rollback feature anymore. If you still want or need it, just use the old version...
Can you please do the same parameter "; descriptions" for the R-OSSE profile? Also (and only if not too much additional work), any chance the OSSE and ROSSE links to Desmos on your website be modified to utilize the same parameters letter currently utilized in ATH? It would make visualizing/understanding the impact of parameter adjustments a lot easier for a slow learner like me :).
 
Thanks for posting those measurements, @Patrick Bateman. I struggle to grasp coverage and directivity index design goals. Will you please explain your thought process behind the coverage/DI choices you made in this design? For example, why did you choose to increasingly narrow coverage above 2,000Hz at the rate you narrowed it. Based on your Geddes reference I suspect you did it to create a specific type side wall reflection but I'm not sure if I understood that correctly.

Thanks


6aswX37.png
 
Hi, in genral it looks very close match to simulation, except all the undulations that seem to increase in magnitude off-axis and have some kind of periodicity. Very interesting, not clear at all what makes it. Perhaps the device is resonating? cancels itself out on-axis

Ideally the response could look just like the sim. Since the top octave looks very close the sim I would expect rest of it would too.
 
I suspect that something is wrong with the measurement, as if a reflection was increasingly included in the time gate as the angle increases. The beats are a bit strange though, I have no explanation for that. Perhaps it would be helpful to see the non-normalized data. Otherwise the match is astonishing.
 
Last edited:
Here is an example of what happens if the time window (gate) is corrupted by reflections.

This is a tweeter impulse response, and I have a reflection beginning at about 3 ms.

1686423026687.png


If I select the gate window so it does not include the reflection, I get this response

1686423123786.png


If I use a longer 4 ms window, I am now getting the reflection. If the time gate includes reflections, the frequency response is no longer quasi-anechoic.
1686423300139.png

We can clearly see the undulations from 500 - 5000 Hz. This is what @tmuikku and @mabat are talking about.
 
  • Like
Reactions: 1 user
Yeah it would make sense its from the environment, gating issue.

Interference pattern has greater magnitude on low frequency, where directivity is lower. Also, combfiltering has dips and peaks at same frequencies on them all basically meaning secondary sound has same delay on all sweeps. Interference amplitude increases with off-axis angle so there is probably sidewall reflection, assuming its measured rotating dut horizontally keeping mic still, like usual. Perhaps another reflection with much shorter delay to make the peculiar interference pattern, perhaps stand the dut is on?:)

In general, converting IR to FR for crossover work the gating is critical and can lead even more errors than this. If real measured phase is to be preserved then all IR measurements need to be converted to FR with exact same gate to preserve the phase data. But also measurements need to be done with accurate distance ad rotation axis and so on :)
 
Thanks for posting those measurements, @Patrick Bateman. I struggle to grasp coverage and directivity index design goals. Will you please explain your thought process behind the coverage/DI choices you made in this design? For example, why did you choose to increasingly narrow coverage above 2,000Hz at the rate you narrowed it. Based on your Geddes reference I suspect you did it to create a specific type side wall reflection but I'm not sure if I understood that correctly.

Thanks


View attachment 1181925

For the most part, I just took Marcel's "Tritonia" waveguide and made some tweaks to it, so that it:

1) worked better with my dome tweeter

2) was more asymmetrical


There's a pretty good chance that I'll go with a five channel setup for my home theater. This means that I had to keep vertical height relatively short, but I have as much horizontal room as I could ever want. (My TV downstairs is a Samsung QN900A 85" and my setup upstairs is a Sony SXRD projector with a 120" screen.)

The end result was fairly close to the JBL 708P, which is well regarded. My speaker controls directivity down to 350Hz while the JBL peters out at 600hz:

wrclWgk.jpg


SPL%20Horizontal.png



Note that my measurement is from zero to 45 degrees while Erin's is from zero to 90.
 
  • Like
Reactions: 1 user
@Patrick Bateman, thanks for the explanation.

@hifijim, thanks for the gating example.

I corrected the gating on my earlier B&C DE111 measurement and made a new measurement for a B&C DE250. Same waveguide geometry but different 3D prints in addition to the physical difference in compression drivers. The gray material on the back of the DE250 waveguide is plumber's putty so I can easily remove the outer mouth termination and replace it with a different print. It's raining where I'm at so I'll remeasure outside when it dries up. IMO, the physical print of the DE250 is superior to the DE111. The DE111 waveguide is a little warped and wasn't assembled as well as the DE250 waveguide. I didn't expect the DE111 to perform better. I'm guessing the rear waveguide differences worked in the DE111's favor but I don't know enough to know. I think I'll figure out how to attach the DE111 to the DE250 waveguide and measure again to see what happens when it has a smaller sized compression driver attached.

PXL_20230611_012703188.jpg


This is the DE111 (small compression driver) measurements posted in #12,728 but now with corrected gating, Microphone at 2 meters.

46_8inch_DE111_2m.png


This is the DE250 (larger compression driver) with the same gating used for the DE111 except the microphone is 1 meter closer.

46_8inch_DE250_1m.png
 
  • Like
Reactions: 3 users
Member
Joined 2004
Paid Member
BTW, in the CircSym mode it's easy to manually add a driver body to the model, simply by moving the points in 'nodes.txt'.
Here I just quickly sketched something similar to a DE250 -

1686467226966.png
1686467240889.png


You see that the small midrange diffractions are due to the driver itself. Here it is relatively large compared to the waveguide.
 
  • Like
Reactions: 2 users
Adding the driver to the simulation is a huge help. Thanks.

These are the differences in the waveguide configurations and the separate 3D print files.
Throat.Ext.Angle = 0
Throat.Ext.Length = 22.5 (DE250); 10.75 (DE111)

R-OSSE = {
R = 101
a = 46
r0 = 9.5 (DE250); 9.0 (DE111)
a0 = 23

m = 0.76
r = 0.30
q = 3.65
k = 18.6
b = 0.0
arcterm = 160
}

Rot = 12
 

Attachments

  • DE111.zip
    673.6 KB · Views: 38
  • DE250.zip
    1 MB · Views: 44