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.
Anyone have Chrome iOS/Vanilla issue where you can’t see what you type.
Anyone else getting this? Where the keypad covers what you type so you can’t see it? It means you can’t use the auto-complete for tagging, etc. Is it a Vanilla Forum thing or Chrome?
Comments
Yep I’m getting this issue right now as I type. I’m using iPhone SE.
Long press the KB icon, in the very bottom right of the iOS KB.
If it says ‘Dock’ , select that to re-dock the KB.
That happened to me out of the blue, too.
KB got undocked somehow.
This was on an iPad, though.
Maybe you are having an iPhone issue that is different.
Worth a check, though.
just put few enters first (after you tap into textarea for writing), then scroll up and write your text :-)
problem si just that the texarea where you write mesaage is initially small and it enlarges itself durimg you write, in each new line - but page is not scrollimg up automatically
Thanks for the suggestions. This is new so I’m wondering what has changed. Maybe I will test that setting on the iPad and see if it fixes the iPhone as I get the problem on both devices.
Cheers.
This worked great on the iPhone! Thanks
![:) :)](https://forum.loopypro.com/resources/emoji/smile.png)
The whole forum could need a bit of love on mobile devices. There's many nuts-driving issues, like:
This seems like a Chrome issue, as Safari works fine for me. But I get the same issue with Chrome.