Page 1 of 1
Bug in Scope5 for Xite1 with Samplers
Posted: Tue Jan 26, 2010 4:40 pm
by bdvox
Hi folks,
Everything seems to be fine in this new setup, except for all samplers (from the 2k to the 5k)
When i add one of them in the routing windows i've got :
"Can't find DSP file MVC STS 5000 VxD - Please Check Installation."
Enter OK then the sampler receives MIDI messages but not audio, neither in programs or sample edit.
Config : Core 2 Quad, Intel P43 Mobo, 4Go RAM, 7 32bits Finale, and last Scope 5 for xite downloaded from S|C; ran as admin.
Somebody to help me ?
Thanx for advices.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Tue Jan 26, 2010 8:14 pm
by dawman
I must have the files under different names as I can load what you see here before it askd for optimizations. etc.
VXD files were old carry overs from Win 98 and we won't be needing those anymore.
Check your pm.
untitled.JPG
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Tue Jan 26, 2010 10:45 pm
by garyb
vxds aren't used in Scope 5, i believe. maybe you should rerun the installer. did you install the latest version?
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Tue Jan 26, 2010 11:06 pm
by bdvox
@Xite/4live : except i see you're lucky to run many samplers in your project, i did not understand what i have to do => "Check your pm" ?
how to do to make a clean desinstall and a new reinstall ? because, of course, i 've tried to run again the install. And with the last that is on S¦C platform.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Tue Jan 26, 2010 11:12 pm
by bdvox
Ok JAV, i've just remembered what a "PM" is
i'll try that this evening.
Bye.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Wed Jan 27, 2010 11:02 pm
by bdvox
still the same error message ...
I emailed the problem to S|C support but no answer.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Wed Jan 27, 2010 11:22 pm
by garyb
do you have pci cards or the software for the pci cars on that computer?
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Thu Jan 28, 2010 1:47 am
by bdvox
I had a Pulsar I on this PC, but now, not any more.
I used desinstal prog once PCI card had been removed, but maybe something of the old setup is still there.
How can i do to be sure of that ? I would appreciate not format my hard drive and reinstall 7.
Thanx for your help.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Thu Jan 28, 2010 9:22 am
by garyb
you could remove any references to Creamware in the registry to start.
actually, first...
is that an old project? what happens with a new project that you load a new instance of sts? i think that the program is searching for a device that was in the old Scope(pci) folder.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Sun Jan 31, 2010 10:36 am
by bdvox
that was a new project.
So i've desinstalled app once again, and hunted all scope entries in the registry to eliminate them.
Still the same problem.
I've noticed that this is the same problem with the VDAT device.
If it can help you there's the tree of my xite dir in attachment.
Thanx for your interest.
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Sun Jan 31, 2010 11:24 am
by garyb
have you downloaded the possibly new versions of those devices from the S/C ftp(scope 5 folder)?
Re: Bug in Scope5 for Xite1 with Samplers
Posted: Wed Feb 24, 2010 11:01 am
by t_tangent
I have also had that same problem when loading STS Samplers as well as a couple of other devices such as Solaris, and I am also running Scope for XITE-1 on Win 7 32bit.
There was an official response from SC about this
Basically they said to run Scope for XITE as administrator and the easiest way to do this is to right click on the Scope icon and select Properties, then go to Compatibility tab and tick the bottom box where it says Run this program as an administrator.
This fixes the issues with not finding those vxd files etc. But it presents a new issue that when running as administrator you cannot copy files directly from windows explorer to the Scope Routing window. Although this is a small issue, it can be useful to do that sometimes when testing devices etc.
I presume this is all to do with account permissions or Ownership of a program in Win 7 and I have been looking at ways to change these settings so that our normal user account has full permissions as that might solve both issues. But so far I've not had any success, so maybe someone else has a better idea.
Will report back if I find any more about it, or SC might be on to that in the next update, hopefully.
Cheers