Instrument Definition Form Tool

Hapax
1

I’ve been messing around with the HAPAX for a few weeks. I made an instrument definition form tool.

Not sure entirely sure how helpful this is yet because I’m still new to the HAPAX. Happy to add your instrument definitions and/or add more features. I need to add my own definitions soon.

17 Likes
Hapax Instrument Definition Tool (s)
2

Looks pretty clean :pinched_fingers: I’ll have to upload some of the defs I have but thanks for taking the time to put this together.

2 Likes
Hapax Definition file manager
3

This looks great I am a new user so still getting my head around Hapax but once I get a better understanding of the parameters I will use this tool to try to set up some definitions

Thanks for making it

1 Like
4

Good job!
I made one too (which I haven’t yet submitted to the community) but I think yours is really cleaner and safer

1 Like
5

Thank you very much for your work! This will help a lot!

1 Like
6

This is great @pxxp :slight_smile: I’m running 20+ triggers and 50+ cv lanes from hapax into eurorack via fh-2 and friends, and was going crazy trying to remember what each automation lane (cc12, cc13, cc14…) was actually doing. I didn’t dare to create the txt files by hand, since I suffer from “code-fright”, but since I found this tool I was able to configure and rename everything. Now it all just makes sense. Thanks dearly for this!

2 Likes
7

Thanks! I need to spend some time to update this with all the form definitions folks have added over the year.

8

That looks great! Will try this the next time I make a new definition.

Thank you for creating and sharing this!

9

Hi, what is the version number for? In the instrument definition.

10

It’s probably used internally by Squarp. If Squarp ever wanted to change the format/schema of instrument definitions it would be difficult if they didn’t know what version the instrument definition was created against i.e. if they released version 2 of instrument definitions with new capabilities.

So, the version probably helps the instrument definitions be backwards/forwards compatible if Squarp ever decided to change the instrument definition format. They would just look at the version number and deserialize it based on the schema.