PlanetZ forums - scopeusers.com

Is anybody familiar with this exception?

"PepDisplayObject::MoveAllRoutings::invalid pad name (Pad1)"

I used to have no problems with it, but now this message appears everytime I open my default project. After clicking the OK button the project fully opens, but the nagging question just irritates me.

I tried to save it to a different name, but it didn't solve the problem. Rebuilding the project is not an easy job, because it's very complex. Any ideas?

One of the connections seems broken. Sounds like some disagreemend in th eblue wires you see in the project and the actual DSP connections. Disconnecting and reconnecting stuff will reveal which connection is erratic.

I disconnected everything from my STM mixer, but the problem is still there.

The only way to get rid of the message is to delete my mixer from the project. I'll try to make a preset of the mixer, delete the whole mixer afterwards, insert a new mixer, load the preset and reconnect everything again. Hope it works...

Hmmm.. that get's rid of the message, but I can't get the STM presets to load properly.

Opening a Channel Preset only loads one channel without the settings of the channel's inserts.

The Preset button on the main mixer strip is not loading the complete mixer. Strange.. shouldn't it be possible to save ALL mixer settings in one preset? Including the settings of all used inserts? Like a Total Recall function?

Maybe an insert was actually the problem?

Do you still have your original project?

I think the problem started when I saved my Midi controllers for the STM mixer. From that moment on the message appeared. When loading the controllers it also pops up. Deleting all Midi Controllers didn't help though...

An insert causing the trouble? Could be. I used a gate on all channels.

In the meantime I inserted a new STM mixer and reconnected everything, so I'm up and running again. Pitty I don't know how to prevent this in the future.

Hi Booster,
I'm not so expert like some other gurus here ( ) but watching your last posts I've saw tath you are experimenting different throubles. Maybe your intallation hase gone bad or maybe some file has been corrupted.
In your situation I would maybe try to reinstall the whole scope software.