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
@midiSequencer said:
Great! With falloff velocity and intervals in there on a per-step basis and on chords, I can see a lot of new really cool creativity options opening up.
Thanks for the audio demos. Sounds good!
@midiSequencer This was the setup. I need to quote myself....
@ArcaneScreams said:
I like the sound with Crystalline and Grain Science, btw. Cool stuff!
@arcaneScreams - when midiSequencer has the rack it will be multitrack, with each sequence (chords and all) routable to devices or defineable midi bus (like group channels on a mixer) for transposition. With this will come the ability to deal with snapshots as patterns on tracks - so a song mode - where you can apply logic to patterns (e.g. repeat x2 then go to pattern 1).
This will be the final structure I am aiming for.....
@midiSequencer said:
Awesome. I think we're talking about the same thing. I can't wait.
@ArcaneScreams said:
Awesome +1
Ok, just out of curiosity, and to see how far I could push midiSequencer, and my iPad, I did this. And it's a bad musical example, haha, but it works. midiSequencer controls Genome thru MidiBridge on a step, controls Thesys on a step, and Magellan on another. Genome controls Sunrizer, and Thesys controls Animoog. Genome and Thesys are triggered separately, Magellan throughout. There are some really interesting possibilities here, especially using the Step Ornaments in midiSequencer, using apps of your choice, I think. Anyway...
I can't make the MIDI clock work with SeekBeats. It will neither start/stop SeekBeats if the Master, nor allow SeekBeats to start/stop Midi Sequencer if it's the Slave. I have turned MIDI Clock messages on. I've tried adding SeekBeats's clock as an input device, but MidiSequencer still won't accept the clock messages. I've enabled the clock (have tried both input and output) on the SeekBeats side of things.
The reason I want to sync the apps up is that I'm getting some pretty major drift between them when both are set to play at the same tempo.
I have checked that the SeekBeats clock works with Xynthesisr as a comparison, and that combination is fine.
Is anyone else having MIDI clock issues with this version of MidiSequencer?
@Michael_R_Grant I can sync midiSequencer with SeekBeats using MidiBridge. In midiSequencer, Output MidiBridge, Active, clock on. In SeekBeats, midi sync, MidiBridge in, not out. In MidiBridge, MidiBridge is connected to itself, and midiSequencer is connected to MidiBridge. (See pict)
@ArcaneScreams - interesting audio - sounds african/primordial due to the repeated notes.
Interesting also you have the bug in Sunrizer - this time from Genome to Sunrizer - Sunrizer will not accept note-off's for small note durations - I've managed to duplicate this with midiSequencer - Magellan, Nave, Animoog etc are fine.
Alot of issues with midi clocking is down to whos virtual midi you are using. I don't have the SeekBeets app to try, but remember there are two ways to connect one app to another 1) App1 sends output to App2 Virtual port (e.g. midiSequencer sends output to Animoog named virtual device) and 2) App1 sends output to it's own virtual midi port and App2,3,...etc listen to that port. This method is often better than 1) as not all apps can listen on their own virtual midi port either at all or accurately (although midiSequencer ensures it listens on a high-priority thread).
I have an outstanding exercise to try midiSequencer <-> coreMidi <-> other apps and publish the results. For example some apps like Auria don't listen to midi clock but to MTS (midi timing song positions)....
@midiSequencer said:
I totally agree with you about 2. Method 1. tends to leave me finding a bridge at times, like MidiBridge or FreEWI, and then making sure those are configured correctly, and taking up valuable memory space. And it is more accurate, like you say.
I'll try your experiment with midiSequencer <-> core midi <-> other apps later tonight. I'm curious as to what will happen.
Chords are great! Thank you for all the work. I don't quite get the UI yet but if mash it enough it does my bidding.
I too often have troubles syncing the app with other apps. Usually I can just hit 'play' in the other app at the right time and will remain in sync long enough to keep me happy (after a few tries anyway). Alas, last night MIDI Sequencer -> Sunrizer was creating hiccups that would knock the caveman sync out of whack. I hadn't restarted my ipad or turned on airplane mode so that may have been it.
There's a little visual bug with the mute buttons you've probably already noticed. If you hit mute on any step the step 3 steps before it also has its mute graphic toggled (though it plays fine).
@arcaneScreams - let me know what you find. I was intending to do mine we a debug version (so I can monitor exact midi in & out) to make sure it wasn't a bug with midiBus library (which is used in MidiSequencer now)
@syrupcore - what's caveman? Continue to send me issues and I will try and fix them, or at least understand limitations of coreMidi and other apps - it benefits everyone in the end!
I couldn't replicate the mute button issue you had. You realise that the lit blue led (on the main screen) represents the current step in the sequence, but the UI for the chord/added notes can refer to another step (by you pressing the skip button on the main screen). You can see this from the title in the Chord screen.
Why is this - its because the sequencer may be playing but you might want to add notes on the fly for a particular step. I need to add some sort of animation to the skip button to indicate current selection....
Let me know if it's something different!
In this screen shot I hit the mute button on step 9 only. I hit pattern reset before hitting mute. Step 3 still plays. Almost positive it was 3 steps last night. Looks like 6 now.
'caveman' wasn't about your app—it was about me! Caveman == when you set two devices to the same tempo and hit 'start' on the second device (app) at the right time.
What do you mean by pattern reset (Reset button - rest sequence to default)? I still can't duplicate this?
I notice by the screenshot that Syrupcore is using MS inside AB, could that be causing this behavior?
Yes, reset sequence to default. Think I figured out what's up (well, how you might recreate it that is). I had offset the sequence with the arrows next to the play button. How much or little I offset it changes the distance between the actual muted track and the ghosted graphic only muted track. That explains why it was 3 last night and 6 today.
Just noticed that if I hit the chord/step button it also graphically depresses the offset track as well.
@midiSequencer It appears that I can get Auria to start and stop with midiSequencer, as mS as the master. In Auria, Midi Inputs, choosing Receive MTC, Receive MMC, and Receive Clock, all three. Nothing else highlighted. In mS, Output, both Auria and mS are active and clock is on. Tempo change doesn't work, so that's a pain. Haha. I don't know how accurate the clock is. I'll play more later. Need to work now.
Good catch @yowza. When I take it out of AB, it doesn't happen.
Found another little graphical thing. If you turn on cycle and then hit play/stop over and over the size of the play button grows! First is after about 15 hits. Second is after I dunno, a lot.
Ah ok - managed to duplicate it outside of AB too - so two bugs a) first shift < or > displays the steps a little lower b) after doing a shift of steps selecting a step to mute also mutes another!
To be honest I'd forgotten about the shift left/right in the sequence. So easy bugs to fix.
I don't think it relates to AB - which would have been very weird.
note that, for me anyway, it doesn't actually mute the other steps. just a graphic glitch.
Another thing I noticed last night is that I couldn't get the tempo multiplier to do anything, so is there anything special that needs to occur to get that to work?
Also I'd really like the note names on each step to reflect the actual note being played because as it is now when you invert or transpose a sequence the note names stay the same as the original even though you can hear that they have been changed by inverting or transposing. I noticed this when I had transposed a sequence and was trying to play along using another app and couldn't use the name of the notes to tell what key I was in.
@syrupcore - yes it's a display problem. Almost fixed it.
@Yowza - the tempo multiplier now keeps the same tempo (if it can), so if tempo=128 and mult=x1, then selecting x2 will move the slider to the left and keep 128 - this is to allow smooth changes during performance if you want to use a higher range.
Yes, the slider notes show the step note names - not any transpose or inverted. This final note name is displayed on the bottom right as the note is played.
I will look into this possibility - showing them under the sliders - but it requires any small changes in invert or transpose to update all 16 note labels (in the current key) in the fly. I'm going try this out tomorrow and check the performance is ok.
Invert, incase anyone was wondering is really reflect - as it reflects midi notes around the invert key - so it works out the semitones above/below the invert key and makes the new note that many semitones below/above the invert key. So it's good to choose an invert either at C-2 or G8 or in the middle of your melody key range.
@midiSequencer, did you see my post at the end of page 4 about the Huge Ever Growing Pulsating Play Button That Rules from the Centre of the Ultraworld? Not a big deal but it looks like we posted within a minute of each other and once a page flips on the forum it's easy to miss the last one from the previous page.
The play button animates if you have cycle enabled - it shows that its pending a stop.
So without cycle, you can stop immediately, with cycle it waits until the end of the sequence....
Nice update! I've bought the chord IAP :-) Having a problem sending notes to external hardware. Is there a global option for MIDI Channel out?
@sdesign - this is what you need to output midi to usb hardware device:
1) Large gray Midi Muted button lit to show Midi Send
2) Devices Panel - outputs - select your hardware usb interface port - and click the active button so it's lit
3) Press Play and you should be off!
@syrupcore - wow see what you mean about huge in the 2nd pic!
Will fix that....
@midiSequencer thanks, turns out it was the crappy midi interface I was using. Just tried another and it works perfectly :-)
Thanks for making what is undoubtably the best analog-style step sequencer on iOS!