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
We need Tim Webb to make some complaints and start calling people out on this. People listen when Tim makes complaints. :-)
Just bought MIDI Probe.
Loopy works with Molten AND DM1. It sends a Start event followed by a stream of MIDI Clock events.
Cubasis, on the other hand, only works with Molten. It sends a Start event, then a Continue event, then a stream of MIDI Clock events.
Meteor, which also only works with Molten, sends a single MIDI Clock event, then a Start event, followed by a stream of MIDI Clock events.
Now, you tell me which of these sequences is correct, and which are wrong, then we'll have an idea who to complain to...
It may not even BE the MIDI data, it may be the port connections not matching up...
Good work @PaulB. That's exactly the seed of a discussion that can hopefully continue on the shadowy grounds of the AB developer forum.
I'm not sure which is correct; I'm not even sure there is a 'correct'. Doesn't matter - there just needs to be an agreed upon standard.
Still haven't had a chance to retest Loopy and DM1. Looking forward to it. Really hoping @hmtx and @paulb aren't filthy liars.
No lies here, but filthy is debatable and depends on if I'm in the mood for dubstep. :-D
Which, is not that often lately.
I am really surprised people are having trouble with Loopy and DM1. I haven't touched Molten in months, DM1 is so much easier for me.
For the record: they are not filthy liars. After a 'close everything and restart' loopy triggers DM1 just fine - with and without audiobus. Not sure what conditions I had set up originally but I super duper extra drooper promise that was not the case for a couple of nights - DM1 just sat there, sad and alone, not playing with the other kids (including molten).
Just to confuse the issue, some Apps, and some modern hardware, send/receive CC events instead of the official Real Time Start, Stop, etc. Korg is one such offender. Stream Byter is the only remedy.
Start then Continue is kinda strange but legal, I guess, depending on what the slave does with it.
As to Clocks, they really should be going all the time from a clock master. Otherwise the slaves have no opportunity to derive BPM and good stable flywheel DPLL sync to it before Start. It takes several clocks to get that right.
With BM1 and DM1 I have never got BM2 to properly sync the first beat out of DM1. Roll-in may be an issue, but how to progam DM1 to match?
Ok...
Got this sucker working, albeit with limitations. I suspect it's a routing problem, no idea whose fault it is though.
Cubasis control of DM1
Load Cubasis, DM1 and MidiBridge. I have not tested if the order is essential, but this one works.
In MidiBridge, go to preferences. In the CoreMIDI Destination Host/IP Address field type "localhost" (without the quotes). Touch the Connect button.
In DM1, go to the MIDI setup panel via the Song page. Under 'DM1 Receives MIDI Data From:' select TEMPO for Network Session 1. Make sure Audio Background is on in the Song page.
That's it. Cubasis will happily start and stop DM1 and set the correct tempo without setting up any MIDI output, even with a new empty project. The limitation, and I just KNOW some of you are going to whine about this, is that It will only work starting at pointer position zero, so if you stop, it won't restart from where you left off. Probably due to Cubasis only sending a continue event rather than a start event.
I haven't tried the MIdiBridge trick with Auria as I don't have it, but perhaps I can leave that to someone else. After all, I have no need for MIDI sync, personally.
great work,thanks a lot.I'll give it a try later.Doesn't bother me to start from zero cause i'm creating my stuff using a cycle first.Then i record everything via audiobus in cubasis (well,everything that doesn't need a modulation over a long time etc.) and start to arrange.I will try it with auria as well and report back...
The same trick also works with Meteor. Just send both MIDI Sync and Song Position to Network Session 1 or All Ports. Same limitation re Continue.
Fingerlabs support for DM1 as described in this thread:
"I emailed Fingerlab about this weeks ago. Never got a reply.
"
...and for musyc,copied from the other thread:
"I already got an answer from a guy called Aurelien from fingerlab. He says it's a bug within the current version of 'Musyc' that will be fixed soon"
well,can't say that i like this kind of support behavior.
Pretty odd that Cubasis only works at pointer position zero since it includes the continue event. I wonder how the other DAWs/loopers work within the same Midibridge config.
I think DM1 only reacts to start and stop, not continue.
As I said, Meteor behaves the same way with DM1 in this situation.
Oh...I missed your post saying Meteor behaves the same. Given that, it sounds like the dev needs to add continue reaction to DM1.
@PaulB Great detective work!!! :-) So, we know that DM1 likely needs to listen to continue events, but what is it that MidiBridge is doing to allow the two apps to talk to each other in the first place? What are the apps missing that MidiBridge has? Are the missing parts of the communication coming from the DAWs or DM1?
I think the DAWs are sending on CoreMIDI out, but the apps are listening on either a local version of it, or on Virtual MIDI. The MidiBridge localhost hack hijacks CoreMIDI and makes it available internally.
@PaulB That makes sense! DAWs will most likely want to support outboard hardware as well, so they would be more likely to go with CoreMIDI out as their first option.
Now we need to get the developers talking to each other and supporting these things, so that everything works without resorting to hacks. It would be nice to have both sides support these things, but I would be satisfied if DM1 supported it, because it is the main app that I want syncing with my hosts. Again, great detective work @PaulB!!! :-)