Yes, a Blue Cat’s Connector for my iPad would be great, a game changer for me.
If you’re sending to another machine over the network, there’s no need to worry about IP conflicts. You can simply change the port number for each instance of Connector.
If you’re only using one machine, you’d choose either App or Local Host instead of Network, and for each instance of Connector, use a different port number. Each instance of Connector has very low CPU usage, so it shouldn’t affect the performance of your machine much.
1 Like
What is that App?
If you’re using Connector within the same application, you choose App. If you are using it between different applications(even multiple instances of GP), you choose Local Host.
1 Like
i think my CPU load problems came from the fact that the audio settings were automaticly changed on one of my GP4 instances, while changing settings on another instance.
I was running an ambinet-y FX patch with buffers of 512, that were then set to 128 samples.
( yes, i do set all settings in the settings dialog as much i can, to NOT do automatic things, like autoload and such / but i deal with some inconstency,…hard to tell, since i did such complex multi GP instance tasks very seldom so far )
what edm11 sayed.
you don´t need to “select” a specific app, to add this also.
you quasi just select a mode.
the handshake is selected by giving the sender and the receiver the same IP number.
its like telephone, haha 
It is worth reminding everyone that the Blue Cat Connector is a plugin and not a stand-alone application - you need a host application like a DAW or similar that uses or works with audio plugins. Definitely not a replacement for the various virtual audio cable products that have been discussed in the Community. I have the BCC, the User Manual might be of interest for those interested in what Blue Cat has published about this product.
1 Like
I think this will only work with something like Zero Tier One which creates a LAN from a WAN. Other than that maybe port forwarding might do it. Latency will be an issue though.
BCC is awesome, have many of them running over several GP instances and it works great. I’m even sending audio from one instance to a second instance, doing some processing and then to a third and I don’t perceive any latency. This really opens a lot of possibilities.
2 Likes
yup !
it opens really new doors.
and makes my computer look “half as big” as it was bevore, haha.
Thanks for posting this!
1 Like
has anyone tested this with a DAW and GP4, using GP4 in a similar fashion that you would use Vienna Ensemble Pro?
E.g. have the GP4 instance load up an Orchestral template (where you have all you VI-instances presets and Audio+MIDI-routing setup) that you can then pipe MIDI data from DAW->GP4 and return audio from GP4->DAW?
1 Like
Anyone else getting startup pops with Connector? What about feedback? Just about blew my ears out. Quadruple checked to make sure everything was setup correctly. Wasn’t having these problems before, going back to that.
I’ve just started playing around with BC Connector , I have the demo trial and took a while to figure out how to use it , like originally “where do you host the plug-ins?” oh you don’t , do you ? You create unique Send and Return instances to do that in my case : Successfully playing live Guitar/AmpSim in Reaper on a PC and streaming the digital audio over a small network Gigabit switch into a MacPro 2008 3,1 hosting GP4. Created a track in Reaper with an AmpSim Suhr PT100 and perhaps some verb via a bus , insert a BCC [blue cat connector] Send instance in the Reaper Master Bus , sending over Network to my MacPro with a BCC Return instance loaded in GP4 , 'just blowing in the wind , i.e. no audio nor midi wired into the input of the Plug-in Block , only the BCC Return status in Network and then the audio out of that plug-in block to my MacPro audio interface, works pretty well , pretty stable and buffering around 1024 or so , other than auto . Could also record that stream into Logic Pro by wiring another BCC instance Send which I could also name and then BCC Return instance inside Logic , which then I could assign to a Bus and after make yet another track to record that Bus input , monitoring said input would elicit the latency which was high enough to want to avoid monitoring , that extra jump in Logic wasn’t handled that well, on a midi controlled AU effects track , I’ll try a few more scenarios this weekend , but the opportunities BCC affords are unique and quite useful even at this early stage.
P.S I also use Vienna Ensemble to host Virtual Instruments , and at this early stage I wouldn’t imagine BCC could handle VI’s as well as VE can ,for my experience … however BCC can be a useful tool in the Muti DAW or Multi PC environment it has promise !
1 Like
Blue Cat’s Connector 1.1 is here!
This free update adds a new MIDI meter to monitor MIDI activity and offers a free Windows ASIO driver: you can now use any audio application as an audio server for Connector
I’m curious how this might be used by Windows users with GP. Would it be mainly useful for those without a multi-client ASIO driver?
3 Likes
This is great news. I’ll try it definitely.
1 Like
Hm… maybe this could be a modern replacement for the (still functional but old fashioned) ASIO Link Pro. I think, i’ll give it a try this time. 
2 Likes
It does function well as a 2-channel ASIO server. You can send audio from other applications via the Connector plugin, and a different audio app that is set up to use the BC Connector ASIO receives the audio as a direct 2-channel input and can be processed in that app.
If you require more than 2 channels of audio that you wish to process in that BC Connector ASIO server, however, this approach will not work. For my own personal use, ASIO Link Pro is still required.
1 Like
I just received an email that Blue Cat’s Connector has been updated to v1.12, which can be downloaded from your download page via the link in the update email announcement. Note that I deleted the link from this post because I think it is the URL to my account.
What’s New:
- Improved resampling and drift compensation when the plug-in starts streaming audio.
- The plug-in now reports when more than 100 dropouts occurred.
- Improved user interface meters refresh performance.
- The plug-in has now been tested for long distance communication and online jamming. More information and setup instructions can be found in this tutorial: Jam/Rehearse with remote musicians
- Fixed VST3 MIDI input not detected by Ableton Live 11.
2 Likes
Dream-Mode: an iPad version for Bandhelper and auto-connect to my Mac…
BBB
PS: One of the most annoying things for me: “virtually wire” Bandhelper to my Mac each time I enter the rehearsal room…