I’m wondering if there is a way to save or extract an instrument definition file from the Hapax without creating one myself beforehand. When I set up a track with all the ins and outs and go to the instrument def portion of the track menu I am only able to load a file and not save a new one. Is there a default template that I can load on the SD; edit on Hapax; and then be able to save? Any assistance would be greatly appreciated.
1 Like
To my knowledge, no, you have to do it through a text editor, but you can base it on the template file or an already completed file.
I put in a feature request for this and the response was that this was not possible. It might be possible to decode project files and generate instrument definitions from the tracks, which would be just as good. I’d actually use that for existing instrument definitions to add automation lanes.
1 Like
As far as decoding project files, how would this work? Would this be a feature within Hapax, a text file with all the project data, a program on your PC to extract/decode project files? Would this seperate out MIDI data, effects data, automation data, tracks, etc? Interesting prospects.
Is there a blank template located anywhere for an instrument definition?
I’d like to start on definitions for my monologue and drumlogue but I don’t want to start from scratch.
In the manual under the Instrument Def section there are links to a blank template as well as some already created. I referenced them and was able to create some default style templates that set the inputs and outputs as well as track type (poly, drum) Worked out very well and was quicker to set up many templates on the computer vs the Hapax.
1 Like
It would be wonderful if this information was mentioned anywhere in the manual, or online somewhere not buried in a forum that users have to search through in order to find out. It would’ve saved me a half hour trying to do it on the device, scouring the manual, watching youtube videos trying to decipher it. One sentence in the manual: “You cannot export instrument definitions” and I wouldn’t be digging through a year and a half’s worth of threads on a forum.
1 Like
can also create
4 Likes
BTW I wanted to say thanks for that - I was using it yesterday and it’s a really nifty tool! I’ve been catching myself mapping devices on the Hapax but stopping myself and using that instead; unless there’s a better way to store the mappings on the device I haven’t found yet.
1 Like
THanks! I “vibe coded” most of it over a weekend. If you have any ideas on improving the tool let me know!
1 Like
I just spent 30 minutes trying to figure out how to do this because of course you should be able to, right? You spend all of that time with the encoders setting up a drum kit mapped to specific external ports and channels, of course you would be able to save that instrument definition right there and reuse it in other projects.
This is about the millionth example of how Squarp design like engineers, not musicians. This design language infects everything they do. And yet I keep buying their devices.
Someone programmed a web app that lets you browse insturments (midi.guide) and extract/create definitions and you can create custom devices where you can extract/download harpax instrument d efinitions: https://studiograph.vercel.app/