This version brings new features, important bug fixes, performance optimizations, and we’d love your help testing it out.
This is an open beta, you can jump in right now!
Just head over to this alternate beta website to download the update. The updated online manual is also available there.
Send all feedback to beta@squarp.net
We’re not accepting feature requests at this stage, but we welcome bug reports, small suggestions and general feedback.
For all bugs, please provide a clear step by step procedure to reproduce it, so that we can fix it more easily.
Older firmware versions won’t be able to open project created with beta versions: it is recommended to make a backup of your projects before upgrading to this beta.
Thanks for being part of shaping this firmware with us!
– The Squarp instruments Team
It is hard to see the issue on these fotos, but all pads where lit (on the photos they seem unlit, probably due to fast flickering of them), but believe me, all padds are lit, just the top 3 rows show differen colours on step 2 and 10 (pinkish).
On the screensave (pads) all steps 2 and 10, on every row (!) is pinkish.
BTW Squarp by now has kindly confirmed the issue, and they can repoduce it on one of their units.
Importing of midi into drum tracks is not working for me. It is working into a standard poly track.
When it gets to the import track screen it shows 2 CC events, whereas on the poly track version it seems all midi events. (there are 128 events over 8 bars)
Yes, I did read the manual. The notes are a drum pattern in C0, C#0, D0 and D#0 which I think is correct based on my reading of the manual.
“Each .mid file supports up to 128 MIDI note values (0 to 127).
When working with DRUM tracks:
– The first drum lane (e.g., Kick) is assigned to MIDI note 0 (C0, based on Hapax’s note naming convention).
– The last lane (e.g., Cowbell) is assigned to MIDI note 7.
– Notes beyond MIDI note 7 are ignored when importing a drum pattern into a DRUM track.”
The pattern is 8 bars long.
When I go through the screen where you select the MIDI track it says:
“Do you want to import 2 CC events, 8 bars long”
In other words, it is not seeing the note events.
When import the same file into a Poly track it says
“Do you want to import 128 note and 2 CC events, 8 bars long” and then it works.
The file was created using Logic. I’d provide the file but don’t see away to do so?
Figured it out. The Hapax needs the MIDI notes to be C-2, C#-2, D-2, etc. Then it works.
As a side note, would be awesome if it could match the settings in the drum track. So when it exports it will export the note number of the track and when it imports it would match the note in the imported file to the track and load it there. Appreciate this might be too much to ask.
My drum patterns are all setup using the standard MIDI drum map, Kick on 36, Snare on 38, etc. That way it works in an DAW as well as with many of my drum
Machines which use the same mapping. I have my Hapax setup the same way.
But anyway, got it working and now just need to transpose my files.
This is an open beta, you can jump in right now!
Send all feedback to beta@squarp.net
For all bugs, please provide a clear step by step procedure to reproduce it, so that we can fix it more easily.
Older firmware versions won’t be able to open project created with beta versions: it is recommended to make a backup of your projects before upgrading to this beta.
