Phase, impulse, spectrogram response and group delay are different (accurate?) when you sim maximum SPL and I have no idea why this is.
Non maximum SPL:
Maximum SPL:
I measured this at 2 meters outdoors groundplane at about 80 degrees outside with a calibrated measurement mic and no calibrated SPL, that moving bump at ~71hz is doppler shift from a vehicle about 1/4 mile away. My guess is this is at least 115dB.
Measured group delay:
Measured waterfall response:
Measured frequency response + phase
Non maximum SPL:
Maximum SPL:
I measured this at 2 meters outdoors groundplane at about 80 degrees outside with a calibrated measurement mic and no calibrated SPL, that moving bump at ~71hz is doppler shift from a vehicle about 1/4 mile away. My guess is this is at least 115dB.
Measured group delay:
Measured waterfall response:
Measured frequency response + phase
Last edited:
Hi StainlessSteve,
Could you please post a screenprint of the input parameters window showing the system design values, and also provide details of the Maximum SPL settings used in your test example. Many thanks.
Kind regards,
David
Some News…
Hi Everyone,
You may have noticed that 'just a guy' has not posted to the diyAudio forums for some time now.
Unfortunately he has not been well. He is currently undergoing a 5-month course of chemotherapy and may also require follow-up radiation treatment. He reports that he is now doing well but (quite understandably) has little energy at the moment.
The prognosis from his specialist doctors is positive, and I am sure that you all join with me in wishing him a speedy and complete recovery from his illness.
I for one, miss having him around.
David McBean
Hi Everyone,
You may have noticed that 'just a guy' has not posted to the diyAudio forums for some time now.
Unfortunately he has not been well. He is currently undergoing a 5-month course of chemotherapy and may also require follow-up radiation treatment. He reports that he is now doing well but (quite understandably) has little energy at the moment.
The prognosis from his specialist doctors is positive, and I am sure that you all join with me in wishing him a speedy and complete recovery from his illness.
I for one, miss having him around.
David McBean
Thanks for the kind words. My doctor says I'll be just fine in a few months as long as I don't get sick in this crazy flu season. I just don't have the energy to get into discussions so I won't be posting much for the next while.
I'm still watching what you guys are doing and enjoying the latest features from the last year - frequency range 1 - 2000 hz is amazing, I've also been liking the new filter capabilities and checking velocity at S2 for flared ports.
I also managed to snag a couple of B&C 18tbw100-4 (used but new condition) for $500 CDN all in so I'll be working on a design for them soon. Some type of big horn obviously. Probably tuned around 20 - 25 hz. I don't think I'll be able to build them until summer at the soonest but that gives lots of time to design something.
As always I'm available by email, I just won't be posting much for awhile.
I'm still watching what you guys are doing and enjoying the latest features from the last year - frequency range 1 - 2000 hz is amazing, I've also been liking the new filter capabilities and checking velocity at S2 for flared ports.
I also managed to snag a couple of B&C 18tbw100-4 (used but new condition) for $500 CDN all in so I'll be working on a design for them soon. Some type of big horn obviously. Probably tuned around 20 - 25 hz. I don't think I'll be able to build them until summer at the soonest but that gives lots of time to design something.
As always I'm available by email, I just won't be posting much for awhile.
Hi StainlessSteve,
I found the problem - it will be fixed in the next release.
Many thanks for reporting the bug. It has been there for quite some time, it seems
.Kind regards,
David
Hi David
Was trying to run a filter wizard from the acoustical power window and HR crashed
Made a screen shot of all the parameters in use. I have not managed to find what it does not like yet. Some OD types worked, others did not, and crashed.
Put a fresh copy of HR on the desktop imported the record and it crashed again so attached that file as well.
Regards
Martin
Was trying to run a filter wizard from the acoustical power window and HR crashed
Made a screen shot of all the parameters in use. I have not managed to find what it does not like yet. Some OD types worked, others did not, and crashed.
Put a fresh copy of HR on the desktop imported the record and it crashed again so attached that file as well.
Regards
Martin
Attachments
Hi StainlessSteve,
Thanks for the information. It doesn't matter as far as the bug you reported is concerned
.Just to clarify, the bug is not related in any way to the operating anomalies fixed in the most recent update - it is a completely separate issue.
Kind regards,
David
Hi David
Was trying to run a filter wizard from the acoustical power window and HR crashed
Made a screen shot of all the parameters in use. I have not managed to find what it does not like yet. Some OD types worked, others did not, and crashed.
Put a fresh copy of HR on the desktop imported the record and it crashed again so attached that file as well.
Regards
Martin
Hi Martin,
Many thanks for providing such comprehensive information, it makes it much easier for me to track down these sorts of problems.
By way of explanation, there were some issues with filter data not being saved correctly when created using older versions of Hornresp. Your test record has the filter data shown in Attachment 1. Notice how there are only three characters in the string enclosed by the red box (there should be four).
The easiest way to fix the problem is simply to press the F8 function key when the corrupted record is in Edit mode. This will reset the filter parameters to their default values and you should see the confirmation message shown in Attachment 2. The filter data in the record will then be as shown in Attachment 3, and the Filter Wizard tool should now work correctly.
The F8 feature was added some time ago when the problem of filter data corruption became a growing concern.
Kind regards,
David
