PlanetZ forums - scopeusers.com

Hi Bud! Dante Virtual Soundcard has a minimum latency of 4ms "for the network" PLUS whatever you set for Dante ASIO driver itself (can be as low as 32 samples) PLUS whatever you set for a buffer in-between Dante ASIO and the network (could be as little as 1ms). i have my netork at 4ms, asi...

have you tried marrying scope to Dante with Dante via? https://www.audinate.com/products/software/dante-via
computer has its own eth port(s) anyway

i'm using scope in xtc mode under DAW with Dante virtual soundcard driver. works fine!

if windows build 22h2 and 13th gen cpus are not “now”, i don't know what “now” is...:) i've set it to high performance and min and max % to 100 and still it showed many cores as “parked” and had latency spikes in less than three minutes at around 17 ms. now it's under 4 at all times even if some big...

scope's asio was peculiar even fifteen years ago - espec. with newer software. i didn't go past scope v5.1 to see how good or bad it has gotten because it seemed that XTC capability was castrated out - a crucial thing for a dsp processor card - an interface with a DAW - taken out, essentially leavin...

hmm so you say we should say goodbye to Scope ASIO because they can't code it properly now and stick to SFP - okay, so be it, but then again, in SFP things don't work also - Osiris XP - still being offered on S|C page for $600 (no x64 support), vDAT, even if it is old, it might be exactly why someon...

Incorrect anyway, with Scope 3.1c the driver properly supported multithreaded Windows environments as far as the driver is concerned. if it's incorrect why then if I set affinity of the DAW exe to CPU0 it improves matters with clicking if there are more things running in the background? this happen...

try scope v7, ASIO might behave better in that one.
i _feel_ v 5.1 ASIO is oldschool and not so good with multithreading, and newer windows also have various tricks for improving audio performance, but the driver must use them... audio priorities and what not. that's not present in old drivers...

hello!
just a reality check: on 64bit systems - scope 7, 8 - no vdat, no XTC?

thxx,

... and the project was ripping ADAT to VDAT in sync, and at the same time a rough mix was being done for monitoring and also was bouncing to another VDAT... interestingly, VDATs didn't want to be cascaded from the same clock and even threw some error that it can't be done but nevertheless functione...

oh, i see the image has been mangled beyond visibility so i must reveal the system - windows server 2012 r2 without KB2919355 update

https://pranza.audiomastering.lt/IMG_4070.JPG ripped some оld ADATs from XT last week! even the sync input works as we can see. however, sync output from scope doesn't want to go as discussed earlier on https://forums.scopeusers.com/viewtopic.php?p=321742&hilit=savastatsync#p321742 i wonder if ...

uuuu, v8

is XTC mode back?

wow guys, gotta try this!

5.1 still works

IT WORKS WITH WINDOWS 11!

do this: https://www.techperiod.com/disable-sign ... ed-driver/

and then install the driver.

also, run scope.exe as administrator, as otherwise it won't be able to load some modules.

the same applies to windows 10...

i can confirm PCI Scope v 5.1 working on windows 11 laptop via pci to pci (magma cardbus) to cardbus to pci to pcie adapter chain ;) however, as with any windows system past win 8.1 without KB2919355 applied, vdat's attempt to record results in a hang. also, with such impressive chain of pci convert...

14 and 15 dsp cards should be the same length and also 15dsp is older...

time to return that expansion solution if you still can...:) i'd still suggest magma over internal slot as difference in sound quality is so unbelievable i'm still shocked (although i use only digital i/o to external dac!). maybe my pc is so bad because it's full of stuff but anyway it's good to hav...

oh yes, i'd gladly use two scopes with different i/o panels or an xite instead, but lynx covers up for missing samplerates (88K and above 96K), also as a wdm/wave i/o (with scope it doesn't work on x64, or maybe with version 6 it works, but then XTC doesn't work), so I use Scope as strictly ASIO i/o...

it's a pity i've forgotten to check pci performance with scope seated directly in motherboard. as there have been some different maximum reverb counts with magmas i have a theory that despite being an 'external' bridge, it still goes under motherbiard/bios command regarding pci performance parameter...