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
Yeah. If Midiwrench didn't see it, it wasn't there. How are you making the connection? Is SD listening to a virtual output port created by SLM, or is SLM sending to a virtual input port created by SD? Remember, what you don't want to do is point each one at the other's port; that will just cross the wires.
Thanks UD - in SLM SD is set as a destination port. In SD SLM is set as the MIDI input. No other connections are enabled at this stage while I am testing it all out.
In the Activity log (in SLM) it is showing the data is being sent...but there is a bit of a glitch in SLM that I am currently checking...not sure the data is actually going OUT of SLM even though its log shows it being sent.
I have just been testing sending MIDI ccs to Softdrummer and it is responding as expected. So try sending to the midi monitor (streambyter is free and has other uses). Are you sure you are sending on the correct channel?
I can't tell you how many times I forgot that SoftDrummer is set to channel 10 by default.
What you describe is the crossed wires that I mentioned. It sounds like SLM is sending to the SD virtual input port, but SD is listening to the SLM virtual output port. If SLM sends to SD, then SD should be listening to its own virtual input. In SD, that may be called virtual MIDI bridge, or something else, indicating that it is its own MIDI port. Some apps handle this better than others, making it seem transparent, but SD may not be one of those.
SD now listens to its virtual port automatically and no longer lists it as a separate port. I just tested sending to its virtual port and it worked for me. In old versions, this did not work. And if that app has a virtual port worth trying that, too.
I think Drum Perfect Pro suits your user case, it has several patterns in very different styles and kits. using the auv3 player you should be able to change pattern (it has song mode) without complex setups. Hope it helps
Yes, thanks. I have changed the MIDI channel to 1 in SD. The data IS going out from SLM as I checked in its own MIDI monitor. It is sending as HEX data though, not sure if that should cause any issues though,
Thanks, I'll play around with that.
In SLM there are three : Network Session; All Ports; Soft Drummer ....I have been using Soft Drummer. I'll try using the other ones, and changing the port in SD
I'll have a look, thanks
If SLM is sending to Soft Drummer, then Soft Drummer shouldn't have anything set for MIDI In. With nothing set it listens to it's own "Soft Drummer" port, which is what SLM is seeing.
Nah, made no difference. I just turned them all off in SD, still nothing
You are successfully changing the Rhythm Bank and Sound parameters? Using MSB/LSB and PC?
Yes. I haven't tried the program change. But, yes, no problem changing the bank and rhythm and using G2 (midi note 55) to start and stop Soft Drummer. I am sending to the Soft Drummer port.
@uncledave : sending to Soft Drummer's port is working fine for me even if SD is listening to other ports.
Would you mind if I asked what app you are sending those MIDI commands from please?
@pax-eterna : what OS are you using? Are you using the latest version of Soft Drummer?
I made a little Streambyter script to simplify testing. Streambyter is free and can be used as an AU.
Load Streambyter into AUM as a MIDI node. Route it to SoftDrummer.
Paste this script into Streambyter. Tap Install Rules.
IF LOAD
ALIAS L1 midiChan
ALIAS L0 ccheader
ALIAS L2 q0cc
ALIAS L3 q1cc
ALIAS L4 q2Val
ALIAS Q7 chanSlider
ALIAS Q0 rhythm
ALIAS Q1 bank
ALIAS Q2 playstop
ALIAS Q8 dummy
ALIAS L5 noteHeader
ALIAS $100 noteLen
ASS midiChan = 00 #midi channel
MAT ccheader = B0 + midiChan
MAT noteHeader = 90 + midiChan
ASS q0cc = 0
ASS q1cc = 20
ASS q2Val = $55 #note 55
Set bank Bank $0 $127 +slider
Set rhythm rhythm $0 $127 +slider
Set playstop Start +B
Set dummy dummy +B
set chanSlider Channel $1 $16 +slider
set LB0 noteLen
SET SLIDER_DISPLAY 1
END
IF M0 == F0 7D 01 00 #q0 tapped
SND ccheader q0cc Q0
SET LB0 SQ0
End
If M0 == F0 7D 01 01 #q1 tapped
SET LB0 SQ1
SND ccheader q1cc Q1
End
If M0 == F0 7D 01 02 #q2 tapped
SND noteHeader q2Val $127
snd noteHeader q2Val 0 +DnoteLen
SET LB0 SQ2
End
If M0 == F0 7D 01 07 #channel slider moved
ASS midiChan = chanSlider
MAT midiChan = midiChan - 1
SET LB1 midiChan
MAT ccheader = B0 + midiChan
MAT noteHeader = 90 + midiChan
END
It doesn't matter. I have done it from Mozaic, StreamByter, Loopy Pro using its MIDI commands.
Since those all work, I think there is something funny going on with the app you are using or the MIDI channel isn't right. Hex is just a display format. MIDI is MIDI. Different monitors display it differently. HEX is convenient for people that know how to read it. But it doesn't make a difference how it is displayed -- but when setting numbers it is important to know whether you are looking at HEX or decimal.
Remember that in raw midi, the channel number is one larger than the hex number. I.e. MIDI Channel 1 is really channel 0.
Yeah thanks I was aware of all of that...MIDI channels match. Its the first thing I check. But the data has to be going out first!
Funny, I've asked the developer of AUM (several times over the years) to add all three stages of PC change messaging (ie MSB and LSB as well as the already included PC command) however he always refused stating "what would you need it for"....well this is a perfect case...where one is using an IAA that cannot recall state info...having it load in a session and automatically send the app setup data would make using IAA apps so much easier.
Alternatively, if Lumbeat apps could allow a user to recall a song via a MIDI PC message, then at least AUM could tell it (the Lumbeat app) to load a song when a session was selected in AUM (would give you 127 choices). But neither is the case so unless you are ok and have the time to manually select setups in Lumbeat apps, then you are forced to look at crazy work-arounds like this!!
Now, perhaps I am being unfair to Lumbeat but as there are no manuals and no MIDI spec sheets, and as I have not yet got that to work, I have to assume Lumbeat apps do not allow a user to select songs via MIDI.
The MIDI mapping for the LUMBEATS app is user customizable -- and the mapping in use IS there in the MIDI Setup dialog. Take a screenshot as a convenient reference.
There are many apps and AU that can send custom MIDI stuff -- so, I don't fault jonatan for not adding it to AUM.
It may be customisable but one needs to be able to access it. And again, a developer goes part way to having access but not full
I have never understood the reluctance to add two simple MIDI spec commands! He already has the PC command, adding MSB and LSB would not be that difficult as he obviously has a strong command of MIDI programming!
Having people load up separate apps in some arcane and convoluted chain is a bit ridiculous really! Especially with what is available today! It's not 1987 anymnore!
Anyway, that is a digression. Thanks for your assistance.
Is the streambyter script working?
I think you imagine that ios music app developers are earning much more money for their work than they are. None of what you said is difficult to program BUT there are a zillion feature requests for both apps -- and the devs have to prioritize. What is essential to you may not be as essential to others. I'd cut the developers a bit of slack -- and realize that one of the prices we should expect to pay as customers is that we will have to be creative in our solutions if we expect to pay such small amounts of money for the software we use.
Yeah, fair enough. I just tried an experiment with my chart app (Unrealbook) which has a MIDI section for sending MIDI data.
And without any pre-set up of connecting this to this and that to that, it simply worked when I created a MIDI string to change the setup in Soft Drummer. So it MUST be something to do with Setlist Maker.
TBH, if I could connect my chart iPad (ipad pro) to the iPad mini I am using as the "drum machine" I'd just use that. Not found a way yet to connect two iPads together (well, easily at any rate) haha!
Btw, if you haven't used Live Pads in the LUMBeats apps they are pretty useful in my opinion for puppet stringing the Lumbeats apps
Thanks - I have seen them but with no manual it's a bit tough to visualise what to do with them. I might hunt YT and see if there are some vids on using them.
They are pretty self-explanatory. There are 8 (I think) pads. Each one has a corresponding note number. Each has a pattern, intensity and jam level assigned to it. You can set things up so that fills happen when you switch between the pads or not. You save the assignments in sets. I have sets set up for different feels and time signatures and can step through them to vary feel as needed.
Bluetooth MIDI should work great for this, and it should not be difficult. Of course, you might not want to rely on Bluetooth during a live performance, but in most cases it should be fine. I'm sure we can help you with the Bluetooth MIDI connection if you need it.
Another option is to get two USB ethernet adapters and then use Network Session over an ethernet cable. That's a little more complicated scenario though.
Yes, basic stuff like assigning a rhythm to a pad is easy - and you can use fill every change, but how would you program the variation (ie toggle ride)? How would you program a pad to play the fill to out (or stop if you like) All that gets saved on the pad is whatever rhythm and kit is displayed above.
Thanks...I assume you are meaning using something like midimttr? Which is ok but uses BT which is not only not secure, but for some strange reason on the iPad Mini, when running BT the battery life drops to about 2 1/2 hours, no idea why (and neither do Apple) It's a 4th gen mini so still relatively current model.
A bit moot now anyway as I discovered another "gotcha" with the Lumbeat stuff. I cannot send it tempo data, IE I cannot send a fixed tempo (which does have a GM set of CCs to use) of say 110 when selecting a rhythm. I can have tap temp assigned to a key but that just adds yet another time user (only seconds but it all adds up) thing to the setup, and I'd not be that accurate with it anyway.
midimittr isn't needed. But no matter BLE Midi isn't a good option for you.
If you host the apps in AUM or Audiobus, IAA host sync will take care of the tempo for you. Just control the tempo through the host. Alternatively, you can use Ableton Link whether hosted or not. As long as you disable Link Start/Stop so that all the apps don't start together.
Also, if you're having problems sending MIDI from Setlist Maker to the apps, maybe sending MIDI to AUM, then routing to the apps using AUM will work.
Ahhh yes of course (re tempo)...my bad, I got so involved in one way I lost sight of the other haha! Still having the issue though with the footpedal starting any Lumbeat app that is open, but that is with them all in "stand-alone" mode...albeit with a different midi ch set for each.
Good tip on sending to AUM from Setlist maker... I'll give it a try
If they're not hosted in AUM, and you do the routing through AUM, then only the ones hosted in AUM will start when you start AUM's transport. The key is to not set the Lumbeats apps to listen to the foot pedal (or anything else). Set AUM to listen to the foot pedal. Route the foot pedal to AUM midi control, then map the transport and tempo to the controls you need.
If you need to send anything to the drummer app(s), use AUM's routing to send to them. Just make sure that there is no conflict between messages you send to AUM midi control and those that you send to the app. For instance, if you use Note C2 to start AUM's transport, make sure that's not mapped to anything inside the drummer apps.
I'm not sure it'll work as I don't know of any reason why you wouldn't be able send to the Lumbeats apps but would be able to send to AUM. But it's worth a try.