I’m aware that Polybrute Connect has issues with establishing connection with the hardware. I want to add my own experience to the reported instances.
I own a Polybrute 6. Polybrute Connect works in standalone mode, but not in the two DAWs that I own - Cubase 13 Pro and Ableton Live 11 on Windows 11 Pro. Polybrute Connect just doesn’t track changes in the hardware in my DAW and can’t send any non-MIDI messages to the hardware either. The Polybrute is on the latest firmware. The Polybrute Connect is also updated to the latest version as well.
Things I’ve tried:
No hub, powered hub - it doesn’t matter.
Cable length - I tried cables of various length, ranging from 1 meter to 3 meters, with our without USB cable repeaters. No luck.
Type A or Type C - this doesn’t matter either.
This behavior is very persistent and as I said before it happens in both DAWs, so it’s not a connection issue. Also the fact that this behavior is limited to the DAW instance but not the standalone app tells me this is a bug in Polybrute Connect that messes up non-MIDI messages to be received and sent in the VST instance.
Any ideas, anyone? My experience with the Polybrute Connect has been unjoyful, to say the least. Polybrute Connect was one of the selling points of the Polybrute ecosystem and here I am just spending time on trying to fix it.
Hi there. I think I have a solution that may work for you.
This has happened to me with Ableton 11 on windows 10 and then again on windows 11 when I upgraded. From what I can tell its really just the first time it links in the VST that is an issue. Once you get it the first time it will work in future sessions with no issue.
1 - Start Ableton or whatever DAW you use (without turning on your polybrute)and start a new MIDI track with polybrute connect.
2- Once connect is fully loaded turn on your polybrute.
If this does not work try starting the DAW with the polybrute on launching the vst and while it is not responding turn the polybrute off and wait for the electricity to cycle so you don’t damage anything before turning it back on.
You may have to try this several times. Eventually it will connect. And like I stated earlier once it connects once it will no longer give you these issues.
I hope this helps you. I know I was very frustrated myself until I figured out this workaround.
Adding more data: with a PB12 and Live 12.1, the method described by brandonjames444 worked for me via power cycling after Connect was loaded.
Before that, I can not connect by default (and even got Connect to crash Live a few times it seems like).
It works great for me in Bitwig except I have to initially establish a connection via the Link button as opposed to the big obvious “Connect” button (!)
_Need help ?
When you can't find the answer online or in the product manual, the Technical Support Team is here!.
_Stay tuned
Follow us for the hottest sounds, fresh content, exclusive offers and Arturia news as it happens.