Scope x86 under Win64 ?

[dante]

Is anyone running Scope 32 bit ( eg installed in Program Files(x86)/ ) in Win 64 bit ?

Just wondering if thats possible as one could still use STS etc in Scope project, but at the same time have more than 4 gig RAM for Kontakt samples in a 64 bit Native host app.

Or does ASIO break if all connected apps aren't 64 bit?

[dante]

Bounce - surely someone who tried this ?

[djmicron]

scope is already 32 bit app.

[dante]

Yep. And it's also a 64 bit app. Theres both on S|C FTP. Just like there's versions for PCI and XITE ( 4 variations in all ).

I want to know if anyone has tried running Scope 32 bit on Windows 64 bit in conjunction with say Cubase 64 bit.

With Cubase having Scope XITE ( or Scope PCI ) selected as its main audio driver.

If it did, then would we not have an environment where the STS samplers would run in Scope, and at the same time with say Kontakt running in Cubase as a VSTi with access to more than 4 GB RAM.

[dawman]

Yes but Reaper uses x86 and x64 simultaneosly, perhaps I should try this XTC shit while I have a new build I'm testing just to see.
I'd love to get even 2GB's of RAM from the STS5000 as I also have an excellent AKAI collection. 265 FDD's actually.
I always wanted to use the D50 partials and other small looped goodies that can be used like a matrix where 4 x parts are mixed, and maybe each have a seperate output into some of my latest Modular Effects and routings...

what's it called ..? XTC/VSTim..?
Sure beats waiting if there's a work around.....
I actually have Kontakt 2 still and if I remember it loaded alongside of other K4 instances that were loaded, It was an accident, hope I didn't erase the dll.s
But I use 32but Bidule VST and then it houses X64 in its shell too...

[dante]

If you got a good AKAI collection then good reason to try it in SPF mode at least (dunno bout VSTim mode).

The other workaround is to use the Volkswagon sampler on x64 (that should play yer AKAI sounds and is available on ftp://sonic-core.net/software/Volkszaempler/ ) that should run as a VSTi whilst yer still load big Kontakt libs in big x64 mem space.

But its the clarity of the STS on DSP I'm after Horton.

[garyb]

that's not how it works(afaik).

it's the 64bit EVIRONMENT of win7 that is incompatible with Scope samplers. Volksampler runs on the CPU. even though it's very similar to the STS, it's not the same.

the 64bit version with the 64bit driver is REQUIRED for 64bit windows, period. otherwise, why spend the man-hours developing it?

much(most) of the Scope program IS a 32bit app, though.

[djmicron]

Yep. And it's also a 64 bit app. Theres both on S|C FTP. Just like there's versions for PCI and XITE ( 4 variations in all ).

I want to know if anyone has tried running Scope 32 bit on Windows 64 bit in conjunction with say Cubase 64 bit.

With Cubase having Scope XITE ( or Scope PCI ) selected as its main audio driver.

If it did, then would we not have an environment where the STS samplers would run in Scope, and at the same time with say Kontakt running in Cubase as a VSTi with access to more than 4 GB RAM.

what i mean is, the scope 64 bit package is 32bit app with 64 bit drivers.

the sts is buggy under 64 bit os, it's a windows app, it's not like the other devices, it doesn't run on the scope dsp.

[dante]

that's not how it works(afaik).

it's the 64bit EVIRONMENT of win7 that is incompatible with Scope samplers. .

Thats what I thought might be the case, just wanted to know in case there was an unexplored workaround.

[timstoel]

I've attempted installing the 32 bit Scope software on x64, it did not work for me, but you got me thinking about it again now. I tried a lot of different ideas to get around this and have not had any luck yet. It's a real bummer the 64 bit doesn't work 100%, because everything else on that machine is 64 bit.

I can't really blame Sonic Core specifically for this problem either, there's still a lot of stuff out there that hasn't gracefully migrated over to x64, despite it being available for about ten years now (since Windows XP x64 came out, which I adapted WAY to early.)

Tim