Thank you for your interest in Gig Performer Essentials.
Please enter your name and email address in the field below. Links for both Windows and macOS downloads will be sent to you.
By providing your email address, you will be subscribed to our newsletter from which you will be able to unsubscribe at any time. Make sure you use a valid e-mail address and if you don't receive our e-mail, please check your spam folder.
Please enter your name and email address in the field below. Links for both Windows and macOS downloads will be sent to you.
By providing your email address, you will be subscribed to our newsletter from which you will be able to unsubscribe at any time. Make sure you use a valid e-mail address and if you don't receive our e-mail, please check your spam folder.
Gig Performer crashes when you try to change the sample rate
In some cases, when you try to change the sample rate, Gig Performer may crash.
This issue mostly happens due to two reasons: – Incompatible ASIO drivers on Windows crash Gig Performer. – A plugin crash due to its inability to handle sample rate changes that occur after that plugin has been loaded.
Incompatible ASIO drivers
If you suspect that you drivers are incompatible, please download the latest version of the driver for your audio interface. If that doesn’t work, try an an older driver. Alternatively, you can try ASIO4ALL.
Next, stop Gig Performer from automatically loading the last gig file. Please read this article to learn more. Afterward, open Audio Options and try and change the sample rate. If the ASIO4ALL driver works, then the problem is definitely due to incompatible ASIO drivers for your audio interface.
Plugin issue
The best practice is to change audio settings on blank gig file. There are two reasons for this recommendation. First, your gig file will not be reloaded after you change the sample rate. Second, you avoid crashes in faulty plugins. It may happen that a plugin us unable to handle sample rate changes that occur after that plugin has been loaded.In this case, the same advice applies. First, try with an update version of that plugin. If that doesn’t work, try an older version of that plugin.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok