Loopy Pro: Create music, your way.

What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Atom | Piano Roll 2 is now available

1…6768707273…90

Comments

  • noniman93noniman93

    Also, was seriously blown away by the “tempo = pitch” demonstration. Wondering if we can generate some our standard pitches (like an A3 = 220hz) through some combinations of Atom’s loop length, Atom’s tempo multiplier and Aum’s tempo control. That way we can generate, for example, the A3 note using different instruments in AUM giving different timbres (quality?!) but the pitch will be the same. 😳

  • blueveekblueveek

    @espiegel123 said:
    Do the config files allow the setting of the default clip length of new clips?

    Not documented, but it would be fairly simple enable.

    @ipadbeatmaking said:
    Any chance for someone to make a Roli Lightpad app(s)/script(s) for it?

    What kind of integration would you like to see? Is it strictly clip launching and auto-routing? Something more exotic?

    Related: I wanted to do this for a while, but I'm seriously reaching the limits of what I can find in stock (at least in my corner of Europe). I had to buy a Lumi to ensure Atom works well with MPE and external controllers, and it was a serious ordeal finding that in stock anywhere, never mind other controllers like a Seaboard or Sensel which seem to have vanished off the face of the Earth these days...

    @noniman93 said:
    Also, was seriously blown away by the “tempo = pitch” demonstration. Wondering if we can generate some our standard pitches (like an A3 = 220hz) through some combinations of Atom’s loop length, Atom’s tempo multiplier and Aum’s tempo control. That way we can generate, for example, the A3 note using different instruments in AUM giving different timbres (quality?!) but the pitch will be the same. 😳

    It's really cool isn't it? Certainly blew my mind when I first learned about it. Here's a cool presentation on this topic too.

  • noniman93noniman93

    @blueveek said:
    It's really cool isn't it? Certainly blew my mind when I first learned about it. Here's a cool presentation on this topic too.

    Oh gosh! Brilliant. So intuitive too.

  • ipadbeatmakingipadbeatmaking

    @blueveek ALL the above 😂 seriously though I don’t know what I’d specifically like to see. You’ve done a great job already imagining so many features with Atom!

    I guess we could start with whatever the launchpad integration looks like. I’d really also like a scale feature of some sort where changing scales in atom reflects on the Lightpad etc etc. so in totality I don’t know if this would be different apps on the Lightpad or different lightpad screens/layouts in a single Lightpad app that can be toggled.

    I’ve got a Lightpad I could loan out for the cause.

  • SergiuSergiu

    Yes, scales and keys are amazing

  • sloJordansloJordan

    @blueveek said:

    @espiegel123 said:
    Do the config files allow the setting of the default clip length of new clips?

    Not documented, but it would be fairly simple enable.

    +1, would be very useful.

  • MisplacedDevelopmentMisplacedDevelopment

    @blueveek I’m moving to using PC as pattern switch and clip launch control based on the conversation the other day about MPE-proofing and being able to record MIDI while launch activity is taking place.

    I have created a simple StreamByter script to convert note number to PC as I can’t find an efficient way of generating them on a timeline. With this in mind, can I ask whether the clip launch PC trigger value is ignored for the purposes of pattern triggering, e.g. if I have the clip launcher listening for PC trigger 48 then am I safe to assume that the pattern switch code will ignore this value. If they do share the same namespace then I can move the pattern switch to listen on a different channel as a workaround.

  • blueveekblueveek
    edited May 2021

    @MisplacedDevelopment said:
    @blueveek I’m moving to using PC as pattern switch and clip launch control based on the conversation the other day about MPE-proofing and being able to record MIDI while launch activity is taking place.

    I have created a simple StreamByter script to convert note number to PC as I can’t find an efficient way of generating them on a timeline. With this in mind, can I ask whether the clip launch PC trigger value is ignored for the purposes of pattern triggering, e.g. if I have the clip launcher listening for PC trigger 48 then am I safe to assume that the pattern switch code will ignore this value. If they do share the same namespace then I can move the pattern switch to listen on a different channel as a workaround.

    Yes! The pattern-assigned trigger will be ignored by the pattern switching logic if that specific message is also assigned to clip launching. In other words, clip launching takes priority and swallows the event.

  • MisplacedDevelopmentMisplacedDevelopment

    @blueveek said:

    @MisplacedDevelopment said:
    @blueveek I’m moving to using PC as pattern switch and clip launch control based on the conversation the other day about MPE-proofing and being able to record MIDI while launch activity is taking place.

    I have created a simple StreamByter script to convert note number to PC as I can’t find an efficient way of generating them on a timeline. With this in mind, can I ask whether the clip launch PC trigger value is ignored for the purposes of pattern triggering, e.g. if I have the clip launcher listening for PC trigger 48 then am I safe to assume that the pattern switch code will ignore this value. If they do share the same namespace then I can move the pattern switch to listen on a different channel as a workaround.

    Yes! The pattern-assigned trigger will be ignored by the pattern switching logic if that specific message is also assigned to clip launching. In other words, clip launching takes priority and swallows the event.

    That’s good news, exactly how I hoped it would work. It certainly looked like that was what was happening but I thought I had better make certain before I started on this next journey.

  • OscarSouthOscarSouth
    edited May 2021

    @blueveek said:

    @OscarSouth said:

    @blueveek said:

    @OscarSouth said:
    Is there a way to select and change the channel of an inputted note? I can only find how to write new notes in on a new channel.

    When recording or with step inputting from an external source, make sure that source is emitting on the channel you need, I assume you're using AUM. To change which channel AUM's keyboard outputs on, tap on the wrench on the lower right, and select the appropriate channel. If you're not using AUM, consult your host's manual.

    When manually entering notes in Atom, long press on the 'add' button and pick your channel there.


    Thank you. I'm using Audiobus and I did find that 'add' button setting. I'm sending in multi channel MIDI through a DIN cable from another module and this is being received fine. Is there any way to change a note to a different channel though, after inputting/recording?

    Not yet. Atom is mostly concerned with recording MPE data when it comes to multiple channels, and there's not much use for changing per-note-channels after the fact in that case. It's a relatively simple thing to implement though, so I'm curious, what's the use case?

    I'm using an external multitimbral ROMpler for orchestration, with each orchestral instrument responding on a different channel.

    You can see an example here, where the MIDI to the ROMpler is being generated by code:

    The live-coding aspect of it is a bit niche though, so it's handy to be able to arrange the orchestra by hand on a piano roll too (if I just wanted a short loop to sample or to accompany a sample or something like that).

  • gusgranitegusgranite

    Facebook group now available https://www.facebook.com/groups/atompianoroll

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • gusgranitegusgranite

    Amazing when you look at the updates @blueveek has released in under 8 weeks! 👊

    Version History

    2.0.8May 4, 2021

    • Full MPE and automation support for MIDI import/export, in addition to recording. Working directly with MIDI files will now include pitch bend, modulation, sustain and all other CC or aftertouch events.
    • Full MPE compatibility for Linnstrument and Continuumini hardware.
    • Greatly improved performance on all devices when recording MPE that generates a lot of data.

    2.0.7May 2, 2021
    *** MPE and automation ***
    - Added support for MPE recording. All new clips will have MPE enabled by default, no configuration required!
    - Added support for pitch bend, modulation, sustain, and “black box” automation recording. Each pattern has its own dedicated automation group, which includes all event lanes.
    - Added “Multi-Channel” support: each note, in each pattern, in each clip, can have its own dedicated MIDI channel. Each clip can be configured to output in “filter” or “funnel” mode.
    - Recording will honor the MIDI channels for incoming MIDI events.
    - Note entry will honor the MIDI channel and velocity settings specified in the new “Advanced Add” panel.
    - Included a “MIDI Channel Colors” style: enable it to colorize notes based on their individual channels.
    Note: To turn on MPE for clips created in previous versions, enable “MPE” and “tick all” channels from the Output toolbar.
    *** New features ***
    - MIDI import is now non-destructive: all other patterns, settings, and history will be preserved in the current clip, and only new patterns will be added for each lane in the MIDI file. Each pattern has its own grid, time signature, bar count and loop makers.
    - Scales can be fuzzy-filtered. Search for scales by their name, mode, or notes. Bad spelling works too.
    - Patterns can now also be switched with CC values. Map patterns to a rotary encoder (knob) on your controller, in any host.
    *** Tweaks and fixes ***
    - Added: Playhead position will now be remembered in the history stack. Useful when undoing step-input.
    - Added: All the non-destructive processes now have toggles for snapping the effect strength.
    - Added: Configurations now include preferred styles. E.g. setting "Larger Controls" will now apply the appropriate fonts by default (but still overridable).
    - Added: Logs will include messages about which ports are disconnected.
    - Fixed an unintuitive off-by-one situation when launching patterns with velocity.
    - Fixed an issue where recording wouldn't work as expected with MIDI generated from audio units which sometimes never off'ed notes (e.g. Autony).
    - Fixed an issue where the "paste at playhead" button for the first snippet wasn't tappable.
    - Fixed an issue where the UI remain stuck in a perpetual loading state.
    - Fixed an issue where the UI would freeze for a second when refocusing, if patterns were frequently switched while the view was in the background.
    - Improved: The total memory usage is now down to ~90mb per 512 instances.
    - Improved: MIDI files with incorrect file extensions can now also be imported.

    2.0.6Apr 22, 2021
    *** Overhauled Patterns ***
    - You can now use just a single instance to build all of your clips on a single track.
    - Added the ability to switch patterns using notes, CCs, PCs and even velocity, on any channel. Playback uses immediate-gate mode.
    - Added switch with legato for patterns. Switching between patterns will now let the notes naturally ring, so the changes aren’t abrupt.
    - Decoupled pattern editing from playback: patterns can now be edited while other patterns are playing.
    - Added 'Focus' and 'Play' buttons beside each pattern thumbnail.
    *** Drambo integration ***
    - The most advanced modular sequencer befriends the most advanced modular host.
    - Atom patterns will now follow Drambo patterns, synced to quantum.
    - Clips will now auto-launch when instantiated in Drambo.
    *** New features ***
    - MIDI export will now export all patterns on separate channels.
    - Implemented crop to loop, crop to notes and crop to selection.
    - Added 16 new scales: all Modal Hexatonic variants (6 modes), Hirajoshi (5 modes) and Kumoi (5 modes). Give Hirajoshi a try, it’s awesome.
    - Added “Auto Swing Duration” in the swing processing toolbar. When on, swing timing strength will automatically set swing durations.
    - Made the tempo slider snap in increments of 0.05 when dragging. Adjustments are in 0.01 increments when tapping.
    - Made the tempo parameter go down to 0 (it was 0.5 minimum previously).
    - The “Play pattern" parameter, as well as the "Clear active"/ "Duplicate active" pattern parameters, now all work with Launchpad controllers even when the instance itself isn't focused (visible).
    *** UI tweaks ***
    - Bars now alternate their background color in the grid.
    - The focused pattern number is now displayed above the keyboard. The playing pattern number is now shown in the Clip button.
    - The grid and time panels are now persisted; this allows changing snap and grid settings during note entry.
    - Scales, Layers, Clipboard and Pattern controls will now always stay in view when scrolling.
    - Double tapping a pattern thumbnail will now select all notes in that pattern.
    - Increased the touch area for the note resize grabbies.
    - Relocated the Listen button to the bottom-left.
    - Changed the long-press indicator style for buttons with hidden menus.
    - Fixed playhead position not updating with undo/redo.
    - Fixed playhead position not visually seeking forward with step input.
    - Many layout improvements, especially for iPhone when used in vertical mode.

    2.0.5Apr 15, 2021

    • Enabled iOS 13 compatibility for Launchpad controllers.
    • Added nonuplets, undecuplets and tredecuplets for quantization, swing, and general editing, in addition to triplets, quintuplets and septuplets.
    • Added 39 new scales, grouped by their main mode, and including all of their corresponding modal flavors, for a total of 74. All scales are sorted with music theory in mind and ordered by their respective modal brightness, from “bright or happy” to “dark or sad”. The new scales include Double Harmonic, Persian, Neapolitan Minor, Neapolitan Major, Flamenco, Enigmatic, Octatonic Whole-Half Diminished & Half-Whole Diminished, Major Hexatonic & Minor Hexatonic, Whole Tone, Augmented & Six-Tone Symmetric, Prometheus and Tritone scales.
    • Added Program Change clip triggers, available in the advanced launch settings.
    • Added auto-routing support for the Akai MPK Mini 3 controller, which also serves as a simple example hardware script for adding your own custom routing.
    • Added receiveCC, receivePitchBend and receiveProgramChange, in addition to receivePolyphonicAftertouch and receiveChannelAftertouch, to the scripting sandbox.
    • Fixed an issue where controller scripts in would sometimes connect to the same ports twice.
    • Added a “Disabled Animations” configuration that reduces motion.
    • Added a “Reload UI” button for quickly reloading the configurations and styles.
    • Revamped configs, styles and scripts menus, now with icons, sorting and helpful tips for getting the most out of user extensions.
    • Now preventing accidental dismissal of the manual view when tapping on the background.
    • Now presenting doorhanger menus modally, disabling input for the background.
    • Better performance when opening various menus like Scales.
    • Fixed sliders also scrolling containers, and "Process" toolbars appearing incorrectly on narrow screens (e.g. on iPhone in vertical mode)
    • Layers now sorted by track.
    • Default quantize toolbar strength now depends on the top-level quantize button.

    2.0.4Apr 4, 2021

    • A user manual is now available. Find it in an instance's app menu.
    • Tapping will now preview notes on the piano roll vertical keyboard.
    • Powerful new swing controls: apply negative swing, nudge the timings or control the durations.
    • Drag and drop not just MIDI, but also scripts, styles or configurations onto your clips, and they will immediately apply to your session. Want to try out a different skin? Or bring your controller to life? Just drag and drop. Easily import and use code that others wrote!
    • Scripts now support message logging. A new directory called "Logs" is created in your Atom folder containing log files. Devices, input and output ports are automatically logged for convenience. Use console.log(...) to log a custom message from your script.
    • Controller scripts specifying an input and output port can now use either the short name or the longer label for port identification.
    • Added new ways of visualizing velocity: with colors, opacity, bar positioning or thickness, or the numerical value itself.
    • Added new ways of visualizing pitch: octave colors, highlighting in and out of scale notes and others.
    • Added a plethora of additional example styles to get you inspired.
    • Fixed an issue where certain controllers (like the Lauchkey Mini) would emit high-pitched sounds when manually routed.
    • MIDI clock is now passed-through with Novation controllers when routed through clips.
    • CC messages are now passed-through when routed through clips.
    • Mutation panel controls are now reset to default after baking non-destructive processing operations.
    • The velocity offset slider is now more accurate.

    2.0.3Mar 27, 2021

    • Full support for Apple Pencil, and greatly improved input responsiveness overall.
    • Added a new advanced launch setting: "Choke Mode".
    • Added on-screen track choking with the Launch buttons in AUM. Turn your AUM session into a mini on-screen Launchpad.
    • Track choking and clip exclusivity via MIDI or parameters is available with the custom "Choke Mode" settings.
    • Added the ability to arm record multiple clips at the same time from Launchpad X and Launchpad Pro Mk3 controllers. Enter "Record Arm" mode and tap on the pads you want to arm.
    • More layout configurations and more font themes. Combine “Larger Controls” with “Larger Fonts”, or “Sausage Fingers” with “Sausage Fonts”, or mix and match.

    2.0.2Mar 21, 2021

    • MIDI files will now automatically set the clip length, time signature, and adjust the loop markers when imported.
    • Multi-channel MIDI files will include all lanes as separate Patterns when imported.
    • Drag and drop import from other apps. Open Files side by side, and drag MIDI files onto Atom instances.
    • New style: "Larger Fonts".
    • New Pattern controls: “Select Notes”.
    • Added basic support for the "Quantize" function on the Launchpad Pro Mk3.
    • Added support for the “Clear” and “Duplicate” functions on the Launchpad Pro Mk3 when the instance is visible.
    • Exposed AU parameters and scripting hooks for clearing patterns, duplicating patterns, and toggling recording quantization.
    • Broadened the types of operations remembered on the history stack when applying non-destructive processing.
    • Improved handling of overlapping notes with applied swing for monophonic synths.
    • Improved discoverability and added helpful tips for the advanced configuration panels (available with a long-press).
    • Better performance when using many instances or importing very large clips.

    2.0.1Mar 15, 2021

    • Support for the Launchpad Pro Mk3 controller.
    • A "Sausage Fingers" mode, for people who want bigger UI elements.
    • A "Roboto" font based theme, for people who want larger and more legible text.
    • New pattern controls: "Add Default", "Add Empty", "Add duplicate", "Reset Pattern", "Delete Notes".
    • Help messages using non-destructive processing operations.
    • Better track cloning support in AUM, cloned tracks now also show up in Layers.
    • Better iCloud support, also preventing a crash when iCloud is disabled.
    • Support for simultaneous touch and mouse input. Using both touch and mouse input together will cause instability in 2.0, update to 2.0.1 when it hits to avoid any issues!

    1.0Mar 15, 2021

  • wahnfriedenwahnfrieden

    Long press and drag will automatically start making a marquee selection, no matter what input mode you're in (it's covered on the second page of the manual, along with all of the other gestures). Is that sufficient, or do you prefer double-click and drag instead? I feel like long press and drag is a more common iOS idiom, so I'd prefer to keep that as is, but I'm curious about your thoughts on that.

    I accept long press with finger, but find it somehow inappropriate for Magic Keyboard’s mouse input but I can’t back this up with an Apple HIG reference. I’ve only watched some of the WWDC talk on the improved keyboard/mouse support that launched along with the Magic Keyboard, they’re quite informative and might clarify these new input paradigms.

    Also bringing this ability to the Apple Pencil would indeed be sweet, and I love the idea. I think it can only work with Pencil 2, but DM me your TestFlight email (if interested in working on this together) and I'll look into adding it to the next version.

    This would be a clear winning option, will DM

  • reasOnereasOne

    Has anyone made a video of how to use an atom to change patterns in other atoms in aum?
    I’ve been mostly using it in drambo cuz i haven’t figured out the aum thing yet. I’m not very technical.

    Would be cool if you could set how many times a pattern repeats before going to the next one automatically but i don’t know if thats possible or in the plans

  • xorxor
    edited May 2021

    @reasOne said:
    Has anyone made a video of how to use an atom to change patterns in other atoms in aum?
    I’ve been mostly using it in drambo cuz i haven’t figured out the aum thing yet. I’m not very technical.

    Would be cool if you could set how many times a pattern repeats before going to the next one automatically but i don’t know if thats possible or in the plans

    Here’s a very quick and dirty example

    In the “controlled” atom:

    • at the bottom of the pattern panel change from PC to Notes
    • (not shown) turn off MIDI thru in the clip panel (tap the blue clip name/number in the top left)

    In the “controlling” atom:

    • play the lowest notes C-1, C#-1, … to select the pattern you want to play (you can change the notes with the pattern setting in the “controlled” atom)

    In AUM:

    • Set the “controlled” atom’s input input to come from the “controlling” atom
    • Make sure that the Atom’s are primed to launch in aum
    • press play
  • [Deleted User][Deleted User]

    Anyone else getting much of this? I can only assume it's about long clips but I could be wrong, I don't think there's been any specific discussion of why this is happening.

    I'm talking about the halt of any response from the UI. Also I'm not sure how the MPE setting came to be on, or showing. It wasn't activated intentionally, but that's not what I'm concerned about. It's the UI in general grinding to a halt, for quite a long time sometimes.

  • blueveekblueveek
    edited May 2021

    @SimonSomeone said:
    I'm talking about the halt of any response from the UI.

    That’s quite bad. Please DM me that project, or some steps to reproduce, and I’ll prioritize looking into it.

    Also I'm not sure how the MPE setting came to be on, or showing. It wasn't activated intentionally

    All new clips have MPE enabled by default. It doesn’t adversely affect performance in any way.

  • [Deleted User][Deleted User]

    @blueveek , thanks, will do.

  • wexywexy
    edited May 2021

    The cc triggers for record and clear seem to change patterns after triggered is this intentional?

  • GdubGdub

    Thanks for the great work

  • MisplacedDevelopmentMisplacedDevelopment

    @MisplacedDevelopment said:

    @blueveek said:

    @MisplacedDevelopment said:
    @blueveek I’m moving to using PC as pattern switch and clip launch control based on the conversation the other day about MPE-proofing and being able to record MIDI while launch activity is taking place.

    I have created a simple StreamByter script to convert note number to PC as I can’t find an efficient way of generating them on a timeline. With this in mind, can I ask whether the clip launch PC trigger value is ignored for the purposes of pattern triggering, e.g. if I have the clip launcher listening for PC trigger 48 then am I safe to assume that the pattern switch code will ignore this value. If they do share the same namespace then I can move the pattern switch to listen on a different channel as a workaround.

    Yes! The pattern-assigned trigger will be ignored by the pattern switching logic if that specific message is also assigned to clip launching. In other words, clip launching takes priority and swallows the event.

    That’s good news, exactly how I hoped it would work. It certainly looked like that was what was happening but I thought I had better make certain before I started on this next journey.

    So close now to getting this working. My remaining problem (which I had hit before but forgotten about) is that record will disarm at the end of a hold clip launch note so I can’t listen to the pattern before the one I’m recording into if there is any gap between the launch notes as the record option is unset just before I want to start recording.

    What I have done as a workaround is to tie the record toggle AU parameter to the same PC used for clip control so recording stays enabled:

    Now when StreamByter sends in the two PC instructions to change pattern and start the transport (PC 48) then recording is enabled. I’ll play with this setup this afternoon and if it works then it means that I can finally ditch my record-only Atom instance and record directly into the pattern I’m working on.

    Has anyone worked around this in a different way?

  • wexywexy

    I think this is a similar issue to what I’m having with record and clear parameter triggering

    I just want the current clip to stay active but it seems to switch patterns

    I’ve managed to code around it too within my Lemur app

    @MisplacedDevelopment said:

    @MisplacedDevelopment said:

    @blueveek said:

    @MisplacedDevelopment said:
    @blueveek I’m moving to using PC as pattern switch and clip launch control based on the conversation the other day about MPE-proofing and being able to record MIDI while launch activity is taking place.

    I have created a simple StreamByter script to convert note number to PC as I can’t find an efficient way of generating them on a timeline. With this in mind, can I ask whether the clip launch PC trigger value is ignored for the purposes of pattern triggering, e.g. if I have the clip launcher listening for PC trigger 48 then am I safe to assume that the pattern switch code will ignore this value. If they do share the same namespace then I can move the pattern switch to listen on a different channel as a workaround.

    Yes! The pattern-assigned trigger will be ignored by the pattern switching logic if that specific message is also assigned to clip launching. In other words, clip launching takes priority and swallows the event.

    That’s good news, exactly how I hoped it would work. It certainly looked like that was what was happening but I thought I had better make certain before I started on this next journey.

    So close now to getting this working. My remaining problem (which I had hit before but forgotten about) is that record will disarm at the end of a hold clip launch note so I can’t listen to the pattern before the one I’m recording into if there is any gap between the launch notes as the record option is unset just before I want to start recording.

    What I have done as a workaround is to tie the record toggle AU parameter to the same PC used for clip control so recording stays enabled:

    Now when StreamByter sends in the two PC instructions to change pattern and start the transport (PC 48) then recording is enabled. I’ll play with this setup this afternoon and if it works then it means that I can finally ditch my record-only Atom instance and record directly into the pattern I’m working on.

    Has anyone worked around this in a different way?

  • MisplacedDevelopmentMisplacedDevelopment

    It appears that using the raw hold note directly from the control clip is actually a better way of toggling the record option as you can then “hold record” rather than using the note -> PC value from StreamByter which is an on/off toggle and keeps getting into the wrong state:

    As the control note is only being read via AUM for the purposes of AU MIDI Control then it avoids showing up in my recording.

  • ipadbeatmakingipadbeatmaking

    @ipadbeatmaking said:
    @blueveek ALL the above 😂 seriously though I don’t know what I’d specifically like to see. You’ve done a great job already imagining so many features with Atom!

    I guess we could start with whatever the launchpad integration looks like. I’d really also like a scale feature of some sort where changing scales in atom reflects on the Lightpad etc etc. so in totality I don’t know if this would be different apps on the Lightpad or different lightpad screens/layouts in a single Lightpad app that can be toggled.

    I’ve got a Lightpad I could loan out for the cause.

    I know you’re a busy man @blueveek Just making make sure u caught this post 👆

  • reasOnereasOne

    @xor said:

    @reasOne said:
    Has anyone made a video of how to use an atom to change patterns in other atoms in aum?
    I’ve been mostly using it in drambo cuz i haven’t figured out the aum thing yet. I’m not very technical.

    Would be cool if you could set how many times a pattern repeats before going to the next one automatically but i don’t know if thats possible or in the plans

    Here’s a very quick and dirty example

    In the “controlled” atom:

    • at the bottom of the pattern panel change from PC to Notes
    • (not shown) turn off MIDI thru in the clip panel (tap the blue clip name/number in the top left)

    In the “controlling” atom:

    • play the lowest notes C-1, C#-1, … to select the pattern you want to play (you can change the notes with the pattern setting in the “controlled” atom)

    In AUM:

    • Set the “controlled” atom’s input input to come from the “controlling” atom
    • Make sure that the Atom’s are primed to launch in aum
    • press play

    It works!!!!
    Perfect
    Thank you for this i finally get it! Easier than i thought

  • MisplacedDevelopmentMisplacedDevelopment

    @blueveek are there any known issues with PC messages getting missed when sending clip control and pattern switch messages at the same time? My StreamByter note->PC script will not reliably change patterns unless I add 1ms delay to the sending of the pattern switch message.

    I’ve attached a graphic below which hopefully explains the setup. Top left: clip controller into note->PC SB script into MIDI Monitor + the clip under control:

  • Edward_AlexanderEdward_Alexander

    @blueveek Victor has so much momentum right now! He’s an unstoppable force!

    He’s churning out updates to the beta so fast that I actually had to turn off the automatic updates to test flight to be able to get anything done lol! Yes, Atom will indeed crash if you have an open project working at the same time one of these beta updates gets automatically installed.

    I don’t think it’s a bug, but maybe just something to look out for if you’re on the beta. Save your work frequently, and turn off the automatic updates on the TestFlight page.

    Amazing amazing amazing work Victor!

  • Edward_AlexanderEdward_Alexander

    Btw, if you’ve saved your work (in AUM for example), if this happens, simply close and relaunch AUM and reload the project and you’ll find all of your new shiny Atom 2 instances all ready for you. ❤️

  • SamuSamu

    @Intrepolicious said:

    Amazing amazing amazing work Victor!

    +1

    I always do manual updates and also quit all open apps before I do.
    Just wish more developers would 'adopt' the insanely tight midi-engine @blueveek managed to cook up!

    Most "sequencers" feel very loose/un-tight/sloppy in direct comparison.
    It doesn't really matter how many cool features they have if they can't do the basic timing things right...

    Needless to say the integration with the launchpads is just an added bonus :)

Sign In or Register to comment.

© Vanilla Keystone Theme 2025