my recommendation is for Presonus to add a choice / algortithm that is smart enough to ignore immediate (subsequent) pad note registers after the first note - if the 'second pad hit' occurs like 1/64 (or less) time then the orig hit.

So is there a "workaround" for this design flaw? Yes. Is it a good workaround? Personally, I don't think so. It's awkward when you need to hit pads in both the top and bottom row. Invariably, trying to hit a top/bottom edge works for some fingers in one of the rows, but not for other fingers that need to hit in the other row. This is because my "aim" is better if I try for the TOP edge of pads in the top row, but instead aim for the BOTTOM edge of pads in the bottom row. But this requires a finger that needs to hit a note in the top row and then move down to the next hit in the bottom row (or vice-versa) to travel much farther than feels natural, which is slower and requires a very curved hand position with lots of finger curling and uncurling. A particular issue with the SQ is that its piano-like layout encourages you to use it as a melodic controller and to play chords and melodies on it, right? It's very different from the original ATOM which is clearly a drum-centric controller layout and you tend to finger-drum in a VERY different way that you play a keyboard, right? In Ableton Live, those encoders suffer from not having any tie to the readout of the Instrument Mode (as in Studio One 5). Here, you literally have to turn a knob and visually eyeball your screen to see what you’re affecting. I have no doubt (or am extremely hopeful) that PreSonus is working on letting users view Live’s parameters within standalone controller view of User Mode. also, I'm not sure there is a way to control 'velocity' (soft / medium / hard) when SQ is used with other DAWs. I think that choice should / could be moved to the Setup Menu (circular button) since other DAWs current don't get the velocity adjustment choice (in the LCD menu).

Atom, the bomb?

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% !

Transport controls allow you to play, stop and record, and enable the metronome via the Atom SQ. Additional functions can be accessed via the Shift and the transport buttons. The menu screen starts in Song mode and displays the transport section along with several options: current tempo; loop selection (you have to set a selection on screen first); zoom loop (to show only the loop you’re working with on the timeline); add markers; scroll from marker to marker; and enable input quantise.

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.

Basically the only way to play in this case is to also set fixed velocity at 80% for example from inspector. That way at least you know that you need to press harder to pass the 4% minimum velocity set by NOTE FX and you will always register ~80% velocity (or whatever you chose) no matter what.When I play in S1 or Live 10, I'm getting tons of double notes - as if the aftertouch itself acts as a note trigger Capture the beat whenever and wherever creativity strikes with PreSonus®' ATOM. An intuitive, musical, MIDI pad controller, ATOM's dynamic, ultra-sensitive pads will give you all the expression you need, whether you're making a beat, creating a driving synth line, or triggering sound effects and loops on the fly. Tight integration with both Studio One® and Ableton® Live mean that you stay inspired without missing a beat. Your focus will be off the screen and on your performance - where it matters most. 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. but I think we all agree/see, that: 'at the end of the day', PreSonus has done very little to communicate with us on what's going on, why this happens, and why they resist putting in a SQ (alternative mode) that allows us to filter out the notes (threshold) of those 'after-touch/after-bounce' pad Double Triggers. To me the big bonus of Atom SQ was the fact that in such a small form factor you can play SCALE only notes from a particular Scale, thus from 32 keys you were being able to play 4.5 and up to 6 octaves, depending on what scale you chose.

This workaround isn't perfect, but it does make the SQ far more *usable* while we wait for a firmware update, if you're a "light touch" player and if you like to rest your fingers on the pads in between new hits.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. The Atom SQ sports 32 velocity- and pressure- sensitive fingertip-sized RGB LED pads. The pads feel solid, not squishy, and are configured in two rows and slightly offset from each other like on a piano keyboard. To the left of the top row of pads, there are two smaller + and – buttons for pitch bending and octave up/down duties. Above the top row of pads is an assignable touch strip that features small LEDs to indicate the value of the parameter to which it’s assigned. The touch strip can be used for modulation, pitch bending, channel volume and more. Let’s take a look at the main key sector, as I’ve already explained before, it has two rows and two columns. The bottom key line is labeled 1/4, 1/8, 1/16, 1/32. this is for looping. And it has four knobs on the upper line. After getting a glance on it, we can just say it’s overall appearance is quite simple yet enough to solve its purpose with ease. I still think this is correctable for 99.9% of use cases with a firmware update that ignores note-ons within a certain time threshold. Assuming the Atom SQ keeps a buffer of timestamped events for inputs, something like: