Creamware XTC mode with SONAR

[kp]

I've (finally!) worked out how to reliably get XTC mode to work with SONAR (tested with 4.01). There are some caveats (below):

Open the Scope cset.ini file, find the
[XTC-Config] setting and make sure it's set as follows:

[XTC-Config]
AddHost=0

before scanning any XTC VSTs: the default is AddHost=1 (no, I have no idea what
it does, but it doesn't appear to make any difference no matter what it's set to). I've
had them working with both DirectiXer and the Adapter (latest version) now.

Oustanding issues
- If you use XTC plug-ins with a WDM driver (ie. not the Scope ASIO), then using
more than one XTC plug-in in a project causes horrendous audio glitching

- If you use XTC plug-ins with a WDM driver, and use just a single XTC plug-in
in a project, having the latency slider set to anything other than the far left
will cause bad (unusable, but not painful like the above) audio stuttering; no
twiddling with XTC buffer settings can resolve this as far as I can tell

- Don't even think about trying to use the XTC plug-ins in something like Sound
Forge, which is using MME drivers - you'll get nothing apart from audio garbling
(I assume this and the 2 above are all related)

- The XTC synths work (if wrapped as DXi's) but adding/removing any FX in any
track seems to cause SONAR to "lose" the synth - I found that just waggling the
volume in the MIDI track controlling the XTC synth was enough to find it again,
but it makes them essentially unusable (although no great loss in my opinion)

- This may be solely a Creamware/Scope ASIO issue, but SONAR is currently always
reporting 23ms latency on opening, irrespective of what the ASIO latency is set
to, and it needs a trip to the ASIO Panel from the Options\Audio dialog to cure