1.
Dan wrote:
It requires much data that can be auto-calculated |
|
|
There is an 'auto-calculate' box at the bottom of the parameters window that is used when entering driver parameters. Click it to calculate unknown values. The Help section details the steps in entering the numbers.
- Parameters may be and should be auto-calculated.
2.
Dan wrote:
WInISD also seems to incorrectly calculate port air speed |
|
|
WinISD displays vent air speed by using a graph, and by default the output is shown as 'peak'. Place the cursor on the "peak" and click to change to RMS. Changes like this are made by using File > Options > Graph. Changes made will be set as default the next time the program is opened.
In the Tempest example, which I duplicated after entering parameters from the Adire site (and using a port diameter of 4"), WinISD displayed air speed at 27 m/sec. But, after changing the graph to display RMS, the display showed 19 meters/second.
3.
Dan wrote:
WInISD does not allow calculations of series/parallel wiring options for DVC drivers. |
|
|
The choice of parallel or series for DVC subs is made in the database editor under the parameters tab. DVC drivers have a different designation (name) than do their SVC counterparts, so when you enter data for that driver and save the file, the program will remember how you have the coils wired. If you want to change series to parallel (or vice versa), open the database editor and change it there. You can save the change and give it a different name, so now you'll have both ways of wiring in your saved database. And you are not limited to DVC; any number of voice coils can be entered.
- Multiple voice coil drivers are calculated according to wiring.
4.
Dan wrote:
WinISD does not even attempt nonlinearities. |
|
|
Nonlinearities at max excursion is beyond the scope of my understanding. And I will bet that is also true with the vast majority of enclosure builders who are looking for a good design help program.
5.
Dan wrote:
The errors in vent sizing alone are reason to avoid it, IMHO. |
|
|
Some people expect the program to give an opinion on vent diameter when a new project is opened. It does not. Instead, a default value of 102 mm (shown as 4.02 in) appears with the calculated port length for that diameter. The program just simply calculates port length according to the port diameter, box volume and tuning frequency. The user must be aware that he can highlight and change the port area to the size he wants to use,( then input wattage and check the graph display to see if the vent air speed is less than 10% of mach). If it's too high, enlarge the port opening. Vent air speed can be verified by using other calculators, such as these two combined.
- I have heard this criticism (errors in vent sizing) more than once, but no one has yet to demonstrate an example where it errs, or has ventured a reason as to why they believe it errs in calculating vent sizes...in any manner that can be substantiated.
There are a number of ways to verify port volume, or diameter vs length calculations, several of which are found in this list.
6.
Dan wrote:
Many T/S parameters are not correct |
|
|
Any part of the overall build can and should be double-checked with other calculators or information, especially the very basic aspect of making sure the driver parameters are correctly entered.
- One should enter parameters himself and not rely on those entered by someone else at some other time. I think that would be wise when using any of the design programs.
The more I use this program the more I find how useful it is. It may be substandard in the eyes of a world-class speaker designer, but for the majority of posters on this forum who want to build their own box it is a good design tool, and becomes very user-friendly with use. Anyone wanting to get some good help in designing enclosures should give it a fair trial, but put forth the effort to learn how and why it forms its calculations and how to interpret the results.
Here is the link to download: http://www.linearteam.dk/default.aspx?pageid=winisdpro
It is free to use.
Build the box so that it performs well in the worst case scenario and, in return, it will reward you at all times.