Correction: most keyboard shortcuts seem to be working. It’s just the Optimize on/off/toggle from the context menu that don’t. Bug?
Again, I understand if that’s a low or no priority issue, as it’s not officially “supported” hardware.
Thanks for the amazing software!
Again, I understand if that’s a low or no priority issue, as it’s not officially “supported” hardware.
Thanks for the amazing software!
Thanks a lot Kimmosto, it answered my second question. But can you help with my first question? There seem to be two types of active xo blocks in the library, ones which have VLC Unity Gain in their names and ones which don't.
I trusted you can see the difference. It's the same connection, but with different user parameter: C or R.
VCL lib is not done by me so there may be some others with close the same functions.
https://kimmosaunisto.net/Software/VituixCAD/VCLLabs_opamp_filter_blocks.pdf
That works too via context menu and Ctrl+W. At least here with real W11 Pro. Components to be toggled should be selected (in blue).
Shortcuts with Ctrl-key don't always work because (mouse) focus is lost to somewhere else than panel containing schematic picture box. I have not tried to force focus back to the schematic.
sorry if already been asked.
Vituixcad doesn't start (or takes too much time, not sure how much) if the last project or any recent files were stored on a network share (e.g. samba share on a NAS) that is not accessible anymore/offline when launching the application.
This on windows 11 (regularly updated). Not sure if there's a windows timeout or if it's in the application.
Vituixcad doesn't start (or takes too much time, not sure how much) if the last project or any recent files were stored on a network share (e.g. samba share on a NAS) that is not accessible anymore/offline when launching the application.
This on windows 11 (regularly updated). Not sure if there's a windows timeout or if it's in the application.
Yes, I saw that it's just a different set of values, therefore I was confused by the name. The VCL ones said "unity gain", so I thought that the non-VCL one would not be unity-gain. But when I changed the Q or frequency, I did not see any change of gain, therefore I got confused.
My limited reading of active filters is that there is Sallen-Key topology and unity-gain, and while Sallen-Key is more flexible in the range of values one can use, it's not unity gain. That's where my questions and doubts came when I saw this other library labelled "unity gain".
Hello Kimmosto,
may I suggest a feature that I'm missing in your great software?
Would you be able to include a voltage curve in the power window of the enclosure tool? Maybe as a switch between current and voltage. when I'm trying to match a driver and enclosure to a given amp I often apply peaking, LT, HP and LP filters and I end up having to calculate the resulting voltage that my amp would need to supply by multiplying the input voltage with the filter gain. A voltage curve in the power window would speed this process up a lot.
Here's a simple example:
Let's say my amp is capable to deliver 40 V above 4 Ω.
Woofer in sealed box, input Voltage: 30V, no filters
same box, but with a 6dB peaking Filter at 135 Hz
now the resulting voltage is 60V at 135 Hz, which my amp can't handle. Unfortunately I can't easily see that, unless i divide power by current or multiply input Voltage with the filter gain.
A Curve like this would help a lot
I'd be really happy, if you could add that feature. Thanks a lot for your effort and your dedication to this great software.
may I suggest a feature that I'm missing in your great software?
Would you be able to include a voltage curve in the power window of the enclosure tool? Maybe as a switch between current and voltage. when I'm trying to match a driver and enclosure to a given amp I often apply peaking, LT, HP and LP filters and I end up having to calculate the resulting voltage that my amp would need to supply by multiplying the input voltage with the filter gain. A voltage curve in the power window would speed this process up a lot.
Here's a simple example:
Let's say my amp is capable to deliver 40 V above 4 Ω.
Woofer in sealed box, input Voltage: 30V, no filters
same box, but with a 6dB peaking Filter at 135 Hz
now the resulting voltage is 60V at 135 Hz, which my amp can't handle. Unfortunately I can't easily see that, unless i divide power by current or multiply input Voltage with the filter gain.
A Curve like this would help a lot
I'd be really happy, if you could add that feature. Thanks a lot for your effort and your dedication to this great software.
Last edited:
^Gain curve does not give voltage directly but it's a bit easier with supply voltage than Power chart.
Anyway, I can investigate how to show V in some chart.
Anyway, I can investigate how to show V in some chart.
Coming in a week... Includes supply voltage U and active filter stages, but not passive components.
2.0.124.0 (2025-05-07)
Enclosure- Added passive parallel filter branch Cp+Lp+Rp to Filter tab.
- Added 'Track Fb and Qtc' checkbox for Linkwitz-Transform. Copies Fb and Qtc of closed or IB to fo and Qo to help setting up L-T.
- Added optional voltage trace to Power chart. 'Show voltage' command in context menu replaces current trace with voltage.
- T/S parameters of the newly added driver are read from driver table into system simulation also when database filtering hides the other drivers.
I can't get VM to run under my version of wine, which is 9.0. Using Ubuntu 24.04LTS. Loaded dotnet452 (but got all kinds of warnings). Attempted emulation under windows 7, 10 and 11. Actually XP64, too. No dice.
The error dump shows a number of routines:
00000038 services.exe
0000003c 0
00000040 0 wine_rpcrt4_server
0000004c 0 wine_rpcrt4_io
00000064 0 wine_rpcrt4_io
0000008c 0 wine_rpcrt4_io
00000098 0 wine_rpcrt4_io
000000b8 0 wine_rpcrt4_io
000000d0 0 wine_threadpool_timerqueue
000000d4 0
000000ec 0 wine_rpcrt4_io
000000f0 0 wine_threadpool_worker
00000044 svchost.exe
00000048 0
00000054 0
00000058 0 wine_sechost_service
0000005c winedevice.exe
00000060 0
00000068 0
0000006c 0 wine_sechost_service
00000070 0
I have the latest version of LTspice running OK under wine so it's not a problem regarding the wine install, as far as I can determine.
Does anyone have any information regarding possible fixes?
The error dump shows a number of routines:
00000038 services.exe
0000003c 0
00000040 0 wine_rpcrt4_server
0000004c 0 wine_rpcrt4_io
00000064 0 wine_rpcrt4_io
0000008c 0 wine_rpcrt4_io
00000098 0 wine_rpcrt4_io
000000b8 0 wine_rpcrt4_io
000000d0 0 wine_threadpool_timerqueue
000000d4 0
000000ec 0 wine_rpcrt4_io
000000f0 0 wine_threadpool_worker
00000044 svchost.exe
00000048 0
00000054 0
00000058 0 wine_sechost_service
0000005c winedevice.exe
00000060 0
00000068 0
0000006c 0 wine_sechost_service
00000070 0
I have the latest version of LTspice running OK under wine so it's not a problem regarding the wine install, as far as I can determine.
Does anyone have any information regarding possible fixes?
Few tiny adjustments to switches in context menus
2.0.124.1 (2025-05-11)
Enclosure- Added 'Show current' command to context menu of Power chart.
- Added 'Show force' command to context menu of Excursion chart.
- 'Show current/voltage' and 'Show force/acceleration' track visibility set in Traces window.
Please excuse my disorganized rambling, but I wanted to share some of my joys and curiosities of using VituixCAD for Xover simulation and to see if anyone has some observations to improve my understanding.
I have been quite amazed at just how accurate the Xover simulation in VituixCAD is. I'm sure this isn't a surprise to EE's who use SPICE to simulation circuits, but I've noticed that VituixCAD is very accurately predicting woofer responses that are theoretically caused by voice coil inductance interaction with the filter coil inductance. Specifically, people like Wayne Parham of Pi Speakers have published SPICE model simulations which show that for woofers with higher voice coil inductance values a first order low pass Xover with just a coil will almost do nothing to the response, or the inductor must be an excessively high value. VituixCAD simulates this perfectly and I've measured this. VituixCAD also simulates the benefits of Zoebel correction perfectly as well, also measured in response and DATS impedance sweeps.
But, I never provided VituixCAD with any inductance values for the woofer, so how could it simulate the complex impedance and inductance?
I had noticed that the Enclosure Tool had some configurations for Lossy Inductance or an Extended Impedance model, but I was not using the Enclosure Tool, so how could it do, what it was doing?
But, I had read Marshall Leach's paper on "Loudspeaker Voice-Coil Inductance Losses: Circuit Models, Parameter Estimation, and Effect on Frequency Response" and Dr. Leach had shown that voice coil parameters for a lossy inductance model could be found by doing a curve fit and derivative analysis of the slopes and phase of the measured complex impedance. Aha!!! So, maybe Kimmo was doing this from the driver impedance file imported from DATS.
Of course Kimmo gives us a clue as to what's going on in the Help File where he provides a citation to a paper by Thorborg, Tinggard, Agerkvist and Futtrup. "Extended impedance model described in detail in the paper Frequency Dependence of Damping and Compliance in Loudspeaker Suspensions by Knud Thorborg, Carsten Tinggaard, Finn Agerkvist and Claus Futtrup, published in JAES Volume 58 Issue 6 pp. 472-486; June 2010."
So, maybe the mystery is solved, or it's not even a mystery I need to solve. I didn't need to read those papers, I just need to trust Kimmo and be grateful that such a sophisticated, state of the art, speaker driver filter simulation tool is available for DIY that automatically applies the best circuit modeling and simulation we have available today.
If I'm right, I think maybe not enough people know just how good this software really is, but maybe the only way to truly appreciate it, is to do a bit of research and it's okay if it all looks like magic to the rest of us.
Cheers,
Jamie
I have been quite amazed at just how accurate the Xover simulation in VituixCAD is. I'm sure this isn't a surprise to EE's who use SPICE to simulation circuits, but I've noticed that VituixCAD is very accurately predicting woofer responses that are theoretically caused by voice coil inductance interaction with the filter coil inductance. Specifically, people like Wayne Parham of Pi Speakers have published SPICE model simulations which show that for woofers with higher voice coil inductance values a first order low pass Xover with just a coil will almost do nothing to the response, or the inductor must be an excessively high value. VituixCAD simulates this perfectly and I've measured this. VituixCAD also simulates the benefits of Zoebel correction perfectly as well, also measured in response and DATS impedance sweeps.
But, I never provided VituixCAD with any inductance values for the woofer, so how could it simulate the complex impedance and inductance?
I had noticed that the Enclosure Tool had some configurations for Lossy Inductance or an Extended Impedance model, but I was not using the Enclosure Tool, so how could it do, what it was doing?
But, I had read Marshall Leach's paper on "Loudspeaker Voice-Coil Inductance Losses: Circuit Models, Parameter Estimation, and Effect on Frequency Response" and Dr. Leach had shown that voice coil parameters for a lossy inductance model could be found by doing a curve fit and derivative analysis of the slopes and phase of the measured complex impedance. Aha!!! So, maybe Kimmo was doing this from the driver impedance file imported from DATS.
Of course Kimmo gives us a clue as to what's going on in the Help File where he provides a citation to a paper by Thorborg, Tinggard, Agerkvist and Futtrup. "Extended impedance model described in detail in the paper Frequency Dependence of Damping and Compliance in Loudspeaker Suspensions by Knud Thorborg, Carsten Tinggaard, Finn Agerkvist and Claus Futtrup, published in JAES Volume 58 Issue 6 pp. 472-486; June 2010."
So, maybe the mystery is solved, or it's not even a mystery I need to solve. I didn't need to read those papers, I just need to trust Kimmo and be grateful that such a sophisticated, state of the art, speaker driver filter simulation tool is available for DIY that automatically applies the best circuit modeling and simulation we have available today.
If I'm right, I think maybe not enough people know just how good this software really is, but maybe the only way to truly appreciate it, is to do a bit of research and it's okay if it all looks like magic to the rest of us.
Cheers,
Jamie
I bit the bullet and figured out how to run windows on a virtual machine hosted by linux. It's kinda slow but Vituixcad does run. I haven't tried designing any speakers or crossovers yet. I need to work my way through the docs first.