How does quantizing work on the Hapax I’m confused

It is in the works.

14 Likes

Glad to hear this @Thibault_Squarp!

Thank you very much Squarp!

Might not be possible for everyone, but as a workaround, I loop back MIDI from an output to an input.

Use Project B. Turn on live quantize and send the MIDI back to Project A.

If you want stuff on the grid, record it in Project B and loop it back.

This also works to bounce down MIDI FX, have more than 7 FX at a time etc.

You can use a short TRS to TRS cable if use Input B and Output D, very easy.

You can even use a splitter if you need Output D for other uses, or just loop it back using a MIDI router (this is what I do).

Bear in mind, everything adds latency… you might have some latency… there’s ways around that too, like recording to an empty pattern, microtiming the smallest amount left, and then pasting on top of the other pattern.

It’s not perfect. But it’s creative and opens a lot of possibilites.

Maybe one day Hapax will do it natively!

2 Likes

There is a much quicker workaround as outlined in this thread already. Select all notes in step mode and hold the uTime. This is still clunky and your way is beyond clunky lol.

Appreciate the reply, thanks. Of course I realize you can select all notes and reset the uTime.

However, if you dig a little deeper, you’ll realize it’s completely different.

My method allows you to print ANYTHING you want back to the grid. I’ll give you an example… say you want the notes like this:

Quantize 63%
Swing 54%
Accent 47%
Humanize 10%

You can then print that back to a clip, as your new starting point, then adjust/record on top from there.

Not just that, but you can bounce all MIDI-FX down, run that pattern through more MIDI-FX etc.

I’ll say again - the possibilites are endless.

There’s nothing clunky about it - once your cables are connected, all you have to do is change the Input and Channel, hit record, and it works. It takes literally 5 seconds, plus the time it takes to play the pattern through once.

I get why you’re frustrated - the Hapax doesn’t do something you want it to do. Trust me, I have a list of things I wish the Hapax did and I guarantee it’s longer than most people’s lists.

However, instead of moaning about it, why not actually try what I have suggested? It works to solve your problem, and allows you do some absolutely amazing other things.

If you need help/advice setting it up or doing it, I’m happy to help.

I understand what else it can do just fine but for this use case its terrible. And its the most basic thing that I want it to do that EVERY sequencer does. Its not something that is an outlier thing that is obscure. It one of the main things a sequencer does since the 80’s. And I don’t want to print midi FX and if I did I’m sure I could figure out a way. Thanks though lol.

“There’s nothing clunky about it - once your cables are connected, all you have to do is change the Input and Channel, hit record, and it works. It takes literally 5 seconds, plus the time it takes to play the pattern through once. There’s nothing clunky about it - once your cables are connected, all you have to do is change the Input and Channel, hit record, and it works. It takes literally 5 seconds, plus the time it takes to play the pattern through once.”

Bro how is this NOT clunky by having to change cable routing. Are you actually serious? All my ports are taken up too.

@Laser Thanks for the work around and trying to help.

@owensands smh :roll_eyes:

3 Likes

Ok sorry, thanks for trying to help @Laser but respectfully I don’t need/want to use midi loopback methods creatively nor could I as all my ports are all taken. Cool thing you figured out though. I make music with simple fast techniques and I just want simple basic features to work as they should. No use in arguing anymore over it. Squarp already said they are fixing it.

1 Like

No worries, all good!

What I meant though, was you only have to sort the cables once. Then you’re good to go.

All my ports are taken too, I get round that by looping it back in my router. The only hard bit for me was remembering which Input to set it too, I have it a note on my wall now to remind me.

So, once it’s set-up, it’s instant, no clunkiness except for having to listen to the whole pattern record through.

If you find it let me know. I’m pretty sure there isn’t another way though, except wait for Squarp to add it. In the meantime the loopback is a powerful tool, especially if you have FX mapped to controllers, you can play the FX in real-time whilst it records.

I’m not one of those people who say ‘limitations breed creativity’ (not on my gear anyway), I think we should have features and options, as many as possible.

However, I will say this: when you find something you can’t do, you experiment to find a workaround, and often the stuff you learn from that is extremely useful later on.

MIDI loopback is a great tool, it’s not just a workaround, it opens a lot of doors. Not just on Hapax either, you can do crazy shit on the Octatrack by looping it back. In Drambo the dev added loopback to the actual app because so many people requested it.

The thing is, if a device that I use doesn’t do a certain thing, I’m not gonna let that stop me if I can solve it another way.

Little example: no global swing on Hapax (definitely needs it imo). I find a global swing more useful than individual swings. So I built it in Drambo, put a Swing on every track in Hapax, now when I turn a knob it sends 16CCs and all the swings change simultaneously.

By the way, if you don’t use a router and all your ports are taken, there’s a simple way of using jack splitters on the B and D ports. In that case you’d only have to connect one tiny cable, switch one to the other. Doesn’t take a great amount of effort… do you want your music how you want it or not?

It all takes effort as I’m sure you know. The more you put in, the more you’ll get out.

Best of luck!

Bro I cant lol. This is STILL clunky lol. If its an 8 bar pattern at 100 bpms that is 19.2 seconds of playback. For quantizing midi ONLY not printing FX this would be a very cumbersome workaround vs the one we are using now and as you’ve said there could be some slight latency introduced there so it might not even make it on the grid perfectly.

As for other ways to loop back and print midi FX, if you are connected to DAW via usb you can use that connection to loopback too. DAW is an amazing midi router. Yes I am big into hybrid workflow. :slight_smile:

I HATE WHEN PEOPLE SAY THIS. LOL Its like they just hear that crap and parrot it back but have never experienced what its like to be in a studio that is just chock full of POWER. I want tons of options! I never get options paralysis. I get bored if I don’t have tons of options. Hence the reason our ports are all full!

I have it the way I want it now by hitting select all and holding uTime button. It snaps it all to the grid in like 1 second. This is the workaround I am using until they give us a quantization toggle that I can use while banging in stuff live.

I do this too, if I want it completely quantized. I prefer a more natural feel for many parts though, that’s why I don’t mind waiting the 20 secs, often I do something else in that time whilst it bounces.

I’m all about the hybrid workflow too!

Check out a few pics of my setup, and a little bit of info about how it works:

It’s insane… a huge Drambo project (over 4,000 modules) controlling everything on 2 Macs running Ableton, with a load of hardware.

Got a question for you… do you use audio-sync?

I’m running audio-sync from Ableton into my Hapax and to my 2nd Mac. Often after a while (maybe 20 mins or so) I notice it’s not quite synced perfectly. Trying to solve this issue and find out if it’s fixable etc…

1 Like

Holy controllers batman.
Would love to hear the music you make on that.

No I don’t use audio synch I use usb clock actually from bitwig. I clock most everything separately(with offsets etc) from bitwig including the hapax. It’s remarkably stable. I tried audio clock too but it wasn’t any better. Bitwig has nice CV features so it was easy to try it.

Here is my setup:

I see you have the P6 sampler. I did some videos with it on YT.

And my music/YT channel can be found here:

1 Like

Hapax isn’t every sequencer though… it’s the sequencer that eventually the others will be judged by and for that it takes a LONG roadmap. They are getting to your concern… trust.

1 Like

Lovely clean and bright setup, nice!

Sweet production on those tracks too, some great sounds going on there!

It gets pretty crazy! Often messy too :smiley:

I haven’t recorded a single thing yet though, with this setup anyway. Been all about building it and learning to use it… there’s a lot of insane stuff going on.

I’ll get to doing some videos at some point. It’s the kind of thing you really need to see happening as well as hearing it.

this workaround is good enough for me. Not perfect but a great tip!

I’d love to see a destructive Quantize Algo.
Also, I’m frustrated by the fact that the quantize setting is apply Globally to a track. It should be bound to Patterns, not to Tracks in my opinion.

The current quantize function can be set globally or per track. If you only want it per track, turn it off in the project settings and enable it in the 2nd track settings.

Also, a quantize Algo would be very usefull, but I’d love an Input quantize feature as well, so you don’t need to perform another action to quantize after you record something.

1 Like

I meant (and wrote) per pattern, not per track.

Ah, my bad. I think it makes sense per track tbh.

2 Likes