[blog] Tips to troubleshoot your computer based setup

Link: Gig Performer | Tips to troubleshoot your computer-based setup

More tips will be indexed in this thread. :slight_smile:


More tips


[1] Beware of one-click cleaner apps → LINK

[2] Don’t do that! → LINK

[3] Do that! → LINK

[4] Make sure that you have C++ Runtime or other libraries needed for a plugin → LINK

[5] What if USB MIDI port names keep changing on Windows? → LINK

[6] What to do if plugin editor windows are displayed too small? → LINK

[7] Give Gig Performer microphone permissions on Mac → LINK

[8] Review the “isolated client feature” on your router → LINK

[9] If you upgraded your PC and now GP is crashing, start GP in Safe Mode (driver issue) → LINK

[10] Tip to fix your Syntronik or SampleTank internal preset patches → LINK

4 Likes

Don’t do that! :slight_smile:

.


[1] Sample rate

If your audio interface is used by multiple audio applications at the same time (including two or more Gig Performer instances), don’t use different sample rates. If the sample rate is not the same, you will hear audio out of tune, audio pitched down. etc. (example, KB article)

[2] MIDI in (OMNI) block

Don’t use the MIDI In (OMNI) block if you are using virtual MIDI ports. Why? Well, when you send MIDI events into a virtual MIDI port, the events will be sent on through that virtual MIDI port’s output, but because the MIDI In OMNI block listens to all incoming MIDI messages, it will receive messages from virtual MIDI ports as well. So as soon as you send out a single event, it will feed right back into the MIDI In OMNI plugin and sent out again (feedback loop). So if you plan to use virtual MIDI ports in your configuration, use specific MIDI In devices rather than the MIDI In OMNI block (more info).

[3] Uninstalling Gig Performer before the update

Scenario: Gig Performer is running fine on your Windows computer and a Gig Performer update becomes available – but before you update, you uninstall your current version or an automatic third-party uninstaller removes all references to Gig Performer.
Per this blog: “Don’t do that! We repeat, don’t do that!

[4] Gig Performer instances

Don’t open the same instance twice as both opened instances will respond to the
same MIDI and OSC commands and changing any settings in one of the instances will
change it for both, but only one will get the change immediately (more info).

[5] Keyboard splits

Don’t create splits directly on your keyboard controller - that could even be dangerous and lead to stuck notes (more info).

6 Likes

Make sure that you have C++ Runtime or other libraries needed for a plugin (example).

What if USB MIDI port names keep changing on windows - LINK

If you have a particularly high resolution Windows tablet, it may be that some plugin editor windows are displayed too small. You can address this by adjusting Windows scaling behavior. Click here to learn more.

Sadly, not everything scales. I’m running Win11 on an excellent 17" 4K laptop, scaled to 200% (back down to 1920x1080). Some apps don’t scale and are almost impossible to read. I had been trying to find a decent 32" 4K monitor so I could switch back to no scaling, but those monitors are stupid expensive. Plus, I don’t really have the desktop space for one.

1 Like

Do that! :slight_smile:

.


[1] Comment your code

Liberally comment the code you’ve written. Otherwise, you’ll come back to it in a few months and forget completely what you did and why (source).

[2] Create a backup

Besides an operating system backup, Gig Performer allows you to easily export certain data that you may want to keep safe.

[3] Reboot your Mac after updating an AU plugin

Generally, if you install or update an AudioUnit plugin (Mac only), you have to log out or possibly even reboot your computer before the updated AU becomes visible (source).

[4] Install 64-bit plugins and note the install path

VSTs may come as 32-bit and 64-bit versions. Uncheck 32-bit versions and note the location of 64-bit ones; after the installation, add the locations to the Plugin Manager.

[5] Steer clear of plugins that require weekly or monthly authorizations

Most likely you are not connected to the Internet while you are performing; if such a plugin decides to “call home” while you’re offline to authorize itself - it will stop working. Examples: link, link.

2 Likes

Make sure you give Gig Performer “Microphone” permissions on Mac.

This question is posted from time to time (example).

Relevant blogs:

This “isolated client” feature on some routers is worth mentioning in this thread (link).

There are a few points of view to this:

  • When you want your devices to communicate with each other, enabling isolation works against you
  • The security point of view is that enabling this setting helps preventing lateral movement, especially when it comes to malware, for example ransomware.

This means one should carefully weigh these mutual exclusive points of view against each other. It depends highly on the case. Of course a safe network that is of no use for you is also not desirable…

I’m just saying this so that people understand the consequences of enabling or disabling this setting.

Help! What should I do if Gig Performer crashes immediately on start up before loading any gig files or plugins? Every once in awhile we have users who have a Windows OS update installed and GP stops working after the update. Since it crashes on start up before loading any gig files or plugins it can be hard to figure out what is causing this and very frustrating, and it’s often not caused by a plugin. The absolute BEST thing to do is try to run Gig Performer in SAFE MODE (Windows). See the link below to the discussion where one of our intrepid users - LUCASCURTIS - refused to give up, how he did it, and what he found.

-----> Link

2 Likes