Live gig - sound dropping - midi connection fine

It’s gotta be the new version I’m live and every 10 to 15 minutes. All the sounds randomly cut off and I don’t get any sound going to my M4.

I’ve had a reboot the gig file three times and my band had to go out with a keyboard and a keyboard heavy set- I can’t help thinking the only variable at this point is the new version and this is bumming me out

Very unlikely but why don’t you revert back to the previous version for shows so that this issue can be diagnosed without stress?

Are you on Mac or Windows?

Have you rehearsed at home or in your studio? Do you have the problem there?

Are you sure it is not an issue with a particular plugin(s)?

Maybe a plugin lost its activation when you updated GP and it is now operating in trial mode?

Jeff

1 Like

Good morning - muscled through the rest of the gig and now I have time to review what possibly went wrong.

I had the deactivation of one arturia plug come up on the screen at the end of the first set - so that is a possibility. At the break I got an internet connection and reconfirmed the software activation on Arturia (that part didn’t take long)

The workaround was closing GP and reopen with the gig file and that would solve the issue for 10 min sometimes longer.

And for what its worth, in the second set - I don’t believe I had to reboot the software.

Is there any particular must dos when upgrading GP - like reactivate the licensed software? I feel like that would be kind of a big thing to mention as a precaution.

had a practice with the new upgrade for 2 hours - didnt have one failure

As long as you don’t upgrade your OS, you can use GP forever without any need to even connect to the internet. That was a deliberate decision from the beginning because we did not want musicians on stage to be suddenly blocked by GP requiring authorization.

We have numerous customers on tour for many months where the road crew shuts down the machine after a show and just sets it up again at the next location No internet connection, nothing to risk a failure,

Obviously we can’t speak for other plugins that may fail or require reactivation after an OS upgrade but we do tell people that they should not upgrade ANY aspect of their computing environment unless they have several weeks of downtime so that they address any issues without stress.

Im on Mac - and Ill set up today and see where we are at. No gigs for a month.

Awesome. Please let us know sooner rather than later how it goes.

so far no issues - I think it had to be the vsts thinking that they were not licensed - and had no wifi to register them ? Its just weird because I had no issues during practice (maybe I never hit the vsts to the point where they were ending the output)

I guess the question is - what do you do to ensure that all vsts are up to speed when there is an upgrade

other house keeping question - is there a way to remove all non VST3 formats (except for Arturia since Im using Narfsounds and chose VST) in a way that’s convenient?

Do not upgrade some weeks before a gig

2 Likes
  1. Make sure you deeply understand the licensing model of a plugin before you commit to using it for live performance so you can determine if there’s a risk.

  2. Unless it’s broken, don’t upgrade! Seriously. I’m still running my live performance host on a 10.14 machine from 2019 and I have not updated any of the plugins I’m using on it in years.

2 Likes

Im not talking about the VSTs Im talking about GP - I didn’t upgrade the VSTs in question - they just dropped the licensing after GP was updated.

We have no control over what a plugin does regarding their licensing but I’m not sure why just updating GP would impact plugin licensing.

By the way, I think I might have had a similar issue where an Arturia plugin I use in particular seemed to change to a blank preset during a gig, so no sound.

I am still not sure exactly what caused it. I had created the gig file from a particular set list. When I got home and tried the full gig file from which that was taken, it worked fine in that one.

It happened around the same time you had an issue. I wonder if it was the same plugin?

Go figure!