Stereo Tool

I'm trying out the command line version of Stereo Tool 3.14, but whatever I do it allways crashes. The output I get before the fcrash is this:

--8<--
STEREO TOOL 3.14 CONSOLE APPLICATION - (C) HANS VAN ZUTPHEN, 2001-2008
Converting .\house.wav to .\w.wav using settings from .\Portable.sts

AMPLIFICATION:
pre amp: 3.00*
post amp: 1.00*
STEREO: ON
phase amp: 0.00*
width amp: 1.00*
extra phase: +0°
mono<->stereo: 0.00 (-1 mono only...+1 stereo only)
DUALBAND: ON
maxval: 5380 6260
upspeed: 0.00004 0.00004
downspeed: 0.00040 0.00040
MULTIBAND: ON
maxval: 5380 6260 6750 6940 6850 6310 5670 4990
upspeed: 0.00004 0.00004 0.00004 0.00004 0.00004 0.00004 0.00004 0.00004
downspeed: 0.00040 0.00040 0.00040 0.00040 0.00040 0.00040 0.00040 0.00040
Encountered RIFF/WAVE header "fmt ", copying 16 bytes
Encountered RIFF/WAVE header "data", processing 36628156 bytes
--8<--

After this Windows tells me stereo_tools_cmd.exe has encountered a problem and needs to close and shows this error signature:
AppName: stereo_tool_cmd.exe
AppVer: 0.0.0.0
ModName: stereo_tool_cmd.exe
ModVer: 0.0.0.0
Offset: 000047f1

Does anyone have a wav file that is tested to work with the command line version that I can test it with?

If there's a debug switch/version of the command line tool I can try to get somk more info on the problem.

Regards
/Jonas

WAAH! I just tested it and it crashes here all the time too... Will look into it asap!

I've compiled a new version, it can be downloaded now.

My apologies for the inconvenience. I had made a change to the Stereo Tool processing between versions 3.13 and 3.14, but I never realized that it would impact the command line version also. So I completely forgot to test it before uploading it. As in "It builds, let's ship it"...

I will add an automated test of the command line version which will be ran automatically before a version is uploaded to avoid this type of problems for future versions. Thanks for notifying me of this problem.

Note: When using the command line version, you need to specify the FULL PATH to the sts file. So .\Profile.sts won't work - you really need to use something like C:\blabla\Profile.sts ! (For the input and output files, you can use relative paths without problems).

Hans

That was fast!

Many thanks.
The newly uploaded version works fine here. Now I'm off to experiment with the tool.

Regards
/Jonas Eckerman