(and Merry Christmas back to you - Avast thought "setup" was a "setup") - I'm not smart enough to figure out the virtues of a 9th order BP but gave a feeble try: https://i.imgur.com/VTO0CEB.png
shortening vent 3 looks less useless - its tuned pretty deep
shortening vent 3 looks less useless - its tuned pretty deep
Last edited:
I believe alignment "orders" are based on the derived orders of the corresponding equivalent electrical circuits representing the alignment. While we might not know what "components" are in that circuit, we can take a good guess at the order by looking at the dips and peaks in the corresponding impedance curve in the passband. That impedance curve looks like what I'd expect to see with a 6th order alignment (three peaks, two dips in the passband).
... 
...Here my first sim test, using a PR as port 3. Less efficient than a 8th, (as it's more a 6th from it behavior as Brian said) but response seems less sensitive to parameter, while keeping shaping/filtering advantage of 3 chamber design.(and Merry Christmas back to you - Avast thought "setup" was a "setup") - I'm not smart enough to figure out the virtues of a 9th order BP but gave a feeble try: https://i.imgur.com/VTO0CEB.png
shortening vent 3 looks less useless - its tuned pretty deep
From my point of view, this is a way to separate a problem to solve :
Sub range from back port length difficulties solved with PR (CSS 12").
> 45 hz range => filtered with 2 front BP while keeping short vent.
Attachments
Last edited:
Hi Brian,
The three-character band pass options remaining were BP0, BP1, BP2, BP3 and BP9. I decided on BP9 for the latest topology.
The disclaimer in Post #9647 applies in this case also
.https://www.diyaudio.com/forums/subwoofers/119854-hornresp-965.html#post5831999
Kind regards,
David
Attachments
Hi clf,
This is very strange indeed! If you are using an Nd record and are in edit mode, then I cannot explain why a mouse-click on the L34 text box does not highlight the contents. No change made in the last release should have affected this operation. Is it only the L34 text box that doesn't work?
I would be very interested to learn if anyone else is experiencing a similar problem?
Kind regards,
David
I need to explore more, but on a 6th serie record, when updated, in wizard first port appeared as if it add a PR (whereas it cannot obviously).
Duplicating record, duplicated error. Clicking on Apt/Fr (SP1 wasn't even shown in main screen)... solved this stuff. So maybe it should be related to PR new toys implementation. Don't know if it should have effect on other alignement...
In another record, the same kind of error gived me a message inside wizard screen somthing like "wrong data set" (i don't remember exactly the message). But as said, i'll have a to do my homeworks experimenting this new version
Duplicating record, duplicated error. Clicking on Apt/Fr (SP1 wasn't even shown in main screen)... solved this stuff. So maybe it should be related to PR new toys implementation. Don't know if it should have effect on other alignement...
In another record, the same kind of error gived me a message inside wizard screen somthing like "wrong data set" (i don't remember exactly the message). But as said, i'll have a to do my homeworks experimenting this new version
Hi Damien,
The data field used to store the index number of the port replaced by the passive radiator, was originally used for another purpose. Hopefully you won't find too many records that need to be "reset" to remove a pre-existing invalid flag (as you did by double-clicking on the Apt/Fr label).
I thought about making Hornresp check for pre-existing flags and remove them automatically, but that would have required more work, and from tests I did at the time it didn't seem to be an issue anyway.
Kind regards,
David
The data field used to store the index number of the port replaced by the passive radiator, was originally used for another purpose. Hopefully you won't find too many records that need to be "reset" to remove a pre-existing invalid flag (as you did by double-clicking on the Apt/Fr label).
I thought about making Hornresp check for pre-existing flags and remove them automatically, but that would have required more work, and from tests I did at the time it didn't seem to be an issue anyway
. Kind regards,
David
Hi Damien,
The data field used to store the index number of the port replaced by the passive radiator, was originally used for another purpose. Hopefully you won't find too many records that need to be "reset" to remove a pre-existing invalid flag (as you did by double-clicking on the Apt/Fr label).
I thought about making Hornresp check for pre-existing flags and remove them automatically, but that would have required more work, and from tests I did at the time it didn't seem to be an issue anyway
Kind regards,
David
Hi David,
Even before going deeper in experimentation, should you replace velocity screen with PR displacement in BP wizard when PR replace a port ? It actually gives weird non sens velocity curve with PR, or at least, when i tested 9th it as in record shown this post .(sorry i can't export record, i'm at work
)And should it be possible to replace internal port too with a PR ? It should be really interesting for serie-8th loooong and big path needed as in ROAR design.
Kind regards,
Damien
Last edited: