| Author | Topic: Crystal Question |
| trappist | Posted: 1st January 2005 07:17 |
I have been using Crystal softsynth for about 2 weeks now and every once in awhile, it freezes/locks up. Some of the ratings I've read about it mention that it's very processor intensive. I'm using a P4 with 512M RAM....Tracktion hosting.
Is this normal? Any recommendations? | |
| origami | Posted: 1st January 2005 07:19 |
never happened to me...well it uses a lot of CPU that's true, but no problems here (P4 2.4Ghz, 512 ram) | |
| Mighty_Hero | Posted: 1st January 2005 07:19 |
It is sometimes normal. Buy more ram.
Welcome to kvr | |
| Jafo | Posted: 1st January 2005 07:29 |
Try increasing the latency. Working at a lower sampling rate (say, 44.1 vs. 96) also does this, as well as easing the load on your system.
Cheers -- Just Another F*cking Observer http://www.angelfire.com/band2/oddity | |
| trappist | Posted: 1st January 2005 07:41 |
Thanks for the welcome. Um--how do I adjust the sampling rate? This is all greek to me thus far. No manuals of course.... | |
| trappist | Posted: 1st January 2005 11:35 |
Anyone else? Thanks. | |
| Green Red Brownell | Posted: 1st January 2005 11:43 |
The sampling rate is generally set by your VST host. So, if you adjust it, the change affects all plugins. Still that might be the best thing to try. If you don't like it, the change is easily reversible.
Some plugins also have a higher sampling rate internally (usually a multiple of the host rate). This is called "oversampling", and is done to get a better quality waveform, before finally outputting it at the host's sample rate. I don't think you have to worry about that with Crystal, but I could be wrong. Reducing the internal oversampling rate (if there was an option) would also reduce host computer CPU/memory usage. HTH, Green |











