Has anyone been successful getting the STS samplers to work without freezing/crashing on Windows 8, with a multi-core cpu?
As much as I love the speed of making music with strickly VSTs and Kontakt and etc, evrytime I play a song I did with the STS sampler it sounds better to my ears(IMO) and any other dsp based sampler for that matter, missing it right now. Its about the sound for me.
STS sampler on multiprocessor CPU/Windows 8
Re: STS sampler on multiprocessor CPU/Windows 8
32 or 64bit?
there's no issue that i know of in 32bit, but of course there are no sts samplers in 64bit...
there's no issue that i know of in 32bit, but of course there are no sts samplers in 64bit...
Re: STS sampler on multiprocessor CPU/Windows 8
for reasons you mentioned, on 32 bit with a Muti-Processor CPU(non-disabled cores).
Re: STS sampler on multiprocessor CPU/Windows 8
shouldn't be an issue, although there's an update to win8 that's been making trouble, KB2919355
Re: STS sampler on multiprocessor CPU/Windows 8
Does this one cause the many dialog prompts when opening scope? I have that issue and even after reinstalling scope.
I have never been able to get the sts samplers to stop freezing on xp without change the processer type to uni
I have never been able to get the sts samplers to stop freezing on xp without change the processer type to uni
Re: STS sampler on multiprocessor CPU/Windows 8
dialog prompts? i'm not sure what you mean. i'd have to see the screenshots.
uni-processor only on XP? well, maybe in v3 or XP sp1. there haven't been problems with multiprocessors for some time as far as Scope and XP goes. maybe something about your setup or mix of software?
uni-processor only on XP? well, maybe in v3 or XP sp1. there haven't been problems with multiprocessors for some time as far as Scope and XP goes. maybe something about your setup or mix of software?
Re: STS sampler on multiprocessor CPU/Windows 8
have you got the sdk
as some of us had problem where it used an earlier driver file and the delays stopped working
reverting to the scope 5.1 driver sorted this out
as some of us had problem where it used an earlier driver file and the delays stopped working
reverting to the scope 5.1 driver sorted this out