With the release of Hapax, is Pyramid still supported/updated?

please don’t issue personal attacks… this is a discussion forum, we all have the right to express our opinions and perspectives, as long as its done politely and without prejudice.

you are welcome to disagree with my (and others) comments, and to have a discussion around them if you wish (or not, and you can also ignore) - but personal attacks (against any other user) are strictly against the ToC of this forum.


@pyra , It’s a pity you started an otherwise detailed and well-explained post with a personal attack against one of our most helpful contributors. I hope you recognize that you only made people less receptive to your points by being so rude.

1 Like

I edited my post accordingly, but I do not find this contributor’s posts helpful; I find them to be dismissive. It frustrates me to no avail that anytime someone raises a concern about the product on these forums, there are people who rush in to defend Squarp. Like I’ve posted questions about how certain things work, and instead of answering those questions, people tell me why it’s not Squarp’s fault that those things don’t work and how we should give them a break because they are a small company. If people don’t have an answer for the question then they should just not post an answer. Telling users that it’s their fault for not doing enough research before they purchased the product or that they should lower their expectations is in no way helpful.

Fair advice. My point though is that Squarp basically advertises that the gear works one way when in fact it works another. That’s a problem, and I think it’s reasonable for users to be upset when they then abandon support for that product (which they are still selling new on their website.)

I think when many of us see statements like “I don’t like thing!” we read it as a question: “Why does thing work this way?”

In that light, we do not see this sort of response as “rushing to defend Squarp”, but rather as explaining why a thing is happening the way it is. Some of us find that helpful.

But the sense I’m getting from you (please correct me if I’m wrong) is that you don’t care about explanations or whys. You just want it to work different.

That’s certainly a very valid point of view! The only problem is this isn’t really the place for it. None of us here can change the way something works. But we know the boxes really well, so we can usually explain what’s going on. As a result, this is a totally “explanations and whys” kind of place.

The only people who actually have the power to change the way something works (namely Squarp employees) may occasionally poke in, but are not monitoring every post. The best place to get direct support or to advocate for a change to firmware is where it will be guaranteed to be seen by the people who can do something about it. That’s the contact form.

If you’ve reached out via the contact form and were not satisfied with the response, then again you have two options: force yourself to use gear you have an ever-growing resentment for, or sell it and move on. I’ve personally found the latter to be best for my mental health.

I understand your take, here. But I have to be honest, I read the manual a bunch before getting my Pyramid and never came away from it expecting multimode and the looper to interact the way you describe. So when you come in saying “many of the currently existing features work in unexpected ways” I kind of have to say “Hmm. No. I don’t agree.”

If, on the other hand, you simply said “This would work so much better for me if looping and muti behaved like… Would that be useful to anyone else?” I think you’d get a lot of support. Then you’re not asking people to think they way you do (because none of us really think the same) but instead are asking them to imagine new uses for gear. Which let’s be honest, we’re all here for.

Anyway, just some more unsolicited tips that have improved my forum interactions over the years. And a reminder that, even if everyone agrees and you have 1,000 hearts on a post proposing the best squencer feature ever, that doesn’t mean Squarp will see it. The contact form is your friend.


I have to say, your description of this forum really runs counter to my own experiences of it. I have asked the community multiple times for help understanding why something was not working, and I have never gotten a response that was even remotely helpful. For instance,


Even when you ask a question about Pyramid, people often respond with answers about Hapax. For instance:

Right now, as I am posting this response, only 1 of the 14 threads updated in the last two days was about Pyramid, and that was this thread right here asking if Pyramid is still supported with the release of Hapax. I think it’s very telling that this thread has so many responses, and the rare threads where people are asking for “explanations and whys” have so few responses.

From a Pyramid-user point of view, I have found this space to be like shouting questions into an empty field. There is just no one around and the people who are around want to talk about something else (Hapax) or they do not want to spend time helping others learn how to use the device.

Because of that, I think it is a really valid question to ask whether or not, with the release of Hapax, Pyramid is still supported. I felt seen when 909_State posted their question, and conversely, I felt very alienated and turned off by the responses they received for asking that question. The very first comment is super dismissive, suggesting that they should not have used the phrase “abandon-ware” and then literally changing the title for them to make it less “confrontational”. Then, there is another individual who felt the need to lecture them on the fact that “No one should ever buy any product (of any sort from any company) unless they’re happy with what it is at the time of purchase at the price asked.”

All of this feels really dismissive and judgemental. I found those responses much more frustrating than the fact that Pyramid doesn’t do exactly what I want it to do. It kind of made me not want to come back here.

The point of my post was not to say, “hey, I just want this thing to work differently”; it was to say, “hey, some of you might want to reconsider how you responded to the original poster’s question.” The documentation for Pyramid is organized more like a quick-start guide than a comprehensive reference manual, and this forum is pretty much the only other place on the internet where one can search for answers about how the device works … but everyone on this forum is talking about Hapax, not Pyramid. As a result, it is a super valid question to ask if the device is still supported. Rather than censuring the user or lecturing them on what their expectations should have been for the device, maybe just say, “Hey, I hear your frustration. I don’t have an answer but you could ask Squarp directly through the contact form” and then move on.

1 Like

as someone who bought their Pyramid a few months before Hapax was announced, there weren’t a ton of active Pyramid threads here even then. i was resurrecting several old topics as i learned my way around the device, which at the end of the day is over five years old now. it does what it does and still works great at performing those tasks. not sure what more a new user can expect from it at this point, but it’s not abandoned by any stretch


Everyone here is just a fellow Pyramid owner. My wish is that Squarp had a regular presence in the Pyramid forum, the way that, say, 1010 Music has a customer support team member visiting and contributing regularly. I enjoy participating in that forum. In that way, I agree that the Pyramid feels neglected.

Because we are just fellow Pyramid users and not Pyramid representatives or customer support volunteers, you pointing out specific threads in which you thought the suggestions were subpar just comes off as you being unappreciative of someone at least trying to be helpful. You and that person are peers, fellow travelers in using this complex and occasionally frustrating device.

Setting that aside, my guess is that the way you’re using the Pyramid is simply a less common use case, so there aren’t a lot of peers who have the knowledge to answer your questions. I will keep reading any questions you post and if I have some relevant knowledge I will share it.


I very much appreciate the overall civility and thoughtfulness of this conversation, and find myself pretty much in agreement with or at least sympathetic understanding of all parties and perspectives Ive read so far.

But lets be honest. Are you saying that, having read the manual online a few times before purchasing your Pyramid, that when you finally acquired one and used it on a project, that everything worked exactly as you had gleaned from the manual?

Because that was definitely not my experience. There was very much a trial and error exploration and sometimes frustrating, often confusing learning curve, wherein I would be looking at the manual while using the device and scratching my head trying to reconcile what the manual was saying with what the device was doing.

I dont begrudge Squarp this - I consider it the tradeoff of their decision to create a relatively succinct, visually appealing and easy to consume reference guide for a pretty advanced device, rather than a detailed tome like the operator manual textbooks that used to come with old workstation synthesizers.

But I definitely had some preconceived ideas about how the device was going to function when i first purchased it that did not align with the realities of its behavior. Like the way the transpose track works, for instance. As well as the specific limitations of the live recording capabilities, as discussed. Or the behaviors around recording in CCs with the trackpad. I mean, does anyone here actually use the trackpad for anything, ever? Did you think you would before you bought your unit? Ok maybe that last one is just me, I dunno. :sweat_smile::wink:

Make no mistake, I have no intention of getting rid of my Pyramid. It does things that are still unmatched by any other hardware sequencer I know of. But I have on many occasions wished their manual was more detailed.


Yes, that is what I’m saying. There might have been some youtube videos in there as well? I don’t quite remember. And I’d had pretty deep experience with many other sequencers before the Pyramid, so I’m sure that helped.

But I thought the manual did a good job of explaining the core concepts of the Pyramid, what it was doing different, and when I sat down with it those concepts were pretty much as I expected (once I figured out what parts of the UI mapped to which concepts. The cheat overlay helped a lot with that).

And yes, I use the trackpad to draw CCs lots. But, you know, different people are different. No reason to think my experience would be like yours, or that our music is similar, or that we need the same things from the Pyramid. If some people can get what they need from it, I’m super happy for them. If others cannot, move on. It’s a golden age of sequencers. Find something you love!


You know - there’s an argument to be made that the pyramid workflow is more of a recommendation than a requirement. Like, if you apply a controllerism ethos to pyramid and don’t mind doing some trippy shit with midi the pyramid can almost be like a blank control surface with some sequencer features that you can use to do anything.

Anyways, lol, i just had that deep thought and wanted to share it with you while i was reading your thing. Like - sure the pyramid maybe suggests some workflows and yet, the pyramid could kinda do anything you want even without additional development from the squarpies assuming you’re weird enough to get a bomebox or an arduino.

Btw, i’m totally not disagreeing - like i always say, i totally have my want list from squarp. I just needed to share like this adhd deep thought where my mind started expanding.


I wish I could say that. There were things I didn’t understand at all after reading the manual a few times. And I went to the beach shortly after getting my Pyramid, a beach vacation w/o wifi so I took a copy of the PDF version of the manual. I wasted at least an hour trying to trial-and-error my way through something that wasn’t working before giving up and tethering my laptop to my phone to check the web version of the manual. My problem was caused by the PDF manual incorrectly having “is” where the web version correctly had “isn’t”. I stick to the web version now.

I do not.

I did.

1 Like

FWIW, Squarp is great. I doubt they’ll drop Pyramid support, but they are a small team.

I also read the Pyramid manual a few times before purchase and it worked as expected if not better.

I also did not like the trackpad so I turned it off. It’s pretty dry where I live so the trackpad is a bit flaky.

1 Like

I like my Pyramid, but for me that trackpad is a waste of space, should have been used for a larger screen! The manual is complex but works for me when I use it.
FYI: I have my Pyramid synched to a NDLR sequencer, and it’s env/clock out to a eurorack Stochastic Instruments regenerative sequencer, as well as to a Mutable Instr Yarns (MIDI to x4 CV convertor) - all this controls multiple analogue midi synths + euro rack modules - its fun writing songs with Pyramid!

1 Like

yeah, I have to admit, I rarely (almost never!) use the trackpad. (*)

don’t get me wrong , I think conceptually it was a nice idea… (include a modulation source), but for some reason, just doesn’t seem to work out for me.

I think largely for me, the issue is I dont really use the Pyramid as a playing surface … I have a dedicated controller for that… so, for the same reason, I rarely map the pyramid encoders to anything either.

then again… these days, I find the pyramid can be fun for a small eurorack setup.
and in that scenario, perhaps I should map the trackpad and encoders, as I never can have too many input sources there!

(*) that said, I don’t think theres a direct design choice between screen and a track pad … space is not the only concern on product design… a larger screen would have been more expensive, and also draw alot more power (from an already ‘pushed’ USB power source) …
I’d suspect the trackpad as an ‘easy add’ low cost addition :wink:

interesting side note, which is kind of related… the early pyramids also had a gyro, which was dropped pretty early on… but again, a bit odd for sequencer, but was probably just on the MCU so Squarp thought ‘why not’

1 Like

Imagine instead of the track pad there was 8 knobs.

who knows what a Pyramid 2 would use as a form factor… (if it ever was created!)
(and its not as if we are going to retro-fit the current pyramid :wink: )

the hapax has more encoders, more screen real estate … and no track pad, so I guess thats a good pointer…as for sure, Squarp have learnt a lot of lessons from the Pyramid (and Hermod!), that have influenced the Hapax.

anyways, as for the pyramid…
fortunately, its easy enough to connect a midi controller (with as many knobs as you want ;)), and use these either for CC, or to midi learn fx parameters.

so, the Pyramid doesn’t really have an issue in that area.
(in some ways, pyramidi gives it a bit more ‘external control’ that the hapax)


This is a way too technical reply to a comment that started with the word “Imagine” but whatever :roll_eyes:

I think I used the trackpad twice for CCs, but did use it for automation curves a bit, was nice for that. As for the encoders, never ever used them for CCs. I find endless rotation knobs are a nightmare for controlling parameters live (the Nord G2 is a very notable exception, although they have visual feedback with LED rings and no acceleration, which I think helps massively)

Just buy a cheap MIDI controller with loads of knobs on it, and use those. I know it’s an ‘extra’ thing, but it works well.


idk, i mean i almost never use the track pad but when i do it’s super helpful. like say i want a filter to crescendo, i just open that up and draw it in. for me its harder to do x/y programming with knobs.

1 Like