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
I will send email to Cream Mobile developer to see this thread TODAY.
@nerk_, @Clobmert, you guys also need to verify it, because the Ruismaker AU app has this occurred on Modstep to drive the apps.
However now I see the light (and the improvements), mucho gracias for the maker and giver!
Did the "Ignore MIDI CC" switch help at all?
Midi Channels shouldn't matter. Ruismaker listens to all MIDI channels (OMNI), but in general MIDI Channels are not a meaningful concept in Audio Unit World. In other words, Audio Units are not supposed to be tied to a MIDI Channel at all, and it's the host that has to make sure incoming MIDI messages are routed to the proper instrument. You could have hundreds of AU Instruments loaded, and still be limited to 16 midi channels - it's the problem of the host to solve that in a logical manner.
However, sometimes hosts send rogue MIDI CC messages in the background. For example, I noticed one of Ruismaker's knobs behaving weird some time ago. It turned out that Cubasis was resetting MIDI CC#66 (Sostenuto) at the start of each loop. And CC#66 was then still mapped to one of Ruismaker's internal parameters. Hence I avoided mapping any parameters to that CC number from there on. Ruismaker doesn't listen to Sostenuto and Cubasis has no business sending that controller to a drum synth, but there you go.
I'll look into it, but if it only happens with one particular sequencer then I suspect the issue is with the sequencer.
@brambos , @Nerk_, @Cblomert:
Bram Bos, Thank you. I am calling Modstep developers on this thread now. Once again thank you to dig in.
No problem, it's not inconceivable that there is a bug in Ruismaker. Just trying to rule out any other causes.
In this case... The most likely cause is that MIDI CC#22 ("Change Instrument on Channel 1") is receiving an incorrect value, which would result in Ruismaker switching the instrument to Unassigned ("- none -").
I'm not familiar with Cream (although it looks good!).
Can you somehow confirm that MIDI CC#22-29 are not in your cream sequence? These will cause the instrument assignments to go berzerk.
I am very sure I had no midi CC attached to channel 1. There was only a plain simple sequencing on that.
I am now going to play again to see the problem. If I am wrong on it, I will immediate reporting back.
I am writing email to Cream Mobile, now I am delaying it for sending it later on.
Thank you.
@brambos , @nerk_, @cblomert,
In this time have a brand new Modstep file with. Same again the problem!
I have both source and destination on channel 1 or 2 or 3 on separate total 6 tests.
This disappeared kick instrument only happen with midi channel 1. Midi channel 2 and 3 go very fine.
I pay attention to no midi cc being circle. And I also check my Cream mobile has no midi CC being drawn.
The result shows it pretty clear now with only channel 1 and the first instrument.
I try on switching variety instruments. All being well except that problem.
............
There is also another little problem for Ruismaker when the Modstep playhead running, which is occurred when changing individual instrument that I have to press two or even three time for the instrument being changed sometimes. But this is not so serious problem for any fixing contingency.
Thank you!
Photos show what I tick for channel 1 for setup. In this case 'the Modstep' source and destination. So I verify that it is not the named channel problem for disappeared instrument.
Thanks for the thorough testing.. that helps me a lot!
So it only happens when using Cream to sequence? Or also using the internal sequencer of Modstep?
@brambos,
I need time to think what to sequence it on channel 1. Maybe StepPolyArp, Patterning, or even the troublesome setting on Auria Pro to test around. Give me some time with.
@Brambos,
I tested Ruismaker on Modstep sequencing by StepPolyArp and Patterning.
Ruismaker is fine with them. I think the answer is clearly this could be the Cream Mobile with this problem.
Ok, so I can scratch it off the investigation/possible bug list. Sorry I can't be of more help for now.
Thanks for the investigation.
I don't have Gadget or Modstep, but it sounds like you would like Genome. I have it and am not an advanced user, but had no problem figuring it out relatively quickly. No muss, no fuss sequencing on the iPad. Now, if I could find something similar for the iPhone.
Ok, Auria Pro beta 2.05 drives Ruismaker on Modstep, which goes fine too.
It is time to email the Cream Mobile on this subject now!
I have also notice that problem of instrument pressing which vanished with StepPolyarp and Patterning. So a big releasing time for now. It is obvious the Cream Mobile thingie.
Thank you!
Email message has been sent out to Cream Mobile developer.
Using Ruismaker within Garageband on my iPhone 6+, I am bemused by something. The copywriting for Ruis indicates that there are preset kits to choose from, but I can find no way to access a preset menu using it in Garageband. I can choose from the full menu of individual preset hits for each individual pad, of course, but there are no preset kits I can find.
I have the same issue using Viking Synth within Garageband-- there are supposedly a wide bank of factory presets, but having scoured each page of the AU UI I can't access any presets for Viking within GB, only build my own patches which are saved within the song but not in any independent bank...
Apple managed to hide these ridiculously well (as in.. so deep that they might as well not be there at all).
To get to the presets:
Apple clearly needs to polish their AU implementation in Garageband because it's a bit half-baked right now.
If you press the 'sliders' to the left of scale it switches to another screen
If you press the ruismaker button in the centre of that screen it brings up the preset list.
The same process works for Viking.
midiSTEPs hosting Ruismaker,
hehe, can host 4 tracks (64 RUIS instruments). Haven't try modstep CC to it, but the selection is there with midiSTEPs' super good midi connection.
We have good news about the timing issues when recording in modstep: We didn't send the correct timestamps to AUs - so they came a buffer too early, as we schedule all midi events in advance.
IAAs and internal instruments should play sample-accurate though, as long as they support it - as @j_liljedahl already said; unfortunately many don't.
The AU timing will be fixed in the next update, along with several other IAA/AU stability enhancements and fixes
Thanks for the advice about preset access guys! I'll try it on my next break. Can one also save self-built kits/patches through that method?
Super thanks for this!
@Kirnu ,
Developer, please come to see what went wrong with Kirnu Cream Mobile arpeggiate Ruismaker AU on Modstep.
I always bragging about your app, please don't let me despaired.
@wim @skiphunt @nick Thanks for thoughts and intel gents - x
"To get to the presets:
Hmm, so I tried this just now and it didn't work. When I press the parameters view slider icon while in full keyboard mode, nothing happens; when I press it while in Ruismaker UI mode (after hitting the little panpot symbol to hide the keyboard), I do get a new screen, which is a left-right scrollable array of individual sliders to adjust all the parameters for each Ruismaker Pad. But there's no Ruismaker app symbol to be found and tapped in this screen, just the array of sliders, none of which address presets.
In Viking within GB, tapping the Parameters View icon just brings up a mostly empty screen with two toggle buttons on it (Release and Glide) and nothing else, definitely no Viking app symbol.
A peculiarity of the 6+ perhaps?
The way to get to the presets in GB on iPhone is to press the little down-arrow at the top-left of the screen when in full keyboard mode. You'll see "Ruismaker" as one of the options. That will take you to the presets. This will work for Viking too.
@Brambos ,
I have a very detail play with Cream Mobile to Elastic Drum on Modstep today.
Cream is very perfect for ED on Modstep.
Also from my half year long term playing on Cream Moible, I have never met a single missing notes playing by touch or the Cream Mobile pass a missing notes to other programs or a missing preset instrument something.
I don't mind if you honerable don't want a further detective work to your Ruismaker code improving. But I can only say it is only happened to your AU app so far. That channel 1 is important, although few popular apps passed those tests with.
I am not satisfied with your answer so far, I hope you just saying and really doing more for Ruismaker.
Thank you, I would not say again for this if to the contrary of your thought. Cheers.
@Brambos, @Nerk_, @Cblomert,
To prove what went wrong with Ruismaker,
I think 'Modstep developers also carry a bigger responsibility here for this AU drum synthesizer. By these two photos, it is Modstep problem now.
I know you Modstep developers keep quiet on this matter, but I want you to know that this missing AU instrument kit won't happened to AUM mixer.
I show you guys photos how well Cream Mobile to Ruismaker on AUM mixer.
Please, verify what goes wrong on Modstep with Ruismaker.
Photo showing here on midi channel 1, I can see instrument name there with first kick button. Perfect on AUM.
I will look if there's anything I can do from my end. Although I don't have Cream, which makes it hard to test this particular routing setup.
That AUM photos clearly indicates to Modstep developers something...
Thank you, all the best!
Both determined and productive as ever
Is anyone brave enough to post a list of well behaved and non well behaved IAA's ?? Kind of 'name and sham....' I mean encourage them to improve