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.
Beatmaker 3.03 Teaser Tweet
Intua is hard at work making a great product even greater!
Comments
COOooool! Start, End, Little Start and Little End!
(?)
Loop start/end (I think)..
That's cool, but what about the auto transient detection that was advertised in the lead-up to the initial release?
Of course!
Then maybe you need to understand more how BM3 works. I haven't used SP Pro for a while but just downloaded it to test MIDI and was soon using it to drive AU synths in BM3
Yeah i'm also anxiously awaiting for that feature to be restored. I even saw it it listed in the 3.01 .pdf manual and thought it would surely be included in ver. 3.02. The developers reply was:
"detect needs more refinement before we put it back, right now it is disabled since it did not pass our testsuite!"
Hopefully it will be included in ver. 3.03.
Ahh super simple! Just use MIDIflow.
good to see fast progress.
Sample start / stop was probably the no1 issue to be fixed
I'm still gonna wait to use it though
@tga - I'm with you - I want midi in/out
There is still much needed before I invest my creative time into BM3.
but I'm very confident Intua will get things sorted real quick
What was/is wrong with it?
I picked up iMPC Pro in the sale partly for the transient detection (as well as generally getting to know its chops). Will be great when BM3 gets it too.
I just tested Navichord MIDI into BM3 and it seemed to work fine so I don't think it's fair to say that BM3 MIDI doesn't work (that's as far as my testing has gone however). BM3 seems to have a very active support forum so maybe start there if you're not sure how to do something or need to report a bug?
The first betas had it, but it was a little wonky. It will come back for sure.
I don't use it anyways... because it's either to sensible, either too loose. So you end up tweaking the start/end points anyway...
So I prefer doing a rough cut while zoomed out, and then go slice by slice and tweak it.
What I asked for and hopefully it will come soon is LINKED SLICES... so when you tweak the end of a slice it will adjust the start of the next.
I'll take both, please!
Egoist and Reslice give us passable auto detection and easily manipulated slice points. BM3 gives us neither.
Yah, I keep seeing posts 'BM3 needs MIDI' while I am actually using BM3 with MIDI just fine.
The only time I had to use Midiflow was with Future Drummer simply because it does not send sounds on seperate channels. Aside from that though, works great for me.
So it is not so much an issue of BM3 needs MIDI so much as BM3 needs AB3 MIDI?
If your workflow involves sequencing multiple BM3 instuments from external apps/ hardware then you get problems.
With my Beatstep Pro I wanted to play and sequence drums and two other instruments and the only way I could do it was my mapping midi notes from the drum on the BSP to a new midi channel which would then convert midi notes to midi channels. This is a solution for me and I have no other problem with BM3 midi.
But something isnt right with BM3 midi but as the manual is a bit light at the moment its difficult to is see what. The example I would give is midi config of banks and pads. Both have the same setup screen, click the three dots next to pad name or banks name and select midi port and channel. The pad configuation makes sense, configure a pad to trigger by a midi port and channel, notes sent to this pad trigger the sample or instument at the given note. In contrast, bank setup also asks for a midi port and channel which seems conter intuitive because the 16 pads in that bank (in 16 pad mode) correspond to the 16 midi channels unless you override them with a midi pad config.
I have suggested that when you configure a bank's midi then instead of each midi channel corresponding to a pad then differnt midi notes trigger the pads, instead of midi channels. This would stop the ability to pitch the pads using the keyboard but would allow a quick way of mapping the pads to a controller. For my workflow this would eliminate the need for midiflow.
If this doesnt make sense dont worry some workflows are more complicated to explain than fix, Midiflow is a great workflow fixer and is essential if you have a weird way of working @JohannesD
@AudioGus Yes, that is the issue. If you load BM3 in the Audio tab you can send core MIDI to it just fine. It just doesn't work with AB3 or IAA midi.
@tja , I already answered the question of how to connect SoundPrism MIDI for you.
https://forum.audiob.us/discussion/comment/385440/#Comment_385440
https://forum.audiob.us/discussion/comment/385441/#Comment_385441
As for playing pads individually, you're right, it won't do that easily. It will play an individual pad with a plugin loaded into it only by default. To play each pad as a note, you'd need some complicated setup via MidiFlow.
MIDI works perfectly for me, I just also want the option to trigger pads from note numbers rather than one channel per pad. Would make my setup more versatile.
Heil!
Godwin!
Magic Sharples
Well lo and behold! it seems there is a simple solution after-all.
You just need to go to the midi settings and map channel/note to "Trigger Pad ..." for each of the pads. With Auto-Learn this takes seconds. I tested by setting up on channel 16 and playing 16 white keys until I had all the pads mapped. There are also actions for selecting banks, etc, that can be mapped. As long as you have an exclusive input and midi channel there's no problem with this. The only gotcha is if you play unmapped notes it'll play pitched notes on the selected pad. But that's easily avoided, and could be considered a feature as well.
You mean focus actions? They don't work for the kind of instruments I'm making unfortunately. I tried that method but only the active bank receives control input signals (sus, mod wheel etc.). While you could (probably) get around that by adding another layer of midi mapping to the bank/pads, you can still only control the active bank, while I'm going to need 3-4 banks firing off from various MIDI controllers, in performance.
I've ended up (with some insight from @5pinlink) mapping one 'choke group' per pad and setting it to monophonic, then assigning them pads by setting the note numbers on my controller. 16 notes, 4 channel. Not as bad!
Could probably be done inside one pad and one channel too, using layers. I'll have to set it up both ways and decide which is preferable (both have pros and cons that I can see in theory).
More Goodies from Tweeter...
loving these update. especially the keyboard thing.
how soon till an iphone version is released of this?