Feature Requests

Please allow control of font size for radio buttons and stepped dials. I can see a bit of complexity with implementing this because different items in the list will often have different number of text characters. But there could just be a single font size setting for the whole widget and any text that’s too long to fit will be automatically downsized just enough to fit.

Not a huge bug, but on the file saving screen the little icon to indicate announcements keeps reverting back to showing a red dot to indicate there are new messages. But despite the red dot re-appearing, it's still the same old two announcements from April every time I look.

So basically it would be very handy to save all widgets and the plugins they control as a module/preset that can be loaded and added into an existing project. If say you have a synth and some midi and audio FX all controlled by widgets, and you want to load that whole "instrument" into another project so you can mix and match "modules", that would save a lot of time compared to remaking it from scratch in the current project. I realize this can be done by loading loopy as an auv3 into loopy, but then you can't use auv3 as part of the preset/module being inserted so that's a huge downside. This can be done by having an option to save a project as a "module" that can be inserted/loaded into a different project (by adding the saved widget pages to what's already there and by adding the associates tracks and plugins to all that's already loaded in the project) Or alternatively it can be a self contained “module” that can be inserted into a track, kind of like loopy can be inserted into itself as an auv3, except this way it would also be able to contain 3rd party auv3’s. In effect this would allow creating and sharing modules of instrument and effect chains / racks with their own widget performance pages.

(See screenshots below) Example of stop count-out quantization point before downbeat: The last beat of a loop contains pickup notes that lead into the beginning of that loop each time it goes around, but when I've triggered the loop to stop to go to a new section of the song, I don’t want those pickup notes to play right before the loop stops. So I would set the stop count-out quantization point to -1 beat so that the clip stops 1 beat before the downbeat. Example of stop count-out quantization point after the downbeat: I want a bunch of loops to stop for a breakdown section or the end of a song but it would sound more musical for them to stop after playing the final downbeat. So I would set the count-out quantization to happen an eighth note after the downbeat (+0.5 beats). Example of record or play count-in quantization before the downbeat: I want to record pickup notes leading into the downbeat of a loop. And every time I trigger that loop to play, I want it to start with those pickup notes. (A similar thing can already be achieved with the Record Intro setting but it only plays the "intro" pickup notes the first time, not every time the loop repeats). How it could be implemented: This option would exist anywhere that you can set rec, play, and stop count-in/count-out quantization. This includes Clip Settings as well as Play/Stop and Record actions. Underneath where you select between None, Master, Loop, or Custom, there would be a slider titled something like "Quantization Point Offset". It would default to 0 in the middle. If you slide it to the right the quantization point would happen later by however many beats or fraction of a beat (a positive number) and if you slide it to the left the quantization point would happen earlier instead (a negative number). Just like other count-in/count-out quantization settings, this could be set independently for record, play, and stop The count-in/count-out display on the clip could reflect the quantization point offset (if any) as shown in the screenshots

I want to be able to reorder the buttons in a grid, not just the actions. When we click reorder for actions, it should let me move buttons too. Pain point: I have 10 buttons with 6 actions in each, that enable/disable/chang effect plugins. If I decide to add a new one at the top, I can't without a lot of painful moving.

The count-in quantization is useful to get loops aligned, but also to get a minimal amount of time before the recording starts if you're triggering the loops using the ipad screen. But if you're triggering very near the end of the current cycle, you won't get any time at all and the recording will be starting almost instantly. This forces you to pay close attention to the clock cycle and can be quite tricky to anticipate just listening to the loops currently playing if they are of various length. It would be nice to be allowed to set a minimum amount of time / beats that the count-in must have, otherwise it will just wait for the next cycle.

I was told this forum wasn't for bugs, just feature requests. There should be a site similar to this where bugs can be posted and viewed by others. You know like a classic bugzilla db or github bug db or something. That lets people browse existing bugs to see if their issue has already been reported, and lets others vote, and see if there is any fix pending. Much as folks can see what new features are pending here.

CURRENT STATE: The metronome sound output can only be routed to the 1 or 2 or both 1+2 outputs. PLEASE - allow additional output options: 1) As MIDI notes to a MIDI channel 2) As audio 'clicks' to an audio bus channel The 1st option lets a user create a MIDI channel to receive the MIDI notes generated by the Metronome, which can then be sent to their drum machine of choice to generate any click sound they want; which can then be further routed to an audio bus. The created MIDI channel (solely created for the Metronome MIDI output) - appears as a routing option in the Metronome routing dialog box. The 2nd option lets a user, without the need for a drum machine or MIDI, have a unique and separate audio bus channel as a "click track". This option would REQUIRE, that the user create an audio bus channel to receive the metronome clicks. Then again - this audio bus channel appears as an output routing option in the Metronome dialog box. The 2nd option is critical - if a user exports their recording session for import to another DAW (Logic, Cubase, Pro Tools, etc.). Now they can get both the audio tracks (which LP already provides), and a separate /unique click track that lines up with the audio track. The "lines up" with or is in time with the recorded audio tracks is critical. This makes editing any imported audio much, much, much easier since you have the click track the user recorded with. Thanks Bro AJ

You can copy/past/move/reorder actions to whatever level and entry as well. You can copy/past/move/reorder full menu levels . Each entry (no matter what menu level) can be selected from a third widget.

If, then, else.