PlanetZ forums - scopeusers.com

!! But you created a STM preset for all STM settings/inserts !! You must create the midi cc assignment preset IN the MIDI controller folder of the presets window !!

Otherwise, for sure, it doesn't recall midi cc's ! Have a try !

And you'll see : if you create a new preset file, Scope ass the MIDI controller folder automatically and you have to create a new bank folder for STM other settings. Maybe other Scope device keep midi cc in the setting folder, but I'm not sure !
The advantage to have the 2 folder (1 for settings, 1 for midi cc assignment) is to keep midi cc assignments when changing settings preset.

TOM.DJ wrote:

faxinadu wrote:tom the sample players work good here.

can you do a test plz with this

http://forums.scopeusers.com/viewtopic.php?f=16&t=35241

Hi Faxi,
Thanks.
I can/will try this tomorrow.
regards T

This one seems to work!
I've replaced the "SampleOsc in the modular2 with a modular IV "Sample OSC" and it looks like this fixes the problem! (So older modular SampleOSCs should be updated?)

Regards Tom

good

stay tuned more about sampling soon..

catscratch wrote:Sorry I hit post by accident. Yes, I understand that and mentioned it in the post but kept the video to show that faders and mutes are not even close to where they should have been. Thanks for your reply JoPo.

And by saving your midi cc assignments preset in the MIDI controller folder, STM cc assignment is lost ??
If they are, it's really weird ! I don't see how it wouldn't work for you when it works for others, like me or Jimmy..

catscratch wrote:Same test using the midi folder properly(?) results in exception fault. Maybe the .pre file is corrupt? The device file? Don't know.

https://youtu.be/asb-AnFoc5E

Possible !
I had a STM preset file that crashes Scope. Try to delete the preset file, then create a new one, to see...

Oop.. Sorry, apparently, that's what you do on the new video...

Well... The message you get on the video when loadin the preset in not good ! Don't know what character you entered between the X and the 2 to the preset file. Avoid ",;." Put a "_" ...

But I don't know if it's the reason.

I could make the same video as you and show you how it works correctly, here. But I don't have a camera.

Maybe, you could try this : backup the Scope folder entierely, run the installer and try again on this new fresh & clean install. That way, if it works, we could be sure it's a bad file in your Scope install, if it doesn't work, it's an outside Scope issue and I'm affraid I'm unable to help without to make a new windows installation.

Windows 10 x64

XITE-1

ULLI: any settings 1,2,3,6,12 ms

96 kHz

Doesn't work Wave Source\Dest just as in Scope 5.1. If I try to record from MIC or from Wave Source 24 bit it records scratches, noise, harsh and so on.
Wave Dest 24 bit doesnt work ((

Also it crashes from time to time (blue death) if I change latency in ULLI or Sample Rate.

Scope 7 Plug In : SC-BrickWall EQ Crash :

OS : Win 10.0 x64
HW : Scope XITE-1D
CPU: i7 4790 (not overclocked)
MB: Asus Z87
RAM: 16GB
ULLI : 12ms
Sample Rate : 96KHz
Reproduce: Drag and Drop SC-Brickwall from device menu (Effects/Stereo/EQ/SC-Brickwall EQ) to project window.
This previously occured on Windows 8.0. Now it still occurs on a fresh install of Windows 10 Home. Both Scope 7 PCI and Scope 7 XITE

INITIALLY RESOLVED BY SCOPE7 XITE RE-INSTALL BUT RETURNED AFTER REBOOT.
NOW RESOVED BY USING AN OLDER SCOPE INSTALL WITH NEW INSTALLED OVER THE TOP

Scope 7 Plug In : None (Startup). Warning only.

OS : Win 10.0 x64 - Fresh install on clean SSD drive
HW : Scope XITE-1D
CPU: i7 4790 (not overclocked)
MB: Asus Z87
RAM: 16GB
ULLI : 12ms
Sample Rate : 96KHz
Reproduce: Start up Scope XITE

Once this error is acknowledged with a mouse click Scope starts and behaves normally - eg this error seems to be a warning only.
Note: This error does not occur using XITE-1D under Win8 (on the same system). Nor does it occur using Scope PCI under Windows 10 (again on the same system). So it seems specific to Scope XITE-1D under Windows 10.

Now - heres the wierd part - Booted under Win10 but running the Scope 7 from the Win 8 partition, the error does NOT occur !!!

GOST DYNOMIC crashing with BAD POOL errror.

Additional 64bit files were loaded but I get BSOD.

Additional files are stamped to say they're modified from 2011 but the server says 2017?

http://scope.zone/index.php?id=1978&lg= ... dows_64bit

guys it is impossible to sort through here.

anyone that would like, drop me your email here and i will add you to Scope User Reporting i have set up in bug tracking software

I cant get auto start to work on Scope 7, even with the "-s" fix or the "cset.ini" fix.
It worked fine on Scope 5.1

Shot wrote:OS: Win 7 64bit

Scope Hardware: Pulsar2+Luna

Type of bug/error message:
Had few problems with autostart in windows.
Initially it wouldn't autostart Scope app (even though it is in msconfig/startup)
I had to manually place the shortcut into Startup folder under "All Programs"
If it had no "-s" it would then start, but if the link contained "-s" then it wouldn't start
Tried with and without running it as administrator
Fix was to go to cset.ini and replace DontRestart=1 to DontRestart=0
Now it is starting minimised as it should

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

The fact that values don't show up anymore when stop moving the mouse over a device knob is really annoying ! On a lot of controls, it's now impossible to have an accurate idea of the value.

I hope Holger reads Z !

----------------

faxinadu wrote:

djmicron wrote:OS: Windows 10 64 bits

Hardware Xite-1

Ulli 6ms

sample rate 48 Khz


Plug-in: Every Plug-in using sequencer modules(Solaris, modular modules, WC Pro one)

type of bug: Sequencer settings unresponsive until dsp reload(reallocation or sample rate switch)

on scope 7 are you sure? it should be fixed.

Same here faxi. It’s an Xite thing. I wish you had an Xite so you could experience yourself!!!!

Just sb404 and gateseq1 modular module fixed as per the notes in the v7 release.

faxinadu wrote:

JoPo wrote: I hope Holger reads Z !

he doesn't

At last ! I've found the S|C area on google earth ! Indeed, there is no internet connexion.

----------

catscratch wrote:Same test using the midi folder properly(?) results in exception fault. Maybe the .pre file is corrupt? The device file? Don't know.

https://youtu.be/asb-AnFoc5E

I was able to reproduce the behavior shown in your video on my SCOPE 5.1 PCI system.
And I was also able to make it work properly, so maybe there's hope!

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.