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.

TROUBLEMAKER 1.2, now with 64 step sequencer

17810121320

Comments

  • edited January 2017

    Had a good play with this yesterday, and it's a great little thing. Also got me into using Figure and Link, things I'd been avoiding. With Link and some drum and synth apps this becomes a proper thing - though inevitably some linked apps (not Troublemaker) have a habit of dropping out (Lorentz I'm looking at you).

    The app's ease of use makes it perfect as a live instrument, but bass lines can grate after a minute on repeat, so need some filter movement and key changing to keep the listener interested. If you're not in the app at the time (you're mucking about mangling your ElasticDrums beats) the bass remains static, and if you initiate a key change in Figure, it isn't refelected in the baseline.

    So for me, to make the app even more perfect the following would make it more useful for live work:

    64 steps
    Song/scene mode (or automate key changes)
    Patch saving
    Option to randomise voice as well as sequence
    Lock sequence randomisation to a particular key
    Automation
    Undo

    I don't mean to sound negative or greedy - it's a superb app - but this would raise it to another level. Yes I can export wavs to a DAW and arrange them in that, but that takes all the fun and spontaneity out of the thing.

    But still a cracking addition to the toolbox.

  • The more I use this, the less I feel the need for more steps in the standalone app. I think Bram has hit on a very good workflow. Whip up a quick pattern, then export the MIDI. The exported MIDI is four loops long - just long enough to make changing up enough notes within the longer sequence to keep it interesting. It encourages me to get over to the DAW or sequencer quicker rather than staying buried in the app.

    Damn I love this thing!

  • It's very pleasant to feel unmitigated admiration and enjoyment with an app, for me this is rare, yet I am quite unreservedly delighted with this.

    Bassline PARTAAAAYYYYY!!

    @brambos , You Da Man/Person/Squid/[insert preferred being here]! :smiley:

  • Thanks for all the kind words, people. As I said before, this project has been quite close to my heart as this is something I've wanted to make even before I did Hammerhead (which will celebrate its 20th birthday later this year). I'm happy to hear it has landed well.

    Regarding the sequencer: I realize in an ideal world the sequencer and the synth would be identical in standalone and in plugin mode. But AUs are constrained to their narrow letterbox format (on phones it's even narrower than on iPads). I don't think trying to cram the sequencer into this strip would have done it justice, even with kludges like scrolling and panning etc. That's why I decided to give the sequencer the space it needs and offer a workflow into DAWs using the MIDI file export instead.

  • @brambos said:

    @constellation33x said:
    Here a screenshot from span frequency analyzer
    if you could get rid of that piercing high pitched tone this app would be a perfect 10!

    Found the little bugger. It was me trying to be nicer than a 303 :-D

    The 303 has free running oscillators, which can cause clicks and pops at low frequency tones because there is no attack in the envelopes. You can actually hear this in the TB-303 and its analog hardware clones. It didn't like these clicks so I smoothen the amp response a little bit, but accidentally introduced a tiny hint of zipper noise in the process, which is what you spotted.

    I'll be posting an update shortly.

    Thanks again for pointing it out, I wish I had golden ears like you ;-)

    Thats great news Bram!! Looking fwd to the update..
    Meanwhile i found out about ruismaker and snagged it up too.. your plugs are soo good!! love em! will have to get the other ones too.. did you know that ruismaker is flemish dialect for ruzie-maker, which in english is troublemaker.. and those 2 plugs work together just perfectly.. a kind of sequencer (+ability for poly-rhythms per sound) for ruismaker would be soo great (wishful thinking). Looking forward to your forthcoming creations! All the best!

  • @constellation33x said:
    did you know that ruismaker is flemish dialect for ruzie-maker, which in english is troublemaker.. and those 2 plugs work together just perfectly..

    I didn't know that, but that's an amazingly cool coincidence!

  • indeed, a very cool addition to the iOS music toolbox.
    the only odd thing about this app is we have sound presets in the au version but not in the standalone? or am I missing something? it makes sense that the au does not have pattern presets, but the standalone not having sound presets and no way to save and load patches, that seems really strange (unless it is there and I don't see it).

  • This thing sounds awesome and really good job on the interface! Probably the best of the different than basic keys interface ive used

  • Sequencers and arpeggiators seem to big casualty of AUv3. Even Poison 202 has disabled the ARP in plugin mode. None of the drum machine apps are likely to ever work in AU mode either. Looks like we were just lucky when iSem pulled it off with their ARP..I had thought it would be a new trend.

  • Looking forward to hearing some more demos of this in action. Has anyone been using Modstep with it yet? Seems like it would be a good fit with a template.

  • @eross said:
    patterns that can be played like a keyboard

    That's please the dubsteppers

    @MonzoPro said:
    Had a good play with this yesterday, and it's a great little thing. Also got me into using Figure and Link, things I'd been avoiding. With Link and some drum and synth apps this becomes a proper thing - though inevitably some linked apps (not Troublemaker) have a habit of dropping out (Lorentz I'm looking at you).

    The app's ease of use makes it perfect as a live instrument, but bass lines can grate after a minute on repeat, so need some filter movement and key changing to keep the listener interested. If you're not in the app at the time (you're mucking about mangling your ElasticDrums beats) the bass remains static, and if you initiate a key change in Figure, it isn't refelected in the baseline.

    So for me, to make the app even more perfect the following would make it more useful for live work:

    64 steps
    Song/scene mode (or automate key changes)
    Patch saving
    Option to randomise voice as well as sequence
    Lock sequence randomisation to a particular key
    Automation
    Undo

    I don't mean to sound negative or greedy - it's a superb app - but this would raise it to another level. Yes I can export wavs to a DAW and arrange them in that, but that takes all the fun and spontaneity out of the thing.

    But still a cracking addition to the toolbox.

    Spot on to my thinking too.....it is having the ability to mess with stuff so easily that makes these apps worthwhile (over and above the sound itself) a few additions and this thing will get constant use.

    I think it is testament to @brambos that we are asking for additions to the sequencer....it shows what a great job he has done with what he has given us :)

  • @brambos said:
    Thanks for all the kind words, people. As I said before, this project has been quite close to my heart as this is something I've wanted to make even before I did Hammerhead (which will celebrate its 20th birthday later this year). I'm happy to hear it has landed well.

    Regarding the sequencer: I realize in an ideal world the sequencer and the synth would be identical in standalone and in plugin mode. But AUs are constrained to their narrow letterbox format (on phones it's even narrower than on iPads). I don't think trying to cram the sequencer into this strip would have done it justice, even with kludges like scrolling and panning etc. That's why I decided to give the sequencer the space it needs and offer a workflow into DAWs using the MIDI file export instead.

    The right decision in my eyes :) The sequencer is really neat and a very simple and easy to use UI. I want all of my apps to have sequencers like this, or be able to use this sequencer with all of my apps....which is why the requests for longer pattern lengths etc are coming through :)

  • Exporting midi from Troublemaker into Cubasis works very well as an interim solution.

    Now let's hope Cubasis gets 'pattern aliases' or 'pattern loop' so we don't have to do copy&paste as it becomes a nightmare if the pattern needs to be changed...

    ModSTEP would be good option but it's not possible to send two 'tracks' to the same AUv3! (At least I've not found a way to do that). Meaning one track drives the note of an AUv3 and another controls the automation of the same AUv3...

  • edited January 2017

    @brambos said:

    @wim said:
    When I export a midi pattern, I'm not getting the note overlaps that would cause slides where I expect them. Is this by design?

    What are you using for opening the Midi pattern? The notes are overlapping a full 16th note length.

    Having this able to export pitch bend rather than using portamento would enable use of this sequencer (or at least the resultant MIDI) with synths that do not have Porta but do have PB (I'm thinking about sample player apps)....I know it's not the intended use of the sequencer, but that would make it very unique and an indespensible tool, perhaps an enhanced version of the host app that allows loading your desired AU along with the requested more steps....song mode/ scene switching......called MIDIMaker ? ;) ;) ;)

    @brambos Are you regretting yet showing us that you can make a great midi editing tool as well as great sounding sound generators ? :D

  • @Samu said:
    Exporting midi from Troublemaker into Cubasis works very well as an interim solution.

    Now let's hope Cubasis gets 'pattern aliases' or 'pattern loop' so we don't have to do copy&paste as it becomes a nightmare if the pattern needs to be changed...

    ModSTEP would be good option but it's not possible to send two 'tracks' to the same AUv3! (At least I've not found a way to do that). Meaning one track drives the note of an AUv3 and another controls the automation of the same AUv3...

    It's very easy if you host the AU in AUM. just send the output of the automation track and the notes track to the same midi channel e.g:- modstep channel 1. It's pretty much the reason why I mantain modstep+AUM is the best combo.

  • @Samu said:
    Exporting midi from Troublemaker into Cubasis works very well as an interim solution.

    Now let's hope Cubasis gets 'pattern aliases' or 'pattern loop' so we don't have to do copy&paste as it becomes a nightmare if the pattern needs to be changed...

    ModSTEP would be good option but it's not possible to send two 'tracks' to the same AUv3! (At least I've not found a way to do that). Meaning one track drives the note of an AUv3 and another controls the automation of the same AUv3...

    If you host your AUv3 in AUM, and route the midi using AUM, you can then send from multiple tracks in ModStep. ;)

  • @AndyPlankton said:
    @brambos Are you regretting yet showing us that you can make a great midi editing tool as well as great sounding sound generators ? :D

    I guess it's where things are inevitably heading. It is my destiny.

  • >

    If you host your AUv3 in AUM, and route the midi using AUM, you can then send from multiple tracks in ModStep. ;)

    Yeah, but having to use multiple apps at the same time to 'work around' a pretty obvious design flaw is driving me nuts.(Why does ModSTEP and Cubasis for that matter insist on having one instrument per track instead of having a 'rack' of instruments that can be fed with midi from the tracks?).

    Sure AUM can be that 'rack' but the integration is far from smooth and more apps hog more resources...

  • @Samu said:

    >

    If you host your AUv3 in AUM, and route the midi using AUM, you can then send from multiple tracks in ModStep. ;)

    Yeah, but having to use multiple apps at the same time to 'work around' a pretty obvious design flaw is driving me nuts.(Why does ModSTEP and Cubasis for that matter insist on having one instrument per track instead of having a 'rack' of instruments that can be fed with midi from the tracks?).

    Sure AUM can be that 'rack' but the integration is far from smooth and more apps hog more resources...

    If the Auv3 could expose a virtual MIDI port it wouldn't be a problem.....IAA's generally do this so the Hosts haven't had this issue until AUv3 came along, perhaps the next bunch of updates to the hosts will resiolve it. A rack like you suggest would be a good solution, or being able to set the output of a MIDI track to the input of another.

  • @Carnbot said:
    Looking forward to hearing some more demos of this in action. Has anyone been using Modstep with it yet? Seems like it would be a good fit with a template.

    Here comes the modstepper

  • @AndyPlankton said:
    A rack like you suggest would be a good solution, or being able to set the output of a MIDI track to the input of another.

    That's the way it works i most desktop DAWs.

    So the 'technology' is not new. It's just that iOS still seems to be treated like a 'baby' so the bit more advanced features are simply not implemented yet. Let's hope 2017 changes that...

  • Got it... love it...
    Helemaal Te Gek!
    Dank je wel !
    Tot ziens
    :smile:

  • edited January 2017

    @Samu said:
    That's the way it works i most desktop DAWs.

    So the 'technology' is not new. It's just that iOS still seems to be treated like a 'baby' so the bit more advanced features are simply not implemented yet. Let's hope 2017 changes that...

    I feel that on iOS the whole new plugin paradigm needs to settle in a little. For years everything was standalone and needed to manage its own MIDI processing and sound generation and things were only loosely connected through clever and resourceful plumbing tools such as Audiobus and AUM.

    Now that the AU plugin paradigm is finding its way to the platform and integration is becoming a reality, we're seeing a much clearer conceptual distinction between "things that make sound" and "things that manage notes and controllers".

    That's the reason that (as mentioned before) arpeggiators and sequencers get detached from AU plugins ("things that make sound"): because those are the natural tasks for host apps ("things that manage notes and controllers").

    The AU protocol (which obviously originated on the much more mature desktop platform) was fully designed around this distinction, but the hosts were/are obviously not prepared for this change yet. That's why we're still waiting for an AU host that does proper AU parameter automation and features a full fledged arpeggiator.

    I don't doubt this will come. AU is on a roll lately, and this will make its specific needs clearer with every new plugin that comes along.

    Now, what I'm really curious about is how much people will be willing to embrace the new workflow that comes with AU plugins, which will be much more DAW-centered than before. Once the DAWs get more mature and designed around AUs, will you be ready to let go of the familiar "multiple standalone apps + taskswitching" workflow?

    Figuring this out will be crucial for devs to be able to design tools that can help you in your creative process.

  • I discovered that I like both worlds.Working in Gadget, Cubasis o GB only is more comfortable but the modular approach conecting apps each other in AUM or Audiobus is so fun to play live.

  • edited January 2017

    @brambos said:

    @Samu said:
    That's the way it works i most desktop DAWs.

    So the 'technology' is not new. It's just that iOS still seems to be treated like a 'baby' so the bit more advanced features are simply not implemented yet. Let's hope 2017 changes that...

    I feel that on iOS the whole new plugin paradigm needs to settle in a little. For years everything was standalone and needed to manage its own MIDI processing and sound generation and things were only loosely connected through clever and resourceful plumbing tools such as Audiobus and AUM.

    Now that the AU plugin paradigm is finding its way to the platform and integration is becoming a reality, we're seeing a much clearer conceptual distinction between "things that make sound" and "things that manage notes and controllers".

    That's the reason that (as mentioned before) arpeggiators and sequencers get detached from AU plugins ("things that make sound"): because those are the natural tasks for host apps ("things that manage notes and controllers").

    The AU protocol (which obviously originated on the much more mature desktop platform) was fully designed around this distinction, but the hosts were/are obviously not prepared for this change yet. That's why we're still waiting for an AU host that does proper AU parameter automation and features a full fledged arpeggiator.

    I don't doubt this will come. AU is on a roll lately, and this will make its specific needs clearer with every new plugin that comes along.

    Now, what I'm really curious about is how much people will be willing to embrace the new workflow that comes with AU plugins, which will be much more DAW-centered than before. Once the DAWs get more mature and designed around AUs, will you be ready to let go of the familiar "multiple standalone apps + taskswitching" workflow?

    Figuring this out will be crucial for devs to be able to design tools that can help you in your creative process.

    Currently, apart from GarageBand, there isn't a DAW that gives enough different styles of MIDI input interface, Guitar style interface, Drum interface, step sequencer, piano roll etc.....
    The most successfull DAW will be the one that offers the most flexibility in input and editing styles, as long as the regular mixing tools are good.

    I like the feeling of playing an instrument (iFretless) or individual box (Troublemaker) that the individual apps give that editing in a piano roll, or playing everything on pads or keys does not give.

    I think an equivalent to AUv3 but for MIDI input/generators/modifiers would need to exist before I would give up all the different input devices I get with using all the many and varied apps that are out there. Yes we can import MIDI or Audio from those apps into a DAW, but once we've done that the editing interface changes to what ever the DAW offers (piano roll/wave editor)

    Then there is the timeline that a typical DAW imposes.....I have come to love not being tied to a timeline, and feeling free to go where i hear or feel rather than where i see......scene based apps like Gadget, Infinite looper or ModStep are good for loop based work as they will just loop what is there on each track rather than me needing to put blocks in place in order to loop them over a timeline.
    Same is true for the audio based apps like Samplr, blocs wave and Launchpad.....until DAWs have the ability to offer all of these different input and playing styles then I will always prefer individual apps.
    Desktop DAW's have not had to deal with these sorts of issues as the input devices were limited to Mouse/Keyboard/physical input device ( MIDI Controller/Real instrument and Microphone ), this has been introduced by touchscreens and the flexibility of input that these provide.

    What I DO want from the traditional DAW though is that my performance can end up in an easily editable form afterwards, which is where the timeline would come in for me, but when on that timeline I still want to be able to use the original input devices for editing.

  • @brambos said:

    Now, what I'm really curious about is how much people will be willing to embrace the new workflow that comes with AU plugins, which will be much more DAW-centered than before. Once the DAWs get more mature and designed around AUs, will you be ready to let go of the familiar "multiple standalone apps + taskswitching" workflow?

    From Me it's a big YES and one of the reasons I'm so fond of the 'Gadget' concept.

    For the plug-ins to really shine they be should be allowed to transparently switch between 'scaled down' and 'fullscreen' view when needed. (ie. in a worst case scenario, a plug-in in 'scaled down' mode has a few controllers and list of presets or simply a 'button' to go to fullscreen/edit view).

    It's painfully obvious that the UI size-limit that iOS AUv3's must adhere to is based on the Garageband UI most likely due to lack of a 'windowing system' on iOS (And honestly I prefer to run apps in fullscreen when possible to keep focus).

    Let's play with the idea that when we have lots more RAM in our iOS devices a host could via AU Plug-In technology start 'full' apps in a sandboxed mode similar to how AUv3's are loaded today. Apps without scaled down custom UI could just show a button to 'open fullscreen editor'

    This could for example allow 'legacy' IAA apps to be loaded inside a 'sandbox' and this way multiple instances could be used.

    WWC'17 will indeed be interesting to follow this year...

  • @AndyPlankton said: an equivalent to AUv3 but for MIDI input/generators/modifiers would need to exist before I would give up all the different input devices I get with using all the many and varied apps that are out there.

    Fully agree. This needs to happen. And I have faith that it will. An Apple guy on the CoreAudio dev forums recently mentioned that this was requested so frequently that they put it on the roadmap (most likely will be AUv3 plugins which can output MIDI streams).

  • Have to note that patterns import incredibly easily/painlessly/quickly into Infinite Looper.

  • MultitrackStudio for iPad by Giel Bremmers
    https://appsto.re/gb/56auU.i

    Has many different interfaces for recording midi, piano, drum pads, guitar and violin if I remember correctly. I would like to like the app, but somehow I just never do.

Sign In or Register to comment.