There is nothing else loading in the background (as far as I know).
No reponse to the other thing about loading from "new" or from "previous". I seem to alternate between the two styles frequently. I suppose I should do a little experiment and try both routines and see if I can isolate it down to one or the other. What difference would that make anyway?
I already have a dual boot system but not for this purpose (good idea though - maybe I'll set up a third bootable partition for a safety install - that's not a bad idea at all). This isn't a show stopper problem. Just an annoyance. I can actually live with it like this but I just thought I'd investigate to see if there was an easy solution. Will try that ini file suggestion. What's the point of doing that exactly?
I'll do a little more digging here on my end to see if I can find a solution. Thanks for the tips and suggestions so far.
<font size=-1>[ This Message was edited by: krizrox on 2004-08-25 21:38 ]</font>
Scope crashing after switching projects every 3 or 4 times
You say it happens consistently every 3 or 4th time, about the number of recent project entries, and I was wondering if somehow SFP's process of updating the recent entries list (does it just update the ini file or registry?) when changing projects was getting screwy. If you read-only the ini file then it can't update it. This is just a long shot but if you've tried everything else.....
'Recent files' is a list somewhere in cset.ini. I think more of a DSP loading problem really.
DSP are alive. For cleanest and most stable projects, do not edit them endlessly throughout all your tracks. Make a couple of good basic start projects, which set you off in the good direction. It happens that stuff isn't unloaded properly, I think. To my experience this can happen on loading one project after another, or when you work with generations of projects, saved and edited endlessly. Bugs or errors are unavoidable, and they can accumulate throughout generations of projects or loading. For most stable result, restart SFP when loading projects. Load projects from which no stuff has been deleted, adding stuff to make bigger template project doesn't do any harm. This may be all in worst case, but that's how I keep it stable.
The same goes for modular patches of course, it's all the same architecture.
DSP are alive. For cleanest and most stable projects, do not edit them endlessly throughout all your tracks. Make a couple of good basic start projects, which set you off in the good direction. It happens that stuff isn't unloaded properly, I think. To my experience this can happen on loading one project after another, or when you work with generations of projects, saved and edited endlessly. Bugs or errors are unavoidable, and they can accumulate throughout generations of projects or loading. For most stable result, restart SFP when loading projects. Load projects from which no stuff has been deleted, adding stuff to make bigger template project doesn't do any harm. This may be all in worst case, but that's how I keep it stable.
The same goes for modular patches of course, it's all the same architecture.
cset.ini! that's what I meant not scope.ini.
Anyway, I've, on occasion, experienced problems where you get the message about letting scope redistribute dsp allocation and no stdm connections which may be caused by dsps not unloading correctly etc as you suggest but Krizrox is getting app crashes consistently every 3 or 4 times which suggests to me something apart from dsp allocation might be causing him grief.
Ultimately it might be time to rebuild from scratch.
Anyway, I've, on occasion, experienced problems where you get the message about letting scope redistribute dsp allocation and no stdm connections which may be caused by dsps not unloading correctly etc as you suggest but Krizrox is getting app crashes consistently every 3 or 4 times which suggests to me something apart from dsp allocation might be causing him grief.
Ultimately it might be time to rebuild from scratch.
Actually, just went through a rebuild not too long ago. I'm trying to remember but I think this problem really started with 4.0.
I suppose it could be related to my XP installation or who knows what.
Occasionally (but very rarely) I get that DSP allocation error. That happens so infrequently and usually after I've been futzing around loading devices and such. I never gave that much thought because it happened hardly ever.
As far as editing projects, well, that's pretty normal for me during the course of a session. I'm always loading effects into mixer channels, re-routing ASIO drivers, etc.
I'm gonna try the Dr. Watson thing later this morning and see what comes up. Maybe that will shed some light on this.
I suppose it could be related to my XP installation or who knows what.
Occasionally (but very rarely) I get that DSP allocation error. That happens so infrequently and usually after I've been futzing around loading devices and such. I never gave that much thought because it happened hardly ever.
As far as editing projects, well, that's pretty normal for me during the course of a session. I'm always loading effects into mixer channels, re-routing ASIO drivers, etc.
I'm gonna try the Dr. Watson thing later this morning and see what comes up. Maybe that will shed some light on this.