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.

The problem is synchronization (or quantization) when switching loops

13»

Comments

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav : do you want the overall structure to repeat over and over or do you need to arbitrarily trigger it?

    I need to run it arbitrarily

    Could you adapt your workflow so that you trigger one bar or two bars before before you want it to start?

    If you wanted the pattern to cycle that would be easy, or if you could trigger it some number of known bars before you want it to fire. The problem here is that your musical structure is unpredictable...every time this sequence fires it becomes two bars farther out of synch of your eight bar drum loop...and creates a changed overall cycle length. So, can't use a multiple, like you are now, because the length of your structure changes.

    If it were me and I wanted to be able to trigger it arbitrarily, I'd set it up so that I trigger it a bar early and take responsibility for knowing my song well enough to do that. That solution is uncomplicated. It just involves changing the play quantization to 1 or two bars.

    If you are always going to trigger it while guitar1 is playing, you could make stop guitar 1 be the first action of the action sequence before solo. That would guarantee that it finishes.

    There might be a tricky way with dials or follow actions or the sequencer.

    But maybe I am not understanding something about your structure. If it is predictable

    Thank you.
    I'll try to apply your recommendations.

    This is an interesting idea about stopping Git 1.

    What do I need to do to start the workflow one, two bars earlier?

    How to change quantization to 1 or 2 bars?

  • VyacheslavVyacheslav

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav : do you want the overall structure to repeat over and over or do you need to arbitrarily trigger it?

    I need to run it arbitrarily

    Could you adapt your workflow so that you trigger one bar or two bars before before you want it to start?

    If you wanted the pattern to cycle that would be easy, or if you could trigger it some number of known bars before you want it to fire. The problem here is that your musical structure is unpredictable...every time this sequence fires it becomes two bars farther out of synch of your eight bar drum loop...and creates a changed overall cycle length. So, can't use a multiple, like you are now, because the length of your structure changes.

    If it were me and I wanted to be able to trigger it arbitrarily, I'd set it up so that I trigger it a bar early and take responsibility for knowing my song well enough to do that. That solution is uncomplicated. It just involves changing the play quantization to 1 or two bars.

    If you are always going to trigger it while guitar1 is playing, you could make stop guitar 1 be the first action of the action sequence before solo. That would guarantee that it finishes.

    There might be a tricky way with dials or follow actions or the sequencer.

    But maybe I am not understanding something about your structure. If it is predictable

    Thank you.
    I'll try to apply your recommendations.

    This is an interesting idea about stopping Guit 1.

    What do I need to do to start the workflow one, two bars earlier?

    How to change quantization to 1 or 2 bars?

  • espiegel123espiegel123

    @Vyacheslav said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav : do you want the overall structure to repeat over and over or do you need to arbitrarily trigger it?

    I need to run it arbitrarily

    Could you adapt your workflow so that you trigger one bar or two bars before before you want it to start?

    If you wanted the pattern to cycle that would be easy, or if you could trigger it some number of known bars before you want it to fire. The problem here is that your musical structure is unpredictable...every time this sequence fires it becomes two bars farther out of synch of your eight bar drum loop...and creates a changed overall cycle length. So, can't use a multiple, like you are now, because the length of your structure changes.

    If it were me and I wanted to be able to trigger it arbitrarily, I'd set it up so that I trigger it a bar early and take responsibility for knowing my song well enough to do that. That solution is uncomplicated. It just involves changing the play quantization to 1 or two bars.

    If you are always going to trigger it while guitar1 is playing, you could make stop guitar 1 be the first action of the action sequence before solo. That would guarantee that it finishes.

    There might be a tricky way with dials or follow actions or the sequencer.

    But maybe I am not understanding something about your structure. If it is predictable

    Thank you.
    I'll try to apply your recommendations.

    This is an interesting idea about stopping Guit 1.

    What do I need to do to start the workflow one, two bars earlier?

    How to change quantization to 1 or 2 bars?

    Changing the quantization is just a matter of changing the quantization for the first solo action to custom 1 bar or 2 bars

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav : do you want the overall structure to repeat over and over or do you need to arbitrarily trigger it?

    I need to run it arbitrarily

    Could you adapt your workflow so that you trigger one bar or two bars before before you want it to start?

    If you wanted the pattern to cycle that would be easy, or if you could trigger it some number of known bars before you want it to fire. The problem here is that your musical structure is unpredictable...every time this sequence fires it becomes two bars farther out of synch of your eight bar drum loop...and creates a changed overall cycle length. So, can't use a multiple, like you are now, because the length of your structure changes.

    If it were me and I wanted to be able to trigger it arbitrarily, I'd set it up so that I trigger it a bar early and take responsibility for knowing my song well enough to do that. That solution is uncomplicated. It just involves changing the play quantization to 1 or two bars.

    If you are always going to trigger it while guitar1 is playing, you could make stop guitar 1 be the first action of the action sequence before solo. That would guarantee that it finishes.

    There might be a tricky way with dials or follow actions or the sequencer.

    But maybe I am not understanding something about your structure. If it is predictable

    Thank you.
    I'll try to apply your recommendations.

    This is an interesting idea about stopping Guit 1.

    What do I need to do to start the workflow one, two bars earlier?

    How to change quantization to 1 or 2 bars?

    Changing the quantization is just a matter of changing the quantization for the first solo action to custom 1 bar or 2 bars

    OK. Thank you

  • VyacheslavVyacheslav

    Hello.
    Set the quantization of the first action in a sequence (solo) to default.
    Now we have to start the entire sequence 2 bars before the end of the main loops (Guit 1/Bass 1), but this is tolerable.
    P.S. I made the first action of the sequence to stop Guit 1/Bass 1 before Solo, but it didn't help.
    Thank you very much for your assistance.


  • espiegel123espiegel123

    @Vyacheslav said:
    Hello.
    Set the quantization of the first action in a sequence (solo) to default.
    Now we have to start the entire sequence 2 bars before the end of the main loops (Guit 1/Bass 1), but this is tolerable.
    P.S. I made the first action of the sequence to stop Guit 1/Bass 1 before Solo, but it didn't help.
    Thank you very much for your assistance.


    When using the stop Guitar 1 method, you woikd need to change the start quantization of the solo action that follows it to 1bar or two bars, did you do that?

    Can you post a screenshot of of the setup for the stop guitar 1 action that did not work and the solo action and screenshot of the action sequence that includes them and a demonstration of what happens? I am a little surprised that it did not work.

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:
    Hello.
    Set the quantization of the first action in a sequence (solo) to default.
    Now we have to start the entire sequence 2 bars before the end of the main loops (Guit 1/Bass 1), but this is tolerable.
    P.S. I made the first action of the sequence to stop Guit 1/Bass 1 before Solo, but it didn't help.
    Thank you very much for your assistance.


    When using the stop Guitar 1 method, you woikd need to change the start quantization of the solo action that follows it to 1bar or two bars, did you do that?

    Can you post a screenshot of of the setup for the stop guitar 1 action that did not work and the solo action and screenshot of the action sequence that includes them and a demonstration of what happens? I am a little surprised that it did not work.

    Where should I do this? In what settings?

  • espiegel123espiegel123

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:
    Hello.
    Set the quantization of the first action in a sequence (solo) to default.
    Now we have to start the entire sequence 2 bars before the end of the main loops (Guit 1/Bass 1), but this is tolerable.
    P.S. I made the first action of the sequence to stop Guit 1/Bass 1 before Solo, but it didn't help.
    Thank you very much for your assistance.


    When using the stop Guitar 1 method, you woikd need to change the start quantization of the solo action that follows it to 1bar or two bars, did you do that?

    Can you post a screenshot of of the setup for the stop guitar 1 action that did not work and the solo action and screenshot of the action sequence that includes them and a demonstration of what happens? I am a little surprised that it did not work.

    Where should I do this? In what settings?

    I am not sure which settings you mean. The quantization settings? Those are in the individual actions. Play/stop/solo/unsolo and many other actions have quantization settings.


  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:
    Hello.
    Set the quantization of the first action in a sequence (solo) to default.
    Now we have to start the entire sequence 2 bars before the end of the main loops (Guit 1/Bass 1), but this is tolerable.
    P.S. I made the first action of the sequence to stop Guit 1/Bass 1 before Solo, but it didn't help.
    Thank you very much for your assistance.


    When using the stop Guitar 1 method, you woikd need to change the start quantization of the solo action that follows it to 1bar or two bars, did you do that?

    Can you post a screenshot of of the setup for the stop guitar 1 action that did not work and the solo action and screenshot of the action sequence that includes them and a demonstration of what happens? I am a little surprised that it did not work.

    Where should I do this? In what settings?

    I am not sure which settings you mean. The quantization settings? Those are in the individual actions. Play/stop/solo/unsolo and many other actions have quantization settings.


    It doesn't work that way

  • VyacheslavVyacheslav
    edited December 2023

    But this is how it works.

    The rest of the quantization is default



    Thanks for the idea about stopping in the first action in the sequence! I still implemented it, albeit in my own way))

  • espiegel123espiegel123

    @Vyacheslav said:
    But this is how it works.

    The rest of the quantization is default



    Thanks for the idea about stopping in the first action in the sequence! I still implemented it, albeit in my own way))

    You need to tap on the action to adjust its settings. The settings I showed are there. When you tap on the left yiu are setting when the action starts to fire not the settings of the action.

    The settings I showed are accessible.

  • espiegel123espiegel123

    @Vyacheslav

  • VyacheslavVyacheslav

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

  • espiegel123espiegel123

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

  • espiegel123espiegel123

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

    Fine. I want everything to work correctly. What should I do for this? What should I tell you about my settings? What actions should I take in my LP?

  • espiegel123espiegel123

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

    Fine. I want everything to work correctly. What should I do for this? What should I tell you about my settings? What actions should I take in my LP?

    My suggestion is for you to make a copy of your project.

    I should make sure my understanding is correct: you want a sequence of actions that can be triggered any time while guitar 1 is playing and when guitar 1 completes will play your two bar sequence then guitar 2 then guitar 1.

    If that is correct, try to set up the actions I described earlier. If it doesn't work, post screenshots of the action sequence setup and the settings of the individual actions. And a demo of what happens. If you are able to share the project that doesn't work that might be useful, too.

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

    Fine. I want everything to work correctly. What should I do for this? What should I tell you about my settings? What actions should I take in my LP?

    My suggestion is for you to make a copy of your project.

    I should make sure my understanding is correct: you want a sequence of actions that can be triggered any time while guitar 1 is playing and when guitar 1 completes will play your two bar sequence then guitar 2 then guitar 1.

    If that is correct, try to set up the actions I described earlier. If it doesn't work, post screenshots of the action sequence setup and the settings of the individual actions. And a demo of what happens. If you are able to share the project that doesn't work that might be useful, too.

    Ok, I'll do it

  • VyacheslavVyacheslav

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

    Fine. I want everything to work correctly. What should I do for this? What should I tell you about my settings? What actions should I take in my LP?

    My suggestion is for you to make a copy of your project.

    I should make sure my understanding is correct: you want a sequence of actions that can be triggered any time while guitar 1 is playing and when guitar 1 completes will play your two bar sequence then guitar 2 then guitar 1.

    If that is correct, try to set up the actions I described earlier. If it doesn't work, post screenshots of the action sequence setup and the settings of the individual actions. And a demo of what happens. If you are able to share the project that doesn't work that might be useful, too.

    Ok, I'll do it

    Maybe a copy of the project with changes will be enough?

  • VyacheslavVyacheslav

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    I understand what you are talking about.
    I made these settings.
    But they don't work for me.
    I don't know why.

    That is why I asked for you to show them and demonstrate what happened so that I might understand either what adjustment might need to be made that I overlooked or if there is an issue in Loopy that needs addressing.

    What’s stopping you from putting together a similar circuit with the same sequence and figuring out what doesn’t work in it? Everything is simple here, I sent you my project above, and everything is clear in the video.
    8 bars(1) - 2 bars(2) - 8 bars(3) - 8 bars(1)

    If it is working as you want, I won’t try helping you figure out why the method I suggested didn’t work for you.

    Me creating a sequence won’t tell us what went wrong with your combination of elements and events . And if you are happy with what you have , my other idea isn’t important.

    Fine. I want everything to work correctly. What should I do for this? What should I tell you about my settings? What actions should I take in my LP?

    My suggestion is for you to make a copy of your project.

    I should make sure my understanding is correct: you want a sequence of actions that can be triggered any time while guitar 1 is playing and when guitar 1 completes will play your two bar sequence then guitar 2 then guitar 1.

    If that is correct, try to set up the actions I described earlier. If it doesn't work, post screenshots of the action sequence setup and the settings of the individual actions. And a demo of what happens. If you are able to share the project that doesn't work that might be useful, too.

    Ok, I'll do it

    Maybe a copy of the project with changes will be enough?

  • espiegel123espiegel123

    @Vyacheslav

    Here is a mockup which I tested. Triggering the action sequence while guitar 1 is playing will play the 2 bars wen guitar 1 completes then play guitar 2 then start guitar 1

  • VyacheslavVyacheslav

    @espiegel123 said:
    @Vyacheslav

    Here is a mockup which I tested. Triggering the action sequence while guitar 1 is playing will play the 2 bars wen guitar 1 completes then play guitar 2 then start guitar 1

    Ok. I'll repeat it now.
    I will send you the results + a copy of the project.

  • VyacheslavVyacheslav
    edited December 2023

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav

    Here is a mockup which I tested. Triggering the action sequence while guitar 1 is playing will play the 2 bars wen guitar 1 completes then play guitar 2 then start guitar 1

    Ok. I'll repeat it now.
    I will send you the results + a copy of the project.

    I installed your settings.
    You also have 8 bars delay set, as I did earlier.
    Everything is working!
    Here are my screenshots and a copy of the project, just in case.
    Can you comment on the need for your actions with quantization, both in the overall sequence diagram and for each action? They are not very clear to me.

    https://dropbox.com/scl/fi/yphbm1jme86qj3ccbcreg/Old-Song.lpproj?rlkey=kvapybekblmj5sxmw9ojxnauu&dl=0








  • espiegel123espiegel123

    @Vyacheslav: which quantization settings are unclear?

    The reason for the quantization on the “after last “ setting of the second action (the one after the stop) ensures that the event fires precisely on the bar boundary.

    It is possible that it isn’t needed but it les loopy know that you want it precisely on the bar boundary.

    The same is true for the play quantization.

  • VyacheslavVyacheslav

    @espiegel123 said:
    @Vyacheslav: which quantization settings are unclear?

    The reason for the quantization on the “after last “ setting of the second action (the one after the stop) ensures that the event fires precisely on the bar boundary.

    It is possible that it isn’t needed but it les loopy know that you want it precisely on the bar boundary.

    The same is true for the play quantization.

    quantization in action settings is unclear

  • espiegel123espiegel123

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav: which quantization settings are unclear?

    The reason for the quantization on the “after last “ setting of the second action (the one after the stop) ensures that the event fires precisely on the bar boundary.

    It is possible that it isn’t needed but it les loopy know that you want it precisely on the bar boundary.

    The same is true for the play quantization.

    quantization in action settings is unclear

    Play quantization tells loopy at what bar boundary the event should start on. A 1-bar means start at the next bar boundary (including right now if the clock is at a bar boundary). 2-bars means when the clock is on an even bar boundary.

    Does that make sense?

  • VyacheslavVyacheslav

    @espiegel123 said:

    @Vyacheslav said:

    @espiegel123 said:
    @Vyacheslav: which quantization settings are unclear?

    The reason for the quantization on the “after last “ setting of the second action (the one after the stop) ensures that the event fires precisely on the bar boundary.

    It is possible that it isn’t needed but it les loopy know that you want it precisely on the bar boundary.

    The same is true for the play quantization.

    quantization in action settings is unclear

    Play quantization tells loopy at what bar boundary the event should start on. A 1-bar means start at the next bar boundary (including right now if the clock is at a bar boundary). 2-bars means when the clock is on an even bar boundary.

    Does that make sense?

    Yes, I understand. Thank you!

  • espiegel123espiegel123

    @Vyacheslav: here is a more detailed explanation of the settings in the sequence I posted.

    Event 1: Stop Verse loop. Stop Quantization: Loop. This means stop playing when the loop reaches its end.

    Event 2: Solo break (2 bar loop)
    Timing: After Last: 1 Bar quantization. This means that the event happen should happen precisely at the next bar boundary. Since the previous event ends on a bar boundary it will fire immediately and precisely on time.

    The quantization on this event is 1 bar. Ensures that it starts and stops on a bar line.

    The break is set to Play Once. So, it plays once only.

    Event 3: Solo Chorus - 8 bar loop
    Timing: 2 bars after last event. This means that the event will happen 2 bars after the Solo Brea event starts.

    Quantization: left to the default (which is loop). It means it will stop on a loop boundary. In some cases, the play quantization might need to be 1 or 2 bars instead.

    It is also set to play once.

    Event 4: Play Verse (8 bar clip
    Timing:: 8 bars after last. This starts it 8 barse after Chorus started.

  • VyacheslavVyacheslav

    @espiegel123 said:
    @Vyacheslav: here is a more detailed explanation of the settings in the sequence I posted.

    Event 1: Stop Verse loop. Stop Quantization: Loop. This means stop playing when the loop reaches its end.

    Event 2: Solo break (2 bar loop)
    Timing: After Last: 1 Bar quantization. This means that the event happen should happen precisely at the next bar boundary. Since the previous event ends on a bar boundary it will fire immediately and precisely on time.

    The quantization on this event is 1 bar. Ensures that it starts and stops on a bar line.

    The break is set to Play Once. So, it plays once only.

    Event 3: Solo Chorus - 8 bar loop
    Timing: 2 bars after last event. This means that the event will happen 2 bars after the Solo Brea event starts.

    Quantization: left to the default (which is loop). It means it will stop on a loop boundary. In some cases, the play quantization might need to be 1 or 2 bars instead.

    It is also set to play once.

    Event 4: Play Verse (8 bar clip
    Timing:: 8 bars after last. This starts it 8 barse after Chorus started.

    Thank you!

Sign In or Register to comment.

© Vanilla Keystone Theme 2024