I’m looking to buy a Hapax but at the moment just weighing up the pros and cons with a oxi one.
I had a few questions regarding the Hapax, from what I’ve read on the forum having multiple lengths on different lanes isnt possible on the Hapax drum track which is shame is this something that might be addressed in a future update?
Another thing I’m a little confused about is drum notes, let’s say I set up Hapax 8 drum lanes to sequence my 8 drums on my Digitakt. Can I then change the note value per step on a particular lane. I hope I’m been clear it’s hard to explain.
on the Digitakt or oxi for example on a track I would be playing the same sample on each step but I can change the note that sample is played in up and down a keyboard scale. Can the Hapax do that or are you locked into a scale for the whole of that lane.
Not possible currently. I would not be surprised if different length per drum lane will be added in the future. I doubt if they will also add different note value per step. However, I do have high hopes for more drum lanes per drum track in general, which would probably also be an even better solution.
I’m currently between Oxi One and Hapax, as well as a big on Elektrons and having a) variable lengths of a drum lane and/or intervals is fun to play with for polyrhythms, tho more crucial is b) having notes for pitch variations on drum racks
varying notes on drums gives spice but also not every destination is a poured drum hit. Think sequencing a machine that can also play synth voices or samples. Having to open another Track kinda defeats the purpose of using a track for one machine and having it all in one place.
Oxi one just calls their drumtracks “multimode” and it’s exactly that: 8 quasi-independent mono tracks
i recently scooped on a digitakt 2 and I’m experiencing this presently and currently using a drum track for the first 8 dt2 tracks and then hapax poly tracks for dt2 tracks 9-16. note value programming per drum lane would put the hapax on par with the oxi. don’t know if you’d be able to setup automations (or other midi cc routing) per drum lane but that’d also be awesome as well.
It does seem that the drum tracks would really benefit from some updates, I’ve recently purchased a hapax and weighing up if I will return it and try a oxi one, the hapax has some clear benefits over the oxi and then the oxi has some clear wins over the hapax one of those been the multi/drum track.
One thing that I have noticed though is that where the development of the oxi seems to be pushing forward from reading post on this forum what I’ve seem to come across is that there isn’t much memory left inside the hapax to do this or that or that it wouldn’t work because it would be a core change to the os.
I know I’m been negative but maybe the development of the hapax is reaching what they can do with it. That’s not to say it’s not an already great piece of kit.
On this post there was talk of a feature needing a rewrite of the os which was not possible and on another post I read which I’m yet to find there was talk of need to rewrite code to be free up space in memory if it was to be implemented I can’t find that post at the Monent.
im not saying it’s running out of memory I’m just going off what I’ve read from people on here that know far more about it than I do.
I’m also trying out both atm since they’re so similar, yet each of them has some slight benefits on their own — which is totally fine, like the generative modes in the Oxi
There’s just some things that are what I would say “standards” in sequencing now and those are puzzling why Hapax doesn’t use them. One is having the drum tracks also sequence pitch (Elektron does this since forever for example)
As a new (and mostly super stoked) Hapax user, I came to this post on a search for insights toward the lack of CC’s being able to be sent to their respective MIDI channels (that they came into as, and were recorded to the hapax/drum track on with no issue, so this seems a bit inconsistent to me).
I use several pieces of kit that have monophonic tracks that each live on their own MIDI channels, so a “drum” track seems perfect, except that drum track automation is not very useful at all when used on multichannel drum machines. Maybe I can set up macros to relay control to parameters on each devices tracks, but that seems a bit of a step backwards to me. For automation, the instrument definitions are a game changer in immediacy and practicality. Automation > macro > parameter not the same.
The solution I’m leaning towards I guess, unless I am missing something, is to take advantage of the dual project architecture and spread the monophonic and/or drum parts that I want to be able to automate from the Hapax onto their own tracks…? Not quite what I had in mind…
Fingers crossed there is a clever solution for this in the works.
Miracles could happxen. Drum transpose did automagically appear after all Fingers crossed.
I switched to using poly tracks for all 16 tracks on the DT2. I’ve been running both projects on the Hapax at the same time so I can use 32 tracks in total. If you’re still looking to use a drum track for the DT2 it works by setting the notes to 0-7 methinks. I’ll attach a link when I find it but it’s still a little funky and I like being able to have control over each tracks mutes in the mix/mute screen so that’s why I switched.
From elektron forum: “Yes you can do this. Look at section 8.4 of the Digitakt manual. Sending the Digitakt the lowest 8 MIDI notes will trigger the sound of tracks 1-8, and they will not be played chromatically” It’s referencing the DT1 manual but it worked for me on the DT2
using a drum track for the first 8 dt2 tracks and then hapax poly tracks for dt2 tracks 9-16. note value programming per drum lane would put the hapax on par with the oxi. don’t know if you’d be able to setup automations (or other midi cc routing) per drum lane but that’d also be awesome as well.
Fingers crossed.