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.

Xequence 2 is now available!

1…3031333536…62

Comments

  • purpan2purpan2

    Just wanted to say it... this is pretty well perfect now! Many thanks.

  • SevenSystemsSevenSystems

    @purpan2 said:
    Just wanted to say it... this is pretty well perfect now! Many thanks.

    Glad to hear that :) Suggestions and / or problem reports still always welcome of course.

  • BiancaNeveBiancaNeve

    @SevenSystems said:

    @BiancaNeve said:
    Never give a sucker an even break, it would be nice if the multi take loops could be comped....

    Could you give a few more details on the workflow you imagine?

    I imagine being able to composite the takes into one master take and use that.
    It’s an feature in audio in logic
    http://logicpro.skydocu.com/en/record-your-voice-or-a-musical-instrument/comp-your-audio-recordings/comping-overview/
    But it would in theory work with multiple midi takes

  • horsetrainerhorsetrainer
    edited August 2019

    This is a great new feature. It's a lot of fun to work out various iterations on the fly.

    Note: That after you create several "Take Tracks", and you want to keep more than one iteration...

    I discovered that if I use the + button in the "..." menu of the "Main Track", it will create another main track below the first.

    There are ^ and V arrow buttons in the "..." menu of the newly created main track.

    Push the V button to move the new main track to a position above one of the "additional" Take Track that you want to keep.

    Then select the "additional" Take Track that you want to keep, and use the move tool on the right side of the screen and bump the additional "keeper" Track up into that main track.

    Lastly, use the "..." menu on the "other" take track that you want to keep, select "Use This Take", and it will save that take to the "Original Main Track". All the other takes will be gone. When I follow the above steps, I have two "Takes" on Two Main Tracks remaining.

    @SevenSystems
    Thank you for this cool new feature.... Have you considered the possibility of adding an additional button adjacent to the "Use This Take" button. A button that says... "Save Take to New Track" ?

    I see a potential for this feature to be used for the creation of multiple spontaneously composed variants of melody that could be used throughout a musical composition.

    I can also see it being used for producing variants of melody to make into audio loops, that can be imported into loop playing apps like GarageBand.

  • wimwim
    edited August 2019

    Each take is already a separate track. I just delete the takes I don’t want individually, and move the ones I want to use later further out on the timeline.

  • horsetrainerhorsetrainer
    edited August 2019

    @wim said:
    Each take is already a separate track. I just delete the takes I don’t want individually, and move the ones I want to use later further out on the timeline.

    I noticed that too Wim. However my iPad only lets me move One Additional "Take Track" onto the "Main Track" timeline.

    I'm finding that by creating multiple new "Main Tracks" and bumping them immediately above each "Take Track", I can save as many "Take Tracks" as I like.

    If you've found a better way to save Multiple Takes, please share. :)

    Edited to add:

    Unless you mean just use the "Take Tracks" as Tracks, and make sure you never touch the "Use This Take" button ??

    As long as that doesn't lead to buggy behavior, I guess that's fine?

  • SevenSystemsSevenSystems

    @BiancaNeve said:

    @SevenSystems said:

    @BiancaNeve said:
    Never give a sucker an even break, it would be nice if the multi take loops could be comped....

    Could you give a few more details on the workflow you imagine?

    I imagine being able to composite the takes into one master take and use that.
    It’s an feature in audio in logic
    http://logicpro.skydocu.com/en/record-your-voice-or-a-musical-instrument/comp-your-audio-recordings/comping-overview/
    But it would in theory work with multiple midi takes

    OK, just briefly checked that. That's pretty "advanced" and when I last used Logic (2009 or so), it didn't have that feature yet I think...

    It's interesting for consideration in the future... for now though, you'll have to resort to the "Split" tool, then moving all your "wanted" sections to the same track and then "Join". (note that you can split through multiple clips from multiple takes at once if they're all selected). Should be pretty quick already even without that advanced "Logic comping".

  • buskerbusker
    edited August 2019

    @SevenSystems said:

    @purpan2 said:
    Just wanted to say it... this is pretty well perfect now! Many thanks.

    Glad to hear that :) Suggestions and / or problem reports still always welcome of course.

    Well, since you're asking... :)

    It would be very helpful to have some indication that a clip is a linked clip (perhaps the linked clip symbol could be overlayed in one of the corners of the clip?). I know that the numbers there, but they become hard to visually parse after a while if you have a lot of clips and are scrolling through the timeline.

    One example of where this would be useful:
    I'll usually start a song of with a bunch of linked clips, and once things are more or less fleshed out I'll go back and add some fills/changes and unlink the individual clips. Therefore it is handy to know by quickly looking at the timeline which clips have already been refined and which still need some work.

    Also, in general it is good to be able to easily see which sections of your song can be affected by edits elsewhere.

  • SevenSystemsSevenSystems

    @busker said:

    @SevenSystems said:

    @purpan2 said:
    Just wanted to say it... this is pretty well perfect now! Many thanks.

    Glad to hear that :) Suggestions and / or problem reports still always welcome of course.

    Well, since you're asking... :)

    It would be very helpful to have some indication that a clip is a linked clip (perhaps the linked clip symbol could be overlayed in one of the corners of the clip?). I know that the numbers there, but they become hard to visually parse after a while if you have a lot of clips and are scrolling through the timeline.

    One example of where this would be useful:
    I'll usually start a song of with a bunch of linked clips, and once things are more or less fleshed out I'll go back and add some fills/changes and unlink the individual clips. Therefore it is handy to know by quickly looking at the timeline which clips have already been refined and which still need some work.

    Also, in general it is good to see easily which sections of your song will be affected by edits elsewhere.

    Yes I have also often wished that if some clips are selected, then linked clips would display some kind of "Link" symbol or maybe a white outline so that you can see they use the same data... it's under consideration :)

    (note that when you OPEN a clip for editing, you'll definitely be told that it is linked with a brief "xx linked" message).

  • wimwim

    @horsetrainer said:
    Unless you mean just use the "Take Tracks" as Tracks, and make sure you never touch the "Use This Take" button ??

    As long as that doesn't lead to buggy behavior, I guess that's fine?

    yes, thats what I meant.

  • SevenSystemsSevenSystems

    @horsetrainer @wim no, "take tracks" are just "normal" sub-tracks (or totally normal tracks if "Automatically manage tracks" is disabled), so it should be fine to use them in any way you wish. The "Use this take" button also should work at any later point in time, as all information necessary for it is remembered forever in each take, and also separately for each recording "session".

    @BiancaNeve what I wanted to add -- you can also very easily crop clips from the end OR beginning, so it should be pretty straightforward to comp your takes. I don't think given the existing features for editing, there will be a dedicated "comping" mode.

  • rs2000rs2000

    @SevenSystems said:

    @BiancaNeve said:
    Never give a sucker an even break, it would be nice if the multi take loops could be comped....

    Could you give a few more details on the workflow you imagine?

    For me, the most important part is the simplicity of previewing all the different takes after recording. You loop-record all the takes and the logical next step will be listening to each before deciding what to do with 'em.

    What I am missing the most is a hassle-free way of doing that.

    Ideally, I would enable such a mode somehow (e.g. by long-tapping or tap-holding the SOLO button on any track), then by tapping on the track name box this track will be solo'ed.
    Why the track name box and not the solo button?
    Because when recording lots and lots of takes, you will want to zoom out vertically and still be able to pre-listen the takes. The solo buttons disappear zoomed out but the track names remain. By tapping once on the take's track, this track is solo'ed and all others (except the ones that were on solo before) are muted.
    I recommend to leave any track that was on SOLO before enabling this multi-take preview mode untouched because usually you'll want to have more tracks playing in order to preview the takes in context.
    This way, both is possible: Previewing takes in context and quick switching.
    I would not delay the switching except you'd like to add a beat-synced switch to add Ableton-style clip switching.

  • SevenSystemsSevenSystems

    @rs2000 Yes, a special exception for Multi-Take tracks to "Solo on selection" (and only solo inside their "invisible group") would be a good idea. The only problem I can see is how to expose this in the UI or make it clear to the user why these tracks are behaving differently when selected. I would want this to be completely isolated from the "normal" solo buttons / feature.

    But is the current solution really such a hassle? I mean, it's two taps per track (mute last, unmute next), or if you need to be zoomed out very far so that the mute buttons aren't visible, it's four (..., mute, ..., unmute)... OK, that's not ideal.

  • rs2000rs2000

    @SevenSystems said:
    @rs2000 Yes, a special exception for Multi-Take tracks to "Solo on selection" (and only solo inside their "invisible group") would be a good idea. The only problem I can see is how to expose this in the UI or make it clear to the user why these tracks are behaving differently when selected. I would want this to be completely isolated from the "normal" solo buttons / feature.

    But is the current solution really such a hassle? I mean, it's two taps per track (mute last, unmute next), or if you need to be zoomed out very far so that the mute buttons aren't visible, it's four (..., mute, ..., unmute)... OK, that's not ideal.

    You know, music creation on the iPad is all about fun and simplicity, so I would say that every click - sorry, I mean tap - counts. When recording multiple takes, these can easily be 20 or 30 takes in one recording, not only practicing complicated licks but also trying out different riffs during composition. And composition is what Xequence 2 excels at B)

    Regarding the "takes soloing" mode, I agree that it should always be clear what's happening.
    I had to think about this one for a while.
    Given that this is a one-by-one exclusive soloing mode (like drum mute groups), I would suggest the following:

    • Enabling this special solo mode would, first of all, require the recorded takes to be recognized as such, so only these behave differently.
    • The fact that some users will want to play other tracks simultaneously while skipping through different takes means that tracks that have been solo'ed before will remain solo'ed.
    • When in exclusive soloing for multi-take recordings, place a radio button in front of each take's track name because that makes clear that only one track can be selected, and it also clearly shows which tracks are not part of the new exclusive solo mode.
    • If you want to avoid special treatment of the recorded takes then there's a way to achieve that too: After enabling the special solo mode, any track that was not solo'ed before, will now have a radio button in front of the track name so you can preview anything, not just the recorded takes, and you're still free to have additional tracks active simultaneously by solo'ing them before enabling the new mode.
    • I personally wouldn't mind enabling the new solo mode by long-pressing any solo button on any track but no prob with adding an extra menu button like "SOLO" which offers "Exclusive Solo", "Mute All", "Solo All", all being toggles so that after hitting the respective one again, they're disabled. That would also add an indication which mode is currently active: When Exclusive Solo is active, the new menu button could be inverted (and flashing?) just like in DRAW mode. BTW, the mute all/solo all are just ideas for handy shortcuts you could add optionally.
  • horsetrainerhorsetrainer
    edited September 2019

    @rs2000 said:

    @SevenSystems said:
    @rs2000 Yes, a special exception for Multi-Take tracks to "Solo on selection" (and only solo inside their "invisible group") would be a good idea. The only problem I can see is how to expose this in the UI or make it clear to the user why these tracks are behaving differently when selected. I would want this to be completely isolated from the "normal" solo buttons / feature.

    But is the current solution really such a hassle? I mean, it's two taps per track (mute last, unmute next), or if you need to be zoomed out very far so that the mute buttons aren't visible, it's four (..., mute, ..., unmute)... OK, that's not ideal.

    You know, music creation on the iPad is all about fun and simplicity, so I would say that every click - sorry, I mean tap - counts. When recording multiple takes, these can easily be 20 or 30 takes in one recording, not only practicing complicated licks but also trying out different riffs during composition. And composition is what Xequence 2 excels at B)

    Regarding the "takes soloing" mode, I agree that it should always be clear what's happening.
    I had to think about this one for a while.
    Given that this is a one-by-one exclusive soloing mode (like drum mute groups), I would suggest the following:

    • Enabling this special solo mode would, first of all, require the recorded takes to be recognized as such, so only these behave differently.
    • The fact that some users will want to play other tracks simultaneously while skipping through different takes means that tracks that have been solo'ed before will remain solo'ed.
    • When in exclusive soloing for multi-take recordings, place a radio button in front of each take's track name because that makes clear that only one track can be selected, and it also clearly shows which tracks are not part of the new exclusive solo mode.
    • If you want to avoid special treatment of the recorded takes then there's a way to achieve that too: After enabling the special solo mode, any track that was not solo'ed before, will now have a radio button in front of the track name so you can preview anything, not just the recorded takes, and you're still free to have additional tracks active simultaneously by solo'ing them before enabling the new mode.
    • I personally wouldn't mind enabling the new solo mode by long-pressing any solo button on any track but no prob with adding an extra menu button like "SOLO" which offers "Exclusive Solo", "Mute All", "Solo All", all being toggles so that after hitting the respective one again, they're disabled. That would also add an indication which mode is currently active: When Exclusive Solo is active, the new menu button could be inverted (and flashing?) just like in DRAW mode. BTW, the mute all/solo all are just ideas for handy shortcuts you could add optionally.

    I'm having difficulty understanding what your proposing. Sounds like it could be more complex instead of less complex.

    Personally, I'm fine with un-muting each "Take" to audition them.

    **** Another way that I'm using this new "multi-take capability"... Is for playing piano "left hand" base parts using my "right hand" on a few takes, Then on the next few takes I play in melody parts on higher notes ALSO using my right hand....

    Afterward, I choose the two tracks I want to use and join (by un-muting two at a time). I position the two "take tracks" I want to merge by using the track move arrows until both "chosen take tracks" are next to each other. I then select the the lower "take" track, and I use the "move toggle" on the right side of the screen to bump up one "keeper" track on top of the other "keeper" track.

    Then press "Use this Take" on my "two-take-containing" keeper track. I then use the Join function on the resulting "main track" and make one completed Piano track containing both the bass and the melody. :)

    Please don't change anything that will take this capability away.

    Thank you.

  • rs2000rs2000

    @horsetrainer said:

    @rs2000 said:

    @SevenSystems said:
    @rs2000 Yes, a special exception for Multi-Take tracks to "Solo on selection" (and only solo inside their "invisible group") would be a good idea. The only problem I can see is how to expose this in the UI or make it clear to the user why these tracks are behaving differently when selected. I would want this to be completely isolated from the "normal" solo buttons / feature.

    But is the current solution really such a hassle? I mean, it's two taps per track (mute last, unmute next), or if you need to be zoomed out very far so that the mute buttons aren't visible, it's four (..., mute, ..., unmute)... OK, that's not ideal.

    You know, music creation on the iPad is all about fun and simplicity, so I would say that every click - sorry, I mean tap - counts. When recording multiple takes, these can easily be 20 or 30 takes in one recording, not only practicing complicated licks but also trying out different riffs during composition. And composition is what Xequence 2 excels at B)

    Regarding the "takes soloing" mode, I agree that it should always be clear what's happening.
    I had to think about this one for a while.
    Given that this is a one-by-one exclusive soloing mode (like drum mute groups), I would suggest the following:

    • Enabling this special solo mode would, first of all, require the recorded takes to be recognized as such, so only these behave differently.
    • The fact that some users will want to play other tracks simultaneously while skipping through different takes means that tracks that have been solo'ed before will remain solo'ed.
    • When in exclusive soloing for multi-take recordings, place a radio button in front of each take's track name because that makes clear that only one track can be selected, and it also clearly shows which tracks are not part of the new exclusive solo mode.
    • If you want to avoid special treatment of the recorded takes then there's a way to achieve that too: After enabling the special solo mode, any track that was not solo'ed before, will now have a radio button in front of the track name so you can preview anything, not just the recorded takes, and you're still free to have additional tracks active simultaneously by solo'ing them before enabling the new mode.
    • I personally wouldn't mind enabling the new solo mode by long-pressing any solo button on any track but no prob with adding an extra menu button like "SOLO" which offers "Exclusive Solo", "Mute All", "Solo All", all being toggles so that after hitting the respective one again, they're disabled. That would also add an indication which mode is currently active: When Exclusive Solo is active, the new menu button could be inverted (and flashing?) just like in DRAW mode. BTW, the mute all/solo all are just ideas for handy shortcuts you could add optionally.

    I'm having difficulty understanding what your proposing. Sounds like it could be more complex instead of less complex.

    Personally, I'm fine with un-muting each "Take" to audition them.

    **** Another way that I'm using this new "multi-take capability"... Is for playing piano "left hand" base parts using my "right hand" on a few takes, Then on the next few takes I play in melody parts on higher notes ALSO using my right hand....

    Afterward, I choose the two tracks I want to use and join (by un-muting two at a time). I position the two "take tracks" I want to merge by using the track move arrows until both "chosen take tracks" are next to each other. I then select the the lower "take" track, and I use the "move toggle" on the right side of the screen to bump up one "keeper" track on top of the other "keeper" track.

    Then press "Use this Take" on my "two-take-containing" keeper track. I then use the Join function on the resulting "main track" and make one completed Piano track containing both the bass and the melody. :)

    Please don't change anything that will take this capability away.

    Thank you.

    OK, I should have pm'ed this to the developer instead.
    No worries. What you're doing is still perfectly possible, no difference.
    It's a very simple thing described in very much detail, no wonder you're more irritated than pleased by the suggestion o:)
    If you saw in the app what I've suggested you'd certainly agree that it not only simplifies auditioning but also gives you more spontaneous composition options. Nothing changes at all if you don't use the new function.

  • horsetrainerhorsetrainer

    @rs2000 said:

    @horsetrainer said:

    @rs2000 said:

    @SevenSystems said:
    @rs2000 Yes, a special exception for Multi-Take tracks to "Solo on selection" (and only solo inside their "invisible group") would be a good idea. The only problem I can see is how to expose this in the UI or make it clear to the user why these tracks are behaving differently when selected. I would want this to be completely isolated from the "normal" solo buttons / feature.

    But is the current solution really such a hassle? I mean, it's two taps per track (mute last, unmute next), or if you need to be zoomed out very far so that the mute buttons aren't visible, it's four (..., mute, ..., unmute)... OK, that's not ideal.

    You know, music creation on the iPad is all about fun and simplicity, so I would say that every click - sorry, I mean tap - counts. When recording multiple takes, these can easily be 20 or 30 takes in one recording, not only practicing complicated licks but also trying out different riffs during composition. And composition is what Xequence 2 excels at B)

    Regarding the "takes soloing" mode, I agree that it should always be clear what's happening.
    I had to think about this one for a while.
    Given that this is a one-by-one exclusive soloing mode (like drum mute groups), I would suggest the following:

    • Enabling this special solo mode would, first of all, require the recorded takes to be recognized as such, so only these behave differently.
    • The fact that some users will want to play other tracks simultaneously while skipping through different takes means that tracks that have been solo'ed before will remain solo'ed.
    • When in exclusive soloing for multi-take recordings, place a radio button in front of each take's track name because that makes clear that only one track can be selected, and it also clearly shows which tracks are not part of the new exclusive solo mode.
    • If you want to avoid special treatment of the recorded takes then there's a way to achieve that too: After enabling the special solo mode, any track that was not solo'ed before, will now have a radio button in front of the track name so you can preview anything, not just the recorded takes, and you're still free to have additional tracks active simultaneously by solo'ing them before enabling the new mode.
    • I personally wouldn't mind enabling the new solo mode by long-pressing any solo button on any track but no prob with adding an extra menu button like "SOLO" which offers "Exclusive Solo", "Mute All", "Solo All", all being toggles so that after hitting the respective one again, they're disabled. That would also add an indication which mode is currently active: When Exclusive Solo is active, the new menu button could be inverted (and flashing?) just like in DRAW mode. BTW, the mute all/solo all are just ideas for handy shortcuts you could add optionally.

    I'm having difficulty understanding what your proposing. Sounds like it could be more complex instead of less complex.

    Personally, I'm fine with un-muting each "Take" to audition them.

    **** Another way that I'm using this new "multi-take capability"... Is for playing piano "left hand" base parts using my "right hand" on a few takes, Then on the next few takes I play in melody parts on higher notes ALSO using my right hand....

    Afterward, I choose the two tracks I want to use and join (by un-muting two at a time). I position the two "take tracks" I want to merge by using the track move arrows until both "chosen take tracks" are next to each other. I then select the the lower "take" track, and I use the "move toggle" on the right side of the screen to bump up one "keeper" track on top of the other "keeper" track.

    Then press "Use this Take" on my "two-take-containing" keeper track. I then use the Join function on the resulting "main track" and make one completed Piano track containing both the bass and the melody. :)

    Please don't change anything that will take this capability away.

    Thank you.

    OK, I should have pm'ed this to the developer instead.
    No worries. What you're doing is still perfectly possible, no difference.
    It's a very simple thing described in very much detail, no wonder you're more irritated than pleased by the suggestion o:)
    If you saw in the app what I've suggested you'd certainly agree that it not only simplifies auditioning but also gives you more spontaneous composition options. Nothing changes at all if you don't use the new function.

    Thanks for the clarification. :)

  • RajahPRajahP

    Am I doing something wrong, or, are X2 midi exports not recognized in BM3’s midi imports..
    Know there is an issue with BM3 not recognizing type 1 or 0 midi file types..

  • gregsmithgregsmith

    Just got Xequence 2 today. It’s amazing! I’ve only had the Audiobus preset save work once out of about 50 saves today. If I can help debug let me know @SevenSystems

  • wimwim

    @gregsmith said:
    Just got Xequence 2 today. It’s amazing! I’ve only had the Audiobus preset save work once out of about 50 saves today. If I can help debug let me know @SevenSystems

    If I remember correctly, the ball is in @Michael's court now.

  • SevenSystemsSevenSystems

    @gregsmith said:
    Just got Xequence 2 today. It’s amazing! I’ve only had the Audiobus preset save work once out of about 50 saves today. If I can help debug let me know @SevenSystems

    That's interesting. Sorry to hear you're having trouble with State Saving. I sound like a broken record here, but I've spent an actual cumulative week trying to fix this, so it seems like it's still not working.

    Well, if it hardly ever works AT ALL for you, then you may be on to something there and may actually have found the root problem without even knowing or wanting :) I'll PM you for further debugging if you are OK with that (I'm extremely busy with life stuff right now though, so it could take a while!).

  • gregsmithgregsmith

    @SevenSystems said:

    @gregsmith said:
    Just got Xequence 2 today. It’s amazing! I’ve only had the Audiobus preset save work once out of about 50 saves today. If I can help debug let me know @SevenSystems

    That's interesting. Sorry to hear you're having trouble with State Saving. I sound like a broken record here, but I've spent an actual cumulative week trying to fix this, so it seems like it's still not working.

    Well, if it hardly ever works AT ALL for you, then you may be on to something there and may actually have found the root problem without even knowing or wanting :) I'll PM you for further debugging if you are OK with that (I'm extremely busy with life stuff right now though, so it could take a while!).

    Of course, PM when you get a chance.

    I’ll not touch the preset again. It’s an incredibly simple preset proof of concept so I get the feeling I’m doing something wrong.

  • wimwim

    You're probably not doing anything wrong. The success or failure of the save doesn't seem to have anything to do with the complexity of the project.

    I do seem to have better success rate when saving sessions from the fly-out dialog in Audiobus than from the sidebar, but even then it's not consistent. I save from the fly-out, and watch for the message at the bottom of the screen saying the Xequence 2 state has saved. Sometimes it saves even when the message doesn't show, but I don't recall ever having it not save if the message has shown.

    Anyway - If you guys want to include me in the PM, I'm more than happy to help with debugging. Currently out of ideas, but I can try. ;)

  • gregsmithgregsmith

    i have a track which starts with 3 notes held for quite a few bars. Often in playback these notes are getting stuck. It’s playing DRC through AB if that makes any difference. Can anyone advise?

  • wimwim
    edited September 2019

    @gregsmith said:
    i have a track which starts with 3 notes held for quite a few bars. Often in playback these notes are getting stuck. It’s playing DRC through AB if that makes any difference. Can anyone advise?

    Do the notes get stuck if you substitute other synths? That would help narrow the issue down between X2 and DRC.

    Also, if you have a monitoring app such as Midi Tools Monitor, you can stick it in the path in audiobus to see if the note off is being sent when it should be. If it is, then the fault is definitely with DRC.

  • espiegel123espiegel123

    @SevenSystems : thanks for adding the notepad to the app!

  • Tones4ChristTones4Christ

    Guys please remember to update reviews in the AppStore 🤗🙏❤️❤️❤️❤️❤️
    Thank you Mr. Developer! We really are grateful for your continued hard work!❤️🙏☝️

  • gregsmithgregsmith

    @wim said:

    @gregsmith said:
    i have a track which starts with 3 notes held for quite a few bars. Often in playback these notes are getting stuck. It’s playing DRC through AB if that makes any difference. Can anyone advise?

    Do the notes get stuck if you substitute other synths? That would help narrow the issue down between X2 and DRC.

    Also, if you have a monitoring app such as Midi Tools Monitor, you can stick it in the path in audiobus to see if the note off is being sent when it should be. If it is, then the fault is definitely with DRC.

    Just swapped for Viking synth and that seemed to stick the notes too. I have midi tools monitor and can’t see note off being sent.

    If I start from half way through the pattern it turns the notes off so I wonder if it’s something to do with how long they’re being held for? They’re being held for just short of 33 bars.

  • wimwim
    edited September 2019

    @gregsmith said:

    @wim said:

    @gregsmith said:
    i have a track which starts with 3 notes held for quite a few bars. Often in playback these notes are getting stuck. It’s playing DRC through AB if that makes any difference. Can anyone advise?

    Do the notes get stuck if you substitute other synths? That would help narrow the issue down between X2 and DRC.

    Also, if you have a monitoring app such as Midi Tools Monitor, you can stick it in the path in audiobus to see if the note off is being sent when it should be. If it is, then the fault is definitely with DRC.

    Just swapped for Viking synth and that seemed to stick the notes too. I have midi tools monitor and can’t see note off being sent.

    If I start from half way through the pattern it turns the notes off so I wonder if it’s something to do with how long they’re being held for? They’re being held for just short of 33 bars.

    I was able to reproduce the note-off being missed if looping is on. With looping off, the note off came as expected.

    This was a 33 bar pattern with a single note extending to 1/16 note short of the end of the pattern, and loop set to the pattern length.

  • gregsmithgregsmith

    @wim said:

    @gregsmith said:

    @wim said:

    @gregsmith said:
    i have a track which starts with 3 notes held for quite a few bars. Often in playback these notes are getting stuck. It’s playing DRC through AB if that makes any difference. Can anyone advise?

    Do the notes get stuck if you substitute other synths? That would help narrow the issue down between X2 and DRC.

    Also, if you have a monitoring app such as Midi Tools Monitor, you can stick it in the path in audiobus to see if the note off is being sent when it should be. If it is, then the fault is definitely with DRC.

    Just swapped for Viking synth and that seemed to stick the notes too. I have midi tools monitor and can’t see note off being sent.

    If I start from half way through the pattern it turns the notes off so I wonder if it’s something to do with how long they’re being held for? They’re being held for just short of 33 bars.

    I was able to reproduce the note-off being missed if looping is on. With looping off, the note off came as expected.

    This was a 33 bar pattern with a single note extending to 1/16 note short of the end of the pattern, and loop set to the pattern length.

    Loop mode is off as far as I can tell. The song keeps playing way past the pattern and the notes stayed stuck.

    Probably the same bug though just something else slightly different.

Sign In or Register to comment.