Feature Requests

It would be great to be able to create a page where you can type all kinds of information about your song using a notepad widget. What Instrument was used What Plugin was used What Preset Was Used General Song information It just needs to be a blank notepad widget that allows you to type whatever information you are looking to store about your song, with basic formating like Bold, Italic, Underline etc.

Hi.... the step dial takes up soOOOOooOOo much real estate. Is the step dial an important Widget: YES, but is it a real estate hog: Extra Yes !!! PLEASE provide a new flavor of it. A slider or incremented slider (step slider) with 'x' steps AND a text area to the right or left side of the slider (users choice for each instance) where the text of the current selected step is displayed. Allow the user to size BOTH SIDES.... the step slider part, AND the text display part independently. PROS: Allows step dial functionality on the screen using the same or nearly the same real estate as a button or slider. For those controller the slider via foot switch/expression pedal - they can minimize the slider or increment part, knowing their moving (nudging or selecting) it via their feet /MIDI and they get even MORE freed up real estate. Thanks Again!!! MLGA (Make Looping Great Again) ;-)

Open Loopy Pro on a separate device; hold close to original device; canvas extends onto new screen.

Loopy Pro has very weird master channel behavior that is not found anywhere else. For my purposes it is unusable and I have to use additional bus to serve as master channel. Rework master channel so that it applies effects only to the output selected in the master channel, volume changes only the output volume for that master channel.

Or « conditionnal actions »

I use radio button grids or step dials to manage "presets or patches" which are, by my definition, a set or collection of plugins, and also the specific presets for each of the plugins in the set. Each "preset or patch" in the step dial or radio button grid - is or has a UNIQUE set of plugins and/or plugin presets for each of plugins; this uniqueness allows state feedback to "light up" or show which radio grid button is active or last clicked - BECAUSE all of the action items for the SELECT action in the button or step dial complete. HOWEVER..... for some reason, e.g. maybe I changed something in a plugin, or deleted a plugin from some bus.... THEN the preset state feedback doesn't work :: because :: all of the action items in the SELECT action can't complete or execute; but there is nothing in Loopy to "help you" figure out which item, in a long list of action items failed to execute or complete. Trial and Error - here is PAINFUL - and time consuming. SOoOOOOOOo - my feature request is a "test" button (next to the existing delete button when you slide the ) that would test all of the action items in a SELECT action - and tell you when one fails. Perhaps the specific action item in the list could be a different color, like red - once the test runs and assuming an action item in the list failed. While Loopy is super powerful..... using it as a multi-fx process (like a replacement for a Line 6 Helix) requires a TON of configurations between plugins and UI components. It HAS TO GET easier to connect stuff - and troubleshoot when something goes wrong. Thanks!!

Clip details window and import window should have a field where you can enter the musical length of the clip (bars and beats) and have loopy calculate the original tempo from that.

Useful for modify the channel or any parameters of a send midi action for example