Interesting. I'll play around tonight and see if I can get it working again (power cycle being the technical term)
I initially thought I was just imagining things, but after using the loudspeaker wizard and adjusting the values on the fly once again saw no changes, which left me puzzled.
I initially thought I was just imagining things, but after using the loudspeaker wizard and adjusting the values on the fly once again saw no changes, which left me puzzled.
The peak particle velocity can be found at each port output acting independently by using the appropriate OD, OD1 or OD2 configuration. Calculate the results and from the Acoustical Power chart window select menu commands Tools > Particle Velocity > Throat Port Exit.
Hi David, nothing to worry about. I had left the ATC value at zero!
Thanks for your speedy replies.
Thanks for your speedy replies.
Hello David! Thank you for the answer, with one driver it works well, but when I tried to do the same with another one I have this message and program closing. Could you check if it a software bug or just my hands )
Best regards,
Roman
Attachments
Hi Roman,
Thanks for the feedback, it is a bit of both 🙂.
The error has occurred because a passive radiator has been specified with Cmp = 0.00 and Rmp = 0.00. The next update will make it impossible for the user to set PR parameter values to zero. In the meantime, to get around the problem if a passive radiator is specified simply make sure that Sp1, Mmp, Cmp and Rmp are all non-zero.
Kind regards,
David
Bugreport:
Default speaker, change Nd to BP4, Wizard, Other, Auto Ripple 0dB, Chamber 2, reduce Lc2.
At some point while reducing following error occours:
Default speaker, change Nd to BP4, Wizard, Other, Auto Ripple 0dB, Chamber 2, reduce Lc2.
At some point while reducing following error occours:
It works fine for me, and from the information provided it is not possible to identify the part of the code which is triggering the problem for you.
Time to get a Windows computer perhaps? 🙂
Sorry, i was in a hurry, i reproduced the problem with the default speaker, but the screenshot came from an other speaker.
I guess it's not a wine-issue as the calculation basically is working.
Here is now an example and screenshot from the default driver, while changing Lc2 it seems kind of random when the error occours, maybe it only happens on some values and not at a specific max or min value:
Default speaker, change Nd to BP4, Wizard, Other, Auto Ripple -4 dB, Chamber 2, change in small steps up/down Lc2:
I know i sometimes steel your time for the minor group using HR+wine. Thanks that you looked for it anyway.
Unfortunately it is without question yet another Windows - Wine/Linux incompatibility issue.
The good news is that your latest screen print showing the error also occurring when the schematic diagram is displayed helps me greatly in narrowing down where the problem may be occurring. I have made some coding changes which may or may not help. Could you please download a new copy of Hornresp and let me know if things work any better. Thanks.
The update just released for rertrobaer to check, should also have the PR problem fixed.
Because things are being done in "rapid prototype mode" at the moment, the product number has not changed. This will be attended to later.
Get an old decommissioned machine from a skool and install windows even unactivated just for HR , or make a dual boot setup with your current machine , emulate windows under Linux is a hit N miss.
The error doesn't occour when i push "save" after other/auto.
Default speaker, change Nd to BP4, Wizard, Other, Auto, Save
If at first we don't succeed...
Could you please download again and try the same with the Lc2 <- button.
Now the error occurs immediately after the first push on the Lc2 <- button.
Still, the error doesn't occur at all when i push "save" after other/auto, and then "wizard" again, chamber2, etc.
Thanks for your patience.
Does the error occur if you go default speaker > change Nd to BP4 > wizard > chamber 2 > adjust Lc2?
Now that is interesting. I will have to dig deeper - it may take some time...
Maybe running Windows in a Virtual Machine in Linux would be a better way to go. Hornresp is not resource heavy, so while a VM is not recommended for heavy tasks like 3D games, Hornresp should be fine.
https://www.makeuseof.com/tag/set-windows-virtual-machine-linux/