Re: [SoX-users] Help please! Need to stop beating my head against the wall.

[Jeremy N. - ml s. u. <jn....@wi...>]

On 2016-02-18 21:23, Mike Morris WA6ILQ wrote:

> BTW, all the above commands and the -d option worked just
> fine on my old XP system.... just not on Win7.

I've never used W7, just XP and W8[.1], but for the latter I
first had to explore Control Panel -> Sound... and find out
what is set as the default playback (and/or recording) device.

On my system I usually have a plug-in USB audio interface defined
as the default, but if I unplug it sound only sometimes then plays
through the laptop's speakers (it has no headphone socket). Sometimes
when I go into the sound setup menus I find no device is configured.

On W8.1 the relevant settings are also available from a loudspeaker
icon in the systray, but it's easier to explore the options (I think)
via CP.


> On a different topic, on most commands I can type a " > log.txt"
> at the end of any command and get a plain text output of the
> command results.
> Not with sox.  I tried the "Run as administrator" option and
> had same result.

I have (REXX) scripts that issue sox commands on a Win 8.1 system, and
the output does get redirected, but I note from the code that issues the
commands that I'm redirecting both "standard output" (which is what your
redirection does) and "standard error", by also specifying "2>&1".   So
for example a command I might issue is:

    sox.exe parm1 parm2... >log.txt 2>&1

Sox is not alone in needing this; many commands do.

-- 
Jeremy Nicoll - my opinions are my own