Feature Requests

Currently clips are named "CLIP 1, CLIP 2, etc." If an audio file is imported, the clip name has to be edited. If a user creates their file names to reflect song parts (such as "BASS-V1" for the bass audio for verse 1), allow an "Audio File Name = Clip Name" selection so the user does not have to rename all of the clips.

And honor the "Remember Playback State" when playing a group. Mutex behavior would mean that starting play on a clip would stop play on other groups and play all previously playing clips in the newly playing group. Currently mutex groups only work with the All loops play together. When building song sections real time, its would useful to have clips that are stopped within the group until manually starting then (say for bringing in an organ clip during ONLY the third chorus... for building dynamics of song).

Action to jump to a position in the sequencer timeline, or move back/forward relative to current position

There seems to be a non-linear acceleration curve for fader and encoder widgets which causes a slower/faster changes depending on movement and how much open/close the fader or encoder knob is. This concept works great for a mouse or a gamepad but it's not so great for touch control. This makes using the midi widgets for controlling values very unpredictable and unprecise imo. I like to suggest to add a linear curve as a property for these widgets with fixed speed options (low, med, fast). This is how MIDI Designer 2 does it which is simply the most accurate and versatile for touch control on iOS (still not the prettiest looking unfortunately 😂). Also I like to see the encoders to be fully 360 circular instead of just pan style. This would also make the range bigger and therefor even more precise with a linear curve. Thank you!

It would be nice to be able to set the time signature with an action.

In order to idle the effects on a hardware input channel when it’s not in use , loopy needs a way to mute the input the input (since mute is an output mute). An input gain parameter would be useful, too. This has been a source of confusion to people who hope that muting a hardware input will idle its effects. It would be handy if there were an option in the mute action to mute input/output or both. Would need some ui clue when input is muted.

Enter a 'listen' mode in the AUv3 window, then moving a parameter via the AUv3 UI selects that parameter for subsequent binding via MIDI learn. Basically like in AUM.

Like in most desktop DAWs, it'd be great to be able to use the connected computer keyboard (magic keyboard, Logitech combo touch, Bluetooth keyboard, etc) to play notes in an AUv3.

Title says itself. Ramp based on tempo: 1/64 - 1 bar and etc. As well keep option for time duration.