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.

DRAMBO 2.0 is LIVE!!!

1171820222361

Comments

  • Side thought: MidiFire can host Mozaic and also handle in/out routing duties for Drambo. You might be able to concoct some elegant way to support what you want to do with it @AlmostAnonymous .

  • @cian said:

    @AlmostAnonymous said:
    @rs2000 so its not as simple as dropping a midi output on a track and routing it output back to the main track?

    If the workaround is run streambyter in the background, then I would just do that at the coreMIDI level before it goes to drambo and grab it on the way out as well. Rewriting 1000-line mozaic scripts in streambyter isnt gonna be fun (especially when i dont know it). Maybe Mozaic standalone, which will have its own issues (like only being able to run 1 script standalone).

    I guess the other option is to host drambo in something else and figure it out in that host, but thats a whole different issue (and nothing to do with the MIDI).

    https://apps.apple.com/us/app/midiflow/id879915554

    That's worked for me previously. You can also do this kind of stuff in Mozaic relatively easily, so you don't have to use Streambyter.

    I've used midiflow before. The issue here is the scripts aren't just translating and routing. Theyre exchanging large amounts of sysex to control lighting, encoder switching, encoder updates, etc for hardware.

  • @wim said:
    Side thought: MidiFire can host Mozaic and also handle in/out routing duties for Drambo. You might be able to concoct some elegant way to support what you want to do with it @AlmostAnonymous .

    This is where I was going with the coreMIDI thing, but i didnt know midifire could do mozaic. Thought it might have only been streambyter scripts (thus the rewrites). I only messed around with it briefly in the past. Bome Network Pro took care of most of my midi routing/duplicating/etc (no scripts), but it appears my setups are outgrowing it.

  • edited May 2022

    @rs2000 said:
    @AlmostAnonymous
    No!
    You can keep using Mozaic, Streambyter running as a standalone in the background will do nothing but mirror incoming MIDI to its own virtual MIDI port that can be used as an input in Drambo. As you can see in my screenshots.

    ah...now I follow. That very well might work. Merci. I'll give it a go. I probably should rethink my midi routing needs and see if I can handle most of it in midifire before it even reaches host apps.

  • have a 4th post too :p

  • edited May 2022

    @sigma79 said:

    @giku_beepstreet said:
    Finally! It took so long. Downloading!

    .

  • edited May 2022

    @Samu said:
    MPE = MidiPlaguE

    More Pointless Expression
    MIDI Puke Explosion
    My Prog-rock Experiment
    Multi-Port Excrement
    Must Purchase Everything
    Mediocre Performance Enhancer
    Musician's Penis-Envy
    Merlin's Penis Enchantment
    Man-splained Painful Exegesis
    Machismo Puerile Emotion
    MusicRadar's Platinum Endorsement

    (Sorry.. i got a bit carried away there!)

  • Obviously not a complete design as I skipped synth four.

  • wimwim
    edited May 2022

    deleted - wrong thread.

  • edited May 2022

    @wim said:

    @sigma79 said:
    Obviously not a complete design as I skipped synth four.

    Probably in the grubby hands of an App Store reviewer.

    Right wim.

    My crazy setup though. Just for an effect. Another ipad, audio 4c and faderfox pc12.

    Mad.

  • The £1400 effect lol.

  • @Samu said:
    MPE = MidiPlaguE

    MPE = Modwheelx3 Per Eachfingertip

  • @CapnWillie said:

    @Stuntman_mike said:

    @CapnWillie said:

    @Stuntman_mike said:
    …It might be cool to work with a hardware company like Intech to make modules that snap together to control Drambo. I mean Intech has some modules ready to go now. Perhaps Drambo’s modules could inspire new Intech modules. Heck maybe Drambo could double as an Intech editor on iOS one day!

    https://intech.studio/

    How are those working out for you?

    I actually didn’t buy any because I already have Midi Fighter 3D and Twister along with a Korg nanoKONTROL2. I can honestly see a hardware developer making a controller for Drambo one day! Something with buttons, knobs, pads, crossfader and keyboard. The layout to some degree mirroring Drambo’s. 64 pads/step sequencer with MPE. Dreaming 🛌

    Ahh I see. Wish I could find someone who can personally speak to Intech’s quality. It looks like it would be pretty simple to create the controller you speak of out of configuring intechs modular pads, faders and knobs into the perfect portabl control surface. Price and looks are right. Do they deliver though?🤔🥴

    They are always active on their FB, maybe try asking there?

  • @CapnWillie said:

    @Gravitas said:

    @CapnWillie said:

    @Stuntman_mike said:

    @CapnWillie said:

    @Stuntman_mike said:
    …It might be cool to work with a hardware company like Intech to make modules that snap together to control Drambo. I mean Intech has some modules ready to go now. Perhaps Drambo’s modules could inspire new Intech modules. Heck maybe Drambo could double as an Intech editor on iOS one day!

    https://intech.studio/

    How are those working out for you?

    I actually didn’t buy any because I already have Midi Fighter 3D and Twister along with a Korg nanoKONTROL2. I can honestly see a hardware developer making a controller for Drambo one day! Something with buttons, knobs, pads, crossfader and keyboard. The layout to some degree mirroring Drambo’s. 64 pads/step sequencer with MPE. Dreaming 🛌

    Ahh I see. Wish I could find someone who can personally speak to Intech’s quality. It looks like it would be pretty simple to create the controller you speak of out of configuring intechs modular pads, faders and knobs into the perfect portabl control surface. Price and looks are right. Do they deliver though?🤔🥴

    They are always active on their FB, maybe try asking there?

    Hey bro! Enjoying your Dram vids and meetup with @seonnthaproducer good stuff.💪🏽

    Glad you like the series. 😁🙏🏾

    By “do they deliver” i mean in terms of quality. I’m pretty sure i know what they’d tell me but i really want to hear from someone unbiased.

    Yeah, I had the same thought myself.
    The quality seems really good, they like to show that off on their FB page.

    There was a thread about them around here somewhere….I was hoping someone took the leap. I guess I’ll have to be the sacrificial lamb for the community.lol.

    I got another audio interface yesterday so it's up to you....😏

    Have you seen their offerings? Sexy right?

    Yup.
    They are cute...

  • edited May 2022

    .

  • edited May 2022

    @AlmostAnonymous said:

    @rs2000 said:
    @AlmostAnonymous
    No!
    You can keep using Mozaic, Streambyter running as a standalone in the background will do nothing but mirror incoming MIDI to its own virtual MIDI port that can be used as an input in Drambo. As you can see in my screenshots.

    ah...now I follow. That very well might work. Merci. I'll give it a go. I probably should rethink my midi routing needs and see if I can handle most of it in midifire before it even reaches host apps.

    I've just seen more of your requirements incl. sysex - Sorry to say that but on iOS, you might hit more than one roadblock, including limited size sysex messages (unless Apple have improved that in recent iOS versions, dunno).
    Yep, using MidiFire sounds like a good idea if you can get the MIDI part to work there.
    Drambo can even be hosted as a pure MIDI effect there.

  • edited May 2022

    @rs2000 i've hit no road bocks yet. the usual issue is the devices dont respond fast enough and i have to put delays in.
    my launchpad script is sending 18 value sysex arrays x 32 arrays right after each other...no problem with no delays. those are the largest ones i've been working with so far. i could probably go larger.

    and the more i thought about it today, the more midifire is making sense, especially hosting mozaic. if i can work all of the communication between the scripts and controllers before ever touching an app/host, and just route of everything out of midifire on a virtual port...i dont have to work around balancing that midi with a project template midi

  • @mikewb said:
    Something to help out Koala users inside of Drambo. Had a tough time getting the midi to record by just using the pads in Koala. Turns out midi route from the midi tools suite by Victor Porof right after Koala allows the midi to be recorded by using the pads within koala. In Koala midi settings midi map must be selected and everything else off. Not sure if there is a better way to achieve this with the Drambo modules but I couldn't get it to work.

    Speaking about Victor Porof (BlueVeek Atom Midi-developer) - he totally disappear from the stage?
    Victor has’nt logged in here on Audiobus-forum since july 2021 - what’s happening with him? Too much work?

    We miss you Victor!

  • @wim said:

    @el_bo said:

    @wim said:

    @el_bo said:

    @wim said:
    Midi Tape Recorder is already a totally free and https://github.com/gbevin/MIDITapeRecorder (Creative Commons license). So no problem there. But you’re right, some DAWs, including Drambo, have a more fundamental issue with not being able to record midi out from AU plugins in the first place.

    Thanks!

    I knew MTR was free, but didn't know about the licensing.

    I wonder what it is that is stopping certain DAW from being able to record MIDI out from AUv3. Which do?

    Time and resources no-doubt. A DAW is a hugely complicated piece of software and routing is deeply buried in the architecture. I'm sure it comes down to the developer's perceived importance of such a thing. The fact that just about every DAW has shipped out of the gate without the requisite routing to record AU Midi output backs that up. Unfortunately, if that aspect wasn't accounted for in the original architecture of the program, re-fitting it is likely a big job. Just maintaining a DAW for these individual developers or small teams, while trying to work in the never-ending pile of other feature requests, is as much as most can handle as it is.

    Thanks! At least it's not a limitation of AUv3, so there's hope ;)

    Anyway, I know this is off-top (And I'll really stop this line of questioning now), but can you think off the top of your head which DAW do allow it?

    No, not off the top of my head. Probably others can chime in on this.
    I can say with reasonable certainty that of those none can do full MPE recording with any accuracy though. And providing editing capability for MPE is a huge challenge technically and especially from a UI perspective.

    I think the reason that some DAWs don't record MIDI from plugins is to maintain a straightforward "signal path" and in some cases, they may have been designed before MIDI fx were a thing. The complication is that often we want to apply the midi fx to the incoming midi stream but don't want to record the output....we want to record the notes played on the keyboard and when we play the track back we want to apply the effect. That is pretty straightforward. The DAW doesn't have to treat the recording/monitoring any different than the playback. If we want to record the output of the effect then we need the DAW to record the effect output and then turn off the midi effect...because we rarely want to recursively apply the effect.

    None of that is insurmountable, but it just isn't super straightforward...especially if you didn't originally plan for it. The straightforward thing architecturally is to he able to route the output of a midi track to another midi track and have that output be post effect. But for some reason, a lot of apps didn't design that in and it may destabilize the architecture to add it in even if it seems like it should be straightforward.

  • @ErrkaPetti said:
    Speaking about Victor Porof (BlueVeek Atom Midi-developer) - he totally disappear from the stage?
    Victor has’nt logged in here on Audiobus-forum since july 2021 - what’s happening with him? Too much work?

    We miss you Victor!

    If I remember correctly, he works at google now or something.

  • @rs2000 said:
    @tahiche No. This use case wasn't a common request but indeed, step components could be enhanced.
    Would a "Length" slider on a Param Lock step component help?

    Yes it would!. Easy and straightforward. As I said, automation would cover it except for the random/cycle thing.
    It’s funny how use cases are so different. You might see something and think “why is this missing?. It’s so obvious!” When in reality no one else seems to care.

  • wimwim
    edited May 2022

    @tahiche said:
    It’s funny how use cases are so different. You might see something and think “why is this missing?. It’s so obvious!” When in reality no one else seems to care.

    Two words: Choke. Groups. :D
    I’ve given up on that quest.

  • edited May 2022

    @wim said:
    I can say with reasonable certainty that of those none can do full MPE recording with any accuracy though. And providing editing capability for MPE is a huge challenge technically and especially from a UI perspective.

    @rs2000 said:
    I remember the developer of Xequence 2 giving it a serious try long ago but he dropped it at some point.
    Too much work for too few people using it.

    @espiegel123 said:
    I think the reason that some DAWs don't record MIDI from plugins is to maintain a straightforward "signal path" and in some cases, they may have been designed before MIDI fx were a thing. The complication is that often we want to apply the midi fx to the incoming midi stream but don't want to record the output....we want to record the notes played on the keyboard and when we play the track back we want to apply the effect. That is pretty straightforward. The DAW doesn't have to treat the recording/monitoring any different than the playback. If we want to record the output of the effect then we need the DAW to record the effect output and then turn off the midi effect...because we rarely want to recursively apply the effect.

    None of that is insurmountable, but it just isn't super straightforward...especially if you didn't originally plan for it. The straightforward thing architecturally is to he able to route the output of a midi track to another midi track and have that output be post effect. But for some reason, a lot of apps didn't design that in and it may destabilize the architecture to add it in even if it seems like it should be straightforward.

    Ok...Thanks, guys!

    Seems like it's worth dropping the idea, for the moment. I guess MPE is still too early in it's infant-hood for developers to go crazy completely overhauling their apps for what might end up being a fad.

  • As I've said earlier, I'm no stranger to MPE. I use it with my desktop setup.

    The issue is not that MPE is standardised, but that it's not trivial to implement and so it's yet to gain any real traction in the iOS-world. And really, just because there is a standard protocol it doesn't mean that it won't eventually die out (There were presumably standards for implementing 3D on TV screens, but I've not seen one in a store for years).

    The problem in getting MPE off the ground is that the surfaces used to properly interact with it are still way too expensive. As such, it's gonna be much harder to sell the amounts necessary to get it into the hands of everyone, insuring it's longevity, Ironically, it's mobile tech that could lead the way forwards, in this regard, given it needs no other equipment than the tablet already owned.

    If you have any recommendations for solid iOS MPE implementation, perhaps I'll start a separate thread (Given Dr's currently limited implementation, it's off-topic)

    Cheers :)

  • is it possible me to send audio from Aum to be recorded into the flexisampler in Drambo?

  • @vasilymilovidov said:

    @ErrkaPetti said:
    Speaking about Victor Porof (BlueVeek Atom Midi-developer) - he totally disappear from the stage?
    Victor has’nt logged in here on Audiobus-forum since july 2021 - what’s happening with him? Too much work?

    We miss you Victor!

    If I remember correctly, he works at google now or something.

    So is Atom 2 abandoned?

  • edited May 2022

    @eross said:
    is it possible me to send audio from Aum to be recorded into the flexisampler in Drambo?

    Not exactly a pro but I would record to a Drambo ( mfx in aum effects slot ) Save as a project via the aum Drambo but save with samples option. Then open via drambo. You might then also have sequence triggers also. If made via aums drambo but you might be able to route aum output?

  • @sigma79 said:

    @eross said:
    is it possible me to send audio from Aum to be recorded into the flexisampler in Drambo?

    Not exactly a pro but I would record to a Drambo ( mfx in aum effects slot ) Save as a project via the aum Drambo but save with samples option. Then open via drambo. You might then also have sequence triggers also. If made via aums drambo but you might be able to route aum output?

    i’ll try it out. now that i’m thinking of it, it might just be easier to record an audio file i. AUM and just import that into flexi sampler

  • Inspired by @echoopera’s excellent video from the other day, I've started a new YouTube series called 'Let's Beepity Boop'. In this, I get 10 minutes to improvise a track. Obviously I'm starting with a few vids on Drambo and this is the first. The aim is to show off various aspects of Drambo's workflow and create something... not totally shit? No talking after the tiny intro, just some beepity boops!

    Who knows - after 50 of these, I might start making some good music...

Sign In or Register to comment.