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.

New AUv3 MIDI App: ScaleBud

24567

Comments

  • @cem_olcay said:

    @JudgeDredd said:
    As an AU, I kind of expected to be able to have more than one working instance. Did I miss something?

    You can actually, at least in AUM.

    I have tried to get this to work in AUM and can't. I have the first instance of ScaleBud playing Mood and that works great. I have the second instance of ScaleBud trying to play iSem or any other synth and no sound. I have check the MIDI route and everything is where it should be.

    Can others get this to work?

  • @JudgeDredd said:

    @cem_olcay said:

    @JudgeDredd said:
    As an AU, I kind of expected to be able to have more than one working instance. Did I miss something?

    You can actually, at least in AUM.

    I have tried to get this to work in AUM and can't. I have the first instance of ScaleBud playing Mood and that works great. I have the second instance of ScaleBud trying to play iSem or any other synth and no sound. I have check the MIDI route and everything is where it should be.

    Can others get this to work?

    i’m having the same issue. the first instance e of scalebud works fine. but the second does nothing, no matter how
    it’s routed. probably just a little glitch.

  • @eross said:

    @JudgeDredd said:

    @cem_olcay said:

    @JudgeDredd said:
    As an AU, I kind of expected to be able to have more than one working instance. Did I miss something?

    You can actually, at least in AUM.

    I have tried to get this to work in AUM and can't. I have the first instance of ScaleBud playing Mood and that works great. I have the second instance of ScaleBud trying to play iSem or any other synth and no sound. I have check the MIDI route and everything is where it should be.

    Can others get this to work?

    i’m having the same issue. the first instance e of scalebud works fine. but the second does nothing, no matter how
    it’s routed. probably just a little glitch.

    I just tested, and get the same issue in ape matrix.

  • Alright, I'm on it, thanks for the heads up.
    I'll add glissando mode as well, for locking the keyboard scroll..

  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • The user and all related content has been deleted.
  • @ImortalTrashcan said:

    @cem_olcay said:
    Thanks! I'm in for every idea :)

    @ImortalTrashcan said:
    This is a great little AU

    I was playing around with it in AUM and was having trouble with my midi keyboard not playing the black keys in ScaleBud. After looking at the standalone to confirm a bug, I don’t see a midi in option. Was midi in intended in AUv3?

    Either way, thanks for another great app to play with!

    You were probably in the c major scale, which is the default scale when you open the app. Since it has no accidentals, it filters out the black keys in the c major scale. You can use the settings menu in standalone mode for controlling MIDI Outputs you want to send MIDI to.

    Here’s what I’m experiencing. I forgot to do it in the video but the keys in Scalebud all work, it’s just when I’m using midi in. I’m on an IPhone 8plus iOS 11.4

    @ImortalTrashcan, The new 1.0.1 update just released with the fix.

    @tja, that's strange, I'm on it, thanks.

  • Just tested it out, works great. Thanks for the quick response on the bug! Time to mix in some rozetta.

  • @coolout said:
    Also, ScaleBud isn't showing up in Cubasis for me. AUM yes....Cubasis not at all. I tried a full reboot still no dice.

    Cubasis released a new 2.4 update. Can you try ScaleBud with new Cubasis v2.4?

  • edited July 2018

    Cubasis is on 2.5. And I don’t see it either.

  • This is a really cool app. I am using it with app like Chordflow to force the note to the right scale but also to find which scale give the best results in a very fast and easy way. Congrats dev!!

  • Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

  • The user and all related content has been deleted.
  • @tja said:

    @cuscolima said:
    This is a really cool app. I am using it with app like Chordflow to force the note to the right scale but also to find which scale give the best results in a very fast and easy way. Congrats dev!!

    Could you possibly elaborate on this?

    In fact it is really easy. Chordflow is sending Midi to Scalebud and Scalebud is sending midi to a synth (Sunrizer here). Just start Chordflow and change the scale as you like in Scalebud. You can really discover interesting unusual sonorities using special scales


  • Is this app like Rozeta Scalar then but with integrated keyboard and more scales?

  • The user and all related content has been deleted.
  • @gusgranite said:
    Is this app like Rozeta Scalar then but with integrated keyboard and more scales?

    Yes, it is very much like Rozeta Scalar with the addition of chords mode.

  • @cuscolima this is amazing, I love it when people use my apps in such creative ways that I couldn't ever imagine :)

    @studioAB I made a very quick video that shows the AUM midi routing screen. You basically need to route ScaleBud MIDI Out to the synth you want to control. You can check out the AUM screenshot above as well, which includes an AUM MIDI Routing screen.

  • @cem_olcay Thanks for the reply and video. It works great in AUM, I need some help with Cubasis routing.

  • I think I’ve found another bug. I was playing around with 2 instances of ScaleBud in AUM and the second one didn’t seem to be receiving or sending midi. I made another quick video. IPhone 8plus iOS 11.4.

  • @ImortalTrashcan Yes it's working as a single-instance app right now for both Audiobus MIDI and AUv3.
    I'll add multi-instance support soon.

  • @cem_olcay said:
    @ImortalTrashcan Yes it's working as a single-instance app right now for both Audiobus MIDI and AUv3.
    I'll add multi-instance support soon.

    @cem_olcay said:
    @ImortalTrashcan Yes it's working as a single-instance app right now for both Audiobus MIDI and AUv3.
    I'll add multi-instance support soon.

    Gotcha. Thanks!

  • wimwim
    edited July 2018

    @studioAB said:
    Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

    This is indeed confusing. With Cubasis the usual way you would use an AUv3 midi effect is to load it into the same channel as a midi effect. But it doesn’t show up as a midi effect.

    It shows up as an AUv3 instrument, but routing from one track to another in Cubasis isn’t possible, and I don’t think you can route AUv3 midi out and back in through Core Midi.

    It is possible to get it working not as an AUv3 like this:

    • Load it as an IAA instrument on another track
    • Go to the settings in the app and enable Cubasis as a midi output
    • In the midi routing for the Cubasis channel, enable All MIDI Ports for midi output
    • In the Zeeon track midi routing enable Virtual Midi for the input.

    It shouldn’t need to be like this though, and defeats the purpose of it being an AUv3 midi effect as far as Cubasis goes.

    Nice app though. B)

  • @cem_olcay said:
    @cuscolima this is amazing, I love it when people use my apps in such creative ways that I couldn't ever imagine :)

    @studioAB I made a very quick video that shows the AUM midi routing screen. You basically need to route ScaleBud MIDI Out to the synth you want to control. You can check out the AUM screenshot above as well, which includes an AUM MIDI Routing screen.

    quick technical question. how/where do you load your videos on here? I tried the other day but couldnt

  • Well, forum does not accept .mov files, so I make a gif from my .mov video that I captured with quicktime. You simply drag and drop your video/gif to the text box you write your answers, for uploading. Or press the document icon above the text box.

  • @wim said:

    @studioAB said:
    Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

    This is indeed confusing. With Cubasis the usual way you would use an AUv3 midi effect is to load it into the same channel as a midi effect. But it doesn’t show up as a midi effect.

    It shows up as an AUv3 instrument, but routing from one track to another in Cubasis isn’t possible, and I don’t think you can route AUv3 midi out and back in through Core Midi.

    It is possible to get it working not as an AUv3 like this:

    • Load it as an IAA instrument on another track
    • Go to the settings in the app and enable Cubasis as a midi output
    • In the midi routing for the Cubasis channel, enable All MIDI Ports for midi output
    • In the Zeeon track midi routing enable Virtual Midi for the input.

    It shouldn’t need to be like this though, and defeats the purpose of it being an AUv3 midi effect as far as Cubasis goes.

    Nice app though. B)

    OK, there is a catch. ScaleBud is an only AUv3 MIDI app. So, it does nothing with audio or sound processing. But, in order to get them in App Store we need to register them to system like audio AUv3 apps or Apple simply rejects them. So, there is a chance that it show up in audio AUv3 section but not in midi auv3 section. I'm not a Cubasis user, so I don't know the tricks but keep in mind. In AUM it works as expected.
    Thanks, I'm glad you liked it :)

  • wimwim
    edited July 2018

    @cem_olcay said:

    @wim said:

    @studioAB said:
    Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

    This is indeed confusing. With Cubasis the usual way you would use an AUv3 midi effect is to load it into the same channel as a midi effect. But it doesn’t show up as a midi effect.

    It shows up as an AUv3 instrument, but routing from one track to another in Cubasis isn’t possible, and I don’t think you can route AUv3 midi out and back in through Core Midi.

    It is possible to get it working not as an AUv3 like this:

    • Load it as an IAA instrument on another track
    • Go to the settings in the app and enable Cubasis as a midi output
    • In the midi routing for the Cubasis channel, enable All MIDI Ports for midi output
    • In the Zeeon track midi routing enable Virtual Midi for the input.

    It shouldn’t need to be like this though, and defeats the purpose of it being an AUv3 midi effect as far as Cubasis goes.

    Nice app though. B)

    OK, there is a catch. ScaleBud is an only AUv3 MIDI app. So, it does nothing with audio or sound processing. But, in order to get them in App Store we need to register them to system like audio AUv3 apps or Apple simply rejects them. So, there is a chance that it show up in audio AUv3 section but not in midi auv3 section. I'm not a Cubasis user, so I don't know the tricks but keep in mind. In AUM it works as expected.
    Thanks, I'm glad you liked it :)

    Well ... I’m confused then. The Rozeta suite processes no audio, yet those plugins show up in Cubasis’ AUv3 plugin list and work perfectly. I think there must be something that is different about how you’ve approached it. Not a big deal for me since there’s a workaround, but you may want to look into it with either @LFS or @brambos in order to reduce the confusion on part of users.

  • @wim said:

    @cem_olcay said:

    @wim said:

    @studioAB said:
    Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

    This is indeed confusing. With Cubasis the usual way you would use an AUv3 midi effect is to load it into the same channel as a midi effect. But it doesn’t show up as a midi effect.

    It shows up as an AUv3 instrument, but routing from one track to another in Cubasis isn’t possible, and I don’t think you can route AUv3 midi out and back in through Core Midi.

    It is possible to get it working not as an AUv3 like this:

    • Load it as an IAA instrument on another track
    • Go to the settings in the app and enable Cubasis as a midi output
    • In the midi routing for the Cubasis channel, enable All MIDI Ports for midi output
    • In the Zeeon track midi routing enable Virtual Midi for the input.

    It shouldn’t need to be like this though, and defeats the purpose of it being an AUv3 midi effect as far as Cubasis goes.

    Nice app though. B)

    OK, there is a catch. ScaleBud is an only AUv3 MIDI app. So, it does nothing with audio or sound processing. But, in order to get them in App Store we need to register them to system like audio AUv3 apps or Apple simply rejects them. So, there is a chance that it show up in audio AUv3 section but not in midi auv3 section. I'm not a Cubasis user, so I don't know the tricks but keep in mind. In AUM it works as expected.
    Thanks, I'm glad you liked it :)

    Well ... I’m confused then. The Rozeta suite processes no audio, yet those plugins show up in Cubasis’ AUv3 plugin list and work perfectly. I think there must be something that is different about how you’ve approached it. Not a big deal for me since there’s a workaround, but you may want to look into it with either @LFS or @brambos in order to reduce the confusion on part of users.

    Yeah sure, that would be great! I'm waiting for the next month to purchase Cubasis, I'm an indie dev, you know.. ¯_(ツ)_/¯
    At least I can promise you I'll release an update with fixes soon.

    BTW, version 1.0.2 released and now you can use MIDI keyboard mapping/filtering with standalone mode.
    Check out the settings menu, now you can open MIDI input ports for receiving MIDI and you can send mapped/filtered MIDI data to your selected MIDI outputs.

  • @cem_olcay said:

    @wim said:

    @cem_olcay said:

    @wim said:

    @studioAB said:
    Congratulations on the app, @cem_olcay. It is working nicely in AUM. It shows up for me in Cubasis as an AU, latest version of Cubasis, iOS 11.4, but I need some help with the routing as it's not straightforward as in AUM. I'm trying to control Zeeon with it. Zeeon is on track 1, Scalebud is on track 2. Thanks for any help.

    This is indeed confusing. With Cubasis the usual way you would use an AUv3 midi effect is to load it into the same channel as a midi effect. But it doesn’t show up as a midi effect.

    It shows up as an AUv3 instrument, but routing from one track to another in Cubasis isn’t possible, and I don’t think you can route AUv3 midi out and back in through Core Midi.

    It is possible to get it working not as an AUv3 like this:

    • Load it as an IAA instrument on another track
    • Go to the settings in the app and enable Cubasis as a midi output
    • In the midi routing for the Cubasis channel, enable All MIDI Ports for midi output
    • In the Zeeon track midi routing enable Virtual Midi for the input.

    It shouldn’t need to be like this though, and defeats the purpose of it being an AUv3 midi effect as far as Cubasis goes.

    Nice app though. B)

    OK, there is a catch. ScaleBud is an only AUv3 MIDI app. So, it does nothing with audio or sound processing. But, in order to get them in App Store we need to register them to system like audio AUv3 apps or Apple simply rejects them. So, there is a chance that it show up in audio AUv3 section but not in midi auv3 section. I'm not a Cubasis user, so I don't know the tricks but keep in mind. In AUM it works as expected.
    Thanks, I'm glad you liked it :)

    Well ... I’m confused then. The Rozeta suite processes no audio, yet those plugins show up in Cubasis’ AUv3 plugin list and work perfectly. I think there must be something that is different about how you’ve approached it. Not a big deal for me since there’s a workaround, but you may want to look into it with either @LFS or @brambos in order to reduce the confusion on part of users.

    Yeah sure, that would be great! I'm waiting for the next month to purchase Cubasis, I'm an indie dev, you know.. ¯_(ツ)_/¯
    At least I can promise you I'll release an update with fixes soon.

    BTW, version 1.0.2 released and now you can use MIDI keyboard mapping/filtering with standalone mode.
    Check out the settings menu, now you can open MIDI input ports for receiving MIDI and you can send mapped/filtered MIDI data to your selected MIDI outputs.

    @cem_olcay Thanks for midi imput that’s great.

Sign In or Register to comment.