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.
Riffer 3 cc control of fast presets
I’m trying to get fast presets to respond to CCs in Riffer3. Midi in to Riffer3 is set to OMNI.
Shows that CC1 is assigned to fast preset 1, and CC2 is assigned to fast preset 2.
I’m using mfxconvert to convert midi note 0 (C-2) to CC1, and midi note 2 (D-2) to CC2.
Here’s the AUM routing:
I have verified that mfxconvert is doing its job by (temporarily) sending its output thru midi ctrl to another app, and also to midi monitor. The other app responds, and midi monitor shows the expected result.
When I send it thru to riffer though, the assigned fast presets don’t respond.
Anyone else have this problem, or am I missing something?
Thanks.
Comments
I don‘t know if it‘s relevant, but your midi conversion converts the volume of note C-2/D-2 to the value send with CC1/2. Maybe riffer expects th value to be exactly 127 to change a fast preset using a CC
That's what I was afraid of. I was pretty sure I've come across this before. Looks like a small Mozaic script will be more effective. mfxconvert doesn't have that capability. Whatever it gets for volume it sends with the CC.
Thanks for looking into it.
I just tested - as i suspected Riffer needs the value to be 127 to switch the presets.
Here a StreamByter script
or a Mozaic script
The Moazic script is a bit longer as it shows a short description, the conversion ‚work‘ is done in the OnMidiNoteOn. Mozaic blocks per default, while StreamByter passes everything though (so blocks were needed for the rest of the note-ons and all other midi events). Both scripts set their icon name to CONV.
If you don't insist on the default notes C-2/D-2 to CC#1/CC#2 conversion, the following scripts would be a bit more general: they convert each note-on to a corresponding CC # 127
StreamByter
.
Mozaic
Maybe one could also use two instances of mfxConvert in series, one converting the velocity of all notes to 127 and the second mfxConvert changing the note-on to CC as shown above in the screenshots.
Wow! Thanks for your work! That was where I would have been headed in Mozaic. I'm not sure mfxconvert can get to that level of granularity. I'll let you know if this accomplishes the objective!