timeworks compressor

thermos · Post by **thermos** » Sat Nov 13, 2004 10:59 pm

its a great comp. but if my computer has been running for a while and i load it the scope enviromet freezes. any1 else?, any solutions?

next to nothing · Post by **next to nothing** » Sat Nov 13, 2004 11:35 pm

i dont have the device mentioned, but on a more general basis; do this only happen when you use that specific device,or does it happen when you run other demanding tasks as well? not necesarily scope tasks, but typically a load of vst/i's? or maybe if you do some graphic demanding tasks, such as games?

reason i ask is because this symptom is, in general, traced back to cpu or system temperature problems. do u have any data on these values?

<font size=-1>[ This Message was edited by: piddi on 2004-11-13 23:38 ]</font>

Music Manic · Post by **Music Manic** » Sun Nov 14, 2004 12:32 am

I get DSP errors occasionally with Timeworks,especially reverb.

thermos · Post by **thermos** » Sun Nov 14, 2004 7:32 am

this only happens with the timeworks comp, if my computer has been on for a while and i try to insert it then scope freezes. if my computer hasent been runing for several hours than everything works. i have some troubles with the reverb too it sometimes stop working.

iv got a luna, pulsar1 and a pulsar1 srb, maybe the problem is because of the new/old card combination.

astroman · Post by **astroman** » Sun Nov 14, 2004 9:08 am

It's probably not related to the compressor at all.
I experience the same with a lot of synths - the only pattern detactable seems to be the complexity of the device.
It never happens with UKnow (for example), but Vectron is a good candidate for the freeze. 2 Pulsar One and Win98 on Intel-815 btw.

If I want to add a device to the project and Scope has been running empty for > than half an hour, I avoid it by reloading the environment. Since it's predictable (and a rare situation anyway), I don't bother.

cheers, Tom

valis · Post by **valis** » Sun Nov 14, 2004 9:15 pm

A possible solution:

Go into your control panels, go to Sounds and Audio devices, go to the Hardware tab, select your Creamware driver, choose properties. Find the 'disconnect' option (under power options) and DISABLE it. Basically it will let the hardware disconnect from the software after a certain period of inactivity (its a PCI bus thing--introduced with other power options). I found I had a lot of problems until I unchecked that as well (red muze pointed it out to me).

Also beware that I'm not on my SFP box atm so one or two words may be off slightly

wolf · Post by **wolf** » Mon Nov 15, 2004 12:56 pm

Hi,

does it freeze like in "I can not move the mouse and no sound is emitting anymore" ?

1. open your case, perhaps it is too warm inside
2. there might be faulty RAM, try to replace/change it
3. the last time it helped here to recreate the project from scratch, sometimes a project becomes corrupted somehow. You'll have to reassign all midi assignments for that to work without freeze anymore.

hope that helps.
Wolfgang