Re: Gig Performer... Mainstage alternative?
Posted: Fri Jun 09, 2017 9:19 am
Random thoughts on Gig Performer
I downloaded the free trial of Gig Performer. I use MainStage quite a bit so this is really a comparison to MS.
I like that incoming MIDI can be separated not only by device but by transmit channel. That’s one thing that frustrates me about MainStage. I sometimes use a Yamaha MX61 and when you change sounds in part mode it changes the corresponding MIDI transmit channel. Sometimes I’d like to use that to my advantage. MainStage ignores incoming channel data unless the VI itself is capable of multitimbral operation. Most of MainStage’s built in plugins are not multitimbral.
The process of creating the node connections is kinda finicky. I’m doing it with my mouse on a desktop and more often than not I somehow miss the target. Wish they would make a little more room for error on the drop zone of each connection. I can imagine getting very frustrated trying to make or change connections in the heat of the moment on a laptop.
When they say there are no included plugins, they mean it. There are gain change and balance, and one to split a mono signal out to a stereo output, but I couldn’t find one to collapse a stereo signal to mono, which I need fairly often. I tried to create a mono mix by crossing connections (input 1 going to both outputs 1 and 2 and then input 2 going to both outputs 1 and 2), but something didn’t sum right, like one channel had reversed polarity or something. The same inputs mono’d out perfectly in MainStage.
No MIDI processing plugins like arpeggiator or chord trigger. I sometimes find those functions (esp. chord trigger) in MainStage to come in very handy. There is a velocity change capacity, but it isn’t a graphical curve. It’s numeric, as in 1 - 127 input equals 30 - 110 output. You can further choose to remap the velocities by either constraining them to those minimums and maximums or by rescaling the incoming velocities to the restricted range. You can block or remap CC numbers and other MIDI data, but not scale them.
One of the things they tout is that they don’t use the mixer/sends paradigm. Well, I’m comfortable with the mixer and sends analogy. I found myself wanting to grab a fader to change the volume of something rather than have to create a knob first just to accomplish that. Because there’s no mixer you also can’t solo or mute a node without first creating a button on the front panel of your rack space. I could easily create a button to bypass a VI, which is close to muting it but not exactly the same because it works at the MIDI level rather than audio. If I hit bypass with a note held down and then released the note while bypassed the note would still be ringing when I toggled the bypass back to active. This is because it wasn’t muting the audio, but bypassing the MIDI input to the VI, thereby not sending/receiving the note off. In order to build a mute button I had to first add a “Gain and Balance” node and then create a button to toggle the value between 0 dB (no gain change) and off. This wasn’t as straight forward as it might sound because the values of the toggle switch were not scaled in dB, but as 0-100 numerical values. A value of 100 gave a 6 dB increase, so I had to set the max value to 75.1 to get no gain change. That’s a lot of tweaking just to get a mute button. I have no idea how to make a solo button.
There is a very tiny mixer in the lower right corner, but it has no numeric readout and I couldn’t find any obvious way to group two faders as a stereo pair. There is a trim knob at the top of the GUI, but I believe it changes all outputs on your audio interface.
Speaking of the GUI… when you open a plugin in DP or MainStage there are popup menus at the top… above the actual plugin GUI. You can choose presets from there, although I guess most VIs have a place in their own GUI for doing that. I just happened to choose the free OB-Xd from Datsounds and it does not have a preset chooser as part of the GUI. It comes with plenty of presets that are available when used within DP or MainStage, but not from within Gig Performer.
You can do keyboard splits within GP, but there is no learn button for the high/low notes of the range AND you can’t type them in. You must choose the pitches from a very long popup menu! These splits are represented graphically within the editor for each node on a keyboard along the bottom of the edit window, but since each node opens its own editing window you can’t see the various ranges displayed over the same keyboard. I kinda like that in MainStage you can always see the note range of each patch over the same keyboard, at least while in edit mode. GP doesn’t do floating split point (like MainStage does).
When I heard the description of this as using “rack spaces” I’m thinking of DP’s V-racks, where something can be accessible at all times without having to be duplicated, like a main piano patch. MainStage has something like this in that you can instantiate a VI at the “concert” level. I have never gotten that to work the way I want though. Seems like it always plays then, in every patch set up in that concert. Maybe I’m not understanding something. Anyway, I was hoping that “rack spaces” would be the answer I’m looking for. Well, rackspaces is the term for the GUI, not the equivalent of a V-rack in DP.
Each rack space can have variations, but I couldn’t make heads or tails out of what that means. Every change I made at the top level or individually in any of the variations then was carried over to the whole thing. I thought maybe it meant that you could a various front panels for one set of node configurations. Well, that didn’t seem to be the case either. So, you ask, why don’t you just look it up in the manual? There is no manual…
Patch remain seems to work as advertised. You can change rack spaces via MIDI patch change messages. Also, I was able to use a trick that use often in MainStage, which is to assign the two lowest keys on my keyboard to move up and down the patch list. I obviously set the keyboard split zones so that those keys don’t make any sound. This done through Options -> Global MIDI.
I downloaded the free trial of Gig Performer. I use MainStage quite a bit so this is really a comparison to MS.
I like that incoming MIDI can be separated not only by device but by transmit channel. That’s one thing that frustrates me about MainStage. I sometimes use a Yamaha MX61 and when you change sounds in part mode it changes the corresponding MIDI transmit channel. Sometimes I’d like to use that to my advantage. MainStage ignores incoming channel data unless the VI itself is capable of multitimbral operation. Most of MainStage’s built in plugins are not multitimbral.
The process of creating the node connections is kinda finicky. I’m doing it with my mouse on a desktop and more often than not I somehow miss the target. Wish they would make a little more room for error on the drop zone of each connection. I can imagine getting very frustrated trying to make or change connections in the heat of the moment on a laptop.
When they say there are no included plugins, they mean it. There are gain change and balance, and one to split a mono signal out to a stereo output, but I couldn’t find one to collapse a stereo signal to mono, which I need fairly often. I tried to create a mono mix by crossing connections (input 1 going to both outputs 1 and 2 and then input 2 going to both outputs 1 and 2), but something didn’t sum right, like one channel had reversed polarity or something. The same inputs mono’d out perfectly in MainStage.
No MIDI processing plugins like arpeggiator or chord trigger. I sometimes find those functions (esp. chord trigger) in MainStage to come in very handy. There is a velocity change capacity, but it isn’t a graphical curve. It’s numeric, as in 1 - 127 input equals 30 - 110 output. You can further choose to remap the velocities by either constraining them to those minimums and maximums or by rescaling the incoming velocities to the restricted range. You can block or remap CC numbers and other MIDI data, but not scale them.
One of the things they tout is that they don’t use the mixer/sends paradigm. Well, I’m comfortable with the mixer and sends analogy. I found myself wanting to grab a fader to change the volume of something rather than have to create a knob first just to accomplish that. Because there’s no mixer you also can’t solo or mute a node without first creating a button on the front panel of your rack space. I could easily create a button to bypass a VI, which is close to muting it but not exactly the same because it works at the MIDI level rather than audio. If I hit bypass with a note held down and then released the note while bypassed the note would still be ringing when I toggled the bypass back to active. This is because it wasn’t muting the audio, but bypassing the MIDI input to the VI, thereby not sending/receiving the note off. In order to build a mute button I had to first add a “Gain and Balance” node and then create a button to toggle the value between 0 dB (no gain change) and off. This wasn’t as straight forward as it might sound because the values of the toggle switch were not scaled in dB, but as 0-100 numerical values. A value of 100 gave a 6 dB increase, so I had to set the max value to 75.1 to get no gain change. That’s a lot of tweaking just to get a mute button. I have no idea how to make a solo button.
There is a very tiny mixer in the lower right corner, but it has no numeric readout and I couldn’t find any obvious way to group two faders as a stereo pair. There is a trim knob at the top of the GUI, but I believe it changes all outputs on your audio interface.
Speaking of the GUI… when you open a plugin in DP or MainStage there are popup menus at the top… above the actual plugin GUI. You can choose presets from there, although I guess most VIs have a place in their own GUI for doing that. I just happened to choose the free OB-Xd from Datsounds and it does not have a preset chooser as part of the GUI. It comes with plenty of presets that are available when used within DP or MainStage, but not from within Gig Performer.
You can do keyboard splits within GP, but there is no learn button for the high/low notes of the range AND you can’t type them in. You must choose the pitches from a very long popup menu! These splits are represented graphically within the editor for each node on a keyboard along the bottom of the edit window, but since each node opens its own editing window you can’t see the various ranges displayed over the same keyboard. I kinda like that in MainStage you can always see the note range of each patch over the same keyboard, at least while in edit mode. GP doesn’t do floating split point (like MainStage does).
When I heard the description of this as using “rack spaces” I’m thinking of DP’s V-racks, where something can be accessible at all times without having to be duplicated, like a main piano patch. MainStage has something like this in that you can instantiate a VI at the “concert” level. I have never gotten that to work the way I want though. Seems like it always plays then, in every patch set up in that concert. Maybe I’m not understanding something. Anyway, I was hoping that “rack spaces” would be the answer I’m looking for. Well, rackspaces is the term for the GUI, not the equivalent of a V-rack in DP.
Each rack space can have variations, but I couldn’t make heads or tails out of what that means. Every change I made at the top level or individually in any of the variations then was carried over to the whole thing. I thought maybe it meant that you could a various front panels for one set of node configurations. Well, that didn’t seem to be the case either. So, you ask, why don’t you just look it up in the manual? There is no manual…
Patch remain seems to work as advertised. You can change rack spaces via MIDI patch change messages. Also, I was able to use a trick that use often in MainStage, which is to assign the two lowest keys on my keyboard to move up and down the patch list. I obviously set the keyboard split zones so that those keys don’t make any sound. This done through Options -> Global MIDI.