I am considering a Hapax sequencer as I’m genuinely sick and tired of midi issues with my PC & DAW. I’m a drum and bass & broken beat producer from the 90’s so need the Hapax to control the following;
Akai S6000
Akai CD3000XL
Roland XV5080
Korg Triton
Ensoniq MR
Novation: Drumstation-AStation & Super Basstation
Clavia Nord Lead & Nord Lead 3
Waldorf Pulse
Studio Electronics ATC1
Sherman Filterbank
And if it could do all that and even control my DAW that would be a God send!
Could anyone shed some light on how well the Hapax works with 90’s samplers & romplers? Also, what are the pros & cons of controlling your DAW with the Hapax?
I’m a newbie with these types of sequencers but my goal is to get back to having the same kind of fun I was having with my old Atari Ste & a couple of samplers without latency, jitter, updates, crashes, poor drivers, getting in the way.
i sequence my “new” MPC One with Hapax and it should work basically the same for an old school Akai as I understand it. You just get Hapax sending MIDI on a given track/channel out and program the Akai to receive on the same channel IN. the new MPCs are great because each track in there can have a unique MIDI channel so, depending on how you configure Hapax (esp. now with the virtual cables, which i haven’t tried yet) you have at least 16 discrete drum programs/plugins/keygroups to run from Hapax. I don’t know exactly how the old Akai samplers allocated MIDI across different sample programs/projects but my understanding, for example, is when slicing up breaks each slice can be assigned its own MIDI note value, which really should be all you need to get some hectic jungle bizness going with a chopped beat.
with the gear you listed, that looks like a minimum of 10 Hapax tracks but would probably want to dedicate multiple MIDI channels to the Akais or the polysynths if they’re multitimbral. someone more experienced with the new virtual cables function would have a better idea how that might impact the final routing though
i use usb midi from hapax to DAW and route from there to my hardware midi interface which has many 5 pin din plugs. then i just hook those cables to hardware as i would have if i was only using a DAW to sequence. some like to buy a midi router that directly converts usb from hapax into many 5 pin din busses. usb from hapax now has 16 midi busses, each containing 16 midi channels so you can hook up a lot of gear over that single usb cable! and with the bandwidth available on usb from hapax theres no danger of overloading with too many midi commands. but if you can stand it, i would recommend using your DAW as the extremely capable router that they are these days.
the only ‘drawback’ i can see to controlling your DAW with hapax is setting up sync between them which has some people pulling their own hair out. i personally have not had many problems but it was a small challenge to get right the first time i tried it. see the few threads where people complain and then later figure it out. at the moment we are waiting for some convenience fixes from hapax but essentially audio sync works and provides the tightest tempo sync ive ever experienced between hardware and DAW. i dont recommend using midi clock to send sync from DAW to hapax honestly.
hapax by its self is the most advanced hardware midi sequencer that is still a pleasure to use in my honest opinion. the learning curve and visual feedback and elegant layout creates a much less stressful experience than any competitor honestly. stick with it until you get it, its very worth the result.
if you are using a pc running windows, they need help usually to optimize performance. mac not so much. if pc, check this thread out:
i understand optimizing a pc tends to be a lot of steps for a music focused user. i dont relish these steps either, but once you have a handle on them, windows computers become a much nicer environment to create music in. and of course if you have a monster machine these optimizations become less important.
im seriously considering a mac mini m4 these days i must say however! but i do love making a windows machine work well, AFTER the process is over lol!
if the DAW is Logic Pro, as far as I know, Hapax will have to receive sync from Logic and cannot be the clock itself (Apple apparently disabled Logic from receiving external sync several versions ago)
i would not sync a daw to hapax. thats never going to work well in my opinion. audio (cv pulse) sync from any daw to hapax has never failed to produce a very tight sync as i mentioned above.
when the op says ‘control’ a DAW i assume he meant control parameters of the DAW and to send midi note and controller commands to plugin synths and fx etc. which hapax does very well and presumably could be done using logic just as well.
also since latency is a thing when sending midi to software, hapax allows the user to introduce millisecond compensation before and after the tempo clock manually so you can line everything up extemely precisely. sync offset compensation can also be adjusted to midi clock sent from hapax intended to tempo sync other hardware sequencers like mpc or other standalone sequencers. it works super well with my mpc 1000 or polyend tracker but should work with anything.
In terms of controlling the Akais with the Hapax, I initially need to be able to run 16 midi channels on each sampler and also be able to trigger 128 keys separately. So similar to how we would have used the Atari 520 ste with early version of Cubase. Nothing fancy at first but we also did a lot of manipulation with CC data that would control different elements of the hardware (filters, fx sends, envelopes, lfo’s, modulation depth, etc..) and ideally I would have access to this with the Hapax.
All of this is available in the modern DAW of course but tight, acceptable timing is not and that’s what has me seeking out something like the Hapax because the latency/poor timing is driving me bonkers.
The flipside is, if the Hapax does what some have mentioned here, and what I think it is capable of, it means that alongside controlling my old hardware I can also control VSTi’s in the DAW and have tight timing that plays nice with the hardware, which would be a dream come true tbh.
personally have not noticed loose timing on much new midi hardware but your mileage may vary. the kvr thread i linked above has a lot to do with that imo. your choice. (ignore the amd steps if you dont have amd cpu) hapax is imperfect cc heaven also imo. theres not many gripes with hapax from me. good luck!
With this setup, you can run everything from the Hapax easily. The main adjustment is getting used to the sequencer workflow. Want records a snare fill at the end of the 8th bar in real time? Easy peasy on an Atari or a DAW with a linear sequencing. On the Hapax it takes a few button presses and some muscle memory with locators. That’s just one example — there are plenty of situations where you’ll sort of be re-learning.That said, it’s an excellent sequencer and extremely well featured. It’s rock-solid, super tight, and of course you want to be syncing from the Daw using a CV clock plugin/
I suspect owners who lean toward generative/ambient music would gel with it faster than people making structured tracks. I make 4/4 techno and don’t use the plugin FX much yet because its just a bit to random, but I know that will change once I get to know the sequencer really well. Its easy to lay down some parts quickly and get things going but to be able to utilise it better it will require some time to learn. I have a long way to go yet.
PS
I have it synced via an Ableton CV Clock plugin.
The timing is excellent
Its actually not that bad via my Daws midi clock.(but use the CV if you can)
Every midi track/channel has a delay feature. Very handy if you need to shift something back or forward. for example my Roland TR1000 literally has built in latency so even just sending midi notes to it I have to delay those tracks or channels.