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.

Can you replicate this Drambo bug?

edited October 2023 in General App Discussion

(Tried to post in beepstreet forum, but getting “forbidden access error” when posting there atm, @giku_beepstreet)

  1. Start new default project
  2. Select Main track, clip in first row of clip matrix, properties, set speed to 1/4.
  3. Select clip to the right (track 1 clip), properties, set speed to 1/4.
  4. Select first clip again (to the left). Now the length has suddenly jumped from 16 steps to 64 steps.

Comments

  • edited October 2023

    I was in general experiencing a lot of unstable clip length jumping around when trying to set up a project where each scene row is one step longer than the preceding row. It seemed to happen in an almost random fashion, but the above is hopefully a minimal reproducible example.

  • @bleep said:
    I was in general experiencing a lot of unstable clip length jumping around when trying to set up a project where each scene row is one step longer than the preceding row. It seemed to happen in an almost random fashion, but the above is hopefully a minimal reproducible example.

    If I stick to only Track 1 clips without touching any other columns, then I do manage to set up the clips to have speed 1/4 and each row has a length which is 1 step longer, for track 1.
    Tracks 2-8 are unaffected by this, but Main track (still on speed 1) has got all its lengths modified; 16, 20, 24, 28, …

  • edited October 2023

    @bleep said:
    (Tried to post in beepstreet forum, but getting “forbidden access error” when posting there atm, @giku_beepstreet)

    1. Start new default project
    2. Select Main track, clip in first row of clip matrix, properties, set speed to 1/4.
    3. Select clip to the right (track 1 clip), properties, set speed to 1/4.
    4. Select first clip again (to the left). Now the length has suddenly jumped from 16 steps to 64 steps.

    Confirmed. I just reproduced that in the current beta version.

    So what I think is happening here, is Drambo is adjusting those steps to 64 because you changed the speed to 1/4. Now those clips are only 1/4 the speed and they have to have 64 steps to run alongside everything else which is still running at the normal speed.
    (Like if you changed the speed to 1/2, it will probably adjust those steps to 32)

    There’s a number of strange behaviors like that, that can be reproduced by playing with those two menus (the clip menu, and the pattern menu).

    Edit: I said “strange behaviors”, but is it really strange? If you think about it, it’s really kind of expected behavior because we are changing the speed of only one clip, and everything else has to compensate right?

  • Hey while we’re at it, do me a favor and try this (just for fun!)

    Start a new project, default settings.

    Go to the first track, first clip. Maximize the steps to 256 by using the multiply and/or the “+Bar” buttons. Then set the speed down to 1/64th.

    Now go look at the step count in the Main track’s first clip.

    How many steps does it show?

  • 16384!

    It is 256 * 64 = 16384. You can do some serious amount of P-locking here.

    I don't think "everything else has to compensate" - the other tracks don't do that. I think they can all run at different lengths and speed, which is fitting for a modular environment. Should the Main track behave differently? I think it is a bug, but I could be wrong.

  • edited October 2023

    Yep, 16384. I’m doing all my sequencing like this from now on.
    Drambo becomes quite slow at switching tracks, though

  • @bleep said:
    16384!

    It is 256 * 64 = 16384. You can do some serious amount of P-locking here.

    I don't think "everything else has to compensate" - the other tracks don't do that. I think they can all run at different lengths and speed, which is fitting for a modular environment. Should the Main track behave differently? I think it is a bug, but I could be wrong.

    Well, yeah nothing “has to” compensate, but I guess some things “try” to.

    So you’re using the AppStore version and not the beta right?

  • @pedro said:
    Yep, 16384. I’m doing all my sequencing like this from now on.
    Drambo becomes quite slow at switching tracks, though

    lol right! It sure does 😆

  • @Edward_Alexander said:

    @bleep said:
    16384!

    It is 256 * 64 = 16384. You can do some serious amount of P-locking here.

    I don't think "everything else has to compensate" - the other tracks don't do that. I think they can all run at different lengths and speed, which is fitting for a modular environment. Should the Main track behave differently? I think it is a bug, but I could be wrong.

    Well, yeah nothing “has to” compensate, but I guess some things “try” to.

    So you’re using the AppStore version and not the beta right?

    Yeah, I don't have access to the beta.
    Btw, if you have beta then can you also use the AppStore version? I have always wondered about that.

  • @bleep said:

    @Edward_Alexander said:

    @bleep said:
    16384!

    It is 256 * 64 = 16384. You can do some serious amount of P-locking here.

    I don't think "everything else has to compensate" - the other tracks don't do that. I think they can all run at different lengths and speed, which is fitting for a modular environment. Should the Main track behave differently? I think it is a bug, but I could be wrong.

    Well, yeah nothing “has to” compensate, but I guess some things “try” to.

    So you’re using the AppStore version and not the beta right?

    Yeah, I don't have access to the beta.
    Btw, if you have beta then can you also use the AppStore version? I have always wondered about that.

    I don’t think so. If I try to download the AppStore version, it asks me if I want to leave the beta.

  • wimwim
    edited October 2023

    @Edward_Alexander said:

    @bleep said:

    @Edward_Alexander said:

    @bleep said:
    16384!

    It is 256 * 64 = 16384. You can do some serious amount of P-locking here.

    I don't think "everything else has to compensate" - the other tracks don't do that. I think they can all run at different lengths and speed, which is fitting for a modular environment. Should the Main track behave differently? I think it is a bug, but I could be wrong.

    Well, yeah nothing “has to” compensate, but I guess some things “try” to.

    So you’re using the AppStore version and not the beta right?

    Yeah, I don't have access to the beta.
    Btw, if you have beta then can you also use the AppStore version? I have always wondered about that.

    I don’t think so. If I try to download the AppStore version, it asks me if I want to leave the beta.

    You should be able to go freely back and forth between the App Store version and the beta. I've never seen it cause "leaving" the beta in the sense of not being able to re-install the beta version.

    No telling what would happen to your projects though. I doubt you'd lose any files, but if you opened a beta project in the App Store version no telling what might happen if you saved it.

Sign In or Register to comment.