hapaxOS 3.20 stable release is out!

Hapax HapaxOS
41

Normally no need for terminal.

    1. Open System Settings
    2. Click on Privacy & Security in the left sidebar.
    3. Scroll down to the Security section on the right side.
    4. You will see a message stating the app “was blocked from use because it is not from an identified developer.”
    5. Click the Open Anyway button next to it and enter your Mac’s password to authorize it.

I’m not going to pay apple $100 a year to have my free app signed :slight_smile:

You will miss out on a lot of free open source goodies..

42

Yeah I went there and there wasn’t an option to do that for me… are VST3’s treated like Apps and other extensions?

43

Hmm fair point, I don’t know to be honest. I didn’t have to use the terminal on any of my computers in any case, but I don’t remember exact procedure besides placing in correct Components folder. IIRC I sent it to a friend to test on Apple Silicon, I don’t remember he had any issues. I’ll try to figure out, thanks for the feedback.

44

finally ! hapaxOS 3.22 is out: AFTR tracks, pressure everywhere :slight_smile:

A quick one to finish the poly aftertouch job started in 3.20.

LIVE MODE

  • PRESSUR is back on the left screen of AFTR tracks. Its encoder sets the pressure of the notes you play on the pads, sent as poly aftertouch right after each note starts.
  • Notes recorded live on an AFTR track now show up on the piano roll again (they were recorded, just not displayed since 3.21).

STEP MODE

  • A note placed by hand now actually sends its pressure.
  • The + button only offers VELOCITY and PRESSUR. PITCH and TIMBRE are gone, an AFTR track never sent them anyway.
  • The left keyboard is now the POLY one, not the MPE one. Keys get brighter with pressure, each note at its own level.

No serialization change: projects go both ways between 3.20, 3.21 and 3.22.

→ Download: HapaxOS update | Squarp instruments

@RadekPilich, this should answer your three points earlier (MPE keyboard in STEP, TIMBRE and PITCH still there, pressure in LIVE). Let us know!

Big thanks to all of you for your patience

Have fun

Benoit

45

we really need a misc. menu option to turn off this new behaviour where a double stop message restarts the song position.

Bit of a nightmare trying to edit sections while synced with Ableton because 1 pause on Ableton = a double stop on Hapax with CV Run enabled when using CV as the clock source (even in perform mode).

The other option is to turn off CV Run and have my synths hang every time i pause Ableton and have to triple stop on Hapax to kill the midi each time :pleading_face:

46

Yes!

This is horrible, it even does it when not in song mode.

47

Still doesn’t quite work with the Prophet 10 which supposedly does have polyphonic aftertouch. At this point I assume it’s the synth and not the Hapax but I don’t have any other PolyAT synths to test it out. No matter, it’s not a dealbreaker feature for me anyway.

48
49

As it said in that search, it can receive poly after touch via MIDI.

50

I was able to get it to work; I wasn’t allowing aftertouch into the Prophet via my MIDI patchbay. Works great!

51

@squarpadmin

Noticed that the 3.22 changelog entry removed from HapaxOS update | Squarp instruments

Bin is still there: https://squarp.net/hapaxOS/3.22/hapax.bin

Accident? Or something wrong with 3.22?

52

Probably wrong merge / revert of website code due to the release of Core website.

53

good catch thanks ! It’s back to normal.

54

On the Pyramid this was called “Consolidate Track” iirc. and used it all the time and was deeply missed when I start using the Hapax instead. It’s beyond me why Squarp omitted this feature… My solution was to record the particular track from it’s midi output X to midi input Y (with a fysical midi cable) in project B and copy-paste the track back to project A. Not sure if project B is necessary though… HTH

55

Yeah, that was a great feature. One of the things I didn’t expect to still not have on the Hapax this many years down the road.

57

did anyone ask squarp about the feature? i wonder what they say

58

This new update has fixed Pressure for me with Bitwig. Previously I was trying to set individual pressure values to notes and it wasn’t working. Now it does and it’s sweeeeeet!

59

@MADVILLA @Grimbert from what I see, it’s not really a double STOP: any STOP coming from outside (CV Run going low, or a MIDI Stop) sends the song back to its first section, on purpose, so the Hapax and the DAW start again from the same place. So a single pause in Ableton is enough to trigger it.

What about trying the following ?
CV RUN off and set CLOCK TIMEOUT on (Sync In menu). When Ableton stops, the clock stops, and after a few missing pulses the Hapax does a simple STOP: notes are cut, but the song position isn’t reset.

Benoit

60

@squarpadmin

I don’t use a DAW connected to my Hapax. I run it standalone without CV, only MIDI.

What happens is I play a pattern, if I then press stop once, it stops like it should. If I then press stop again (I do this because one synth sometimes has hanging notes) it goes back to the pattern that is first in the song mode list. This happens while in perform mode. If there is nothing in song mode this does not happen. If I don’t press play and just press stop twice it does not go the first pattern.

So in short:

  • Have a song, but use perform mode to switch things up live.
  • Then play a pattern, anything but the first pattern.
  • Press stop twice, it goes back to the first pattern and not stay in the pattern that was playing.

I would think this behaviour is normal when in song mode, but it also does this in perform mode.

I hope this makes any sense.

--edit–

I made a video showing what I mean: https://drive.google.com/file/d/16CAtoIRwMPuT1iOn-Fx5zGtRnozR7KfK/view?usp=sharing