GP relayer issue when starting 2 instances from batch file

Gig Performer on Windows
1

I finally saw a reproducible pattern to narrow it down when this happens… I send audio from 1st instance to 2nd, which then comes back to 1st instance via another relayer to be mixed. When starting 2nd instance from within the 1st instance, no issues. When starting both instances from the windows batch file, I get no sounds from the 2nd instance, until I open the 2nd relayer in the 1st instance (incoming audio from 2nd instance) and turn the switch off and back on. After that it works fine. Seems like the 2nd instance must be loaded after the 1st, but when I start them both together, something related to the relayer doesn’t get loaded properly. Any way to solve this? Perhaps a way to delay the starting of 2nd instance in the batch file?

2

Can you please share you batch file?

3

So I did find a way to delay the command line by adding “timeout /t 30” (this would add 30 seconds of delay before running the rest of the command(s), but this produces a pop up window. Would be nice not to have that. Is there a better way to handle this?

Sure thing:

cd “C:\Program Files\Gig Performer 5”
start GigPerformer5.exe
timeout /t 30 /nobreak
start GigPerformer5.exe -in=“Synths”

1 Like
4

The original was without the timeout line:

cd “C:\Program Files\Gig Performer 5”
start GigPerformer5.exe
start GigPerformer5.exe -in=“Synths”

5

When adding the “timeout /t 50” command, it does delay the start (of the 2nd instance) and seems to fix the relayer issue, but not only does it open a DOS window (which I do not want), as soon as I close the DOS window,it also quits GP instance 1. :frowning:

6

This should be fixed and work fine when starting them without any delay.

I will try to reproduce it.

Thanks!

7

In my case, the 1st instance takes longer to load than 2nd. My 1st instance has to be fully loaded before 2nd for the relayer to work properly. For now, I found a work around to create delay and not open the dos window. I ran the bat file from a vbs (script file). Without the script file, the bat file (with the delay added) would open a window, which would close the 1st instance as soon as I closed this window. Running it from the vbs does not open the dos window and relayer works fine. Here is the script file if anyone might find this useful:

Set WshShell = CreateObject("WScript.Shell" ) 
WshShell.Run chr(34) & "C:\Batch Files\mycommands.bat" & Chr(34), 0 
Set WshShell = Nothing

Of course replace “C:\Batch Files\mycommands.bat” with path to your bat file.

But yeah, if this should just work without the delay, I would love to know what is causing it. Thanks!

8

@ztones

I tried to reproduce the issue without success, maybe there is something else in your gig file which is related to the issue?

Please try to reproduce the issue starting with empty gigs having only the following:

Main gig:

  • MIDI In→Instrument→Relayer send #1
  • Relayer receive #2 → Audio Out.

Instance gig:

  • Relayer receive #1 → Some plugin effect → Relayer send #2
9

Interesting find! I was not able to reproduce the issue in the regular rackspace. However, when I put the GP relayer in the global RS I was. (That’s where I have mine.) I had to turn the incoming audio in GP relayer 2 (instance 1) to send and then back to receive to get it to work. So, for the issue to occur:

1: GP relayers in instance 1 has to be in the global RS

2: Instance 1 has to have a longer load time (more plugins)

3: Start from bat file.

10

@Dadi

11

@ztones

I moved the relayers at instance 1 to the global rackspace but still it didn’t reproduce.

I also started the two instances separately, first with “-in=” and later the main one but still didn’t reproduce.

Let me think what I can do, maybe I’ll prepare a special debug binary for you to test if that is ok with you.

12

@Dadi possibly one more detail! I send audio to instance 2, where I convert the signal into midi using midi guitar 2. It produces a synth sound, which then gets sent back as audio. So it’s audio out and back in but there is a midi conversion in between. Not sure if that matters. I can test later.

13

@ztones

If you can create a small gig file which reproduce the issue, that would be the best.

14

I was able to reproduce repeatedly this morning and now I can’t. Trying to figure out the pattern if there is one. Seems random…

15

Thanks for the update, let me know of any progress.

1 Like