Important information on GSIF (Gigasampler Interface) operation

Performance when using GSIF and ASIO simultaneously

The performance of simultaneous GSIF/ASIO operation can be much better as it is now, even when using a Hammerfall (which uses no CPU copy routines to achieve the smallest possible GSIF latency). The reason for the bad performance is Gigastudio, which increases the priority of the process msg32.exe from \'normal\' to \'realtime\'. A small decrease to \'high\' will immediately improve audio performance (less crackling and drop outs) and MIDI timing. The Hammerfall then can be used with two steps lower ASIO latency.

How can one change the priority of a process? You\'ll need the freeware PrcView

This tool shows all active processes and their priority, and also allows to change it in realtime. Start GS, load the sounds, start ASIO (Cubase etc.) and change the priority of msg32.exe from \'Realtime\' to \'High\'. Much more comfortable is the program gsfix.exe

from Nenad Siskov (who discovered this effect), which does this change automatically. Note that it is shareware at this time.

Please note that the ASIO latency 1.5, 3 and 6 ms isn\'t available during simultaneous GSIF/ASIO operation! The driver automatically activates 46 ms instead.

Nemesys did not comment so far on an update of GigaX, which would make all the above redundant.

Chopped or distorted playback after changing the ASIO latency in simultaneous GSIF/ASIO operation

To avoid this effect set the ASIO latency in the Hammerfall\'s Settings dialog to maximum (186 ms) PRIOR to starting GS and ASIO software. After the start of the programs the latency then can be changed without problems. According to our tests the problem only occurs if the latency is set to a lower value before starting the software (for example 46 ms), and is later increased while running both programs. It seems GSIF can make the buffers smaller (compared to the size at program start), but can\'t increase them.

Tip: Don\'t change settings after the start of Gigastudio.

Chopped or distorted playback after changing settings in Gigastudio in simultaneous GSIF/ASIO operation

Description: The ASIO latency is changed. Then the button Apply is pressed in Gigastudio (for example because of new settings for sample rate or output channels). Result - chopped playback. This is a bug in Gigastudio (confirmed by Nemesys). When pressing \'Apply\' Gigastudio uses a wrong buffersize (the one which was active before the change).

Tip: Don\'t change settings after the start of Gigastudio.