Some of you asked for it for years, here it is :). A new track type, AFTR, sitting right after MPE in the track-type list.
Every note carries its own pressure curve, drawn and edited in Step mode exactly like the MPE pressure lane
One input channel, one output channel, like a POLY track. No MPE zone to set up, no special routing, so it works with any synth over DIN or USB
Move or transpose a note and its aftertouch follows, because the curve is stored with the note
If your keyboard only sends channel aftertouch, an AFTR track still records it : the incoming value is applied to every note currently held
Incoming poly aftertouch is passed through on every track type, not just AFTR, so Hapax no longer swallows pressure data when used as a router
Instrument definitions accept TYPE POLYAT and TYPE AFTR, and the MIDI monitor now displays poly aftertouch under the ONLY PRESSURE filter
HIGHER CV CLOCK RATES
CV CLOCK RATE now goes up to 96 ppqn, with 48 ppqn available too, instead of 24 max. Tight enough to lock Hapax to an audio rate clock coming from a DAW or a modular system. The list is reordered from fastest to slowest, and the index stored in your global settings is migrated on load, so there is nothing to redo.
CLOCK TIMEOUT AND CV FOLLOW TEMPO
CLOCK TIMEOUT : when the external clock goes quiet mid playback, whether CV, MIDI or USB, Hapax falls back to its internal clock instead of hanging, and re-locks on its own when the clock returns. The delay adapts to the incoming pulse rate, so it behaves the same at any tempo
CV FOLLOW TEMPO : decides whether an incoming CV clock drives the project BPM or simply advances the sequencer. Left OFF, a manually advanced gate stays a creative tool
UNDER THE HOOD
Automation processing is optimized : projects with a lot of declared lanes get most of that cost back.
Clock handling was reworked too, so Hapax no longer drifts behind at high PPQN.
And 8 bug fixes : a stuck arpeggiator note when changing pattern with the arp muted, instrument definition default values ignored on load, a freeze when an LFO was pointed at RANDOM note, and an empty .dat file blocking a whole project from loading, among others.
BEFORE YOU UPDATE
As usual, project saved with 3.20 will not open in 3.10. Keep 3.10 and your backups at hand. Upgrading is transparent, but a settings file written by 3.20 is not read back by 3.10.
Big thanks to everyone who ran the betas and sent feedback over the summer. Poly aftertouch went through three rounds and your reports shaped most of what landed here.
Don’t want to be a hater and happy for those who.use this stuff but why the fixation with mpe?
Can we take a poll of how many users value MPE and implore you to focus on the thousands of other brilliant suggestions here on the forum and stop prioritising these MPE functions.
I have no evidence or basis for assuming MPE isn’t hugely in demand so could just be old lonely and bringing grumpy vibes…soz.
I don’t see anything MPE related in this update at all. It’s a very nice update with PA(which is in the MIDI standard so it should be supported), some smaller new features and improvements/bug fixes.
Hapax was, and is, sold as an MPE sequencer. Squarp has made a pretty big commitment towards MPE by saying that Hapax offers “Full MPE compatibility.”. They shouldn’t ignore that because of some poll, they have a responsibility towards their customers to deliver full MPE compability and a great MPE experience.
I say that as someone who has zero interest in MPE.
I converted to Hapax because it supports MPE. So by prioritizing it, they’ve made at least ONE THOUSAND DOLLARS
PolyAT isn’t as important to me but I do know from the long thread on it that folks have been waiting 4 years for it. So good to see the polyAT crowd well served with this release.
mpe was definitely advertised so is a priority. im not into mpe myself. id love to see the lfo/delay sync times get the comprehensive treatment. i still love this thing over any hardware midi only sequencer! sync fixes are hugely welcome!
Thank you for the poly AT - it would be great if you would find a solution how we can use midi effects on drum tracks effectivly. Also i would like to see that we can print the midi fx , or reroute a track output to a track input - maybe with an input FX, so we can record the fx on a seperate track, and work from there- it would also allow very creative usage. (maybe merge with existing notes, inputs replace track or other options) maybe even note side chain would be possible if we could use note input from other tracks, to mute notes. (Not a complaint - hapax is super great- really satisfied with all you shipped already.) But i still think that printing, note input could be super useful for many users. (also possibly to reroute midi controller data to multiple ports.?) (CC translation effect if this would be possible - with some filters to remove unneccessary traffic.)
Thank you Squarp team, the aftertouch channels are awesome and I love the improved audio sync rates. The Hapax really is the glue between software and hardware for me. Now I am patiently waiting for integration with the xp32
