I went with the dark gray regular Chroma Caps. Telecaster knob on the right.
5 Likes
oh youāre going to have fun trying to decide, thatās for sure. so, so many ways you can approach songwriting/performing with either.
iām in the midst of resetting my studio as well and every few days of working on it i stop and wonder āhm, maybe i should just sell almost everything and go to mostly Ableton, get a Push 3ā¦ā but i really, really doubt iāll ever actually go that route. Push 3 looks to make a pretty strong case for making that a setupās centerpiece, but i wonder if it could ever be quite as āfastā as Hapax can getā¦thereās a little too much in the Push interface that is entirely screen dependent to understand what the knobs are doing 90% of the timeā¦Hapax has a touch of this but the options are far more limited, and generally thereās button-lit sections to reinforce what mode oneās in to go along with the screen. i donāt think i could ever operate the Hapax screenless like iām pretty sure i could do with a Rytm or a more knobby instrument, but i think itās in a solid midpoint between those worlds.
1 Like
Sure, this is the one I use:
Makes a big difference to the feel!
1 Like
I do get occasional crashes.
These mostly seem to happen when copy-pasting whole rows of clips, with a lot of data contained within. The workaround is simply copy-pasting a pattern at a time. Takes a little longer, but works.
Tends to be fine for me when the sequencer is actually runningā¦ itās more when Iām preparing stuff.
For me, itās very stable when doing this.
2 Likes
Thanks for the replies, everyoneā¦ Much appreciated.
Hapax is on the way. 
Cheers!
7 Likes
A lot of gear has come and went but the Hapax is something I havenāt had a bit of buyers remorse about and I doubt Iāll ever will. Happy exploring!
5 Likes
Youāre gonna like the way you sequenceā¦I guarantee it.
4 Likes
Really hope youāll enjoy it!! Itās a brilliant performance sequencer! 
2 Likes
1 Like
At one point supposedly on the roadmap and also my number #1 wishlist feature - ability to connect many USB devices via a USB hub to the Hapax. Would love to hook up many USB midi controllers to it and route them to different gear.
5 Likes
Agreed!
I tried a USB switcher but it added latency.
Current workaround is a little USB extension cable and just swap the plugs which are secured to my desk. Not ideal for live jamming. At least you can hot-swap them though!
My prediction is that there will be a major new firmware Q1 next year and really hoping it has that feature added.
Also would love to decouple automation lane lengths from the pattern length, could get some really fun results.
1 Like
Have you sent bug reports to Squarp?
They are usually really good fixing this stuff and always keen to know any issues
Ha ha yesā¦ bugs and requests aplenty. It was me that requested āall pads offā screensaver mode, which they were kind enough to implement in the next firmware.
They seem like great people, Iām reluctant to moan. Letās just say I do sometimes wish that stuff could be fixed a bit faster. Been waiting a loooooong time for certain bugs to be fixed 
1 Like
HAPAX TIP: Tempo Nudge (home-made)
Pretty niche, but maybe helps someoneā¦
Okay, so I sync my Hapax from a Mac, using a simple audio file on an audio track. No CV tools, no pluginsā¦ Why? Because I need the first click to start before the 1, so the Hapax sends MIDI slightly early and then everything gets recorded on the grid (plugins/M4L donāt have negative delay compensation, they canāt know when youāre going to press play etc).
When Iām looping in Ableton, after a while (20 mins+) I sometimes notice itās very slightly out, MIDI vs Looped Audio. This could be just my system being run too hard, who knows.
Anyway, I decided I want tempo-nudge buttons. Hereās how to do it if it youāre interested. Very simple to implement. Iāll explain slowly for clarity, itās very easy in practice:
Create 2 copies of your audio sync track, one above it and one below. Name them Nudge Up and Nudge Down.
Take a chunk of time-sync signal (I used 4 bars). My 4 bar chunk contained 384 clicks (24PPQN). Now I set the Grid to 16th Triplets for perfect cutting.
Cut exactly 8 clicks from the end of each 4 bars on your nudge tracks.
On the Nudge Down track, remove the 8 clicks completely.
On the Nudge Up track, duplicate the 8 click chunk.
So now you have 3 tracks with a clip of differing lengths. A shorter clip on Nudge Down, a perfect 4 bars on your original Sync track, and a longer clip on Nudge Up.
Consolidate the clips so they bounce down. Now set Grid back to Bar. Hold shift and drag each nudge clip so it timestretches back to exactly 4 bars.
IMPORTANT: check each clips Warp mode is set to āRe-pitchā.
Now youāll create a simple muting device. I use a āUtilityā, volume turned down, then weāre going to map the little yellow light (on/off button).
Youāll need a controller with 2 buttons set to momentary as your nudge buttons.
Place a Utility on both the Nudge Down track and the Main Sync track, name them both āNudge Downā. Map the on/off button to your nudge down button. INVERT one of the mappings - you want the Nudge Down track to temporarily un-mute when you hold the nudge down button (and the original sync track to temporarily mute).
Do the same on your Nudge Up track. Youāll be left with a one Utility on the nudge tracks, and TWO Utilities on the original sync track (one mutes when your press nudge up, one when you press nudge down).
Done!
Now, whilst you hold a nudge button, the Hapax will speed up/slow down by around 2% and you can get back in perfect sync!
EDIT: I now think itās better to have a slower nudge, more like 0.5% either way. Cut the 8 clicks from 16 bars, instead of 4 as I wrote above!
3 Likes
Iāve just picked up a Hapax today and having great fun so far exploring it.
Does anyone know how many sections a project can have, and how many sections a song can sequence?
I connect mio, acts as router, can route multiple midi in to one out, can filter etc, to connect multiple controllers. The hapax would need additional filters and routings, to avoid overlapping midi messages. I think currently what the best route would be. Maybe a faderfox with 72 knobs.
Multiple devices on the same host port, would be better ofc. With the mio, device and host port could possibly work as inputs, but then the device port is used up.
Does anyone have some details on the subject of Squarp forum spam attack?
Ha haā¦ Iām kinda maxed out on controllers already 
Iām running 8 LCXLās, 3 Launch Controls, 2 Launchkey Mini MK3ās, 5 Launchpads, Nektar P6, and 4 Ipads running TouchOSC etc.
256 knobs (not counting synths and mixers etc), 68 faders, all routed by a Mio10, a MIDI4+, the MIDI processing handled in part by Drambo.
All my ports on my Hapax are taken. The reason I also use the Host port on the Hapax, is because it works as an extra route in, irregardless of what you have set in a Tracks Input on the Hapax.
So you can use ACTIVE TRACK PORT and set it to MIDI IN HOST, and connect an extra controller that way. It also means basically the lowest possible latency into the Hapax by bypassing any routers etc.
Agreed, this 100% needs an overhaul by Squarp. Currently thereās a bug (and I canāt believe more people havenāt noticed this), where you canāt stop the Hapax passing unwanted MIDI through.
Thereās a setting in MIDI INPUT settings, where you can change ACCEPT/IGNORE/REC ONLY.
Ideally Iād like to use REC ONLY, so the Hapax records incoming MIDI but doesnāt pass it through (because my routers handle the MIDI, I donāt want doubled notes).
But if you set it to REC ONLY, the MIDI Matrix stops working. Iām hoping they fix it at some point!
1 Like
I know itās totally been hijacked! Itās a complete mess over there