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
I do feel that it should always be possible to adjust any setting with an accuracy down to the smallest displayed interval. It’s maddening that e.g. many otherwise great EQs merrily and unavoidably skip over hundreds or even thousands of Hz as their smallest actually achievable increment, despite the numerical figures suggesting the full range. But it’s just not possible to get to those values the knobs or sliders skip over. I’m bemused that this is true even of some EQs claiming surgical precision.
The taper property
An example of setting up the cutoff frequency knob in the https://github.com/AudioKit/ROMPlayer/blob/master/RomPlayer/Controllers/AUMainController.swift
freqKnob.range = 100 ... 16000
freqKnob.taper = 4
freqKnob.value = 1000
That taper formula is based on a specific formula (which you can find in the code). If you're asking about how to do more basic logarithmic stuff in Swift, you can see examples in the Analog Synth X repo cutoff knob.
In Swift, constants start with let. For the sake of accuracy, that's not a constant, it's a variable.
If your intention is to change the knobSensitivity based on touch position, that functionality could be added in the setPercentagesWithTouchPoint method in the Knob class.
You could also easily modify the functionality to change the knobSensitivity based on vertical vs horizontal movement.
For example, to make the knobs move through values slower when moving up/down:
knobValue -= (touchPoint.y - lastY) * knobSensitivity/2
If you manage to find out yourself and send me proof, I’ll give you a promo code for an IAP of your choice
Simply offering code. I make no claims that it is good.
I imagine there are performance issues at play in all this as well. some sort of screen sampling cycle rates when It comes to detecting touch input... (Insert hand waving and grunting)
Etc...
Double-tap on any amazing ape knob and you'll find a slider to control its responsiveness. They're capable of intricate fine control. I maintain that they're excellent and if the developers are reading this thread, I'd just like to say thank you
Swish! Lol
I do think it’s possible to improve the performance and standardization of app controls but it’s dependent upon having some sort of consensus among users and developers as to how that should work and having enough developers engaged and committed to such GUI standards.
Until AU come along, even existing standards such as MIDI and MIDI sync were implemented differently. Even with AU when something as basic as how presets are saved and shared isn’t addressed you end with a situation where some AU apps are able to share the same presets among different AU hosts whereas others fail to do so and you have to recreate presets in each new app.
If there was a subscription or some sort of social funding campaign to improve the infrastrure for music app development, I’d be all for it. I think @analog_matt with Audiokit and the work @Michael has done in the past have been in this vein.
In addition, many developers operate from a cross platform economic model and unless there’s a viable cross platform solution for these issues, they won’t be able to participate in such a solution.
Regarding a cross-platform UI Library, there is a popular DAW manufacturer working on creating an open-source UI/UX library. They are planning on open sourcing it... Kind of an alternative to the JUCE UI tools... And will require learning a unique scripting syntax. Regarding setting knob sensitivity to some sort of universally accepted metric/scaling, I'll suggest it to the head dev. Lots of good ideas on this thread!
I've probably already said too much. 🤭Carry on.
@tja said:
I don't understand. All my apesoft apps (Idensity,Ipulsaret,Stria) have a double tap feature to easy adjust the sensitivity for the controls. You can even enter a value using the on-screen keyboard. No problems at all fine tuning the controls using my fingers.
You must have very strange fingers.
I'm ambivalent on on this one. I do like the 'shift' in concept, but I do not like to have to use two hands. More often than not I'm holding my iPad with one hand. Trying to hold down shift with one finger, then stretch over and move another is close to impossible. If there's a shift button, it should be a toggle. Tap once to push it down, then again to release it. IMO.
I like something similar. One tap sets it permanently. A subsequent tap turns it off (as you describe). If however you long hold the button, it activates it but then on release turns it off. Then the tappers get their way as do the holders.
This absolutely applies to any and all apps. Cubasis I'm calling you out here too.