PlanetZ forums - scopeusers.com

While trying to map a number of Scope synths to the Ableton Push, which is a great tool for this! I have noticed quite a few bugs/quirks in Scope.

The latest issue might not be a bug, but it really is something you should be aware of.

If you have a device that makes sound, it doesn't mean that it is properly loaded! Maybe your system was only able to load say 80% of the device, but you really can't tell unless you know how the device/patch/preset is supposed to sound.

Now for the troubleling part, if you create a preset (midi or patch) of the device while it isn't loaded correctly in scope, this flawed device-load configuration will be saved with the preset.

This might be an option, if you have found a sound you like.

But if you are mapping a device to a midi device, and you save the midi preset for your scope device, the faulty loaded device will be saved in that preset and all your work is more or less useless, unless you really like the way the device is not loaded correctly.

For some reason, Scope isn't only saving parameter settings in a preset, it is saving the device configuration as it is loaded in Scope (flawed or not) as well!


I'll let you be the judge: bug or feature?

I wonder if this explains some of the issues with projects loading.

it's more or less a feature of all object oriented Systems (Scope falls in this category)
in any case it's totally diffent from a (say) preset à la DX-7 which is just a list of parameters
some may remember those 'presets' from Scope's early days - which were actually full copies of the device
it's a very complex system under a (simple looking) hood and once this complexity exceeds a certain level...

thumbs up for a good finding, though

cheers, Tom

jksuperstar wrote:I wonder if this explains some of the issues with projects loading.

Maybe - the same "feature" applies to project presets as well, which can ruin a carefully tuned project which you have spend hours creating, assigning devices to dsp's etc., which for me swings this issue into bug territory.

I'd rather have a preset/project save parameters only, that way I'd always be able to reload a project and know that the devices are working as they are supposed to.

I second your point - but there's no other way to handle things in such an environment
... and without the environment Scope couldn't act as it does - it's technically impossible

so your only option is a smart backup strategy

as mentioned earlier different runtime versions of .Net may confuse things
(they may accumulate by installing-uninstalling applications or plugins)
.Net is about an estimated 50 million lines of code - go figure...

on the other hand I wouldn't expect much trouble on a clean install
Scope cards are valuable devices (which still offer a signature sound) - PCs are cheapo today

cheers, Tom