PlanetZ forums - scopeusers.com

SB404

OK, after more extensive use of SB404 I think the errors lie in the Delay effect section. Whenever I try to build a preset with delay or call up an old preset with delay a get the following two errors

1."Module SDRAM XiteDelay is not appropriate for his hardware".
Press OK. The next message then appears:

2. "PepAddRouting: Pads untitled.Ch and MidiControllerList.Channel are incompatible, cannot route".


Operating system version: Windows 7 64-bit
Scope Hardware: XITE-1
Sampling Rate: 44.1kHz
Plug-in: SB404 V2

sunmachine wrote: ↑Sat Dec 09, 2017 11:52 am
What seems to make a difference is from where you save the preset file.
It looks like the preset file won't work properly when saved while removing the device.
So, please try saving it only from within the preset window and see if that works better.

Seems to be the same in version 7, so I'll make a bug report later.

Glad you brought this up. I have found this to be true as well. Save the preset file BEFORE closing the device and if it asks you if you want to save while exiting, select NO. I just went through a circus with the dNa effects rack because I forgot and selected yes, then the device kept crashing the system whenever I loaded it. Solved by reloading a fresh preset file but the price paid was the loss of all presets for that device.
Agree this should be reported in the bug list even though it is a carry over.

Mr Arkadin wrote: ↑Wed Dec 13, 2017 9:39 pm SB404

OK, after more extensive use of SB404 I think the errors lie in the Delay effect section. Whenever I try to build a preset with delay or call up an old preset with delay a get the following two errors

1."Module SDRAM XiteDelay is not appropriate for his hardware".
Press OK. The next message then appears:

2. "PepAddRouting: Pads untitled.Ch and MidiControllerList.Channel are incompatible, cannot route".


Operating system version: Windows 7 64-bit
Scope Hardware: XITE-1
Sampling Rate: 44.1kHz
Plug-in: SB404 V2

confirmed! (same config)

yayajohn wrote: ↑Thu Dec 14, 2017 4:54 am Glad you brought this up. I have found this to be true as well. Save the preset file BEFORE closing the device and if it asks you if you want to save while exiting, select NO. I just went through a circus with the dNa effects rack because I forgot and selected yes, then the device kept crashing the system whenever I loaded it. Solved by reloading a fresh preset file but the price paid was the loss of all presets for that device.
Agree this should be reported in the bug list even though it is a carry over.

Thanks for the confirmation! I already made the report.

Mr Arkadin wrote: ↑Wed Dec 13, 2017 9:39 pm SB404

OK, after more extensive use of SB404 I think the errors lie in the Delay effect section. Whenever I try to build a preset with delay or call up an old preset with delay a get the following two errors

I've added a bug report for this one as well.
Everyone can do it by the way... See here for more info: viewtopic.php?f=1&t=35261

Rebu wrote: ↑Fri Dec 08, 2017 7:15 am Hello guys i solved my fx crash problem that's how:

In Scope settings, global, Screen Mode i choose "Show Desktop" (generally i work in "Hide Desktop")

In "Show desktop" mode all fx work without any crash tested on:

Scope PCI

1- Win7 64
2- Win10 64 (fresh installation)

In Hide Desktop mode a lot of fx crash scope

Hope that help someone had same problem

I can confirm this - Scope Setting -> Global -> Show Desktop. Enabling this STOPPED the R6025 'pure virtual function call' error I was getting on loading the SC-AutoGate and the SC-Brickwall EQ. These plugins now load normally. Switch to 'Hide Desktop' option and the crashes occur again. This is Scope XITE x64 and Scope PCI x64 both Win8 and Win10 fresh installs.

both load here in Win10 64bit with desktop hidden.

Did you install Scope 7 over the top of 5.1 ?

yes, and no....

i have done it both ways.

Lol

Anyway, about Scope - its not OS specific, so may be hardware specific ( eg graphics card issue). I cleaned out and re-installed the C++ runtime so doesn't seem like that's the issue.

i don't know what's going on with different people's computers. it's very hard to pin down what is happening with only a few people having a problem and so little information. obviously, something is happening. i don't know if it's a service tweak or a windows tweak or some kind of hardware incompatibility, or a software bug that is only revealed with certain combinations. i guess it's not something done to the installation, like overwriting new files with old ones, since it seems recurring to those who experience it...

what chipset / graphics card U running ?

old ones.
nothing tricky here.

It's software problem, 5.1 not have this issue..

maybe so, but v7 does not have this problem, here.

Yes, so we have yet to reduce this to a unique set of (reproducible) conditions. We only know that there are 2 conditions (Scope 7 and Show Desktop) but there may be 1 or more. We know the following :

1) its not OS specific (happens on both Win 8 and Win10).
2) I doubt its related to a C++ Runtime version conflict, because I uninstalled ALL versions of C++ runtime and Scope still worked and the error still occured. Same after I used to Scope 7 installer to re-install the C++ runtime.
3) Its not Scope hardware type related (happens on both PCI and XITE)

Unknown factors include :
1) Does it happen on 32 bit systems ?
2) Specific hardware conditions such as IRQ conflicts, video card etc.

But the fact it relates to 'show desktop' or 'hide desktop' suggests to me it could be video related, although that would be a lot easier conclusion if it were reversed. EG 'Show Desktop' crashes rather than 'Hide Desktop'. ...

Anything weird in my IRQ ?

no, nothing weird.

it really does not happen here. not at all.

PLAY v6.0.1 (EASTWEST plugin) isn't compatible with ASIO SCOPE PCI ==> crash with Blue Screen of the PC (systematically reproductible).

edit : It's only the standalone version which has issue !!!!

NOTION v6 idem ...

any application which attempts to setup the soundcard will fail with a bluescreen.

Why is it like that ? doesn't scope drivers could be modified to remove this issue ?