Hi all , Kevin , Emilie
I have noticed in this forum there a lot of problems with Spark and PC users.
Most of these problems relate to high CPU usage and stuttering because of load.
These problems are usually expressed in terms of, I have this system and I can run X software without problems.
There seems to be very few people who can pinpoint what is happening in their system when their problems occur.
For example I was using a system in XP with 1Gb chips (4GB total) and had problems when the memory reached around 1.2GB being used
I changed these for 2GB chips (still 4GB total) and only had problems when memory reached around 1.7GB
Certain kits in Spark cause more problems than others.
When stuttering starts in a pattern I can press stop and start and the stuttering will go away until I have selected a number of patterns.
What number is not precise, but seems to indicate some buffer is being filled.
TSR (Terminate stay resident) programs have an effect. NIHardware, AntiVirus, Network all seem to have an effect. So I disconnect from the net and terminate all unnecessary programs using task manager.
I dont know whether OSX uses on-demand calls for support programs or if it uses TSR as Windows does.
I have recently upgraded to a PCIE soundcard and am using a unified driver which has less TSR stuff associated with it and the problems do not occur as much.
Anyway these are just some of the things I have noticed.
My suggestion to anyone having problems is to unplug any external hardware (controllers) terminate any drivers for them using task manager (dont worry they will come back next time you reboot) turn off the internet access and your antivirus, even disable your network card.
So basically you just have your bare machine with your soundcard/audio interface and try and run Spark, see if it still has a problem. (when I get to this point Spark runs fine for me.)
Then add in each of the above one at a time keeping a watch on your task manager to see if it is a highend (running too many programs on the cpu, shows in amount of memory used) or a lowend (to many programs are trying to use too many resources, like direct sound to ASIO, shows in processes)
Personally I believe it is the latter but I am not the dev so I dont know how the port was done.
Anyway that's my 2c worth.