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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
@Johnny - thanks. Videos will be done I promise.
I posted some pics here to get you all started on midifx...
https://www.facebook.com/pages/Midisequencer/558588387561014?hc_location=timeline
Tony, think we may have talked about this before but what about making a list of the videos you think mS needs and then letting the community try putting them together? Perhaps a promo code for your new app as a thank you to the most prolific contributors.
"Do an mS video" is daunting. "Do a snap shot demo" or "Do a MIDI config demo" isn't though.
@Syrupcore - interesting idea. The promo wouldn't work as you really need the app & IAP's to do this.
I have a decent DSLR camera but need some time to put this all together but I need to do this asap!
From my point of view there are 3 things in the way of me doing these videos now:
1) x-mirage is broken in IOS8 - I use this for screen capture. I find(or rather found) this the quickest way of grabbing a screen play. However, I now have my wife's IOS7 mini which I could use.
2) I'm a coder not a video producer, so haven't yet learnt enough to be able to put together a decent video
3) IOS8 & AB - finding an combination that behaves and still sounds great. It's getting better but nothing worse than doing a video and finding out the synth doesn't respond halfway through.
So I wrote a manual, and indeed that's out of date now as it takes awhile to annotate the screens! But I realise that most people prefer videos, so that's what I will do.
I'm thinking of the following for videos:
1) Must be short - say 5min only
2) Build this up covering basics first - so topics could be a) when would you use a step sequencer vs a daw sequencer b) using MS with hardware c) using MS with AB, IAA, x/y/z synth d) coreMidi - what is virtual and how many endpoints do I have.
3) It should cover some of the design decisions I made - noodling, cycle delay, step logic, NRPN for controlling hardware, sysex, ornamentation, chords vs added notes - that sort of thing.
It should also cover known limitations & issues - things the design didn't cater for yet - like echo needing to be at the end of the fx chain, synth woes (Sunrizer not playing octave 6!).
4) I can then do some expert sessions - things like playing the mini keyboard in chords in realtime b) special effects you can get from synthesizers (e.g. portamento or arpegiated patches being played fast) c) and extreme tempos (low for fx, high for ethereal.
So making sure I label this correctly (beginner, core, expert) to avoid a mess,
I can see this stretching to many videos!
Let me work on the list and people can suggest additions and nice to haves... Areas that confuse them maybe and need clarification on.
That's a nice looking list. Didn't even consider stuff like 'why use a step sequencer'.
I meant a promo for the TBD piano roll app. Not that I'm trying to get one! If I make a single video it will be infinitely more than I made in the last 365 days.
Bought the IAP last night for MIDI FX. It's well done! Being that it's a MIDI note effect, the FX react differently than, say, throwing a delay in after your output. Not really sure I understand how they all work (so I would enjoy a video!), but the transposer was doing some neat things and you can trigger it live. The probability feature will be huge for people who like slightly (or dramatically) randomized sequences. Thanks!
@stormJH1 - it's certainly going to add some weirdness to your rhythms and scaling to your pitches
Just remember echo last (as it sends the note to active outputs).
The %probability is going to feature per step (along with swing & humanise) - and I want to be able to select FX slot 1..8 as enabled per step too - like Effectrix. But that's a little later....
@syrupcore - still feel some people don't understand the noodleness appeal of a repeating small sequence of notes.
I've an idea to split the the sequence into two so that it plays two sequences in parallel.... just for the lights of course - I saw a coffe machine do it yesterday.....
@midiSequencer Sounds good. I think your idea of breaking them into pieces is great for the user, but will also maybe help you get your arms around knocking them off 'bird by bird'
Had a a good play with the IAP tonight. Some very cool stuff going on! Is there a way to set the MIDI FX on/off for a step without loading the details screen for each step? Would love a way to quickly toggle it per step.
I had a hell of time getting any of my drum machine apps to sync with it. I've had good luck with Funkbox in the past but no joy tonight. Tried funkbox, DM1 and Stroke Machine to no avail. Is there one known to work well with it on iOS 7.1?
Sidebar: I might be the only one but I can never figure out if I'm dealing with Inputs or Outputs when in the Devices screen unless I do some sleuthing ("App X doesn't have a midi output so I must be on input"). The input and output button states mess with my head; "Does that mean it's depressed or does that mean it's on?". For me anyway, that toggle suffers the same problem as the iOS Shift Key—I can't ever figure out if it's on or not! Would lurve for it to be something like a slide toggle with a really clear indication of 'you are here'.
@syrupcore - from the skipButton panel(which has ornaments etc) you can toggle fx on/off - you can keep this panel open and select one step after another to set.
To get apps to sync with it there are a number of options:
1) make sure Options Panel has Midi Clock out! Without this no midi clock or start/stop/continue is sent
2) In Devices Panel / Output - make sure the active midi device has Clock enabled.
3) In Devices Panel/ Output you can also add latency to the midi out messages (effectively delaying them per device endpoint)
4) In Options I've added an overal output latency to delay all midi messages by up to 1 second in 1msec intervals.
Give that a go and if no joy send me a bug report so I can get the combo working.
The above does all depend on the recieving device of course being enabled and not doing anything strange.
Re input/output button - whichever is coloured and not gray. You will only see the rotary & buttons for latency & send CC's on outputs. The button is only to switch the list between the two (input list or output list).
The Active button is the one that says enable midi in (if inputs) or enable midi out (if outputs).
This is made a little confusing by having virtual ports (called duals in midibus) linked - you can't seperate them. MidiBus library limitation I'm afraid.
So focus on the list - it will tell you what's on or not. And remember you don't need to send to every midi endpoint (every item in the list is an endpoint) - you could disable MidiSequencer if you only want to send to the synth app virtual port. MS will duplicate all midi messages to ALL active ports so no need. Some apps don't listen to their own virtual midi ports however - so generally MidiSequencer as output - all others disabled works best.
I've retested the saving on midiFx - there are a few display bugs I have fixed. Only one vaue not saved (compressor gain).
Will submit this today hopefully as v1.10 with the below:
which gives me an opportunity to add the following:
1) %probability per step - this works in addition to fx.
2) Swing - will introduce fixed delay on other step played (so toggles rather than fixed step 2/4/8/ etc).
3) Humanise per step. This works by varying the step by a random + or - amount. The amount is what you dial into the step. There will be 3 values to harmonise:
a) Note pitch (+/- 127 semitones) - clamped to 0..127 range & an option to conform to scale
b) Note Velocity (+/- 127) - clamped to 0..127 range. This is useful for drum type apps to vary the loudness.
c) Note Time (-50..+50) - which is a % of the step time (the time it takes given the tempo to play just one step) - this will effectively delay or bring forward when the step starts.
I've allowed extreme ranges on these options to allow you to experiment!
Nice! Humanize on velocity will also allow some interesting randomness when associated with the velocity switcher.
Thanks for the thorough reply, Tony. I will double check my sync settings—I'm pretty sure I had it configured correctly. Is there a drum app you like to use with it?
That's kind of the problem. On that same sub-panel, there are other buttons that share the same coloring and 3d style which invite you to press them. It's confusing to have that same style as the 'on' state because in reality the greyed out one is the one you can press to change the view. This is me being a UX nerd firstworldpromblemista so feel free to ignore — you have far more interesting stuff to solve for/cook up.
@syrupcore said:
i wouldn't mind these improvements. I find the settings to be confusing as well, but I'm easily confused (it happens to me in some other apps also...and also with the ios keyboard/shift button).
ok, have improved it
This ok? Now you just toggle the button to show Input or Output.
Man, I didn't mean to distract you with this. It's all ok! But this has the same problem I think. I look at the button and I'm wondering "Do I press that to go to the output screen or is it telling me I'm on the output screen?"
First suggestion: Ignore me. Second suggestion, use the current button style, display both [Input] and [Output] buttons and change the label above the buttons as needed. Instead of "MIDI Input/Output" change it dynamically between "MIDI Input" and "MIDI Output".
Or, sticking with the single button to both toggle and communicate state just add a label to the left of it: "Viewing:", just like 'Active' and 'MIDI Clock'.
No, no, no....you need a man out front with a red flag.
@midiSequencer the fx IAP is great. One request would be to have the option of sending midi clock only to a midi port (e.g. Effectrix when you don't want midi notes changing the fx settings).
@syrupcore - let me try again - I understand now you mean the heading... and normally you would press a button labelled outputs to go to outputs
Easily changed.
?
@johnny or is it a white flag
@Paulinko - you mean ignore notes & CC rather than just notes? Added to list. Glad you like the fx - no one has asked for anything additional on these yet, but I see alot more going into the echo (e.g. improve the ping pong pitching or the swing - which both seem a little tame compared to the pitch, delay interval, gain & number of echoes).
@paulinko - can probably go one better on that request - allow notes, CC, fx individually at the global level (Options screen) or output device (currently just says send only CC).
So a button to enable each (enabled by default).
I'm redoing the midi device output screen anyway.
I don't think this belongs in the fx (filter) section as fx are global (i.e one set of fx for sequence rather than outputs or steps - although I'm looking to enable each fx 1 to 8 individually per step ).
@syrupcore - here are the new Device input & output panels. They switch when you click the top left button.
What this also shows is the new filters for output. Rather than send CC only, every output device can now be filtered to not send notes, cc's or fx. Not sure if I want this on inputs yet.
This has a nice ability to be able to send echoes only to a device and notes to another. Echoes being often faster than the step note, add a nice arpeggiation in the background if you choose the right patches.
i've also completly rewritten the midi output for fx as I discovered a bug when putting this in - secondary devices where not getting step midi notes if fx echoes were playing in a lower (in the list) device. It's to do with midi timestamps - so now I make sure I send all the main step notes first for all devices, then send any post fx (like echo notes).
What an awesome app/ dev! The FX push it even further. Probability and echoe create changing, interesting melodies over time. For a midi noob like me it's surprising what else this app can do and i have always good times using it. Thanks you for your constant supply of goodies.
@peanutcram - thanks. This app is getting there
I'm thinking there must be some better ways to do % probability - one dial seems not enough!
I've added per step probability but wondering if I've missed a trick? Anyone know of hardware of software feature that would be good to emulate? Let me know!
^ Numerology by Five12.
Today the last day of the sale? How's the midi timing on ios8.1? I'm getting timing fluctuations with Auria sending clock to Thesys with AB. I don't know if this is just inherent issues with ios or something else but Paulinkos' FR of sending clock to effectrix would be great! Nice to see all the development and FRs being added.
Also will it run as an IAA app in Auria and send midi to other IAA apps? Thanks!
Gah, gone back up but it still says on sale. Thought i had until midnight GMT!
@papertiger - thx will check it out.
@musikmachine - I think it's tuesday 11th it switches to the old price.
On the timing, I've been doing some performance testing today on it as I've recoded all the fx. I'm looking next to do some specific tests on switching to other apps whilst playing sequences and seeing why it's losing priority whilst in the background - which I think is to do with my silent IAA (which isn't technically allowed) - so I may need to transmit something to keep Apple system thinking I'm still alive.
I have your email, but let me know some combinations (e.g. ipad air + MS+Theysis) so I can test like for like.
Running up apps in particular is a cpu intensive task - multi-core improves that (e.g. 3 in the air 2 mean I haven't seen the issues - you have 2 in the air 1).
Tony, you nailed it. Thank you!
@Tony thanks! Appshopper shows a recent price increase on the 8th so i'm a bit confused! It's a gamble buying it and the IAPs so i was really hoping to test the free version first then i could decide whether to buy it for driving hardware and vsts.
@musikmachine - after some performance tests on ipad 3rd gen & 6th gen(air 3) I have noticed the following:
1) Running up apps during a sequence is bad. Many apps take up to 10x cpu of MS, so of course it's going to take a hit. CPU meter (via instruments) says it takes up to 75% of the combined cpu %.
Apps are designed to runup quickly (they will timeout and not launch if take too long) but this has to be balanced with loading resources (graphics, sound files, opening AB etc). Some apps are quite bad at this (e.g. iSem).
2) On air 2 - I couldn't really get it to deviate in tempo - even during loading up iSem etc.
3) On ipad 3 (so below your air spec), I did notice some very small stutters when swapping between apps.
Will try some more things that may give a better timing. Always looking to improve things!
Anybody using this with Gadget? I was just trying out the free lite version with Gadget and see some potential.
Fwiw, I've never been happy laying out chord progressions with most midi based apps. Midisequencer might change that.
Sent from my iPad using Tapatalk