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.
VB3m - can someone please confirm, does NOT respond to ALL NOTES OFF (CC#123)?
I'm hosting it as an AUv3 in AUM, have made sure the CC filter of that channel is allowing all CCs, midi channels match, also that CC #123 is reaching the plugin - but notes do not turn off as they do with my other plugins. I've also checked VB3m's own prefs but there seems to be nothing there regarding this message. TIA
Comments
I did some further investigating with a much simpler setup of my controller keyboard connected to VB3m running standalone, and it appears it does not respond to either all notes off (CC #123) or all sound off (CC #120). I consider this ability basic to any midi-controlled instrument – but maybe there's something about this plugin I don't know. All my other instrument plugins respond to, at minimum, all notes off.
I don't have VB3m, so I can't say. I do know not all synths respond to CC#123. I've run into that often as a matter of fact. iOS app developers often aren't MIDI experts. More than once even something as basic as Sustain pedal has been overlooked.
If it's a bug or simply overlooked, I'm sure the developer would benefit from hearing directly about it.
My memory is completely shot, but I vaguely recall some older keyboards causing the opposite problem for me with plugins that I used with a sustain pedal hooked up to the same keyboard — I’d have to filter out CC123 because the keyboard would always send it after any final key up, overriding my sustain pedal over MIDI out. I have no idea if it’s a weirdly related issue. 🤷🏻
(To this day, ALL my AUM templates involving piano and other percussive instruments with long sustain are set up to filter out CC123.)
Yes, I've run into situations where I needed to filter out #123 but this isn't one of them!
Most if not all VB3m's parameters can be attached to midi controllers, and Guido has been at this for a long time. While he's done Mac & Windows apps for longer than iOS apps, CC 120 & 123 have been around since midi 1.0 and I find it hard to believe he simply forgot to implement them!
BTW I believe CC 123 is not supposed to cut off sustaining notes if implemented correctly. This from a website I just found - "Mutes all sounding notes. Release time will still be maintained, and notes held by sustain will not turn off until sustain pedal is depressed." (I'm guessing they meant to say "released" instead of "depressed").
There's only one way to find out.
I opened a ticket with them.
Yes, I’ve found that different plugins implement it in varying ways. It was enough to make it a blanket rule for all pianos! 😆 My guess is that devs have been deliberately baking this into their plugins!
It’s not just VB3m — plenty of other AUv3 instruments don’t respond to CC123. (I haven’t tried sending the message with a hardware controller, but just used Loopy Pro.) Curiously, AUM’s “All notes off” always works. I suspect it’s doing more than sending CC123 to the instrument.
I'll take a guess: it's keeping track of all the note on/off data passing to the plugin, and when you click "all notes off" it sends note-offs for any currently open note(s).My Mac hosting sw (Plogue Bidule) has a module that does this ("close open notes").
Yes, and I suspect there’s a good reason why it goes that extra mile!
GSi customer support replied to me very quickly - and confirmed that CC #123 is not implemented in VB3m yet - but a coming update will add it. That's nice.
What I use CC #123 for is to "idiot-proof" my iPad rig. I have a button on my controller that enables left-hand bass, zoning the key range to put a bass on the lower two octaves and transposing all other plugins down one octave. If I'm not careful to have no notes sounding when I switch, I get hanging notes. I send CC $123 to all my plugins every time I switch to & from left-hand bass mode as a safety measure.
Right. I use a little StreamByter script to implement a keyboard split on my MIDI controller, with knobs to transpose each side by different amounts. If I turn a knob uncautiously, that can create a hung note, so I implemented a "panic" button to send All Notes Off. It's def a feature that should be supported.
Great minds think alike!
I too use Streambyter for this. Crazy how easy this is to do with that app. Your use sounds a litle more involved than mine though!
My plugs are Korg Module & Virsyn AudioLayer (multiple instances of both), KQ Dixie, Synthmaster One, and VB3m - VB3m is the only one out of those that won't shut off its notes with CC 123, at least for now.