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

Help me solve this problem.
I have three groups of loops: verse (8 bars); bridge (2 bars); chorus (8 bars). The main group constantly playing is the verse.
You need to press a single key on a MIDI controller (or widget) to solo the bridge, then the chorus, and return to the verse.
No matter what I do, when I return to the verse group, it starts playing 2 bars earlier.
P.S. I apologize for my English, I'm using Google translator.

«13

Comments

  • @Vyacheslav said:
    Help me solve this problem.
    I have three groups of loops: verse (8 bars); bridge (2 bars); chorus (8 bars). The main group constantly playing is the verse.
    You need to press a single key on a MIDI controller (or widget) to solo the bridge, then the chorus, and return to the verse.
    No matter what I do, when I return to the verse group, it starts playing 2 bars earlier.
    P.S. I apologize for my English, I'm using Google translator.

    Please post screenshots of all relevant settings .

    A video demonstration would also be helpful

  • edited December 2023

    It seems that something is starting to work out, but it’s not working correctly, there is no synchronization when entering a command from MIDI.

  • edited December 2023








  • Sorry for the chaos, I'll add a video a little later.

  • I am having a little bit of a hard time following what is supposed to be happening and where it doesn’t do what you expect.

    At which step in your action sequence is the behavior different than you expect?

    What are the global play/stop quantization settings and what are the play stop quantization settings in the stop action?

  • @Vyacheslav said:
    It seems that something is starting to work out, but it’s not working correctly, there is no synchronization when entering a command from MIDI.

    What do you mean by this?

  • If you could annotate the screenshot and circle the point in the sequence where it doesn’t do what you expect and indicate the time in the video where it happens that might help.

    It also might help if you explain what you are trying to achieve step by step. Something like,

    • the green loop plays for x bars
    • Then the yellow loops should play for…

    Something like that. My guess is that it is related to the particular quantization settings and possibly the master cycle’s phase.

  • The two loops in the top row, yellow and blue, are 8 bars in size and rotate cyclically until a command is received from the MIDI controller. After the command is received, these loops stop and a pink loop is started, having a size of 2 measures, it is played once and stops, after it stops, the playback of two loops in the bottom row, yellow and blue, is started, which are 8 measures in size and are played once, then stop, and cyclic playback of the two upper loops, yellow and blue, starts back up.

    In the video, when you press the MIDI controller key again, a glitch occurs and you can see the playback (1:04) of a row of lower loops superimposed on a row of upper loops, there is no synchronization.

  • I deliberately left the sound in the video so that it would be clear where the overlap occurs.

  • @Vyacheslav said:
    I deliberately left the sound in the video so that it would be clear where the overlap occurs.

    How does that correspond to the action sequence in

    https://forum.audiob.us/uploads/editor/m6/ai639g9yskgx.png

    Does it always fail in the same place in that series of actions?

    Any chance that you can re-post the pictures so that they are in the order that corresponds to the action sequence and before each set of pictures for that action, use words to describe what should happen.

    As it is now the first picture is timing setting of action 3, the next is timing setting of action 2. So it is hard to follow.

    It would be best if everything related to the first action were together with a description of what should happen. Then a description of action 2 and its related pictures.

    One thing I notice from your description is that the underlying loop is 8 bars and you mention a a 2 bar part to be followed by an eight bar part which adds up to 2 bars. So it sounds like the eight-bar loop that plays third will move two bars farther out of sync each time the sequence plays.

    Is that intended?

    Also what is the master cycle length when this happens?

  • edited December 2023

    Crashes occur when the "solo" command is repeated for a 2-bar cycle, etc. This can be seen from the video at 1 min 04 sec. The main loop suddenly ends 2 bars earlier and everything else is shifted by 2 bars, shifting and superimposing one on top of the other.

    I'll try to repeat the explanations with pictures.

    Yes that's right. There is a shift of 2 bars. This is not intended. How can this be fixed?

    The length of the main loop depends on the command to "solo" the 2 bars part, after which the 8 bars part must be soloed and returns to playing the main 8 bars loop.

  • @Vyacheslav said:
    Crashes occur when the "solo" command is repeated for a 2-bar cycle, etc. This can be seen from the video at 1 min 04 sec. The main loop suddenly ends 2 bars earlier and everything else is shifted by 2 bars, shifting and superimposing one on top of the other.

    I'll try to repeat the explanations with pictures.

    Yes that's right. There is a shift of 2 bars. This is not intended. How can this be fixed?
    The length of the main loop depends on the command to "solo" the 2 bars part, after which the 8 bars part must be soloed and returns to playing the main 8 bars loop.

    What do you mean crashes? I don’t see a crash at 1:04.

    It seems like a it might be helpful to try to get each element working in series rather than tackle everything at once.

  • edited December 2023

    When sending the "solo" command, a failure occurs for 2 measures, this is visible and audible on the recording.

    I'll post pictures with explanations soon.

    And I'll make a more correct video

    1. The main loop 8 bars is played
    1. A “solo” command was received from the MIDI controller
    1. Solos a loop of 2 bars (play once)
    1. Solo cycles of 8 bars (play once)
    1. And the main loops are played again, until the next “solo” command from the MIDI controller
    1. The next command is “solo” from the MIDI controller. There is an offset from the main cursor by 2 bars.
    1. Fixed by restarting the entire project
  • Now, step by step setting up all commands

  • Timing Settings

Sign In or Register to comment.