MIDI learn in AUM: using Xequence Pads to Launch Atom 2?

richardyot

I'm probably just doing something dumb, but I can't seem to set up Xequence Pads to clip launch Atom 2. See this screenshot:

I've pointed the Xequence pads to each instance of Atom 2, but then when I try to get AUM to MIDI Learn the control it doesn't work. If I tap the Xequence pad with the AUM parameters panel open the act of tapping the pad closes the panel and MIDI Learn doesn't work.

And because AUM doesn't use standard note names I can't figure out how to map C4 (or whatever note) to the control.

My routing is OK I think:

With a hardware controller connected this would be so easy, but trying to get AUM to MIDI learn from an internally hosted AUv3 is glitchy, unless I'm missing something.

Tim6502

@richardyot - In AUM anything you control receives it thru "MIDI Control" - so send the Xequence pads there (not to Atom).
And C4 is 60 (at least for the AUM keyboard, which starts at C-1, might be 72 for keyboads starting to count from C-2) - though this should be learnable when MIDI Control receives it.

Now Atom 2 also has its secret handshakes - but only with HW controllers AFAIK.

richardyot

@Tim6502 said:
@richardyot - In AUM anything you control receives it thru "MIDI Control" - so send the Xequence pads there (not to Atom).
And C4 is 60 (at least for the AUM keyboard, which starts at C-1, might be 72 for keyboads starting to count from C-2) - though this should be learnable when MIDI Control receives it.

Now Atom 2 also has its secret handshakes - but only with HW controllers AFAIK.

Thanks for the help

I've rerouted Xequence to MIDI Control instead of Atom, so thanks for that pointer.

Unfortunately MIDI Learn still doesn't want to work with Xequence, and neither 60 nor 72 seem to respond to the note C4. 🤷‍♀️

Has anyone managed to launch Atom 2 clips from an AU MIDI controller app?

blueveek

@richardyot said:

@Tim6502 said:
@richardyot - In AUM anything you control receives it thru "MIDI Control" - so send the Xequence pads there (not to Atom).
And C4 is 60 (at least for the AUM keyboard, which starts at C-1, might be 72 for keyboads starting to count from C-2) - though this should be learnable when MIDI Control receives it.

Now Atom 2 also has its secret handshakes - but only with HW controllers AFAIK.

Thanks for the help

I've rerouted Xequence to MIDI Control instead of Atom, so thanks for that pointer.

Unfortunately MIDI Learn still doesn't want to work with Xequence, and neither 60 nor 72 seem to respond to the note C4. 🤷‍♀️

Has anyone managed to launch Atom 2 clips from an AU MIDI controller app?

@tk32 did, both with Xequence and ChordPolyPad afaik. Pinging him in case he has time to go into the details.

I will note that there's 2 ways to MIDI learn launching with Atom:

• either use parameter mapping and MIDI learn from the host (e.g. the 3rd button in AUM's window titlebar, then tap the parameter learn icon in the top right), then tap the Launch button,
• or long press the Launch button in Atom and set the note there yourself; don't forget to disable Thru Input from the clip menu if you go this route.

uncledave

@richardyot said:

@Tim6502 said:
@richardyot - In AUM anything you control receives it thru "MIDI Control" - so send the Xequence pads there (not to Atom).
And C4 is 60 (at least for the AUM keyboard, which starts at C-1, might be 72 for keyboads starting to count from C-2) - though this should be learnable when MIDI Control receives it.

Now Atom 2 also has its secret handshakes - but only with HW controllers AFAIK.

Thanks for the help

I've rerouted Xequence to MIDI Control instead of Atom, so thanks for that pointer.

Unfortunately MIDI Learn still doesn't want to work with Xequence, and neither 60 nor 72 seem to respond to the note C4. 🤷‍♀️

Has anyone managed to launch Atom 2 clips from an AU MIDI controller app?

Have you tried configuring the MIDI event manually? You don't have to use MIDI learn to set it up.

Also, have you tried sending MIDI messages direct to Atom 2, using your original routing? It might work, if you send the "secret handshakes" built into Atom 2.

By the way, there is no "standard" note naming except for MIDI. MIDI note 60 is middle C, always. Long ago, Yamaha chose C3 for that note, while Roland chose C4. There's another convention that uses C5. It gets confusing mixing apps using the different conventions.

blueveek

@uncledave said:
Also, have you tried sending MIDI messages direct to Atom 2, using your original routing? It might work, if you send the "secret handshakes" built into Atom 2.

Just fyi, there's no "secret handshakes" when it comes to launching. It's all just public parameters, or dedicated MIDI note triggers from the Launch panel (long press the Launch button).

richardyot

@uncledave said:
Have you tried configuring the MIDI event manually? You don't have to use MIDI learn to set it up.

Also, have you tried sending MIDI messages direct to Atom 2, using your original routing? It might work, if you send the "secret handshakes" built into Atom 2.

By the way, there is no "standard" note naming except for MIDI. MIDI note 60 is middle C, always. Long ago, Yamaha chose C3 for that note, while Roland chose C4. There's another convention that uses C5. It gets confusing mixing apps using the different conventions.

Thanks for the pointers - I got it working by setting AUM to send note 60 and then poking around with Xequence Pads until it triggered the right note, in this case it was C5.

tk32

@richardyot I don’t have Xequence, but ChordPolyPad is absolutely brilliant for launching Atom2 clips in AUM.

Once you’ve spent a bit of time setting things up (and saved the project as a preset) Chordpolypad behaves just like a virtual launchpad (without the bright colours)

Here’s a preview of the template I made during the beta. Unfortunately it no longer loads because it was made with an earlier version of atom2, but I could easily make a fresh template and share it with you.

Note - when you see me latch mutiple clips/scenes in the video, it’s because I am using multi-touch. Most of the time Chordpolypad works by latching/unlatching one clip/scene at a time (which is exactly what you’d want)

tk32

Here’s how it works...

• I dedicate the bottom row to stop commands, and the furthest right column for scene/row triggers, this leaves me with a 7x7 grid for triggering individual clips.
• Each Track is configured to launch via MIDI notes an octave apart (Track 1 starts at C-1, Track 2 starts at C0, etc up to Track 7 starts at C5)
• Each of the 7 clips in each track is configured to trigger chromatically (slot 1 = C, slot 2 = C#, etc up to slot 7 = F#)
• The Scene launchers play a chord of unison notes across the 7 octaves (scene 1 plays C-1 + C0 + C1 + C2 + C3 + C4 + C5) — as shown in the screenshot below

Poppadocrock

Big up, Big up @tk32 thanks for clarifying that process.

richardyot

@tk32 said:
@richardyot I don’t have Xequence, but ChordPolyPad is absolutely brilliant for launching Atom2 clips in AUM.

Once you’ve spent a bit of time setting things up (and saved the project as a preset) Chordpolypad behaves just like a virtual launchpad (without the bright colours)

Here’s a preview of the template I made during the beta. Unfortunately it no longer loads because it was made with an earlier version of atom2, but I could easily make a fresh template and share it with you.

Note - when you see me latch mutiple clips/scenes in the video, it’s because I am using multi-touch. Most of the time Chordpolypad works by latching/unlatching one clip/scene at a time (which is exactly what you’d want)

Thanks! That looks useful 👍

gusgranite

@tk32 🏆

audiblevideo

ChordPolyPad, I’ve used it for years and never once looked to see if you could name pads...

It’s been there all this time. 😅