Hi!
With some synths, for example the Pro-12, I get a problem if I leave it running overnight/for hours. When I come back, the midi keys no longer work normally. If I press one key, it seems to be alternating between three different tones repeatedly. And there is no difference what key I press, they all sound the exact same. And often when I come back after some hours, if I don't just quit Scope and restart, but just try to reload synth and stuff, I end up with a blue screen of death flashing by before the computer reboots ...
(I don't remember right now which other synths I experienced this on, but it was more than one other of the Creamware synths, but not problem with f.ex. UKnow or the Zarg Solaris Core demo.)
Anyone else experienced this, or is it just something related to my hardware/drivers?
--
flips
<font size=-1>[ This Message was edited by: flips on 2006-09-18 04:19 ]</font>
Weird problem with SFP on WinXP with certain synths
this looks like keyboard tracking is lost somewhere on the way - on my System this happens (at least it seems) exclusively with patches that have some kind of glide funktion activated (portamento etc).
Turning that off may bring the keytracking back, but the next patch with portamento will loose it again...
I've never been able to find a pattern behind this, it's not restricted to CWA synths - but in fact seems to require one of the more 'sophisticated' devices
when I leave my system running idle for a long time, (say at least half an hour) then it will most likely crash when I add another device to the project.
seems to be related to the countless energy saving and power control options between bios, OS and hardware...
I just ignore it - as both annoyances are predictable(to a degree) and not too frequent.
cheers, Tom
Turning that off may bring the keytracking back, but the next patch with portamento will loose it again...
I've never been able to find a pattern behind this, it's not restricted to CWA synths - but in fact seems to require one of the more 'sophisticated' devices

when I leave my system running idle for a long time, (say at least half an hour) then it will most likely crash when I add another device to the project.
seems to be related to the countless energy saving and power control options between bios, OS and hardware...

I just ignore it - as both annoyances are predictable(to a degree) and not too frequent.
cheers, Tom
Always SAVE before leaving your machine for extended periods of time. Most of my XP installations definately seem to lose sync between the hardware & software at some point (extended idle periods). There is a setting buried in your control panels (reset board when idle) which, in theory, if unchecked will keep the software & hardware in communication regardless of how long it is idle, but I've found that I still have to re-initialize Scope somehow after long idle periods. Usually (for light work) I'll just reopen the same project, or do a new project. If it's an important project I close & reopen Scope to insure that everything is stable. I leave all my machines on all the time...
Now for what it's worth, the vast majority of my PROFESSIONAL software isn't happy to be left open overnight. Almost all of it will slowly eat resources somewhere. Adobe products seem to have memory leaks these days, a lot of audio sequencers will slowly become unstable when idle, etc. The fact that I can simply reload the current Scope project (or close/reopen for ultra-safe) doesn't really hinder me all that much. Try waiting for an Illustrator project to reopen that uses a gig & a half of ram (or a Logic project for that matter)....
Now for what it's worth, the vast majority of my PROFESSIONAL software isn't happy to be left open overnight. Almost all of it will slowly eat resources somewhere. Adobe products seem to have memory leaks these days, a lot of audio sequencers will slowly become unstable when idle, etc. The fact that I can simply reload the current Scope project (or close/reopen for ultra-safe) doesn't really hinder me all that much. Try waiting for an Illustrator project to reopen that uses a gig & a half of ram (or a Logic project for that matter)....
I read this as I have a problem with sticking midi notes in a lot of my CW synths.
But I do not get the 'idle' problems - I can leave CW running for long periods - say 16 hours,a day - and return, all ok. I switch off overnight as it saves electricity (save the planet etc); and I don't use the PC at night.
One thing that made my XP Home system unstable was viruses and spyware, it was unstable, improved to 100% working fine after using AVG Grisoft anti virus, Spyware Doctor, and recently Microsoft Defender. This cleared all the invisible stuff that was tripping up the system. PS I don't work for these people!
I'd do this before any arcane hacks etc.
<font size=-1>[ This Message was edited by: geoffd99 on 2006-09-21 04:09 ]</font>
But I do not get the 'idle' problems - I can leave CW running for long periods - say 16 hours,a day - and return, all ok. I switch off overnight as it saves electricity (save the planet etc); and I don't use the PC at night.
One thing that made my XP Home system unstable was viruses and spyware, it was unstable, improved to 100% working fine after using AVG Grisoft anti virus, Spyware Doctor, and recently Microsoft Defender. This cleared all the invisible stuff that was tripping up the system. PS I don't work for these people!
I'd do this before any arcane hacks etc.
<font size=-1>[ This Message was edited by: geoffd99 on 2006-09-21 04:09 ]</font>