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.

MIDI sequencer in Audiobus.

I found myself many times in a situation where I'd load a drum machine and a synth ready for noodling and find that I need to load a sequencing app to drive the synth. This is even more true for AU apps as they always rely on a host sequencer as opposed to having their own in IAA.

This is probably AB4 we're talking about here but wouldn't it be great if midi implementation extended to relatively simple sequencing capabilities. Just a grid with the usual variables. Something like a drum grid with variable number beats per bar, something that would automatically connect on plugging in of a slave app.

Are there any reasons why it wouldn't be a good idea @Sebastian @Michael ?

Comments

  • Maybe, but I think it'll be better when AUv3 sequencers start rolling out, which you can then save in AB3 presets. The same for AUM. I think it'll help keep the host lean and you can decide which sequencer is best for each app.

  • Yes I did see it, cheers. I was thinking more of a native, integrated midi flow type of affair. Something that automatically slaves to the ab transport. Midi flow style iap would fare well me thinks.

  • @supadom said:

    Yes I did see it, cheers. I was thinking more of a native, integrated midi flow type of affair. Something that automatically slaves to the ab transport. Midi flow style iap would fare well me thinks.

    If it's better, I'd buy it too! :blush:

  • Well, I have just made a sequencer =) I’ll have a think about it

  • @Michael said:
    Well, I have just made a sequencer =) I’ll have a think about it

    Cool!!!

  • edited September 2017

    @Michael said:
    Well, I have just made a sequencer =) I’ll have a think about it

    Ride the wave!

    I hope it doesn't imply the need to adapt slave apps to utilise it otherwise it sounds like a compatibility nightmare.

    If using existing midi protocol should be a reasonably straightforward process.

    Especially because you've just built a sequencer so most of the work's already done! :)

    Synchronicity

  • @supadom said:
    I found myself many times in a situation where I'd load a drum machine and a synth ready for noodling and find that I need to load a sequencing app to drive the synth. This is even more true for AU apps as they always rely on a host sequencer as opposed to having their own in IAA.

    This is probably AB4 we're talking about here but wouldn't it be great if midi implementation extended to relatively simple sequencing capabilities. Just a grid with the usual variables. Something like a drum grid with variable number beats per bar, something that would automatically connect on plugging in of a slave app.

    Are there any reasons why it wouldn't be a good idea @Sebastian @Michael ?

    This is really what is missing from the AB/AUM workflow. All these AU synths don’t mean a thing if I can’t sequence them all whilst tinkering with the knobs. I can’t play 3 synths at the same time (I struggle with 1) and simultaneously knob twiddle. Modstep, to me, is too sophisticated and detracts from my creative flow when I’m “jamming”. It would make a huge difference if I could assign a (native) sequencer to each AU synth in AB3 or AUM. I think Chris Randall mentioned the nonsensical lack of sequencers in AUM and AB in a post a while back.

  • This is probably why I use IAA versions of Ripplemaker and Troublemaker along with the likes of Xynthesizr when jamming in AUM. Their native sequencers keep the workflow simple. Whilst AU apps like Zeeon aren’t getting as much use as they should.

  • can't have enough sequencers!

  • @supadom said:

    @Michael said:
    Well, I have just made a sequencer =) I’ll have a think about it

    Ride the wave!

    I hope it doesn't imply the need to adapt slave apps to utilise it otherwise it sounds like a compatibility nightmare.

    If using existing midi protocol should be a reasonably straightforward process.

    Especially because you've just built a sequencer so most of the work's already done! :)

    Synchronicity

    @Michael Do this after finishing Loopy Pro, please!

    I have several options for generating MIDI in AB3 (including the brambos stuff) and I suspect we will see even more various AB3 midi sequencers popping up soon enough.

  • @lukesleepwalker said:

    @supadom said:

    @Michael said:
    Well, I have just made a sequencer =) I’ll have a think about it

    Ride the wave!

    I hope it doesn't imply the need to adapt slave apps to utilise it otherwise it sounds like a compatibility nightmare.

    If using existing midi protocol should be a reasonably straightforward process.

    Especially because you've just built a sequencer so most of the work's already done! :)

    Synchronicity

    @Michael Do this after finishing Loopy Pro, please!

    I have several options for generating MIDI in AB3 (including the brambos stuff) and I suspect we will see even more various AB3 midi sequencers popping up soon enough.

    I think there might be a dedicated midi flow coder already ;)

  • Well I‘d like to build one, but the „problem“ with AUs is that their parameter changes are not sent via MIDI to the host, but via the Audio Unit API. An Audiobus MIDI filter behind such an AU would not receive any parameter data that it could record. So, the AB app has to be the sequencer. An external app can’t do this with the current Aufiobus SDK. Right @Michael ?

  • Yep, sounds right to me, @JohannesD

  • edited September 2017

    @JohannesD said:
    Well I‘d like to build one, but the „problem“ with AUs is that their parameter changes are not sent via MIDI to the host, but via the Audio Unit API. An Audiobus MIDI filter behind such an AU would not receive any parameter data that it could record. So, the AB app has to be the sequencer. An external app can’t do this with the current Aufiobus SDK. Right @Michael ?

    Any chance you could create a more randomizing tool like the Ableton Random tool for generating more interesting probabilities during sequencing. I love all your tools but the Randomizing one you currently have isn’t quite cutting it for me. Any chance you could update it with a Percentile Probability of a note actually playing to the value sets in there now.

    Thanks in advance.

  • @supadom said:
    I found myself many times in a situation where I'd load a drum machine and a synth ready for noodling and find that I need to load a sequencing app to drive the synth. This is even more true for AU apps as they always rely on a host sequencer as opposed to having their own in IAA.

    This is probably AB4 we're talking about here but wouldn't it be great if midi implementation extended to relatively simple sequencing capabilities. Just a grid with the usual variables. Something like a drum grid with variable number beats per bar, something that would automatically connect on plugging in of a slave app.

    Are there any reasons why it wouldn't be a good idea @Sebastian @Michael ?

    Good idea. But both step sequencer and notation a la Symphonix EV, would be great.

  • Yeah I imagine Audiobus would need updating to allow proper AU sequencer support. Jonatan is always asked to build one into AUM but I think he plans to build a sequencer which is compatible but also independent. Seems to make most sense to me so you can use it with different hosts if you want :)

  • @JohannesD said:
    Well I‘d like to build one, but the „problem“ with AUs is that their parameter changes are not sent via MIDI to the host, but via the Audio Unit API. An Audiobus MIDI filter behind such an AU would not receive any parameter data that it could record. So, the AB app has to be the sequencer. An external app can’t do this with the current Aufiobus SDK. Right @Michael ?

    I think with ideas like this it is very hard to set boundaries and stick to them. I've imagined something as simple as just a note sequencer but of course once tha is done one would expect CC sequencing which could be made more straightforward using midi learn which would cut out modstep style CC templates. I.e. Wait for the next incoming midi message within AB environment and assign actions to it.

    As you've said it would require mid to travel via both regular midi and AU protocol. I don't know the exact technical ins and outs but user experience should definitely be on top of the list. There's too many amazing sequencers that are basically as complex as flying an airliner. I think it doesn't have to be like that.

  • edited September 2017

    Ok, I thought a bit more about this and....

    I thought that it would be great if the experience was similar to the one in Gadget I.e.

    a. Open AB and load a preset

    c. set the tempo/ loop length

    d. arm recording and press play.

    e. once notes are recorded move to record automation on the fly

    Is this a distant dream or is there a fair chance this could actually make it into beta reasonably soon? I think this might just move AB from mixer territory to a live daw territory. Whether you want that to happen or not, that's another story ;)

  • @supadom said:
    Ok, I thought a bit more about this and....

    I thought that it would be great if the experience was similar to the one in Gadget I.e.

    a. Open AB and load a preset

    c. set the tempo/ loop length

    d. arm recording and press play.

    e. once notes are recorded move to record automation on the fly

    Is this a distant dream or is there a fair chance this could actually make it into beta reasonably soon? I think this might just move AB from mixer territory to a live daw territory. Whether you want that to happen or not, that's another story ;)

    Aren't you describing a MIDI generator with really good, simple UX? It's just that nobody has created this yet...

  • @lukesleepwalker said:

    @supadom said:
    Ok, I thought a bit more about this and....

    I thought that it would be great if the experience was similar to the one in Gadget I.e.

    a. Open AB and load a preset

    c. set the tempo/ loop length

    d. arm recording and press play.

    e. once notes are recorded move to record automation on the fly

    Is this a distant dream or is there a fair chance this could actually make it into beta reasonably soon? I think this might just move AB from mixer territory to a live daw territory. Whether you want that to happen or not, that's another story ;)

    Aren't you describing a MIDI generator with really good, simple UX? It's just that nobody has created this yet...

    Yeah, something like a car that doesn't need a mechanic to drive ;)

  • audiobus with midi sequencer would be basically DAW :-)))

  • edited September 2017

    @dendy said:
    audiobus with midi sequencer would be basically DAW :-)))

    Yeah, a non linear live daw or a modular groovebox, no longer a router. Freakin amazing!

  • AU + MIDI = Headache/MiniHost

Sign In or Register to comment.