I am revisiting my post a few months later. I am putting things in perspective that in December 2022 this was slated for Q1 2023 and it has been pushed repeatedly since then. I do hope that we see this feature return to the Hapax this year. As I stated, I would be fine to have this handled similar to an MPE track. Realistically, I really don’t know if we will ever see this feature. As half of my synths can receive PolyAT (and many can’t handle MPE), this functionality would make my studio come alive with more expression. It would be interesting to take a poll to see who else is really eagerly waiting for this (folks with Hydrasynths or Ensoniq controllers as an example).
I have Hydrasynth Deluxe and Explorer and almost every patch is designed around PolyAT. I’m sympathetic to Squarp prioritizing other issues but it would really add a lot of value for the Hapax if PolyAT was enabled. I can see it is probably a huge pain to have this kind of per-note automation.
Hapax has 12-voice polyphony limit per track, or so I’ve read, and I would definitely be happy to give up 12 automation lanes to enable PolyAT. I would also be okay if PolyAT was “deeply embedded” in note events and not directly visible or editable, so long as it can be a mod matrix destination (with all concurrent PolyAT events affected equally by same math) so it can be manipulated a little bit on its way out of the device. Another acceptable limitation IMHO would be if warping note events shorter causes destructive downsampling of embedded PolyAT data. Hopefully at the track level we could define PolyAT rate limit to help avoid MIDI overruns.
In a dedicated PolyAT track, you could disable or restrict CC lanes (for PolyAT recording) and stay within the 12 note polyphony limit. I see a lot of ways that it could be implemented with some “boundaries” to limit the chance of MIDI overruns. Still, it would definitely work the CPU with that type of data (and standard midi data on other tracks to go along with it). You could limit projects to a maximum of one or two PolyAT tracks, depending on the stability of this. In theory, if the Hapax can handle MPE data, then it should be able to handle this as well.
I’m a big fan of the HAPAX, but this topic is now 3years old. Still no real poly pressure/aftertouch support? Please overthink the priorities There are so much PolyAT keyboards out there now!