Post #15,186 would suggest otherwise - for some situations at least 🙂.
Curiosity got the better of me, so I investigated further 🙂.
Notice how in your screenprint below the L12 flare is shown as exp (lower case e) when it should be Exp (upper case E)
Looking at a snippet of the relevant Hornresp source code:
/////////////////////////////////////////////
If frmMain.lblHp(6) <> "L12" And frmMain.lblHp(6) <> "Con" And...
While creating the python code at FreeCAD to generate hornresp txt file for inputdata, sometimes when I used lower or upper case different from Hornresp standard, while importing the file the hornresp accepted it and change the text in the screen as in this capture.
Things that may work smoothly on windows can be buggy on Linux, program development is a "logical patient art".
Once I overwrite my hornresp files I can't check if the buggy came from linux update or hornresp update, is there a place that we can download previous hornresp files for testing purpose or order to try to provide you more data when needed?
I had suggested a few pages ago that David make a test build for Linux guys:
1. Open each form/module that contains code.
2. Press CTRL+A to select everything.
3. Press CTRL+SHIFT+L to convert everything to lowercase.
4. Repeat for the next form/module.
5. Save and compile.
Only David can make these changes, since only David has the source code.
Don't worry that everything has been converted to lowercase. The IDE, Visual Studio etc. is smart enough to change the commands and keywords back to title case automatically. What this method will do is to change all the variables, constants and labels to lowercase, which might work better on Wine.
Worth a shot, IMHO. If it doesn't work, it can be abandoned and you go back to the way things were before. If it works, but you prefer the original formatting, you could compile a Linux build whenever you release an update.
1. Open each form/module that contains code.
2. Press CTRL+A to select everything.
3. Press CTRL+SHIFT+L to convert everything to lowercase.
4. Repeat for the next form/module.
5. Save and compile.
Only David can make these changes, since only David has the source code.
Don't worry that everything has been converted to lowercase. The IDE, Visual Studio etc. is smart enough to change the commands and keywords back to title case automatically. What this method will do is to change all the variables, constants and labels to lowercase, which might work better on Wine.
Worth a shot, IMHO. If it doesn't work, it can be abandoned and you go back to the way things were before. If it works, but you prefer the original formatting, you could compile a Linux build whenever you release an update.
Hi David, here's the record.
I use the 5700-241216 version.
I tried a previous version, 5460-230408 and it works.
I use the 5700-241216 version.
I tried a previous version, 5460-230408 and it works.
Last edited:
Pretty-much all of the HR executables are still in the wayback machine. You (one) should back-up your .dat files every time you upgrade the executable. To date, only the one major file structure change is not backward-compatible
Not that anyone is asking, but my 2c, as a very long time wine-HR user, is that
1) I am completely grateful it runs AT ALL. Yes, there have been issues for a long-time--take the win as it is and with gratitude. We chose non-native OS's.
2) I know it's not supported (and not to bother David with issues resultant from "Wine stuff"
3) Everybody running Linux has so many different configurations & versions of wine running that it's impossible to support even if attempted
4) If ever something doesn't work in HR on Wine, we should absolutely verify that condition in some flavor of Windows before posting ANYthing about it.
Not that anyone is asking, but my 2c, as a very long time wine-HR user, is that
1) I am completely grateful it runs AT ALL. Yes, there have been issues for a long-time--take the win as it is and with gratitude. We chose non-native OS's.
2) I know it's not supported (and not to bother David with issues resultant from "Wine stuff"
3) Everybody running Linux has so many different configurations & versions of wine running that it's impossible to support even if attempted
4) If ever something doesn't work in HR on Wine, we should absolutely verify that condition in some flavor of Windows before posting ANYthing about it.
...and also please use the latest release of Hornresp when verifying on a Windows machine.
I have every version of Hornresp back to August 2012 if you want an older version drop me a message.
Thanks campbell p for confirming that you are using Windows.
It is very strange indeed that Hornresp works just fine for me but not for you or Tacchi778. In an attempt to identify the reason for this, could you please conduct the following three tests in the order given, and let me know the outcomes.
TEST 1
a. Select the existing record that does not work.
b. Click the Edit button.
c. Select the Tools > Chamber Type > Throat Ported menu commands.
Q1. What is shown in the Ap1 and Lp input boxes?
TEST 2
a. Import a copy of the export record you posted.
b. Click the Calculate button.
Q2. Is the error still generated with this imported record?
TEST 3
a. Use the Input Wizard to create a TH record using the following options:
Half space
Horn loaded
Tapped
3 segments
Conical
Conical
Conical
No rear chamber
No throat chamber
Q3. Is the error generated with this record?
Many thanks,
David
It is very strange indeed that Hornresp works just fine for me but not for you or Tacchi778. In an attempt to identify the reason for this, could you please conduct the following three tests in the order given, and let me know the outcomes.
TEST 1
a. Select the existing record that does not work.
b. Click the Edit button.
c. Select the Tools > Chamber Type > Throat Ported menu commands.
Q1. What is shown in the Ap1 and Lp input boxes?
TEST 2
a. Import a copy of the export record you posted.
b. Click the Calculate button.
Q2. Is the error still generated with this imported record?
TEST 3
a. Use the Input Wizard to create a TH record using the following options:
Half space
Horn loaded
Tapped
3 segments
Conical
Conical
Conical
No rear chamber
No throat chamber
Q3. Is the error generated with this record?
Many thanks,
David
Check thread below, it may give you some guidance
Small front load horn may give you better result. See thread below, post #11, you can find measurements, etc.
Assuming that the enclosure is rectangular and not circular, and given that the x and y dimensions are shown, presumably in inches, what are the z dimensions? Also, where is the driver located - on the rear panel of the enclosure or on the horn throat panel?
Good afternoon DMB! I'm getting the following error when switching from Nd to TH when clicking on the functions. HR switches to stepped mode and fills all the segments with 0.01. It also happens when switching Ap & Lpt. I got a new HP laptop for xmas.
Hi BP1Fanatic,
Many thanks for the feedback!
Having heard nothing further from Tachi778 or campbell p I didn't know where to go looking for the problem. The information you have provided has enabled me to hopefully resolve the issue once and for all. I will try to release an update in the next day or so.
Note that switching to stepped segments when clicking from OD2 to OD3 (Ripole) is quite normal.
Thanks again for helping to make Hornresp a better product.
Kind regards,
David
Many thanks for the feedback!
Having heard nothing further from Tachi778 or campbell p I didn't know where to go looking for the problem. The information you have provided has enabled me to hopefully resolve the issue once and for all. I will try to release an update in the next day or so.
Note that switching to stepped segments when clicking from OD2 to OD3 (Ripole) is quite normal.
Thanks again for helping to make Hornresp a better product.
Kind regards,
David
Just to clarify, I should have said not cylindrical rather than not circular.
Hello David,
Sorry for not replying earlier; I've been up to my ears with various stuff.
So, the fix you released didn't work right away. I tried completely reinstalling Hornresp while keeping the Drivers folder, and what's weird is that the issue was still there. I called it a day that time. Some time later, I went back to Hornresp, and the issue was resolved seemingly on its own.
A few days later, I built a new PC, moving just the Drivers folder to the completely new system where I freshly installed Hornresp. Since then, I haven't experienced any issues with Tapped Horn mode.
By the way, I think it might be Windows Defender or some new safety features interfering with the lesser-known program. They've been pretty aggressive lately, and I get like a million warning screens every time I install or update Hornresp. Maybe you should try debugging it on Windows 10 version 22H2.
Quick question: of all the horn types that Hornresp can do, how many can have multiple segments? How many can use the Loudspeaker wizard?
Is there a table or something that shows what's possible and what's not?
Is there a table or something that shows what's possible and what's not?