I couldn’t find any topic or announcement on this, but apparently HapaxOS V1.12 RC2 is available from https://beta.squarp.net/hapax/firmware/ since a couple of days back.
5 Likes
That’s a very nice list of improvements. And holy crap, when they promised improvements regarding load times of instrument defs and projects they weren’t joking.
4 Likes
Have been testing it for a few days and it fixes a lot of issues for me!
The main thing: I was having hanging notes on synths connected to the USB Host port, especially when playing chords. This seems to be fixed!
It also adds a sidechain function to the envelope, although this is not mentioned by the release notes. This was something I requested a while ago. Now I hope they will allow for other midi channels/tracks for the envelope destination! 
4 Likes
Just installed it… wow project loads are so much faster! Love that!
- NEW+ project now shows ‘BLANK - DEFAULT - CANCEL’
I’m not seeing “DEFAULT” as an option here, but I like the concept. I have a template project with all my instrument defs so it would be nice to be able to set this as the default.
Would also be awesome to have the option for Hapax to just load whatever project was loaded when it was last shut down…
3 Likes
Maybe You need to save a project as “default” at first? 
Haha, I’m not surprised y’all found it on your own!
We sent it to a couple of people who reported some issues to get their feedback, but we meant to announce it this week for all to try out.
Please bear in mind this is a beta version, so there’s still a couple of things to iron out.
6 Likes
Absolutely. Is it in your interest to file bug reports against it?
[that question isn’t necessary anymore after an edit in the post above ]
Of course, that’s what it’s for !
Haven’t seen that as an option at the Save or Save As screens. Am I missing something? The manual doesn’t mention anything about this.
Do you mean just name it “default”??
edit: ok I named it default and that worked!
4 Likes
”Speak friend and enter”
1 Like
Yep, my hint wasn’t exactly detailed. 
I’m glad you found out anyway. 
It’s cool that FILL is now a modulation source, but it would be even COOLER imo if FILL was a destination! 
4 Likes
Aha, sorry for stealing the show
I figured since it was public, you were fine with it being shared. Hopefully you’ll get bug reports a bit sooner this way.
That was my first thought, exactly. With fill as destination, you would be able to trigger it from litterally anything. 
1 Like
About half of my definition files show errors when I run this firmware. They work fine on V1.11. Is anyone else having issues?
Absolutely! Thank you!
Me too, I have 3 different syntax error messages.
Unlike before, 1.12RC2 seems to enforce syntax checking in the [PC] section. Or rather, doesn’t fail silently anymore. All my error messages came from PCs >127.
@polynil RC2 was mistakenly validating (0-127) instead of (1-128) for PC.
That will be fixed next revision. 1.11 was correct, 1.12RC2 is not.
FYI, @c.furrow 's issue had to do with non compliant syntax, which worked in 1.11, but not in 1.12.
This will NOT be fixed as non compliant syntax will not be supported, and should be fixed to improve future compatibility.
Here are a few offenders, and the corrected lines:
# CC
# Syntax: CC_NUMBER NAME or CC_NUMBER:DEFAULT=xx NAME
# DEFAULT_VALUE must be a valid number between 0 and 127
[CC]
14 CHANCE # this is compliant
14:CHANCE # this is not
106:0 FltrMode # this works and defines a default value of 0 as well as a name
107:BP OnOff # this does not work, ':' should be followed by a number for default value
107 BP OnOff # this works
[/CC]
I’ll take a look in the Instrument Definition category and look for non compliant syntax which should be fixed.
4 Likes