PlanetZ forums - scopeusers.com

Hi.
I'm a Scope user for almost 20 years, as most of you here I guess.
I rarely use Scope synths and samplers but can't imagine working without his excellent routhing.
So all I'm interested in the new v7 are DRIVERS!

Are ASIO, MM and MIDI drivers Improved in v7?
Does Wavelab 6 work with new drivers?
Is it possible to use the Scope MM driver to record?

In Win10 (Cubase ASIO) I have tiny audio distortions despite all system optimising.
Indeed, these distortions are very rare but are still depressing.
In Chrome on YouTube (MM driver) I have even more distortions
Are these failures known to you and whether they are repaired in v7?

Thanks in advance for your answers.

sandrob wrote: ↑Wed Jan 10, 2018 1:17 am

In Win10 (Cubase ASIO) I have tiny audio distortions despite all system optimising.
Indeed, these distortions are very rare but are still depressing.
In Chrome on YouTube (MM driver) I have even more distortions

I can tell for Cubase Artist 9.5 under Win 10 pro 64bit Scope 7 works just fine.
I didn't have any distortions also before in Scope 5.1.

For Chrome i can't tell, but i have second computer with internet and Luna II boards's installed, with Scope 5.1,
where i have heard those clicks and distorted sound, so i'm using earlier version of Opera (version 31), which is working fine,
Youtube plays normal, all newer versions of Opera or Chrome doesn't work well for me.

no 64bit recording into wave drivers yet. the next update should have that fixed. there's a really smart guy working on it presently, afaik.
ASIO is perfectly fine, plus it's win10 compliant and it's signed.

if you have clicks in Cubase that are not from an overly busy CPU, then it's likely to be a setup issue, hyperthreading, EIST, etc, or a hardware clock issue, or an inappropriate setting in Cubase. ASIO should be clean.

it's been a while since Scope was at the present level of activity. if you wanted to wait a bit to update, those issues will likely be fixed. if you update now, i think you will still find it to be an improvement in general.

I did all BIOS and Windows tweaks but didn't help even I use 24ms latency.
I also use Focusrite Liquid Saffire on the same mashine with no problem.

What about Wavelab 6 on Scope v7?
With v5.1 I must use Wavelab Patch for Scope.

sandrob wrote: ↑Wed Jan 10, 2018 3:12 am I did all BIOS and Windows tweaks but didn't help even I use 24ms latency.

What about Wavelab 6 on Scope v7?

Which mobo and chipset do you have ?

I use Soundforge , i can't tell.

fidox wrote: ↑Wed Jan 10, 2018 4:15 am Which mobo and chipset do you have ?

I use Soundforge , i can't tell.

Asus Z97-A Mainboard Sockel 1150 and I have the same issues with Asrock Z97 pro4.
Sometimes whole recording session pass without a single click, but sometimes because of the click I have to record again.

sandrob wrote: ↑Wed Jan 10, 2018 4:37 am Asus Z97-A Mainboard Sockel 1150 and I have the same issues with Asrock Z97 pro4.
Sometimes whole recording session pass without a single click, but sometimes because of the click I have to record again.

I'm using 1151 chipset.

Yea, i know, what you mean, about clicks, pops, while recording.
Occasionally, i have that too, mostly when i'm recording bigger project, with lot's of plugins (effects),
so i must then record again.
I can get best results with those settings in Cubase Artist 9.5 & Elements 9(picture).
Also you can try, it can't hurt while recording to set lower priority to scope.exe.
Task Manager - details - right click to scope.exe and set priority to "below normal".

Thanks, fidox. I will try this seting and I'll let you know how works.

Buying v7 will wait a while until all the drivers are upgraded.

Thanks to all

The signed, updated ASIO drivers work with Bitwig (or other applications that are finicky about sticking to spec) again

Gary, do you think that the WDM (wave) drivers can be made entirely crackle-free?

yes, i do.

it will take a super-genius to do that, which is why the original programmer was brought in for that specific job. if it was as simple as just adding a few lines of code, it would already have been done, of course.

dehuszar wrote: ↑Sat Jan 13, 2018 8:54 pm The signed, updated ASIO drivers work with Bitwig (or other applications that are finicky about sticking to spec) again

it's not about "sticking to spec" regardless of what programmers of those apps might want to say.
it's about the fact that the Scope card is not a Windows Sound Card(though it can fill the function), which can be controlled by the host app. these engineers think that all cards should be the slave of the app. Scope works the other way. it is programs like Bitwig that do not comply and play well with others.

in any case, most trouble apps DO work now. i suggest trying a demo if you want to find out about the apps that you care about.

SuperCollider is one of the candidates, which don't work (yet) with SC windows 10 ASIO drivers (I know, I'm repeating me), it creates a BSOD when enumerating all ASIO drivers. A workaround is to rename the Scope ASIO driver and then use Voicemeet. Very inconvenient.

tell the supercollider programmers to stop trying to setup the soundcard or at least allow the function to time out and i bet it will work, too.

garyb wrote: ↑Sat Jan 20, 2018 12:04 pm yes, i do.

it will take a super-genius to do that, which is why the original programmer was brought in for that specific job. if it was as simple as just adding a few lines of code, it would already have been done, of course.

Awesome - that's what we want - original programmers bought in ! Cool !

garyb wrote: ↑Sun Jan 21, 2018 4:43 pm tell the supercollider programmers to stop trying to setup the soundcard or at least allow the function to time out and i bet it will work, too.

I have the source and the PC dies immediately when calling this function:
LONG AsioDriverList::asioOpenDriver (int drvID,LPVOID *asiodrv)
{
LPASIODRVSTRUCT lpdrv = 0;
long rc;

if (!asiodrv) return DRVERR_INVALID_PARAM;

if ((lpdrv = getDrvStruct(drvID,lpdrvlist)) != 0) {
if (!lpdrv->asiodrv) {
rc = CoCreateInstance(lpdrv->clsid,0,CLSCTX_INPROC_SERVER,lpdrv->clsid,asiodrv);
if (rc == S_OK) {
lpdrv->asiodrv = *asiodrv;
return 0;
}
// else if (rc == REGDB_E_CLASSNOTREG)
// strcpy (info->messageText, "Driver not registered in the Registration Database!");
}
else rc = DRVERR_DEVICE_ALREADY_OPEN;
}
else rc = DRVERR_DEVICE_NOT_FOUND;

return rc;
}
which is called from:
bool AsioDrivers::loadDriver(char *name)
{
char dname[64];
char curName[64];

for(long i = 0; i < asioGetNumDev(); i++)
{
if(!asioGetDriverName(i, dname, 32) && !strcmp(name, dname))
{
curName[0] = 0;
getCurrentDriverName(curName); // in case we fail...
removeCurrentDriver();

if(!asioOpenDriver(i, (void **)&theAsioDriver))
{
curIndex = i;
return true;
}
else
{
theAsioDriver = 0;
if(curName[0] && strcmp(dname, curName))
loadDriver(curName); // try restore
}
break;
}
}
return false;
}

I don't see, how a BSOD can be avoided here. If you have any ideas, I'm happy to test them and contact the SCollider people.

how does everyone else avoid a crash?

Scope can only respond to what it can respond to. it's not a soundcard.

After some debugging sessions (lots of expected BSODs) it boils down to this call:
theAsioDriver->init(info->sysRef);

theAsioDriver is the interface to AsioScopeXite64.dll which should export these functions:
interface IASIO : public IUnknown
{

virtual ASIOBool init(void *sysHandle) = 0;
virtual void getDriverName(char *name) = 0;
virtual long getDriverVersion() = 0;
virtual void getErrorMessage(char *string) = 0;
virtual ASIOError start() = 0;
virtual ASIOError stop() = 0;
virtual ASIOError getChannels(long *numInputChannels, long *numOutputChannels) = 0;
virtual ASIOError getLatencies(long *inputLatency, long *outputLatency) = 0;
virtual ASIOError getBufferSize(long *minSize, long *maxSize,
long *preferredSize, long *granularity) = 0;
virtual ASIOError canSampleRate(ASIOSampleRate sampleRate) = 0;
virtual ASIOError getSampleRate(ASIOSampleRate *sampleRate) = 0;
virtual ASIOError setSampleRate(ASIOSampleRate sampleRate) = 0;
virtual ASIOError getClockSources(ASIOClockSource *clocks, long *numSources) = 0;
virtual ASIOError setClockSource(long reference) = 0;
virtual ASIOError getSamplePosition(ASIOSamples *sPos, ASIOTimeStamp *tStamp) = 0;
virtual ASIOError getChannelInfo(ASIOChannelInfo *info) = 0;
virtual ASIOError createBuffers(ASIOBufferInfo *bufferInfos, long numChannels,
long bufferSize, ASIOCallbacks *callbacks) = 0;
virtual ASIOError disposeBuffers() = 0;
virtual ASIOError controlPanel() = 0;
virtual ASIOError future(long selector,void *opt) = 0;
virtual ASIOError outputReady() = 0;
};

Here ends my voyage, as I don''t have the source for AsioScopeXite64.dll. I don't see anything special during the call chain.
Any help is appreciated.

well, then it should work, as damn near every other ASIO host works.

i see it tries to initialize the control panel. there is no control panel.

That&s the init for? In that case I&ll try to skip that phase.