PlanetZ forums - scopeusers.com

Strictly East, yes, that's the one i have but they come in more flavours: older generation, different amount of slots, 64bit pci card support... i can do 7 Masterverbs on this one with a single 14dsp card. Speaking of motherboard 'native' pci capability vs magma boxes i'd say for current hardware it...

i can confirm that at least Magma 4 slot chassis with PEHIFX PCI-Express Interface Host Card works fine with PCI Scope cards. look for PCI magma on ebay, they have some crazy deals and the chassis are top notch, made of aluminium and with proper power supplies... also, if you want i can sell you a m...

hya! Regarding Scope 64bits - it's just the driver that is 64bits (and it must be so in order to work on 64bit operating systems); all the XTC vst plugins and Scope software are 32bits as before, except some modules that are perhaps "sucked-in" by the driver - these have to be specific for...

thanks for your input! well, i'm still on scope 5 where xtc and vdat do work, but asio requires wet nursing (setting software priorities and affinities to avoid clicks) but it is usable in many older programs. for 88K, wider asio support and wdm audio i/o i use other cards. scope 7 should have more ...

hi, peeps!
just a quick check on scope 7 after some years have passed. let me know if these conditions are still true (for x64 version):
xtc doesn't work;
vdat doesn't work;
88KHz samplerate is not there still;
wave inputs give garbage;

thanks!!

i'm running v5.1 on x64 with XTC. As XTC vst version is quite old (from the nineties), not all daws run these plugs, but some do. For example, Samplitude 11, Live! 8, older versions of Cubase (haven't tried new though)... others just scan them but not initialize. i'm happy with it. it can't 'render'...

no matter if you install scope for x64 or x32 system, scope vsts are still 32bit; xtc mode comes from long ago and seems to be unaltered and follows а very old vst standard which doesn't work on some daws even in 32bit. if you really want to try, try with jbridge. that way you could wrap 32bit plugi...

iSiStOy, ASIO should be fine. If it's not, it can be made with tweaking system, but it really can work glitch-free. I've tried running sine generator (good for auto click detection) and recorded from asio for a day - no clicks if the system is fine. but with wave it's different. it randomly clicks o...

babaorum, it's exactly the same (noise on wave ins, random clicks on wave outs) with xite with x64. Other weird thing that got carried on since old times is that 88K sample rate is unavailable. It would lock on incoming 88 clock and display 96 - and then in sfp it is usable, but if you need actual 8...

babaorum, noise appears on wave inputs, and random clicks appear on wave outputs.

noise on inputs and clicks on ouptuts (wave, not asio!) appears in all 64bit systems.

i don't know about 32bit systems, perhaps it is fine, at least it used to be with v3 and v4 software...

maybe it is called Src 6 or Src 7?

I can confirm that [ tco4: unknown external symbol 'SavAstatSync' ] too - Scope v 5.1 x64

Hi, letting you know that at least in 5.1 x64 PCI and XITE versions channel numbers are upside down - you have to patch accordingly to avoid L/R swap. and i still wonder if wave drivers will be eventually fixed and click free. and will wave dest eventually work on x64? a quick check for you: https:/...

in my opinion, for socket 1150 you can't get better than this: http://www.fujitsu.com/fts/products/com ... 3236s.html

yes, you have to get all sliders a bit higher to compensate...

Sounddesigner, 64bit system would run all your 32bit plugins fine. You loose only 16bit program compatibility when going x64. And you also have to have x64 drivers... In Scope you'd loose wave in, z-matrix, osiris xp and that's about all. As for network... no, my network IRQs are not shared with any...

Yea, garyb, ASIO Scope is working fine when the rest is fine. I've been able to detect a culprit - it's the intel lan driver that upsets Scope and Lynx too, to a bit lesser degree. Got an old version of the driver (proset 19.1) and it's better. Sounddesigner, do you still have that old 'beta?' drive...

Well, Scope ASIO setup presents itself with some routing selections and latency setting panel. So there are buffers somewhere, how to say 'pouch'. If not in hardware, then in software: 64, 128, 256, 512, 1024 samples. And yet for some random clicks even highest setting doesn't help. But VDAT in Scop...

yes, Gary, exactly that, timing! But to cover up for that, we have buffers - the card can hold something in its pouch until the bucket arrives and takes what's in that pouch. But in our scenario, no matter how big a pouch (ulli setting), sometimes its contents is lost, even though asio software does...

Hmm, but what's scope doing in this scenario is pumping some 2Mbit per second over 1000 Mbit/s capable PCI bus through ASIO to a software application that is doing recording and drawing some meters, what takes only 0,1% cpu and this tandem still fails even there are plenty of free resources around.....