Hi
I'm a bit new with VituixCAD and I could figure out two things. So, maybe somebody here could help me.
1) When I'm measuring a speaker from a 1m distance then at the height of a tweeter of 80 cm. Then, should I measure the low frequency driver from the same height and the distance to it will be a bit further (~1,2m) or should I lower the microphone and measure from the height where the height is also 1 meter?
2) How can I add the depth of a horn to the distance of the measurement (1m)?
Measurements are done with REW.
Attached is an illustrative drawing, side view.
I'm a bit new with VituixCAD and I could figure out two things. So, maybe somebody here could help me.
1) When I'm measuring a speaker from a 1m distance then at the height of a tweeter of 80 cm. Then, should I measure the low frequency driver from the same height and the distance to it will be a bit further (~1,2m) or should I lower the microphone and measure from the height where the height is also 1 meter?
2) How can I add the depth of a horn to the distance of the measurement (1m)?
Measurements are done with REW.
Attached is an illustrative drawing, side view.
Attachments
When starting out it's always best to read the measurement guides first. See post 4012 and others.
Member
Joined 2003
Has something broken/changed with the enclosure tool?
Running 2.0.88.8 -- looking at the 22W 8851T Revelator in bass reflex, the tool is showing F3 = 226hz?
This seems way off, and setting the same driver to a closed box gives F3 = 138hz?
Could someone check if the results are different using an earlier version?
Edit I had 2.0.85.7 on my desktop - it shows F3 = 40hz. I think there's a bug in the new version.
Running 2.0.88.8 -- looking at the 22W 8851T Revelator in bass reflex, the tool is showing F3 = 226hz?
This seems way off, and setting the same driver to a closed box gives F3 = 138hz?
Could someone check if the results are different using an earlier version?
Edit I had 2.0.85.7 on my desktop - it shows F3 = 40hz. I think there's a bug in the new version.
Attachments
Last edited:
Member
Joined 2003
I never adjusted it - or did I? not sure - this is the default it comes out with, but on 2.0.85.7 the Qa is set to 100 by default.
1) It is recommended to measure all drivers on their axis. Then VituixCAD is able to calculate the frequency response from any distance. If the geometrical positions of the drivers are also specified in VituixCAD, the vertical radiation pattern can also be simulated, provided that the drivers are rotationally symmetrical.
It is also possible to measure all drivers from one height (e.g. from the height of the tweeter). In this case the predictions of VituixCAD are only valid for the measuring distance. The error for other distances will probably be smaller, the smaller the vertical dimension of the box is.
2) If you have measured with timing reference (two-channel), you should not do anything, because the information about the different positions of the sound sources on the Z-axis must remain in the measurement. To make corrections is not the task of the user who feeds the simulation program, but of the crossover of the speaker to be developed.
Many greetings,
Azrael
Initial value is set when version 2.0 is installed first time ever, but after that it's on you. Program saves the last value in user settings. User and loading enclosure project can modify the field.
By deleting user settings files of all VCAD 2 versions, but that it harsh method for a small and quite visible mistake. Few years ago I also considered setting Qa=100 when user clicks Align closed or Auto align is checked and driver changed, but that would prevent fast comparing drivers with the same Qa<100. Program line is still there as a comment. Some user(s) will complain if I activate that feature. I think it's best to look parameters more carefully.
We can test with the next revision that all six Q-parameters are 100.0 when Enclosure opens. Values are still saved to user settings but they are not read to UI on start-up. This enables comparing different drivers, radiator types and alignments without automatic/forced change in Qa and Qp.
Table alignments play with Ql so that will change when alignment options are clicked. All Q-values are saved to and read from enclosure project files of course. Is this okay?
Table alignments play with Ql so that will change when alignment options are clicked. All Q-values are saved to and read from enclosure project files of course. Is this okay?
Member
Joined 2003
Small mistake on my part: of course, the geometric positions of the drivers must also be specified for predictions of the frequency response from any distance, not only for the simulation of the vertical radiation pattern. For the latter, measurements under angle are additionally necessary.
Sorry.....
Maybe it's best that program saves all or nothing to user config. Skipping Qa, Ql and Qp only would be an exception.
Personally I would not mind if Q factors jump back to defaults because they are quite abstract parameters and don't have much...any influence to driver selection, volume and port dimensions. Mostly just confusing users (including myself) by generating mistakes.
Member
Joined 2003
The correct choice of Qa, Ql, Qp for a given cabinet can be challenging. At least, I find a value <100 is more realistic, I usually end up in the range of 5-30. The user interface simplification would be to remove the specific Q values and just some dropdowns for things like "no fill, partial fill, heavy fill" like some other applications do, but I would still like to know the specific Q value being used so I know what assumptions are being made.
Guys. What is your opinion about prioritizing shapes of curves during crossover designing? PIR, ER, SP, LW? Is it good order? What if I can improve PIR/ER but in cost of SP? Is it worth?
Member
Joined 2003
Hi Kimmo, pls is possible, there is a bug during exports biquads to MiniDSP ? - I'm not able to export all 8 biquads, only biquads, which are really used. Shift key pressed during export button isn't working for me. (Manual definition is bellow)
(Minimum eight (8) biquad blocks are created if DSP system is miniDSP and Shift key is pressed while copy/export command.)
Thanks a lot.
(Minimum eight (8) biquad blocks are created if DSP system is miniDSP and Shift key is pressed while copy/export command.)
Thanks a lot.
Omg, my fault, it's working, sorry for my previous msg. (It was absolutely incredible, my KB was faulty :-D )