Hello!
I'm using this program: http://www.geocities.com/f4ier/newxoversim.htm
But I have a problem using it. I try it to do exactly like in the "manual" and test it with the given files. But I only get error like: "0.0001 is not a valid floating point value". Can someone help me? 😕
I'm using this program: http://www.geocities.com/f4ier/newxoversim.htm
But I have a problem using it. I try it to do exactly like in the "manual" and test it with the given files. But I only get error like: "0.0001 is not a valid floating point value". Can someone help me? 😕
Hi,
The problem is due to the way different Windows Regional Settings represent floating point numbers. Some setups (such as US-style Windows) use the period (.) as the decimal point; others setups (European-style Windows for example) use the comma (,) as the decimal point.
Both Subwoofer Simulator and Crossover Simulator can use either the period or the comma happily... It's just that I forgot to account for the period in the default value of Rs = 0.0001... my apologies.
As soon as you change that period into a comma, everything should be alright 🙂
Users of European Windows need only replace the (.) with a comma (,) to avoid this one tiny hickup by yours truly. Rs is the only number I overlooked, all other floating point numbers automatically get converted from European to US style numbers and vice versa.
I promise to fix this single problem (and add some pretty useful features) with the finalized XoverSim version 1.
Cheers,
Isaac
The problem is due to the way different Windows Regional Settings represent floating point numbers. Some setups (such as US-style Windows) use the period (.) as the decimal point; others setups (European-style Windows for example) use the comma (,) as the decimal point.
Both Subwoofer Simulator and Crossover Simulator can use either the period or the comma happily... It's just that I forgot to account for the period in the default value of Rs = 0.0001... my apologies.
As soon as you change that period into a comma, everything should be alright 🙂
Users of European Windows need only replace the (.) with a comma (,) to avoid this one tiny hickup by yours truly. Rs is the only number I overlooked, all other floating point numbers automatically get converted from European to US style numbers and vice versa.
I promise to fix this single problem (and add some pretty useful features) with the finalized XoverSim version 1.
Cheers,
Isaac
Thanks! Another question... Why the optimizer sheet is blank?
This might be a stupid question. A great software by the way 😉
This might be a stupid question. A great software by the way 😉
Thanks for the kind words 🙂
'Cause XoverSim's user interface is really just a "quickie" interface for the underlying circuit calculation engine. The engine is my first step into the world of general circuit simulators.
The subject of optimization itself can be quite difficult to grasp, but basically one minimizes the difference between the target function and the test function. How one would find the least difference between the two functions is where the (deep) math comes in. I haven't a clue, yet. After that, the optimization programming part would be a bit like making the engine of XoverSim as I'd have to make it so that it can optimize (almost) any circuit size and (almost) any complexity.
🙂
'Cause XoverSim's user interface is really just a "quickie" interface for the underlying circuit calculation engine. The engine is my first step into the world of general circuit simulators.
The subject of optimization itself can be quite difficult to grasp, but basically one minimizes the difference between the target function and the test function. How one would find the least difference between the two functions is where the (deep) math comes in. I haven't a clue, yet. After that, the optimization programming part would be a bit like making the engine of XoverSim as I'd have to make it so that it can optimize (almost) any circuit size and (almost) any complexity.
🙂
- Status
- Not open for further replies.