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 update is coming soon

1…5152535456

Comments

  • Stuntman_mikeStuntman_mike

    Oh lord, Apple hurry up 😆

  • gregsmithgregsmith
    edited March 2021

    @wim said:

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    Come to think of it, this could be a neat way to include other types of events such as bank/program changes, or CC messages that work more like P-Locks than continual values. Just add the idea of a drop-down to select the event type, and an adaptable editor for the type of message.

    oooh. I like this idea a lot. B)

    (I'm not sure how to handle it graphically however if there were multiple events occupying a single place in the timeline.)

    No!

    Feature requests!

    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .

    ...til automation!

  • wimwim

    @gregsmith said:

    @wim said:

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    Come to think of it, this could be a neat way to include other types of events such as bank/program changes, or CC messages that work more like P-Locks than continual values. Just add the idea of a drop-down to select the event type, and an adaptable editor for the type of message.

    oooh. I like this idea a lot. B)

    (I'm not sure how to handle it graphically however if there were multiple events occupying a single place in the timeline.)

    No!

    Feature requests!

    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .

    ...til automation!

    This is automation.

  • gregsmithgregsmith

    @wim said:

    @gregsmith said:

    @wim said:

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    Come to think of it, this could be a neat way to include other types of events such as bank/program changes, or CC messages that work more like P-Locks than continual values. Just add the idea of a drop-down to select the event type, and an adaptable editor for the type of message.

    oooh. I like this idea a lot. B)

    (I'm not sure how to handle it graphically however if there were multiple events occupying a single place in the timeline.)

    No!

    Feature requests!

    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .

    ...til automation!

    This is automation.

    True. I just couldn’t resist a beastie boys reference

  • reasOnereasOne

    No feature requests!!
    .
    .
    .
    .
    .
    .
    .
    .
    Till release

    😂

  • blueveekblueveek
    edited March 2021

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    I have to admit I'm amazed by how creative this idea is. Not only is it doable, but It's likely doable inside just Atom, using one instance to "encode", and another one to "decode" using scripting, just like Mozaic.

    However, I'm actually warming up to the idea of enabling black-box CC recording, with high-level controls for manipulation (e.g. "delete lane", etc.). That would be much better and easier to set up than a scripting solution, and probably 80% of what most people would do anyway.

    @espiegel123 said:
    @blueveek : any sense of a timeframe for the black box record/playback to be available?

    Probably the right after release. I'm working on it now.

  • wimwim

    @blueveek said:

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    I have to admit I'm amazed by how creative this idea is. Not only is it doable, but It's likely doable inside just Atom, using one instance to "encode", and another one to "decode" using scripting, just like Mozaic.

    However, I'm actually warming up to the idea of enabling black-box CC recording, with high-level controls for manipulation (e.g. "delete lane", etc.). That would be much better and easier to set up than a scripting solution, and probably 80% of what most people would do anyway.

    I think I may have confused things by mentioning scripting. I was actually suggesting a non scripting approach leveraging the piano roll. A sysex message (or potentially any other MIDI event) event would be just like a note event but with semi free form byte data content that could be viewed or entered/edited in a pop up dialog box rather than note number and velocity.

    Starting off with simple black box recording and playback seems wise. People are going to be chomping at the bit for pitch bend, sustain pedal, other CC, and MPE recording/playback. Full-on editing of all that seems like a huge task in comparison to simply capturing it and playing it back. But you know that already. 😂

  • krassmannkrassmann

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    Wow, now I got that. But that means for larger projects you will need a big section of MIDI channels in your AUM project and probably must insert a lot of empty MIDI nodes to get to the clip matrix you want to have. To cover a launch pad you need 8 of these tracks - that’s quite a lot. On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    I have to admit I'm amazed by how creative this idea is. Not only is it doable, but It's likely doable inside just Atom, using one instance to "encode", and another one to "decode" using scripting, just like Mozaic.

    However, I'm actually warming up to the idea of enabling black-box CC recording, with high-level controls for manipulation (e.g. "delete lane", etc.). That would be much better and easier to set up than a scripting solution, and probably 80% of what most people would do anyway.

    @espiegel123 said:
    @blueveek : any sense of a timeframe for the black box record/playback to be available?

    Probably the right after release. I'm working on it now.

  • krassmannkrassmann
    edited March 2021

    @wim said:

    @blueveek said:

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    I have to admit I'm amazed by how creative this idea is. Not only is it doable, but It's likely doable inside just Atom, using one instance to "encode", and another one to "decode" using scripting, just like Mozaic.

    However, I'm actually warming up to the idea of enabling black-box CC recording, with high-level controls for manipulation (e.g. "delete lane", etc.). That would be much better and easier to set up than a scripting solution, and probably 80% of what most people would do anyway.

    I think I may have confused things by mentioning scripting. I was actually suggesting a non scripting approach leveraging the piano roll. A sysex message (or potentially any other MIDI event) event would be just like a note event but with semi free form byte data content that could be viewed or entered/edited in a pop up dialog box rather than note number and velocity.

    LOL, this reminds me how we did it in Cubase on an Atari in the end of 1980s. In the beginning of the song we recorded the Sysex of the bank dumps of our synths on on a dedicated MIDI track. If you wanted to work on that song again you could just unmute this track, replay the Sysex data and thus load the correct preset banks into the synths. That was quite neat and simple.

    Starting off with simple black box recording and playback seems wise. People are going to be chomping at the bit for pitch bend, sustain pedal, other CC, and MPE recording/playback. Full-on editing of all that seems like a huge task in comparison to simply capturing it and playing it back. But you know that already. 😂

  • blueveekblueveek
    edited March 2021

    @krassmann said:

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    It's all automatic! Adding, removing or moving slots or tracks around will automatically update on the controller. Not just that, but changing the node color from AUM will also update the clip and pad colors. I worked with @j_liljedahl to add some features on the AUM side that enable this kind of integration. The current AUM version has these capabilities enabled.

    If you have more than 8x8, the up/down/left/right arrows on the controller will offset the pads accordingly.

  • krassmannkrassmann

    @blueveek said:

    @krassmann said:

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    It's all automatic! Adding, removing or moving slots or tracks around will automatically update on the controller. Not just that, but changing the node color from AUM will also update the clip and pad colors. I worked with @j_liljedahl to add some features on the AUM side that enable this kind of integration. The current AUM version has these capabilities enabled.

    If you have more than 8x8, the up/down/left/right arrows on the controller will offset the pads accordingly.

    Totally cool! Best possible solution for AUM users, I would say. But I guess that kind of binds Atom‘s clip launching feature to AUM. What about other AUv3 hosts? What happens in apeMatrix, Cubasis, etc.?

  • krassmannkrassmann
    edited March 2021

    @krassmann said:

    @blueveek said:

    @krassmann said:

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    It's all automatic! Adding, removing or moving slots or tracks around will automatically update on the controller. Not just that, but changing the node color from AUM will also update the clip and pad colors. I worked with @j_liljedahl to add some features on the AUM side that enable this kind of integration. The current AUM version has these capabilities enabled.

    If you have more than 8x8, the up/down/left/right arrows on the controller will offset the pads accordingly.

    Totally cool! Best possible solution for AUM users, I would say. But I guess that kind of binds Atom‘s clip launching feature to AUM. What about other AUv3 hosts? What happens in apeMatrix, Cubasis, etc.?

    Just one more thought. The interface that @j_liljedahl and you agreed upon should best be made public on github for instance, even if it is just a spec. So, devs of other AUv3 host could adopt it and Atom could be integrated in their hosts the same way as in AUM.

    Maybe this is the beginning of a community driven AUv3 spec extension 🙂 @Apple, do you hear that...

  • blueveekblueveek
    edited March 2021

    @krassmann said:

    @blueveek said:

    @krassmann said:

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    It's all automatic! Adding, removing or moving slots or tracks around will automatically update on the controller. Not just that, but changing the node color from AUM will also update the clip and pad colors. I worked with @j_liljedahl to add some features on the AUM side that enable this kind of integration. The current AUM version has these capabilities enabled.

    If you have more than 8x8, the up/down/left/right arrows on the controller will offset the pads accordingly.

    Totally cool! Best possible solution for AUM users, I would say. But I guess that kind of binds Atom‘s clip launching feature to AUM. What about other AUv3 hosts? What happens in apeMatrix, Cubasis, etc.?

    You can pick (or override) the track, slot, color etc. from the UI in Atom. There's a panel dedicated for that, so there's a way to make it work everywhere. But, if other hosts decide to implement this API, then Atom should integrate automagically in them too. I'll definitely make some documentation about that.

  • gregsmithgregsmith

    @blueveek said:

    @krassmann said:

    @blueveek said:

    @krassmann said:

    @blueveek said:

    @zah said:

    @zah said:

    If I am trying to nail down a solo over 8 bars, will Atom, at the end of 8, automatically switch to a new pattern(s) while I continue to try to get those solo ideas down. And then comp together the best sections from the alternative takes?

    @blueveek said:

    Not automatically. Creating + advancing to a new pattern is just one button that does both together, so pretty quick.

    @blueveek
    1 - can that one button be triggered somehow (maybe key/foot switch)
    2 - does Atom have a way to select the best parts of say, three takes, to make one composite take? ie -if I like bars 1-4 on take one, 5-6 on take two and 7-8 on the third. Or would I copy/paste midi notes/parts that I like into a fourth clip?

    Thanks!

    For comping multiple takes, the workflow that's set in place makes use of the "Magic Clipboard", where multiple items can be copied at the same time. They're then available for pasting one after another with the "Paste at Playhead" feature, which also automatically advances the playhead after the paste. I never even thought about potentially having a Logic Pro audio comping style type of UI, but all the pieces are already in place (clip thumbnails loop sliders at the top, single view containing all the consecutive takes), so this shouldn't bee too hard to do!

    For MIDI mapping the take-related functions, I've implemented them yesterday :) It'll be available in a 2.0.1 release a few days after the initial version hits the store.

    @reasOne said:
    I originally was thinking atom 2 was going to let you use just one instance with tabs for each piano roll sending midi out but i think from what i see that it is one sequencer per instance. Either way can’t wait for this release!

    You'll see why I've decided to go this way – using AUM's view as an Ableton-like session view. I'm also integrating with AUM for automatically organizing all MIDI tracks onto controller pads, using the host's clip color and clip name as well. There's going to be a video about it.

    Basically: zoom out a bit in how you think about it. Don't think of Atom as an AU that sits alone and doesn't know about its surroundings. Use it as a MIDI clip placed on rows and columns inside AUM's Ableton-like "Session" view.

    On the other hand it is very elegant to re-use this functionality of AUM. Hopefully you don‘t have to do the mapping to the controller yourself. What happens when you shuffle the nodes or channels? Will the mapping adjust automatically? What if you want to have more than 8?

    It's all automatic! Adding, removing or moving slots or tracks around will automatically update on the controller. Not just that, but changing the node color from AUM will also update the clip and pad colors. I worked with @j_liljedahl to add some features on the AUM side that enable this kind of integration. The current AUM version has these capabilities enabled.

    If you have more than 8x8, the up/down/left/right arrows on the controller will offset the pads accordingly.

    Totally cool! Best possible solution for AUM users, I would say. But I guess that kind of binds Atom‘s clip launching feature to AUM. What about other AUv3 hosts? What happens in apeMatrix, Cubasis, etc.?

    You can pick (or override) the track, slot, color etc. from the UI in Atom. There's a panel dedicated for that, so there's a way to make it work everywhere. But, if other hosts decide to implement this API, then Atom should integrate automagically in them too. I'll definitely make some documentation about that.

    May not be connectable, but @sinosoidal this might be a way to match the pad colours in LK?

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • LiquidmantisLiquidmantis
    edited March 2021

    @gregsmith said:

    @wim said:

    @gregsmith said:

    @wim said:

    @wim said:

    @blueveek said:

    @auxmux said:

    @blueveek said:

    @DarkAum3o said:
    @blueveek might be a stupid question, but I will ask🙈. Has atom 2 a possibility to send program changes to synths, too?

    It was planned, but won’t be a part of the initial release. The big "automation" update is under development.

    @blueveek will automation also include sending sysex?

    Scripting lets you do that in 2.0 already!

    In fact, scripting lets you do some automation bits – albeit poorly, because support for it is incomplete for now. You can receive and store any MIDI messages in a script, including CC and SysEx, and inject them into the MIDI processing pipe when various other things happen in Atom, or based on the transport state etc. One thing I could add in a future update is a "host clock" callback to take it all the way there.

    However, I do understand that scripting might not be for everyone. Not sure how to make SysEx "automation" more accessible though, certainly building a UI around it seems tricky to get right. If you have any ideas, let me know. Otherwise, please give scripting a shot :)

    It does seem that Sysex fits more comfortably at the scripting level. However, I think you could think of it as an event much like a note event. The GUI could have an event easily distinguishable from a note that could be added to the piano roll. Tapping that event could bring up a dialog box with the contents of the sysex message and a way to edit it.

    Recording a sysex event could be as simple as adding it to the timeline when it comes in. Creating one could be as simple as adding it, then adding the bytes needed (the opening and closing bytes would be added automatically), and optionally enabling a checksum method. Playback needs no explanation.

    I could be over simplifying, but that seems like all that would be needed.

    Come to think of it, this could be a neat way to include other types of events such as bank/program changes, or CC messages that work more like P-Locks than continual values. Just add the idea of a drop-down to select the event type, and an adaptable editor for the type of message.

    oooh. I like this idea a lot. B)

    (I'm not sure how to handle it graphically however if there were multiple events occupying a single place in the timeline.)

    No!

    Feature requests!

    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .
    .

    ...til automation!

    This is automation.

    True. I just couldn’t resist a beastie boys reference

    Ah ha! So it was deliberate!

  • tk32tk32
    edited March 2021

    Not deliberately meaning to amp up the hype further.. but did you all see this?...

    https://forum.audiob.us/discussion/44082/atom-2-video-walkthrough-really-coming-soon-biggest-release-of-2021-5-free-copies-to-give-away

    I DO recommend watching Gavinski's walkthrough video.
    I DON'T recommend waiting for your chance to get a free copy. Buy it on first sight!

  • vasilymilovidovvasilymilovidov

    as primarily a drambo user i'm curious are there any significant reasons to choose aum over drambo for atom 2 workflow?

  • SamuSamu

    @vasilymilovidov said:
    as primarily a drambo user i'm curious are there any significant reasons to choose aum over drambo for atom 2 workflow?

    You could always use Atom 2 inside Drambo in those cases the step-sequencer feels a bit limiting ;)

  • Stuntman_mikeStuntman_mike

    @vasilymilovidov said:
    as primarily a drambo user i'm curious are there any significant reasons to choose aum over drambo for atom 2 workflow?

    You need all three!

  • tk32tk32
    edited March 2021

    Far from limiting your host options... I'm pretty confident you will find the opposite is true.

    Atom helps expand your host options.

    Clip launching in any compatible host... yes!
    Sequencing in DAW-less hosts like AUM... no problem.
    Complex chord progressions in Drambo... done.
    Replacing the built-in piano roll... two clicks..

    The AUM-specific features are just extra icing on the cake. Not necessary, but very nice to have.

  • aleyasaleyas

    @vasilymilovidov said:
    as primarily a drambo user i'm curious are there any significant reasons to choose aum over drambo for atom 2 workflow?

    Other way around for me. The clip launching will be cool in Aum - but I'm more excited to use Atom capture and modify track generated midi in Drambo (which as you know can't be bounced onto the main sequencer without workarounds). The Atom features such as note editing, scale quantize, and its strength settings will make for some very interesting generative midi workflows that wouldn't be as fun for me in Aum.
    So, as a primary Drambo user also, I'm personally not going to hop on the Atom workflow train, but am excited for the many ways it Atom can vastly enhance the Drambo workflow(s). Drambo dev has already stated that clips + launching are on the timeline, so I can wait for that native functionality without feeling like I'm missing too much in Aum+Atom.

  • ipadbeatmakingipadbeatmaking

    @tk32 did you ever get a chance to try it in ZenBeats?

  • RajahPRajahP

    Quantize to groove (your own ref. midi file, others , MCP, etc) will be nice...

  • ipadbeatmakingipadbeatmaking

    @RajahP said:
    Quantize to groove (your own ref. midi file, others , MCP, etc) will be nice...

    Boom 💥 ! This is a veteran move!! Count me in for this feature please.

  • Gus82Gus82

    @RajahP said:
    Quantize to groove (your own ref. midi file, others , MCP, etc) will be nice...

    Yes! Is this feature in or coming later?

  • blueveekblueveek
    edited March 2021

    @Gus82 said:

    @RajahP said:
    Quantize to groove (your own ref. midi file, others , MCP, etc) will be nice...

    Yes! Is this feature in or coming later?

    Not in this release, but in our planned features board. I think it was @winconway who added it in a few months ago.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
This discussion has been closed.

© Vanilla Keystone Theme 2025