Has it happened with different graphic cards? You might want to slowly start trying different hardware components to deduce what the problem is. E.g. Graphics card, RAM, etc (don't use more RAM in your system than what's necessary). And make sure no background programs are running and start with a clean Windows O/S install that has no updates. And different Upgrade/Update versions of Cubase as well . Looks like you're going to have to go threw a comprehensive process of elimination.
EDITED
Saving Scope project
Re: Saving Scope project
Personally i doubt it is the sequencer or any other hardware related matter.
Most probably (imho) it is something inside your scope projects.
I would test by running only the scope software and start from scratch, and gradually add devices and do saving,
restarts whatever you suppose is necessary to get the crashing situation.
I would disconnect any midi devices in the physical inputs of scope and also check that copperlan has not any scope sequencer port activated.
If the problem appears with an empty project i would then try reinstall scope and
perhaps everything including windows from scratch.
If the problem appears on a clean installation of windows and scope and with only the scope running and an empty or light project then you are extremely unlucky and you should check for any hardware related issues.
I personally doubt this may be the case.
Most probably it is a 3rd party device, or something like this.
Because you are saying that you filter midi in cubase and then route to scope you mean probably by a different midi interface, but check if you have connected anything to the physical midi of scope or you use copperlan and you have activated any sequencer midi of scope and you send active sensing (it can't be disabled in copperlan)
ps. scope in general does not have any problem with active sensing. It's when you send active sensing to devices in scope that may cause problem. (and not during saving).
Most probably (imho) it is something inside your scope projects.
I would test by running only the scope software and start from scratch, and gradually add devices and do saving,
restarts whatever you suppose is necessary to get the crashing situation.
I would disconnect any midi devices in the physical inputs of scope and also check that copperlan has not any scope sequencer port activated.
If the problem appears with an empty project i would then try reinstall scope and
perhaps everything including windows from scratch.
If the problem appears on a clean installation of windows and scope and with only the scope running and an empty or light project then you are extremely unlucky and you should check for any hardware related issues.
I personally doubt this may be the case.
Most probably it is a 3rd party device, or something like this.
Because you are saying that you filter midi in cubase and then route to scope you mean probably by a different midi interface, but check if you have connected anything to the physical midi of scope or you use copperlan and you have activated any sequencer midi of scope and you send active sensing (it can't be disabled in copperlan)
ps. scope in general does not have any problem with active sensing. It's when you send active sensing to devices in scope that may cause problem. (and not during saving).
Re: Saving Scope project
yeah, that sounds like a good approach and analysis.
Re: Saving Scope project
Thanks to all of you, guys, for all those suggestion...
It happend before I installed Copperlan. But the 3rd party device would be a good candidate... Indeed, in my start project, there are some of them... That would explain all I noticed. I'm going to delete them to see what will happen.
It happend before I installed Copperlan. But the 3rd party device would be a good candidate... Indeed, in my start project, there are some of them... That would explain all I noticed. I'm going to delete them to see what will happen.
-
Sounddesigner
- Posts: 1085
- Joined: Sat Jun 02, 2007 11:06 pm
Re: Saving Scope project
Keep us informed on whether you solve it or not. Would be good for us to know exactly wich component or devices causes this to help future SCOPE users.
Re: Saving Scope project
I will ! 