Joined in 2023 
82 
63 About this deal
the firmware should have a 'double hit avoidance' option that tries to sense 'likely double hits' and ignores the subsequent second note. users could choose if they want this 'filter' on or off. Baphometrix wroteEven after the 1.15 firmware update, I'm convinced that the design of the ATOM SQ pad triggering is flawed at a fundamental level. No matter which Velocity sensitivity I choose, it's still VERY easy to get double-trigger Note On/Off events if you hit anywhere near the CENTER of any pad. This is especially easy to reproduce today with firmware 1.15 in exactly the same way as I demonstrated over and over to Presonus in the early launch days of the SQ. after a 6 week wait to get my SQ and then having to hit the pads hard (even with soft velocity) and get so many skips is disappointing. I have an older Korg PadKontrol which sounds fine, and an Akai MPD232 which sounds fine, Even if PreSonus knew they were using low quality pad triggers, the fact that they won't even help us out with a (selectable) Double Trigger sensitivity filter (in Setup), means they have a complete disregard for real (paying) end users.
Editor – As you might expect with a name like Editor, this mode allows you to edit your work right from the MIDI controller. Of course, you need to be using Studio One or Ableton to utilize this mode correctly, but it really helps to simplify the process. Instead of having to use a mouse or keyboard, you can cut out the middleman and use the ATOM SQ for all your editing needs. The ATOM SQ is built so that you can use it right out of the box. It is designed to be used with either PreSonus Studio One software or Ableton Live. Both of these are wonderful systems, with Studio One being a bit easier to navigate using the ATOM SQ since they were made by the same company. Studio One I think all of us are well meaning and gave PreSonus a fair shot to do something to help, and they just don't care. More features -- no -- how 'bout getting these things not to double trigger (with a setup mode option to ignore the finger release double taps). These pads all have some bounce -- and musician's like bounce dynamics. We are being penalized here by not having our hands / fingers magically disappear after the first push down on the pads. In the real world, it takes time for our fingers to get off the pads. The world would be a sad place musically if our fingers aren't allowed to bounce a bit. That's why these Atoms are not playable. It seems like the physics of these pads was designed by someone who never bothered to listen to the results. But what this workaround is doing is preventing the ultra-light movements from your finger lingering/resting on the pad after a hit from being registered as a new Note ON gate. And some of us might tend to do a micro-bounce or micro-wiggle when we lift our finger OFF a pad, which can also trigger double-hits from ultra-low new velocity values.
PreSonus ATOM SQ Features:
I have shelves of hardware and controllers (many of them pad controllers) just waiting for improvements (manufacturer promises) that never came. always 'need to get' MK2, MK3, on and on. I've tested the Atom SQ in numerous DAWs and SO5 and when there is a DAW option for a Midi Velocity Filter (as noted in this thread) to filter out MIDI velocity below 4 (out of 128) it gets rid of most of the multi-triggers.
Atop the touch strip are eight encoders, all of which feel chunky and robust, and have just the right amount of resistance so that they feel good under the fingers. When the unit is initially connected to Studio One or Live, these encoders will be preconfigured for common functions But they are otherwise freely assignable.If i do NOTE FX as described at 4% in the quote, having set Velocity to SOFT in SETUP and if i try to write a song, the harder to press pads and sometimes all of them no longer register properly the notes that would normally be triggered when the system considered registering at 3.9% !
Appearance is really an important factor when choosing a MIDI. They make up the Gui of the controllers and even have a massive impact on the workflow that the unit provides. Let us have a look on the appearences of both atom and atom sq. Commonly for both users, it requires 32GB of HDD space, USB-C or USB A-2.0 port compatibility & Studio one 4.1 for native integration. While talking about Atom SQ, its requirements are mostly the same as above but there are some changes i.e For both Windows and macOS users, it requires a USB-2.0 port, 20 GB of HDD space & obviously Studio One for native integration.It may work however in HUI or MCU modes in V4 but with less integration. Although the native SQ driver does not even show up in V4.
Great Deal 
New Comment