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.

"reached end of list" error message displaying before the last song is reached in the setlist

humbuckrhumbuckr
in Loopy Pro

I have 5 songs in a setlist. After I select the load project action of "next project in set list" from song 2, i get this message. When I hit previous I get the same message. seems to be a bug. Ideas?

Comments

  • espiegel123espiegel123

    @humbuckr said:
    I have 5 songs in a setlist. After I select the load project action of "next project in set list" from song 2, i get this message. When I hit previous I get the same message. seems to be a bug. Ideas?

    If you create a new set list from scratch that includes the same projects and update the actions in your widgets and midi bindings, does it happen?

  • humbuckrhumbuckr
    edited October 2025

    really dumb question.

    I created set list 1 using 4 projects A-Z. I created set list 2 with the same projects Z-A
    i then updated the previous and next actions to use set list 2

    Hitting previous next buttons still throws reached end of list error

    Would sure be nice to be able to see the name of the setlist at the top of the loopy app to the right of the play button

    Set List Name | Project Name

  • wimwim

    Can you clarify what the load next and previous actions are placed in? Buttons? Midi bindings? Both? A screenshot of the actions might help too.

  • humbuckrhumbuckr

    UPDATE: when i looked at the setlist view i saw an exclamation symbol next to one of the songs. Loopy lost its reference to project and once i located (the project never moved tho) the project again - the next and previous buttons are working.

    Is there a setting to avoid the confirmation when it asks to load a new project?

    would be a better UX to simply advance song to song with a single click

  • wimwim
    edited October 2025

    @humbuckr said:
    Is there a setting to avoid the confirmation when it asks to load a new project?

    It's the first setting (Confirm) at the top of the Load Project action.

  • humbuckrhumbuckr
    edited October 2025

    Thanks for help with set lists. These are working as intended with one intermittent issue

    I've configured the load project action so it loads the next project in lists and starts the clock. BUT I don't want the project to automatically begin to play. I have a play button that sets track level, tempo etc.

    Initially loopy did not start the project playing when I loaded the next project. Cool. But then some of the project in the setlist are playing immediately upon load and some are not. Head scratcher.

    Any ideas on why this is happening inconsistently?

    Thanks

  • espiegel123espiegel123

    @humbuckr said:
    Thanks for help with set lists. These are working as intended with one intermittent issue

    I've configured the load project action so it loads the next project in lists and starts the clock. BUT I don't want the project to automatically begin to play. I have a play button that sets track level, tempo etc.

    Initially loopy did not start the project playing when I loaded the next project. Cool. But then some of the project in the setlist are playing immediately upon load and some are not. Head scratcher.

    Any ideas on why this is happening inconsistently?

    Thanks

    The Load Project action had a start clock option. Make sure it is off.

  • humbuckrhumbuckr

    I understand. The issue I was having was that sometimes when start clock was selected the clock was enabled but the project wasn't playing until I hit my play button.

    I am now disabling the start clock like you suggest and using start clock in my play button

    Cheers

  • espiegel123espiegel123

    @humbuckr said:
    I understand. The issue I was having was that sometimes when start clock was selected the clock was enabled but the project wasn't playing until I hit my play button.

    I am now disabling the start clock like you suggest and using start clock in my play button

    Cheers

    If start clock was on but the transport was not starting that would be a bug—unless the project being opened was intentionally doing something to suppress the clock.

    If that is reproducible, I’d like to know details such as whether it was always with the same project.

  • humbuckrhumbuckr
    edited October 2025

    @espiegel123 said:

    If start clock was on but the transport was not starting that would be a bug—unless the project being opened was intentionally doing something to suppress the clock.

    If that is reproducible, I’d like to know details such as whether it was always with the same project.

    Interesting. Unfortunately I saved over the projects. Will see if I can reproduce as 90% of the projects did not play Until I hit play

  • espiegel123espiegel123
    edited October 2025

    @humbuckr said:

    @espiegel123 said:

    If start clock was on but the transport was not starting that would be a bug—unless the project being opened was intentionally doing something to suppress the clock.

    If that is reproducible, I’d like to know details such as whether it was always with the same project.

    Interesting. Unfortunately I saved over the projects. Will see if I can reproduce as 90% of the projects did not play Until I hit play

    Is it possible you hadn’t turned on the option to start the clock?

    Or that the projects themselves had something that stopped the clock in a follow action?

Sign In or Register to comment.