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
It's out!
I have to say, this is a fascinating little plugin. I'll be exploring it further.
Thanks, Fred!
This is what I thought too, it’s what I was expecting. Fosfat is very useful but quite limited, specially in that it only has one type of noise.
I’m a bit disappointed because, unless I’m doing something wrong, in Fizzica you can’t select a frequency range that the envelope follower will listen to. My intended use is for example to add some noise to a dull or very bassy kick so it stands out, or add some low end to a thin snare, etc… But without a frequency range selector the fizz is applied to everything, which might be what you want but is less useful if you want to target a specific element.
I thought that the “specialized auv3” as compared to the module in Punchlab would allow for this but doesn’t seem like it.
Its still cool in the use case I mention if you add it to individual tracks but I’d be nice to be able to target specific elements in a drum loop or cases where for example you want to just affect the low end to make it stand out…
Fizz would make for an interesting addition to Bandit too -- that would have allowed for just this use case.
I agree. It is much more flexible than the Fizz module in Punchlab but it would be great to be able to apply the effect only to a specific frequency band.
Could always use this “Multiband” app and then put your fizz on your desired band?
https://apps.apple.com/us/app/multiband/id1522438777
Good shout. I actually did this but the wiring got a bit complicated with the sidechain multi as well, etc. very do-able though and it’s the way I will use Fizzical if it’s a big ask for the developer.
After further investigation (and unless I'm overlooking something obvious), I wouldn't mind seeing a comb filter added to the options. Just my 2¢.
And to be clear, I do like this plugin so far.
I’ve played yesterday and this morning with FAC Fizzica, and I can confirm that it is a completely different beast from Fosfat. The best feature for me is external input via sidechain, it opens up a lot of possibilities, and it’s right in my alley.
Congratulations to @FredAntonCorvest! 🤩 This tool is simple but versatile. Light on the CPU and joy to use.
Yeah, it’s different and not suitable for your needs. I also hoped it would replace Fosfat in the same regard, with so many modulation options instead of just one noise. I think that the noise in Fosfat is there just to slightly boost energy in that particular freq. range.
Here is my video demo for Fizzica
Hi, i just want to inform you that i published my Mozaic script Keytrack FAC Fizzica that allows to keytrack the AUv3 parameters MAIN.Freq and MAIN.Filter_cutoff with note and pitchbend support.
It features separate +/- octaves and +/- semitone offsets for these two parameters and pitchbend range configuration.
How does it work:
Incomming note-ons and pitchbends are converted into two 14bit pitchbend values (computed from the base note, the offfsets, input pitchbend and scaled into the range of the respective Fizzica parameter) and send out on channed 16 for MAIN.Freq and 15 for MAIN.Filter_Cutoff . These resulting pitchbend messages can then be routed to the respective FAZ Fizzica AUv3 parameter so that the freq and cutoff follow the note input.
The parameter modulation of FAZ Fizzica works on top of the freq modulations of the script, they are applied to the keytracked base settings.
For instance you can configure a closing resonant filter that starts 4 oktaves above the note being played that moves down until 2 octaves above the base frequency of the current note (using -24 semi mod).
Like FAZ Fizzica, the script is monophonic (and OMNI), it reacts to note-ons and pitchbends on all channels. There is no midi forwarding, only the new two pitchbends are send out.
.
Why can‘t i simply convert the notes to CC values and use these to drive the AUv3 parameters ?
Due to the different frequency ranges of the main frequency, cutoff frequency and frequencies corresponding to midi notes its not possible to simply directly convert notes into CCs and uses these as input for AUv3 parameter automation. These 7bit values are not precise enought to select the correct frequency values. With 14bits its a lot better, but still there are minimal freq offsets like 440.1hz instead of 440hz.
.Very cool Ki, thank you for this!
It works flawlessly, now it’s a completely different game with Fizzica. 🤩 Ki, thank you so much!
Just updated the Keytrack FAC Fizziva script v1.1 that supports higher positive octave offsets for both Freq (-5..+7) and Cutoff (-3..+7) while keeping the double-tap to zero feature of these knobs.
Hey Ki, Can you please make the option to change pitchbend message channels 15 and 16? It would be great to be able to use more than one Fizzica in the AUM project. 🫶
@Luxthor No problem, there are two unused knobs on the MAIN.Cutoff page ;-)
I will also add an option to disable the sending of each of the PBs with the new channel selection knobs. (Ie OFF, or channel 1-16) . And add a warning if both are configured to the same channel.
Hmm, perhaps it‘s clearer to move the pb-range knob to the MAIN.Cutoff page so that each of the pages has 1 unused knob that than can be used to configure the output channel for that page, preferable at the same knob position with the same label making it easier to describe in the instructions.
If i would go for the option to put both output channel knobs on the Main.Cutoff page (where 2 knobs are currently unused), i would need quite long knob labels to show their purpose and its inonsitent to configure the Freq channel on the page meant for Cutoff configuration…
I still would prefer to keep the pb range on the first visible and probably more used Freq side. But there are only 4 knobs, so have to choose between the downsides of the two options…
Oh, that would be great! 🤩
Or, you can use one knob for pairs (both cutoff and freq.): 1-2, 3-4, 5-6, 7-8, 9-10, 11-12, 13-14, and 15-16. I think five instances of controlled Fizzica are more than enough for anyone.
Too late, already implemented and uploaded v1.2 with independand channel config
I also just checked that the text length for SetKnobLabel 3,{𝘰𝘶𝘵 𝘤𝘩 15+16}“ would have been too long due to the italic unicodes counting as several chars and Mozaic UI starts clipping that to „𝘰𝘶𝘵 𝘤𝘩 15+…“
I just tested it, and it works like a charm. 🤩 Now we can put multiple Fizzicas in one channel and do triads, seventh, and even ninth chords, haha. I bet Fred didn’t even count on this one.
Ki, for one more time, thank you so much! You moved Fizzica to another level with a simple Mozaic script. 🫡
I have a code for the fastest to react, enjoy 😉
NKKFWN63FFKA
Code already claimed when I checked just now. Thank you for the offer though - very kind 🙏
Thank you, @FredAntonCorvest, for the fast feature update. Now it’s easy for anyone to MIDI control the main frequency and filter cutoff. 👍🫶
Don't miss the midi-control of the envelope output value (Enable Midi Control for the Envelope Source).
Oh, this feature works fantastic with mod-wheel! If you need to draw an automation curve even better, I’m usually using internal or external signals, but this is a great addition.
Yepp, I would have liked to see an option to control the 'envelope sensitivity' with the mod-wheel (ie. the ring around the envelope circle) but I can always map it with something else, this would have been super handy to control the modulation depth when the envelope follower is being used.
Cheers!
Who would keep Fizzica and maybe beef
vs Punchlab
I could buy Fizzica on a deal
Or just buy Punchlab.
Punchlab is more versatile but Fizzica does its audio rate modulation thing better than the audio rate modulation module in Punchlab. So it really depends what you are looking for. Beef vs Punchlab? Hmm, not sure, never compared directly and haven’t used Beef in a while.
Cheers Gav.
Apps are good.
Closer to the Wormhole ( Than Before )
Locked