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
BTW, here's the registration link for the Universal version:
https://testflight.apple.com/join/9arSp29l
ENJOY!
This sorted the issue for me too. I’d forgotten that I’d set zoom this way.
Turns out I can’t use my phone generally without it being zoomed. Too small!
If I wanted to use this on iphone I’d have to change the zoom setting every time.
As noted by @MobileMusic, there seems to is a way to make the app ignore this. Which makes sense, as I’ve never needed to do this before.
Just updated to latest iOS 13 and AU works well. It didn’t on 12.3.1.
Just finished the new X skin, the next update is around Sunday/Monday guys!
Will the midi learn ever be fixed in this one?
Don't get the question ?
Which CC is not working for you?
cc 41 is shown as accepted by midi learn on synthmaster one but the knob does not move and parameter not changed. I'm using a novation Launch control and had no issue with this CC41 on other synths with midi input.
I been asking for about a year and a half, is it fixed now?
No.
Great thanks for your support! ..... NOT!
I understand your frustration but I can not fix something I can not reproduce. Did you log any MIDI messages sent by your controler when it sends that CC 41?
I sent you videos and screenshots in the past.
No as an answer is frustrating.
@kv331audio_bulent
Here is another video, shows midi cc 41 not working with SM1 and midi cc 42 does.
Also shows the midi cc 41 is being received in AUM via Streambyter
https://www.dropbox.com/s/o3b9zcs1ja5n2e9/Midi cc 41 not working with SM1 midi learn.MP4?dl=0
What I need is raw MIDI output of your controller. CC 41 is not treated in any way different than 42 in our products.
Dude I am not a developer, i gave you all the information i have. Please be more specific if you want more information, I have no idea what you mean by 'RAW' midi data? The video clearly shows the error. in this video like the ones i sent before you can see the midi CC in Streambyter.
I have no idea how your apps works but it doesn't midi learn on midi cc 41 for me as shown in the video.
Thank you sir for confirming.
Thanks for the video. I see that SM1 actually learned CC41 (when the popup menu shows up, the menu item displays "Remove link with CC41), but somehow it's not responding. will debug further tonight.
Just to confirm - I set a knob on my Nektar Impact controller to CC41. Confirmed in NS2 MIDI Learn that I was getting CC 41 and it was controlling the proper parameter in NS2. So it was working as expected in NS2 with a different AUv3.
I was able to assign the Nektar knob to a parameter in standalone SM1. SM1 recognizes the connection but doesn’t respond to it.
FURTHER BAD NEWS - now SM1 is not responding to learned CC’s that it did respond to earlier in my testing. Will investigate further.
Test in progress. Will resolve these issues before the next beta build.
Thanks!
i'm not helping on the beta so I appreciate an update to the live version please. You have ignored my messages for a year and a half so a quick fix would be great. Bah humbug.
Working great in my 6s Plus👍🏼
@kv331audio_bulent Save button dropdown menu in iPhone version has only 2 items (Save As and Set As Default) compared to iPad version. Both in standalone mode.
@kv331audio_bulent Scale menu is empty inside Cubasis as AU. It is displaying the keyboard in some custom scale (beige and yellow keys) by default and that's about it.
Keyboard X-Axis should be factory-defaulted to Glissando in AU mode as that's how all apps have their keyboard behavior set. Users would not use Off for X-Axis because gliding over keys doesn't do anything with Off.
I believe I fixed the issue today, it will be in the next beta (Sunday/Monday). Our v1.3 release date is January 6 if you don't want to check out the beta.
For presets in banks, this is the default behavior. Save the preset as a new one, and then it'll display the other menu items.
Thank you
Which CC is that?
Performance is somehow lower on iPhones. this is beyond our control.
65