Rename Channel Input/Outputs

General discussion about Gig Performer
1

Is there a way to rename the inputs/outputs?

I have 32x32 channels of I/O and it would be nice to not have to remember where I am sending it.
My audio Interface is X32Rack. It is working out quite well.

Took me a while to get it to work on my Windows 10 machine. Wouldn’t recognize RME ASIO drivers. I solved it by loading all4asio.
I realize the product is new, and will have issues to get worked out. Decided to support it anyway and purchased the dual license.

Next task is to get my Kemper Profiler integrated, and then add Onsong.

BTW- My live rig is setup with a MacBook pro. It is working good, except the GP software crashes almost every time I exit.

2

Thanks for all the feedback - glad you like it and we assure you we continue to support it fully as well as enhancing it. See below for specific responses.

Not yet but it’s on our list

Is there a way to rename the inputs/outputs?

Yes, our sound engineer uses this as well, feeds the effects through GP

My audio Interface is X32Rack. It is working out quite well

Not sure why your RME drivers don’t work but we do mention specifically on our download page, right below the Windows download (/downloads.html) to try ASIO4ALL when other drivers don’t appear to work or can’t be found. Did you download from somewhere else? I have a UFX which I normally use with a Mac (where it works fine) but I’ll try and check it with a Windows machine. Which Windows OS are you using?

Wouldn’t recognize RME ASIO drivers. I solved it by loading all4asio.

Please open a ticket and send us the crash report so we can see what’s going on.

except the GP software crashes almost every time I exit
3

FYI I have also reported the RME issue to RME – it would probably be useful for you to report the problem to them directly as well.

4

Thanks David. My windows PC is running Windows 10 Pro v1703. i7-6950x with 128GB RAM
My RME PCIE card is the RayDAT. Driver version 4.17

I actually did download ASIO4ALL (as recommended on an older thread…I just called it the wrong thing :slight_smile: It solved my problem and let me see the RME

My 2014 MacBook Pro is running OS Sierra. I sent the crash report that pops up on restart, 2 times.

A few more thoughts…
I was originally thinking I would use Gig Performer on every channel of my X32…sort of like I was using Waves Multirack. I have since changed that strategy. While I like Multirack, the limitation to Waves plugs only was ultimately a show stopper for me. I have way more than just Waves Mercury that I want to access. Gig Performer has the power to open up the limitations that Waves placed on me with multirack. It then adds all kinds of functionality and control that I didnt have with Waves. Really, they are not even close to the same. Yes, they both host plugs, but that is about all they have in common…at least from my point of view. I can basically use Waves StudioRack inside Gig Performer. Little fish just ate the big fish. :slight_smile:

For my needs, I think Gig Performer seems to be best suited for setting up surgical insert effects for my vocal channel, building my guitar rigs using GTR, S-Gear, BIAS AMP/FX, and even outboard gear like my Kemper Profiling Amp. I can use everything together inside of Gig Performer. How cool is that!

Then…I plan on hosting send effects to supplement/replace what I have in the X32 for the band. Every studio plug I now have can be used live. I have many different plugs form all kinds of sources. I seem to find ones I like from many different companies. Now I can choose anyone of them, and change them on the fly from song to song.

In addition, I can control all kinds of functionality embedded right into midi data on my Onsong charts. It really seems unlimited for programming the initial setup at the start of a song.

This approach allows me to still mix everything with the x32, and configure it so I can continue the gig if my MacBook gives me trouble when in a live setting.

the real power for me is that it makes it possible to use my plugs without using a DAW. I have tried to use a DAW (Cubase) and it seem to unstable for me to trust it live. I get tangled up in tracks and how to change settings on the fly. Just to clunky and rigid trying to play with a DAW. Maybe a different DAW would work better, but Cubase is what I know. I have Logic and Mainstage, but just never really got the feel for them.

Overall, I look at Gig Performer as another useful tool in my arsenal. I will discover it’s strengths and then integrate them with other tools to create the setup I want. I am not limiting myself to an either/or approach. We dont do that to ourselves with plugins and stomps…why put that limitation on any product? Find what works in your workflow, and then expand you horizon to make room for future tech. That is what I did by buying Gig Performer. I am hoping Gig performer with prove to be rock solid as the vision suggests.

BTW- Will LILO be adding a link to the forum, or hosting the forum? It seemed convoluted for me to find this forum…which is probably why it is not that heavily used.

5

Have you tried using a non Waves plugin? From looking at the crash reports, it looks like this might be an issue with Wave stuff not cleaning up itself properly

6

“Have you tried using a non Waves plugin?”
Yes, but I can’t say that I ever ran it without a waves plug loaded. I will try it when I am back in the studio.

7

So…I tried all kinds of options and I can’t get it to crash on exit now. So, not sure I can recreate the problem to try and point to the source. I will post back if I happens again.

One thing I did notice…
If I want to open the audio out or input device when I am in the rack back view, I have no way to scroll to see all my channel faders. They go off the screen when I have 32 outputs. No scroll bar and cant resize the window. Not a big deal, just thought I would point it out. This is on my Macbook.

8

Thanks for the report. We’ll get this into our bug tracking system and fix it as soon as we catch a breath :slight_smile:

Having said that … the sliders at the front of the GP window (Left side- INPUT, right side - OUTPUT) are actually those same sliders. They are not global, but rather rackspace specific and simply reflect the sliders from that block so if you have to - you can access all of them right there.

We always advise however that users adjust the I/O levels on the actual interface itself to get the best possible sound. This is independent of GP or any other software - you just get better levels and cleaner sound is your gains are adjusted at the interface level. Think about the “Gain” knob or control on your classic mixing console. If your gain is too low - you can bring the fader on that channel up to adjust it, but the sound will never be as good as if you were to adjust the gain properly. Same if your gain is too high - you can later try to trim it with the fader, but it will still distort… not even mentioning if you try to send part of the input signal to an effect etc…

Not a big deal though - the faders are there to be adjusted and it is perfectly ok to do it, but I would just advise against radical adjustments there. This, of course, does not apply if you actually attach a MIDI control to one of the faders and use it to say lower the output level gradually for the song fade-out… You can use the widget’s “Recall value on activate” and reset the levels to 0dB every time you switch back to that rackspace for example so that you can always be sure that you have good levels at the start, but can fade out if you want to.

Hope this helps and thanks again for the report.

9

George, regarding the RME issue, I just got a report back from RME that they tried running Gig Performer on Windows 10 and the RME ASIO drivers were immediately recognized. If you are still not able to see those drivers, you might want to reach out to RME directly.