I’ve seen this issue posted by other users, but haven’t been able to find anyone who has answered with a solution.
I’m using Logic Pro with Polybrute Connect, although have seen the same issue reported by users of various DAWs…
So, I can successfully record and playback only some control data - e.g. pitch bend, aftertouch - from the Polybrute 12 into Logic. If I try to record ribbon data, for example. it doesn’t work, although frustratingly, if I monitor the event window when recording, I can see the ribbon data briefly flashing up and then instantly disappearing!
The only way that I can get any non-standard controls to record is by enabling “Polybrute VST” within Logic (against Arturia’s recommendation) and it will then record whichever expression is played as automation data. However, even with this method, when playing back, the modulation has no affect on the patch (despite the correct movements showing on the Polybrute Connect VST).
Does anyone have a solution to this? It seems inconceivable that this issue could be left unfixed, given that the expression capabilities are one of the main selling points of the synth.
Not new this issue. This is from the legacy forum in 2022:
I think the MIDI data management needs a little more attention.
For what I need the PB for would be the option to make the seq/arp NOT to start automatically when (in my case) it gets a “Start”, “Stop”, “Continue”, or “Song Position” data from the MPCX.
I use a filterbox to prohibit this data flow. Works fine, but…
Backdraw: I need to set the LFO almost always to “retrigger” as the LFO runs in “Mono”/“Poly” at its own start point, resulting in a shifted LFO start - somewhere. A very narrow minded setting of the seq/arp - I would call it.
And I need to be precise, as there is no quantizing help for Note On - legacy of the analogue synth world
In a nutshell: A MIDI filter setting to ignore “Start”/“Stop” for the sequencer and arp, but keep them in sync.
