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.
iPadOS 16: using StreamByter auv3 problem not showing keyboard to edit lines
![[Deleted User]](https://secure.gravatar.com/avatar/1c1077b2778f9583f19c9c2c88287881/?default=https%3A%2F%2Fvanillicon.com%2F7a185c239ad728d71535dad3f11317b8_200.png&rating=g&size=200)
As in the title.
Under StageManager LoopyPro minimise keyboard too fast when opening SB gui, under Drambo the keyboard shows properly. I use both apps together so I can edit in Drambo, save preset and load in LP.
Comments
This has been happening for a while, for me with StreamByter in AUM. It is not new with iPadOS 16. The only cure I've found is to force-quit and reload the host.
You don't need to use Drambo as a host for editing outside LP. You can edit in StreamByter stand-alone, Install Rules, then save the script to iCloud. Then you can load it in the AUv3.
I have this issue in both streambyter and in Mozaic. My fixes (for AUv3, not standalone. no issues in standalone for me):
The mozaic one works 90% of the time, the SB work 110% of the time. No need to reload hosts.
It seems if you attach the keyboard in a basic OS function, like saving or a built in iOS app, it resolves itself for a while.
I actually reported this and had a few convos w/ Bram Bos. He said it’s a real bitch to get keyboards attached in AUv3 and when you move the AUv3 window, the keyboard sometimes doesn’t know where to attach itself.
(i could be paraphrasing the a bit too much)
Edit: this issue appeared in iOS15 for me. Never had an issue before, but I only used Mozaic before. Can’t speak to when it appeared in SB.
@AlmostAnonymous . Thank you for doing the extra research. I forgot that I had noticed it in Mozaic as well. And it is a significant point that the keyboard is a "floating" object that needs to be attached (by the host) to the already floating AUv3 window.
Now it’s only my crappy code to cause me frustrations and not keyboards…..
….now back to putting logic conditions on else’s for me
facepalm.jpg
Thank you both for inspiration 🙏
Ok , it is related to connected novation launchpad mini mk3 which lastly get “keyboard” function.
When it is disconnected everything is like normal, but after connecting the onscreen keyboard no longer pop up , as iPad think I have connected normal keyboard to type.
Do you know guys how to enable “show keyboard” even if there is connected physically recognised keyboard?
Do you see a keyboard icon in the lower right of the screen? This would be when you're in a text entry field. This works for normal situations, with a real KB and a document editor, like Notes. Not sure if it would work in an AUv3. Also, you may still have the problem of AUM (or Loopy Pro) not allowing the keyboard to appear.
Do you need the keyboard commands? I haven’t updated my Launchpad (nor used it much) because of this new “feature”. Possible to downgrade the firmware to 1.0.5 or something?
Im consideing downgrade, dont know If possible. But… in case of working with SB … at least I know that simplest is… to disconnect Launchpad.