Page 1 of 1

Posted: Tue Oct 12, 2004 4:35 am
by Rogurt
when having opened a project on different days let´s say for the 7th time there suddenly appear error windows ("Nil..." or "cannot route...").
Generally spoken one could say that when having worked on a project for some time it is more and more likely that errors occur (without having loaded new devices, just turning knobs and saving presets).

I have posted some other problems as well and they are all from ONE (exemplary) job I have. No thrd party devices or anything...
Really professional platform that is :sad:

Posted: Tue Oct 12, 2004 9:24 am
by krizrox
see my Optimaster thread... misery loves company

haven't seen this "nil" problem in years though. what is your system config? the more info you can provide the better.

Posted: Tue Oct 12, 2004 9:39 am
by Rogurt
doesnt really depend on sysconfigs. It´s the third PC I have built for Pulsar....
And the Errors vary

Posted: Tue Oct 12, 2004 1:58 pm
by blazesboylan
The core SFP modules in themselves have never given me those errors over the past 3 years of continual use.

However...

There are numerous 3rd party modules that give me those messages on startup.

And I've also made routing connections that give me similar errors.

For example, the "cannot route" type messages can be generated if you have an infinite loop in your project. This is surprisingly easy to do.

The only way to track down the source of the problem is to load up the project, and carve it up into smaller ones (by deleting most of the modules). Load each smaller project until you find which one causes the problem. That should tell you which modules and / or connections are causing you grief.

And yes, I know how painful it is. I spent all summer trying to find an infinite recursion problem in one of my projects. But as I've said elsewhere, dealing with SFP problems is much easier than dealing with outboard ones. And in any studio, you have to be both patient, flexible and nimble -- no matter what gear or software you use.

Cheers,

Johann

Posted: Wed Oct 13, 2004 3:54 am
by Rogurt
well then. lets hope there´ll be some kind of debuging windows that gives some information on where such errors could be...