I'd like to explain something which may help people who are experiencing blue screens or meltdowns under large loads.
You may recall that Giga 2.5 and earlier versions had a solid polyphony cap.
Now (Giga 3.0, top tier versions) there is no practical polyphony limitation built in. This is something the user base overwhelmingly desired, me included...the ability to max out a given hardware setup.
It has a dark side, though, in practice. Because Giga is running in the Kernel, Windows is not going to come to the machine's rescue if Giga pushes your hardware past its limits. The OS will not shut down gracefully. At best you are going to blue screen. At worst, you'll go black with a pop, and reboot.
That's not something that is going to be fixable. That was why polyphony was always limited before...to protect us a bit from ourselves. We said we were big boys and girls, and we could handle it ourselves--thank you very much. We have been given that opportunity...but it comes with a price, as all opportunities do.
The upshot here, and the practical advice of this message: You MUST SET A POLYPHONY LIMIT within the ability of your machine...No matter how fast your machine is.
If you just leave the brakes off, or you don't clamp down right under your machine's croak-point, you can--and you will--starve your processor before Windows can defensively and safely protect disk operations. Most of the time, this will be recoverable. You could get unlucky, though.
If you are running a Giga-only system, you have the easiest shot at this, since you can be very accurate about your limits. Find the level at which you start getting playback artifacts, and cap it just below that.
Understand this: You will actually get better PRACTICAL polyphony performance by doing this, because when you've set a realistic maximum, Giga will invoke its polyphony management to give you a "virtual" polyphony which sounds higher--it has very intelligent and good sounding note stealing capability.
If you don't set the cap, you won't get that benefit, because the machine won't know when it's about to go bye-bye. It will just go.
If you are running Giga in a general use DAW, and have other programs running, start with a lower polyphony cap. Try 160. See how it sounds when you push up against that...e.g., when the meter just goes up there and sticks. Does it still sound pretty darn good? If so, the polyphony management is working well, and your machine is capable of sustaining this polyphony easily. Then start pushing it up...I'd go by values of 10. See if you can get artifact-free sound at 170. 180. You get the picture.
If you always run certain other things simultaneously, run them while doing this. Try to get the best possible realistic usage pattern as a baseline for setting your polyphony maximum. You'll be rewarded with better performance from everything, not just Giga.
When you start getting playback artifacts, back down until you do not get them.
This is how you can determine the very best setting for your machine.
If, on the other hand, you try the idea of going from the very maximum, or even from a very high setting, and blowing up the machine--then trying lower--you are going to expose yourself to a lot of potential heartache and unneccessary crashes.
So, to summarize:
1) You need to set a polyphony "cap" no matter how powerful your machine, so that the polyphony management system can give you "better" virtual polyphony than your machine can get on its own. This is the most important thing to understand about GigaStudio's polyphony limitation, conceptually--that you WANT to set a limit, so that Giga can work its management magic and get you better performance for your given rig than you'd get "wide open."
2) Because Giga can starve your processor before Windows can protect disk operations, and because there is nothing practically possible to stop this, you must be conservative about determining your polyphony cap. You'll get better performance if you set it ten voices too low than ten voices too high.
3) The best way to determine your polyphony cap is to set a very practical limit (say starting with 160) load up a piano patch, and play wildly with the pedal down. Does the meter "stick" at 160, yet still play with no audible artifacts, indicating that the polyphony management system is stealing notes as transparently as possible? Good. Set the limit at 170, and do the same experiment. Keep repeating until you hear artifacts. Then back down to the last "good" setting. You're ready to rock.
I hope that this is helpful. It's not official Tascam dogma to my knowledge, just my practical experience. And it is my belief that people may save themselves a lot of heartache and find that Giga is actually a lot more stable than they think, if they'll take the time to do this very necessary bit of setup.