I couldn't live without VMWare, it's essential for this type of work. Here's the hypervisors I've tried, and how I'd rate them for 'desktop virtualization.' (IE, mouse responds quickly, windows update consistently, it's not a nightmare to configure sound, network and USB, etc...)
#1 - VMWare player (free)
#2 - VirtualBox (free)
#3 - VMWare ESXi (free)
#4 - KVM (free)
I'm on Ubuntu and I'd expected that KVM would be the one to beat, but VMWare player is soooooo much easier and responsive IMHO
I got the same error with a MBP running bootcamp XP SP3. But I don't have this error with another PC XP SP3 systems.
In a Win7 Pro machine, I use XP mode.
Last edited:
what script it should be in dym driver in akabak to calculate "expole expore fre" or how to calculate them?
I have been going through this great tutorial and have been frustrated by Akabak's sometimes quirky operation.
Just trying to put in speaker parameters can be frustrating.
This one, for example:
Def_BassUnit 'BU1'
dD=25.98cm |Piston
fs=57.5Hz Mms=47g Qms=5.54
Qes=0.229 Re=6.3ohm Le=1mH ExpoLe=0
Xms=2mm
Vb=0 Qb/fo=0.1
It will not load. If I try to put the values into the wizard it will not accept Mms when I push 'Evaluate'. If I save to clipboard and close it lists Mms as '0'.
These values are for the Beyma 12MI100. I am getting the values from WinISD, which makes sure the values 'work'.
Any ideas what I am doing wrong? 🙁
Just trying to put in speaker parameters can be frustrating.
This one, for example:
Def_BassUnit 'BU1'
dD=25.98cm |Piston
fs=57.5Hz Mms=47g Qms=5.54
Qes=0.229 Re=6.3ohm Le=1mH ExpoLe=0
Xms=2mm
Vb=0 Qb/fo=0.1
It will not load. If I try to put the values into the wizard it will not accept Mms when I push 'Evaluate'. If I save to clipboard and close it lists Mms as '0'.
These values are for the Beyma 12MI100. I am getting the values from WinISD, which makes sure the values 'work'.
Any ideas what I am doing wrong? 🙁
i always use hornresponce to get me started,simply export the data to akabak script.
you can also check ts parameters in hornresponce by double klik sd.
you can also check ts parameters in hornresponce by double klik sd.
Just a quick glance of the tutorial.........pg. 55: Mms is defined in Kg, so try inputting 0.047.
GM
GM
It worked.
So, this is a known bug? Every other box seems to work the way it is supposed to, and it says 'g' right under the box in question - why then does it not work?
Rather frustrating.
So, this is a known bug? Every other box seems to work the way it is supposed to, and it says 'g' right under the box in question - why then does it not work?
Rather frustrating.
I've no experience with AkAbak beyond what I posted.
??? Are you saying that in loading other drivers it accepts Mms in grams or just that the input box implies it should be in grams?
GM
??? Are you saying that in loading other drivers it accepts Mms in grams or just that the input box implies it should be in grams?
GM
As a general rule, if a field in a wizard has one or more unit names below it, you need to specify the unit if you want to use other than the default.
For the case in question:
1. Paste epa's def_bassunit into an Akabak script. Leave the cursor in the data.
2. Select Def_BassUnit (Ctrl-B)
3. Note that the "Mechanical Mass Mms..." field has "47g" in it, and the legend underneath says "kg,g,..."
For the case in question:
1. Paste epa's def_bassunit into an Akabak script. Leave the cursor in the data.
2. Select Def_BassUnit (Ctrl-B)
3. Note that the "Mechanical Mass Mms..." field has "47g" in it, and the legend underneath says "kg,g,..."
Seeing that it specified 'g' as an alternate unit I did write 'g' after the '47'.
At any rate, I am going to try a couple of other drivers tomorrow and see what it does - but at this point it looks flaky to me.
In what other ways does it act flaky?
At any rate, I am going to try a couple of other drivers tomorrow and see what it does - but at this point it looks flaky to me.
In what other ways does it act flaky?
Every time AkAbak has given me "flaky" results it has been because I got lazy and forgot to explicitly specify a unit for a parameter. Note that in some of the wizards the input boxes allow you to specify alternate units depending on whether you have Thiele-Small parameters or mechanical parameters. Here is part of an "AkAbak for Dummies" doc I wrote a few years ago:
From the top menu select "Def -> Def_BassUnit...".
A data entry window will open, called "Definition Def_BassUnit / Calculator".
In the top row of boxes, enter the parameters for the driver you are using.
You should have everything except maybe the voice coil inductance.
Note the units choices for some of the boxes.
Akabak allows you to specify your driver in physical values (Mms, Cms, Bl etc) or Thiele-Small values (Qms, Qes, Vas etc), or a mixture of both. Right-button clicking on a box will pop up a list of parameters that Akabak will accept for that field.
For example, the second box from the right may be labelled either "Mechanical Mass (Mms)...", "Equ. vol. to compliance (Vas)...", or "Mechanical Compliance (Cms)...".
You can either change it to the value you have by selecting from the right-click menu, or just enter the value you have with the correct unit suffix. To enter Vas, specify volume units, for example in cubic feet (2.4ft3) or litres (49L). Mms, Vas and Cms have different units of measurement so Akabak will know which value you have entered.
Also, the driver "Diaphragm diameter" (dD) is more commonly specified as "Diaphragm Area" (Sd). You can enter the value as a diameter (for example, 16.5cm) or area (for example, 200cm2).
In the second row of boxes you can enter the Xmax parameter if you have it, and the volume of the enclosure. The rest of the fields can be left as they are.
Check for Typos
---------------
Press the "Evaluate" button at the bottom of the window. If all of the required values have been entered, AkAbak will populate the two rows of values at the bottom left of the window. Values such as "fc", "Qtc", and "f3" should be close to those calculated by your other program.
If the fields do not populate, look to see if the cursor has moved to one of the input fields at the top of the window. The value may be missing (and required), or AkAbak can't understand the entered value.
If the evaluated values are very different than your pre-calculated box, then Akabak has likely misinterpreted one of the input values. For example, AkAbak defaults to "cubic metres" in the "Vb" field. Entering "165" will be interpreted as 165 cubic metres. Specify the unit, for example litres (165L) or cubic feet (6.2ft3).
From the top menu select "Def -> Def_BassUnit...".
A data entry window will open, called "Definition Def_BassUnit / Calculator".
In the top row of boxes, enter the parameters for the driver you are using.
You should have everything except maybe the voice coil inductance.
Note the units choices for some of the boxes.
Akabak allows you to specify your driver in physical values (Mms, Cms, Bl etc) or Thiele-Small values (Qms, Qes, Vas etc), or a mixture of both. Right-button clicking on a box will pop up a list of parameters that Akabak will accept for that field.
For example, the second box from the right may be labelled either "Mechanical Mass (Mms)...", "Equ. vol. to compliance (Vas)...", or "Mechanical Compliance (Cms)...".
You can either change it to the value you have by selecting from the right-click menu, or just enter the value you have with the correct unit suffix. To enter Vas, specify volume units, for example in cubic feet (2.4ft3) or litres (49L). Mms, Vas and Cms have different units of measurement so Akabak will know which value you have entered.
Also, the driver "Diaphragm diameter" (dD) is more commonly specified as "Diaphragm Area" (Sd). You can enter the value as a diameter (for example, 16.5cm) or area (for example, 200cm2).
In the second row of boxes you can enter the Xmax parameter if you have it, and the volume of the enclosure. The rest of the fields can be left as they are.
Check for Typos
---------------
Press the "Evaluate" button at the bottom of the window. If all of the required values have been entered, AkAbak will populate the two rows of values at the bottom left of the window. Values such as "fc", "Qtc", and "f3" should be close to those calculated by your other program.
If the fields do not populate, look to see if the cursor has moved to one of the input fields at the top of the window. The value may be missing (and required), or AkAbak can't understand the entered value.
If the evaluated values are very different than your pre-calculated box, then Akabak has likely misinterpreted one of the input values. For example, AkAbak defaults to "cubic metres" in the "Vb" field. Entering "165" will be interpreted as 165 cubic metres. Specify the unit, for example litres (165L) or cubic feet (6.2ft3).
Thanks for your reply Don. Love your tutorial - is in fact what I am using to learn the program. 🙂
I was sure I was doing something wrong as I said in post #46, but so far no one has been able to show me what that is.
Even now I am sitting here with the wizard populated and when I write in '47g' it does not accept it, and when I write in .047 it does accept it. All other values the same, paying particular attention to write '47g' as stated in the label below the box.
So I am trying a different driver - the Eminence Deltalite II 2512 - and I am getting the same results. Mms is 49g in this driver, and it will not accept '49g', but accepts '.049' just fine.
Really - no one else has this problem? I mean, I'm not going to cry about it if it's the only bug in the program, but it does seem quirky to me, no matter how you slice it.
I was sure I was doing something wrong as I said in post #46, but so far no one has been able to show me what that is.
Even now I am sitting here with the wizard populated and when I write in '47g' it does not accept it, and when I write in .047 it does accept it. All other values the same, paying particular attention to write '47g' as stated in the label below the box.
So I am trying a different driver - the Eminence Deltalite II 2512 - and I am getting the same results. Mms is 49g in this driver, and it will not accept '49g', but accepts '.049' just fine.
Really - no one else has this problem? I mean, I'm not going to cry about it if it's the only bug in the program, but it does seem quirky to me, no matter how you slice it.
Well, I marked and copied the bassunit spec from post #46 and pasted it into a new AkAbak script. I put the cursor in it and pressed Ctrl-B. The wizard came up OK, and pressing "Evaluate" populated the solution boxes at the lower left.
I deleted and typed in "47g" and also tried "0.47". They both evaluated the same. See the attached screenshot and compare it very carefully with your screen.
Edit:
I've just looked carefully myself. Vb should not be zero. Try specifying the enclosure volume.
Attachments
Last edited:
I figured. 🙂
Stranger and stranger....
Thanks for your investigations Don. I went back and copy/pasted the parameters listed in post 46 into a new script and hit Ctrl-B and sure enough it populated the Bass Unit Wizard with an Mms of "47g", accepting either '47g' or '.047'. Okay.
It is true that I hadn't written a Vb in post 46, however I had been trying it with and without Vb values in trying to get it to work. FYI, I settled on a Vb of 3L for a f3 of 199 Hz. The evaluation problem was there whether or not I entered a Vb.
Strange thing - that value does not work with the script generated in that fashion. With this script, it takes 4L for an f3 of 200 Hz. With a Vb of 3L this script gives an f3 of 214Hz. Also, if I go back to the Def-Bass Unit wizard and enter the values manually, it still will not accept '47g', but does accept '.047'. If I fill the wizard manually, 3L still gives an f3 of 199Hz - with all values appearing the same.
I am considering two possibilities at this point; Perhaps there is something wrong with my installation. Perhaps at some point when I was first playing with the program I screwed up some setting somewhere that is playing havoc with parameter entry. Or, perhaps there is something wrong with these numbers. Even though I got the numbers from WinISD, which is also famously finicky when entering T/S data, there is something about the numbers it just doesn't like, and is able to interpret the numbers somewhat differently depending on how they are entered.
Really though, I have no idea. 😱
Last edited:
OK, I tried it "manually" and saw the problem. It appears to want the Vas instead of the Mms value. I'll play with it some more in my "copious free time" (ha, ha). It is probably sensitive to the order in which the parameters are entered. It only occurs on manual entry, I found that if I do a def_driver and then do a def_bassunit with the cursor in the driver parameters it also works OK.
I doubt it will ever be fixed, it'll just have to be worked around. I suspect I haven't seen the problem because I try to work in one parameter space or the other - either all Thiele-Small or all electro-mechanical.
E-M: Mmd, Mms, Cms, Rms, Sd, B, L, Re
T-S: Vas, Fs, Qms, Qes, Qts
Years ago I wrote a note to myself in my workbook:
"Suggested entry order for auto-calculators such as WinISD and LspCAD:
Qes, Qms, Fs, Vas, Re, Le, Xmax, Pe"
I doubt it will ever be fixed, it'll just have to be worked around. I suspect I haven't seen the problem because I try to work in one parameter space or the other - either all Thiele-Small or all electro-mechanical.
E-M: Mmd, Mms, Cms, Rms, Sd, B, L, Re
T-S: Vas, Fs, Qms, Qes, Qts
Years ago I wrote a note to myself in my workbook:
"Suggested entry order for auto-calculators such as WinISD and LspCAD:
Qes, Qms, Fs, Vas, Re, Le, Xmax, Pe"
Interesting, the manual lists the values that have alternate terms and Mms isn't one of them.
GM