Scope 7 Bug List

[valis]

A cancel would be nice, I also encounter this when loading devices to see if I have everything registered that’s installed

[Spielraum]

Don't know if this was already reported (seems to be a very old bug - see here for example: viewtopic.php?p=298721#p298721).
When you want to register a new device and don't have the key yet, you're stuck in a loop and have to force quit SCOPE, because the registration window keeps coming back again and again.

< Protection keys have the highest security relevance.
They react to every scope event.
Workaround until the fix:
Therefore, it is very important that no other device is stored in the project window (such as mixers, inputs, outputs, etc.) when reading a request string! The worst case scenario for an abort attempt is when the device being queried is bound to the mixer via autoconnection.

https://forums.scopeusers.com/viewtopic.php?p=298721#p298721
...cannot find DSP file...

< I sent Holger my report on September 14, 2025, with a reconstruction of the scan error, action log since 2019, along with library files for comparison, and error AB photos. He was unaware of the problem and will look into it. I recommended that he compile a separate DSP-Scan.exe, which takes more time for a thorough rescan and can be started manually. Reason: Scope scans the system extremely quickly every time it starts, and sometimes incorrectly. Incorrect paths are occasionally stored. The error remains unnoticed until you try to load the associated device. I always have these problems when juggling DSP, and I recommend creating a backup of the DSP folder beforehand. After a rollback and possibly several retries, the library will eventually be created correctly...
you have to be patient and put the musical moment aside for a while!
P.S.: The scanning problem also exists in older Scope versions, so it's a childhood problem.