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.
Button-based volume adjustment interfaces all have the same flaw
I would be interested in hearing feedback on this. I've wondered about this for a long time, and it doesn't only apply to volume adjustment, but basically to ANY continuously variable value.
Most, if not all, button-based volume regulation systems (Volume Up/Down buttons, keyboard shortcuts for the same, etc.) provide a very frustrating experience because they treat these button presses or keystrokes like REGULAR KEYSTROKES MEANT FOR TYPING.
What I mean is that the first press changes the volume by a certain stepped amount, then there's a delay, then the volume suddenly changes dramatically because "Key Repeat" kicks in and the volume changes uncontrollably and quickly in too many steps in too little time (especially if you have a high key repeat rate set in your system settings, which is USEFUL FOR TYPING, but NOT for changing the volume).
This is highly frustrating for adjusting an analog value.
It would be far better if the volume just simply changed smoothly at a constant rate while the key is being held.
i.e.
- hold key 0.1 seconds = volume changes by 10%
- hold key 0.3 seconds = volume changes by 30%
This would be far more intuitive and less frustrating.
Has not a single hardware/software engineer realized this in the 50 years since button-based analog value changes came about?
Comments
Agreed.
I don't think the length of time held should adjust the amount it increases by I think that's too much for the user.
If you can manually adjust the amount that it increases by then it would be even better.
Press hold for 1 second (abitriary number here) and it starts to increase
by the amount the user requests in a menu/popup errmm value input thingy.
I've known hardware to be able to do this.
I cant remember precisely off hand but it's often used in hardware.
My external reverb units for instance.
Just in regards to iOS specifically, I think they are making pretty broad assumptions about the reason a user would hold the button as opposed to repeatedly pressing it. I don't know why they think this is a safe assumption, and I've personally had more than one occasion of being blasted with loud noise as a direct result of this. But, these are do-all systems that try to account for every possible use scenario across any conceivable software that may be run on it. Specialized hardware, like an audio interface with a volume knob, will always work better for niche tasks.
Purely speculation here, but I doubt that an organization as large as Apple, Google, etc. are basing a lot of design choices around what hardware and software engineers realize (or don't realize).
I think you misunderstood, what I mean is that the volume simply changes at a constant rate while the button is depressed. No "key-repeat" or "typing delay" shenenigans. Just the logically (and technically) simplest implementation possible.
OK. That's some relief 😄
Yes, me too. There's also the infamous Bluetooth bug where randomly, the volume of a Bluetooth audio device (headphones, ...) would suddenly go all the way to 100% for no reason -- it SOMEHOW seems to be related to pressing the volume buttons, YouTube and locking the device, but nobody knows how. Certainly not Apple, as the bug has been there for years!
Not really. The OS, even in a complex device like a smartphone, is perfectly and accurately aware of the state of all hardware buttons. It's really trivial to do what I outlined above. Complications arise of course as soon as you try to assign MULTIPLE meanings / functions to the same button. But in that case, you should simply add MORE BUTTONS (not REMOVE them, as manufacturers have been doing for years 🙄)
I did understand what you were describing however I prefer set increments
rather than one that adjusts according to length of time that the button is depressed
hence why I mentioned an input vaue for the rate.
So instead of
hold key 0.1 secs = changes by 10%
held key changes by incremental value set by user.
I put together something like this in dRambo awhile back which
involves key presses however I think it could be modified for continous use.
OK. I find this baffling. Why would you prefer this? It just reduces flexibility. Why not simply a continuous variation? Like an analog knob does. I mean nobody would prefer a turn-knob with fixed increments to a continuous one for adjusting something like volume. Or am I crazy?
Ahhh.... I see you want it to behave like an analog knob???
In that case I see where you're going with the length of time=value change.
If I want a knob to feel like an analog knob I simply map it my midi controller.
Sorry that was me being selfish there in my thoughts.
Have you actually tried this knob thingy? and what is it going to be used for?
When I've used buttons like this on hardware the rate is fixed
Press for x secs and the value changes at a set rate.
hence why I mentioned a user value input.
Sure, I agree with you about the potential. They (in my observation) are trying to cover as many bases as they can with the buttons they provide. The volume buttons on iOS devices support both fixed and ramping increment/decrement, and they (again observation and guess here) seem to feel like that is good for "all cases." Compared to a device that is purpose-built for some task, it's likely to fall short in some ways.
One issue I have had with the iPhone, specifically, is that the volume buttons are easy to hit accidentally. I've had instances of working in a vehicle engine bay, with bluetooth headphones or earbuds, and my volume button got pressed against the fender or bumper, etc. In those cases it takes me too long to retract and get my hands free to rip the headphones or earbuds off. I'd almost rather have no buttons at all, and just rely on the touch slider in the iOS control center.