I’m testing the current Loopy Pro for Mac beta, v787, as a VST3 inside Gig Performer and I’m running into an issue where GP appears to expose Loopy’s inputs correctly, but no audio actually makes it into the plugin.
My eventual goal is to use Loopy Pro as the looper inside my existing Gig Performer rig, with GP remaining the main host.
When I instantiate Loopy Pro VST3 in GP, the wiring view shows the Main input on channels 1/2, Aux Input 1 on 3/4, and Aux Input 2 on 5/6. The Channel and Bus Layout window also shows Main Input, Aux Input 1, and Aux Input 2 as stereo input buses, along with the Main Output and several Aux Outputs. So Gig Performer does seem to be recognizing Loopy as a multibus VST3.
To rule out anything in my normal rig, I made a very simple test setup using only the melda oscillator routed directly into Loopy Pro.
I first routed the oscillator to Loopy’s Main Input 1/2. Inside Loopy, I added a Hardware Input source and selected the Main input. No signal appeared inside Loopy. I also routed the same oscillator to every input on the wiring module and within the vst checked every input 1-32… no audio into the channel. I tried routing the oscillator to the Main input as well as the available Aux inputs. Inside Loopy I created Hardware Input sources and selected Aux 1, Aux 2, etc. from the routing popup. Still no signal.
I’ve also tested with monitoring turned both on and off inside Loopy, with no change.
The output side does work. I imported an audio file directly into a Loopy clip and played it, and that audio appeared correctly at the output of the Loopy VST3 block in Gig Performer.
So Loopy is definitely running inside GP and sending audio back to the host. The problem seems to be specifically on the input side.
As a comparison, I instantiated the same Loopy Pro VST3 v787 inside Ableton Live and Logic pro – then routed audio directly to the loopy plugin. Loopy immediately received the audio at its Hardware Input, so the VST3 itself appears to be installed and working correctly.
Loopy also shows up as an Audio Unit in Logic and Ableton, but I don’t see that version available inside Gig Performer, so all of my testing in GP has been with the VST3 version. But i think thats because GP does not support AUv3.
At this point I’m wondering if there is some additional VST3 bus activation or channel-layout setting in Gig Performer that I’m missing, or if this may be an interoperability issue between Gig Performer and Loopy’s current VST3 implementation.
If anyone has seen something similar with a multibus VST3, or has any ideas for other tests I can run, I’d appreciate the help.
I can also provide screenshots or a very simple .gig file that reproduces the issue if that would be useful.
THANKS HEAPS!
