Hi there! I run gigastudio 160 on a pentium 933 - and logic/protools on a mac.
Whenever I play the piano (or any other instrument for that matter) with a lot of polyphony and the sustain-pedal working, gigastudio freezes. It just can\'t handle all these messages after a while...
Does anybody know how to work around this problem???
Your help is highly appreciated!
It seems as though GigaStudio v2 had a bug with using sustain pedals. When I did poly tests with a piano and alot of sustain GigaStudio used to bomb out on me around the 80 voice mark. When I did a similar test without sustain and using Cakewalk to pile the notes on thick I would get 120 voices before break up.
Now, with GigaStudio v2.2, I can get the full 160 when playing the piano with the sustain pedal floored.
If you haven\'t upgraded I\'d urge you to do so. If you have then maybe you should try doing a test without sustain, using your sequencer, and see what poly you get. If you\'re looking for a cloud of harmonics, as I was, you may acheive similar results using reverb to create sustains.... a bit of a botch perhaps but sometimes an artists limitations can lead to new innovations.
Besides getting the fastest available CPU and hard drive of course, I found out a strange way to increase polyphony on GigaStudio 2.01 (haven\'t tried 2.20 yet). I was able to get near 160 by increasing the vcache MaxFileCache in the System.ini file to values like 24576. I know this is not recommended for computer audio applications since this will increase the amount of buffered data in disk reads and writes, but it has worked for me. (The much lower recommended vcache value of around 4096 gives me polyphony of around 128, which is still pretty good.)
[This message has been edited by Mega (edited 06-18-2001).]
I run GS 160 on a dedicated PII-800 with 512 meg RAM. I own most of the available pianos and have no problem getting 160 notes polyphony with heavy sustain pedaling. I have found that disabling Virtual Memory gave me the best improvement in performance. Next, setting both MinFileCache and MaxFileCache to 131072, and ChunkSize to 4096 (in SYSTEM.INI file) gave the next highest noticeable improvement. The combination of motherboard and ATA controller appear to be a major factor in disk I/O performance. There have been lots of complaints about \"add on\" controller cards; my board, an Asus CUBX (100 mhz FSB) has a built in ATA66 controller (on IRQ 10) and performs well reading samples from a dedicated IBM Deskstar ATA100 drive. My C drive uses the other onboard ATA33 controller (IRQ 14 & 15). I use an EgoSys Waveterminal 2496 sound card. Using the latest EgoSys v1.0 through v1.2 E-WDM drivers has caused nothing but blue screens on my machine, so I reverted back to using the the older non-WDM drivers. The GigaStudio v2.2 upgrade did not provide any additional performance gains but it does give some new features that are quite good (i.e., \"accelleration tags\"). It is important to make sure your audio card is in a PC slot getting it\'s own dedicated IRQ. IRQ
Interesting setup you have there, David. You might want to optimize your MaxFileCache number by finding the lowest one that gives you the same GigaStudio polyphony and sustain pedaling performance as you have now. Companies like Cakewalk and Frontier Design actually recommend a very low MaxFileCache of 4096 because unlike many other software, audio applications do a lot of serial disk read and writes so having a huge disk buffer will affect audio track performance. Also, a high MaxFileCache will take away valuable RAM from applications and sample loading (although that is less of an issue in your case since you have 512 Mb RAM). So it is a good idea to try to optimize the MaxFileCache if the recommended 4096 setting does not seem sufficient. In my case, I can maximize GigaStudio polyphony and sustain pedal use with a MaxFileCache of 24576.
Doug, you change the MaxFileCache with the line \"MaxFileCache=####\" (where #### is the value you decide on) under the [vcache] section in the system.ini file in the Windows directory. Then you need to reboot the computer.
[This message has been edited by Mega (edited 06-19-2001).]