A couple of weeks ago I posted the topic
"XTC or SFP for VST on DSP". Besides some general banter, I detailed a problem I was having with XTC. I had contacted Creamware and eventually they very kindly got back to me with as much help as they could give me. They even sent me a PDF guide of setting up your PC to work best with your Creamware cards. (Yay Creamware!)
The disapointing thing was that the person replying told me he had never come across the error message I was getting:
"ScopeDriverIoctl (1908888) returned error code -99"
I've been changing my configuration ever since to see if I could crack the problem.
I somehow got all three of my Creamware cards - 2 x LunaII and a 14 DSP booster - operating on their own IRQ's. No interferance from things like USB or FireWire. The problem continued however.
A day or so I developed a hunch that perhaps the problem may have been caused by registraion and ownership of various elements of my system. The card in that system that is fully registered for SFP4 and all the plugins that I use is one of my LunaII's.
When I checked in 'cset.ini' I found that the host card in XTC had been set by default to "Scoperev=128". I changed the line to "Lunarev=130". This was just a guess mind you. I'm not good with code of any description. I checked the revision number of my board and made up what I thought might work.
Since then I've run two tests on a session that was giving me the error almost as soon as it loaded or as soon as I added another Vinco to it. Twice now I've been less then gentle with the adding of XTC plugins and switching of outputs in VST Connections, both of which were causing the error message previously. In both tests I've managed to max out the DSP and bring it back again and have not had the error message!!!!
![:smile:](./images/smilies/icon_smile.gif)
Cross fringers I've solved the mystery problem.
Happy Scoping everyone.
Cheers,
AudioDan
_________________
Mixing in DSP XTC
<font size=-1>[ This Message was edited by: AudioDan on 2005-06-20 20:55 ]</font>