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.
New StreamByter script : Velocity Enhancer
After several weeks of learning, imagining, scripting, testing and fine-tuning, I am proud to present my first serious attempt : Velocity Enhancer
https://audeonic.boards.net/post/5431/thread
This script is dedicated to all virtual pianos enthusiasts who are looking to improve the response of their Midi controller.
It all started from a dissatisfaction I experienced with one of my keyboards (an optical midi sensor retrofitted in an upright piano). Inconsistencies from note to note or with a same repeated note, some “hot” notes (vel = 127) under some circumstances, inconsistencies in trills and arpeggios and a sense of energy lost in fast runs where it should not…
So this script will fix most of these issues (sometimes partially) and give the impression you play on a keyboard with more inertia and evenness.
It relies on the following basic physical principles :
- the faster you play, the faster your fingers must depress the keys to move at the requested pace, thus the higher the velocity
- the faster you repeat a note, the lower the variation of velocity between 2 strokes.
- in a certain extend, the previous statement is also true for fast consecutive different notes
So the idea is to apply some kind of initial compression to spare some headroom (somewhere between 5-15 points of velocity) and use this additional headroom to implement the principles described just above.
It should also provide a sense of greater dynamic range as in any case :
- if your keyboard output is set high : you can't have any more your keyboard repeatedly max out at 127
- if your keyboard output is set low : you will be able to exceed your current maximum reachable value
In the 1st screen you set the parameters, in the 2nd screen you monitor incoming velocity versus outgoing velocity.
Parameters :
- Headroom : apply a kind of compression to decrease the overall velocity and creates some “room” for the extra velocity bonus that will be generated during the further steps
- Memory : time during which previous velocity values are remembered for smoothing (strength decreasing exponentially)
- Speed Feedback : how much playing speed can generate extra velocity (try this with arpeggios, tremolos)
- SF_Threshold : velocity above which speed feedback engages (‘below the threshold, speed feedback applies negatively)
- Derivative : Increase the variations of 3 consecutive increasing or decreasing values (for example, the succession of values 30-50-80 will become 30-50-90). This acts like an edge sharpening in image processing to counteract the former smoothing/denoiser.
You can use it in a AUv3 host or in standalone mode.
In the latter case, I recommend to use Midimittr : plug your incoming MIDI in Midimittr, send it to Streambyter, from your virtual instrument select only Streambyter as Midi source.
Hope you will enjoy !
Comments
Interesting! Thanks for sharing. I’ll give this a spin during the week.
It would be an interesting idea apply an LFO to modulate the changes in velocity and then drive it from Rozeta LFO or mLFO.
Cheers. I’m not that familiar with StreamByter but I just copy and pasted the script, then installed, then saved locally. I should be good to go correct?
Also just to confirm you just load this in your midi fx chain like Mozaic. Correct?
Yes.
Yes.
I hope everyone realizes StreamByter is free. There are some very cool Streambyter scripts on the audeonic forum. You don't have to understand the code to use the scripts.
It’s still free. That’s cool. I got it when it went free awhile ago but I thought they eventually gave it a price again. Guess I’m mistaken.
Thanks. Yea I’ve loaded about 10 scripts but I always forget about the app. Thanks for making this, sounds cool. Gonna try it out later.
It took me quite long to understand how wonderful StreamByter is. And yes, free ! 🙏
How many scripts are buried in that forum? I loaded everything in the boutique when I first downloaded, but is there gold in them hills, lol?
You scared me... I had to check using Safari on my Mac since the iPad store won't show you a price on something you own:
https://forum.audiob.us/uploads/editor/r6/cluf5e1mc8uq.png
You can always check the current price of an app you own by searching for it on AppSliced.
Good point... using Safari or any browser on IOS or whatever.
It sounds like it could be useful. It would be nice to hear an example of a composition/recording that is improved by this.
I've been thinking it would be nice to use some kind of "velocity curve compressor" when playing notes on a Launchpad, because the most sensitive setting is really sensitive, and it would be nice to have that increased resolution without such inconsistent velocities. But for that, I was thinking it might be a good idea to have three "velocity layer" esque ranges, where the incoming value is magnetized toward 64, 100, or 127.
I suppose the goal would be similar to your "derivative" setting. I'm curious to know if you tried any algorithms that were left on the cutting room floor. And are there situations when you wouldn't use this? When I hear "Speed Feedback" I'm picturing Fur Elise being played on an Akai MPK Mini. But...maybe you have a lower end hammer action keyboard like I do, and you're just more aware of its shortcomings.