I noticed a strange behavior of the poly aftertouch mode when the PolyBrute 12 is in split timbrality.
Usually, if the aftertouch mode is set to “Poly”, the aftertouch of a single key only affects the voice of the key. But: If I switch the PolyBrute 12 to “split” timbrality, I noticed the following behavior:
If aftertouch is activated on a key in the lower part, aftertouch affects only the specific voice, regardless of the mode chosen. This is expected.
If aftertouch is activated on a key in the upper part with “poly” polyphony, aftertouch behaves the same: Only the single voice is affected. As expected.
But if the upper part has “mono” polyphony and aftertouch is activated on the upper part, the aftertouch affects the single voice of the upper part and all voices of the lower part in addition.
This seems wrong to me because that means the poly aftertouch does not work correctly in split mode if the upper part has “mono” polyphony. It seems to me that the PolyBrute simply deactivates poly aftertouch in “mono” polyphony because only one voice is active at the same time, so there is no need for polyphonic aftertouch. But in split mode, this means that all active voices are affected - not only the single voice of the upper part.
Is this a bug or intended? I have not found anything in the manual about it so far.
Hey @stanft and thanks for posting, I’ve just had a search through the manual and can’t find anything myself either, i’m not fortunate enough to own a PB myself though so i can’t help any further other than raising this as a bug for now.
If you can, hopefully some nice PB owner will be along to enlighten us fairly soon.
I can confirm this. It exhibits this behaviour both ways as well, i.e. if either or both parts are Mono, the PAT affects the other part. I also agree that this is not expected behaviour.
Has there even been a single firmware update since the launch of the Polybrute 12?
It seems not and the bugs + required improvements are numerous on the machine as well as the companion software side of things.
It’s now one year and it’s not a cheap machine…
Unfortunately not. I am still waiting for this fix — and a few other fixes for bugs that I have reported to the Arturia support team directly.
I had quite some hopes that something would be announced at the Superbooth because it would also be a good opportunity for new features. But it seems that this is not going to be the case.
All I know from Superbooth on the Arturia front is that there are 3 products which are to be launched soon by Arturia (supposed to be nice stuff but seemingly not as groundbreaking as Polybrute 12, so that must be what they’ve been focusing on).
They also announced NKS compatibility with their newer controllers, so between that and the release of V collection 11, the Polybrute firmware progress doesn’t seem like a priority.
It should though. I ve got one on order for testing purposes but would expect that Arturia release a new firmware sooner than later hopefully.
Had I got the Polybrute 12 on launch a year ago, I would be annoyed about the lack of progress. Too many products kills the products…
_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.