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
Ok, so...
Grabs (MP first, followed by VK) followed by screen-rec:
https://vimeo.com/manage/videos/849192886
@el_bo : the MIDI looks the same in both. I don't see anything weird.
So, now back to BeatMaker 3. Let's rule out something funny with the MIDI setup in either BeatMaker 3 and/or MP.
Can you show screenshots of the MIDI Setup in each of those apps. In BeatMaker, let's look at both the MIDI setup in its AUDIO and MIDI Devices Settings and for the bank bank where you are using it. Also, show the screenshots of any setup panels in MP for MIDI Settings.
p.s. tag me or reply when you post or I might not see the added into.
@espiegel123 Ah, ok. Thought any reply would send a notification. Good to know that's not the case.
Here are the screenshots you asked for:
The first of the MP shots is the top-level MIDI menu. From there, I've taken 2 shots of the different ways of sending I've tried. Both end up with the same issues. I hope there's something obvious that I'm not seeing. but I keep coming back to the fact that the Beatmaker settings are fine as soon as i switch to Velocity Keyboard. And the MP settings are fine within AUM.
Within Beatmaker, I already tried all buffer sizes.
@el_bo: since Musix Pro is sending to BeatMaker 3’d virtual midi port, see what happens if you turn off musix pro in the BeatMaker 3 midi setup.
Btw, there is also midi setup n BeatMaker 3 for the individual tracks/instrument.
De-selecting MP in BM3 cuts the signal completely.
I have used the MID part of the sampler when threshold- sampling sections from IAA instruments. But it doesn't appear to be there when using AUv3. User-error, I'm sure...
Did another test, trying to play the internal keyboard and VK fast enough to induce crackling/popping. I did manage to get some clicks out of both if I played super-fast and haphazardly. However, the amount and loudness of the clicks came nowhere near to how they are with MP, and don't get triggered anywhere near as easily. Repeated the same test with iSEM standalone, its internal keyboard, VK and MP, and couldn't get any clicking.
So unless there's any other options that are strikingly apparent, this might just have to be put down to Beatmaker 3 being so long in tooth. And why so problematic with MP? Who knows? Clearly, there's going to be no point in writing to INTUA, though I had thought to write to Shiverware (Musix Pro developer). But not sure what the chance is that they'll be able to help.
What happens if you turn off the MusixPro input in BeatMaker 3 and uave the BeatMaker 3 input on?
Fwiw, having tried all the virtual keyboard apps I have and four different midi controllers with iSEM loaded in BeatMaker, without a glitch on an iPad 6...if the issue is in BM3, it is caused by something unusual and wouldn't be quick to ascribe it to BM3 being long in the tooth.
No sound input from MP when that connection is cut. Internal keyboard still works.
Good to know you checked with other apps.
I did go to the BM3 Appstore page. I'd forgot it was updated in 2021, which is atill pretty recent to my mind. So no...not long in any teeth. And I'm not bashing BM3 at all. In fact, once I'd decided not to sub to Logic, it became my platform of choice (Been decades since I've had a sampler-centric workflow).
Pre-Logic, i found it clunky with too many button presses and moving between tabs. Now, in comparison, it really flows. It does help that I spent more time with the manual and watched some key videos that suddenly made sense of things that had previously eluded/frustrated me.
I also really like the included 64-pad setup, and that would've been perfect except the zones for triggering velocities become so much harder to hit than with the 16-pad option. That's why I ended up trying MP and VK, both of which I've owned for some years. The pressure/hit velocity is much more intuitive and controllable, but I would still prefer not to have anything external connected to BM3 (IAA apps notwithstanding).
Anyway, rambling aside, there seems to be something very strange happening with this specific combination that doesn't appear with any other combo I've tried. And the solution will be to just avoid using alternative options for when I want to use iSEM.
I'm definitely open to conducting more tests, should you come up with more ideas. But for the moment I'm happy to let it go. Thanks for all your help with this. It's way above and beyond what I'd have hoped for. And I've learnt some stuff in the process.
Thanks, again.
Something sounds like it is set up wrong.
If MusixPro is set to send to the BeatMaker 3 MIDI port in MP, BM3 won't need the MP midi port turned on...because the MIDI will be coming in through the BeatMaker 3 port not the MP port.
Conversely, if MP is set up to send MIDI Out through its virtual port, you only need the MP port enabled in BeatMaker 3 and not the BeatMaker port.
In BeatMaker, go to the MIDI Setup for the bank and set it to receive all MIDI from all devices. This really means "all devices enabled in BM3's MIDI Setup".
Go to the pad's MIDI Setup and make sure it is set to use the bank's setting
In BeatMaker's MIDI setup enable only one port either the MusixPro port or the BeatMaker 3 port. Set MP to send to the port you selected.
Ah...This isn't something I've had to interact with yet. Will give it a go in the morning, and let you know how I get on.
Cheers.
@espiegel123
I did give a quick try with your latest instructions. Unfortunately, the same crackling issues persisted. I then tried to record the MIDI coming in. Managed to get MIDI on to the track, but on each attempt at playback (Also, once on record) the audio engine would get completely cut, and the iSEM instance would crash, necessitating a BM3 reboot.
Unfortunately I didn't do a screen-recording. I should have some time tomorrow or Monday, so I'll screen-record the entire process.
Bummer.
Bummer, indeed!
But...what if Musix Pro was just aggravating and masking the real issue?
Have attached a project file. Curious if you're able to get it to play?
I recorded the MIDI using BM3's internal keyboard. It contains a very quick looped-run, to recreate the crashing audio-engine situation I experienced with MP.
For context, I have an iPad 9. And when playing this line with the given preset, the CPU-meter flickers between 5 and 7% i.e certainly not anywhere near overload. Despite this, I can only get a couple of looped plays done before iSEM disappears from the keyboard view and the audio engine dies (I'm assuming that's what is happening).
I've tried the same MIDI loop with many other synths, with zero issues, even when swapping them in and out while the MIDI is still looping. So no 'kid-gloves' needed. Even Layr doesn't struggle.
I've not heard any crazy popping when the audio crashes, but obviously take precautions
Cheers
@espiegel123 Just giving a nudge in case you missed my last post.
I haven’t looked into it. When you say “audio system crash”, do you mean the AU crashed or that no tracks can make sound ?
Can you confirm that you were able to get musix pro playing by making BM3 the midi target and turning off musix pro as a source in BM3?
I can confirm I'm able to get musix pro playing by making BM3 the midi target and turning off musix pro as a source in BM3.
And trying the audio again, it seems that only iSEM crashes. At first the UI disappears from the keyboard view. But when trying to delete the plugin, it reports iSEM has crashed. But loading another plugin seems fine. So, not the audio engine as I originally thought.
Also, no rush to get back to me. I just had a feeling wither you'd seen it or I'd said something to piss you off.
@espiegel123
Been playing around with iSEM in AUM and have noticed on a few occasions that if I leave AUM idling in the background and return at a later moment it will likely have crashed.
As I hinted at earlier, perhaps the issue is general instability in iSEM that is then aggravated by some instability within Musix Pro.
It seems like it.
Perhaps, if you get a free moment some time, you could try that Beatmaker project and perhaps anyone else can chip-in to share if they have crashing issues with iSEM in AUM.
I appreciate your help, very much.
Cheers
Without even trying the project, I can say that iSEM seems more crash prone in BM3 than in AUM.
Have sent a support request to Arturia regarding crashing and general instability of iSEM.
It would be nice to be able to confirm that this is a more widespread issue rather than just a me issue, so if anyone else can test for crashing and instability in any host, I’d be happy to pass along more detail when they reply.
Cheers.