Feature Requests

Description This feature request proposes the implementation of independent layout canvases for portrait and landscape orientations within Loopy Pro. Currently, the application utilizes a single canvas layout that adjusts based on device orientation. However, this approach can lead to suboptimal user experiences, as layouts designed for one orientation may not translate effectively to the other. By enabling separate canvases for each orientation, users can create optimized layouts tailored to the specific advantages of portrait and landscape modes. Problems Layout Distortion : A single canvas adapting to both orientations can result in stretched or compressed layouts, compromising usability and aesthetic appeal. Inefficient Workflow : Users may need to constantly adjust their layouts when switching orientations, disrupting the creative process. Limited Customization : The inability to design orientation-specific layouts restricts users from leveraging the unique benefits of each mode. Proposed Solution Dual Canvas System : Introduce the capability to design and save separate canvas layouts for portrait and landscape orientations. Automatic Detection : Implement automatic detection of device orientation to switch between the corresponding canvas layouts seamlessly. User Control : Provide settings that allow users to enable or disable the independent canvas feature based on their preferences. Examples Live Performance : A musician designs a landscape layout with expanded controls for live performances and a portrait layout with simplified controls for quick edits on the go. Studio Production : A producer utilizes a detailed portrait layout for intricate editing tasks and a streamlined landscape layout for mixing sessions. Educational Use : An instructor creates orientation-specific layouts to demonstrate different aspects of Loopy Pro's functionality during lessons. Benefits Enhanced User Experience : Tailored layouts for each orientation improve usability and visual coherence. Increased Efficiency : Reduces the need for manual adjustments when switching orientations, allowing users to focus on their creative work. Greater Flexibility : Empowers users to fully utilize the unique advantages of both portrait and landscape modes in their workflows. This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Separate layout (canvas) for portrait/landscape mode Wouldn’t it be awesome if the portrait and landscape settings were independent of each other? Having the possibility to shape the canvas in portrait mode but still be able to have a different layout in landscape mode. Let’s go! 💪

Description This feature request proposes the addition of a dedicated action to reload or replace AUv3 effect instances within the application. The aim is to enhance workflow efficiency by allowing users to reset or swap out effects seamlessly during live performances or production sessions. Problems Manual Reloading : Currently, reloading an AUv3 effect requires manual intervention, which can be time-consuming and disruptive during live sets or intricate production workflows. Lack of Automation : The absence of an automated action to replace effects hinders the ability to create dynamic setups where effects can be toggled or cycled programmatically. Performance Stability : Some AUv3 effects may become unstable over time, necessitating a reload to restore optimal performance. Without a quick reload option, this process can interrupt the creative flow. Proposed Solution Reload Action : Implement an action that allows users to reload a specific AUv3 effect instance, effectively resetting its state without the need to remove and re-add the effect manually. Replace Action : Introduce an action to replace an existing AUv3 effect with another, facilitating quick swaps between different effects within a signal chain. Integration with Actions System : Ensure these actions can be integrated into the existing actions system, allowing for assignment to buttons, MIDI controllers, or automation sequences. State Preservation Options : Provide options to preserve or reset effect parameters during reloads or replacements, giving users control over whether to maintain their settings or start fresh. Examples Live Performance Recovery : A performer experiences a glitch in an AUv3 effect during a live set and uses the reload action to quickly reset the effect without interrupting the performance. Dynamic Effect Switching : A producer sets up a sequence where different reverb effects are cycled through automatically using the replace action, creating evolving textures in the mix. Template Optimization : Users create templates with predefined effect chains and utilize the reload action to reset all effects to their default states before starting a new project. Benefits Enhanced Workflow Efficiency : Streamlines the process of managing AUv3 effects, reducing downtime caused by manual reloading or replacement. Improved Performance Stability : Provides a quick solution to reset unstable effects, maintaining the integrity of live performances and production sessions. Greater Creative Flexibility : Enables dynamic manipulation of effect chains, fostering innovative sound design and performance techniques. This summary was automatically generated by ChatGPT-4 on 2025-05-09. Original Post: I would like to be able to reload and replace the auv3 effect by long pressing, like the auv3 instrument, because TONEX often crashes on startup and I would like to make it easier to recover. I would also appreciate it if the settings connected to the radio buttons can also be fixed by reloading.

Description This feature request proposes the implementation of a dedicated action in Loopy Pro that allows users to set the length of a clip directly via a widget or MIDI control. The goal is to enhance live performance flexibility by enabling dynamic control over clip lengths without navigating through menus or manually adjusting settings. Problems Manual Adjustment Required : Currently, setting a clip's length necessitates manual configuration within the clip's settings, which can be time-consuming and impractical during live performances. Limited Real-Time Control : The absence of a widget-based action to set clip length restricts performers from making spontaneous adjustments on the fly. Inconsistent Workflow : While actions exist to multiply or divide clip lengths, there is no straightforward method to set a clip to a specific length directly through a widget or MIDI command. Proposed Solution Introduce 'Set Clip Length' Action : Develop a new action that allows users to define a specific length for a clip (e.g., 1 bar, 2 bars, 4 bars) directly through a widget or MIDI control. Widget Integration : Enable this action to be assigned to on-screen widgets, such as buttons or dials, facilitating quick and intuitive adjustments during performances. MIDI Learn Compatibility : Allow the action to be mapped to MIDI controllers, providing hands-free control over clip lengths. Quantization Options : Incorporate quantization settings to ensure that length changes occur seamlessly in sync with the project's tempo and timing. Examples Live Looping Performance : A musician uses a MIDI foot controller to set the next clip's length to 4 bars before recording, allowing for precise loop durations without manual intervention. Dynamic Arrangement : During a live set, a performer adjusts clip lengths in real-time using on-screen widgets to create evolving musical structures. Studio Workflow Enhancement : A producer assigns different clip lengths to various buttons on a MIDI controller, streamlining the process of building complex arrangements. Benefits Enhanced Performance Flexibility : Provides performers with the ability to adapt clip lengths on the fly, fostering creativity and spontaneity. Improved Workflow Efficiency : Reduces the need for manual adjustments, allowing for a more streamlined and intuitive user experience. Greater Control Precision : Enables exact specification of clip lengths, ensuring consistency and accuracy in musical arrangements. This summary was automatically generated by ChatGPT-4 on 2025-05-16.

Description This feature request proposes the implementation of dynamic audio destination switching in Loopy Pro, mirroring the flexibility currently available for MIDI routing. While Loopy Pro allows users to enable or disable MIDI destinations dynamically through actions or MIDI bindings, similar functionality for audio routing is absent. Introducing this capability would enhance live performance adaptability and streamline complex audio setups. Problems Static Audio Routing : Currently, audio destinations are fixed once set, requiring manual reconfiguration to alter routing paths, which is impractical during live performances. Inconsistent Control Paradigm : The disparity between MIDI and audio routing flexibility can lead to confusion and limits the potential for cohesive control schemes. Limited Live Adaptability : Without dynamic audio routing, performers cannot easily adjust their audio signal paths in response to real-time needs or creative decisions. Proposed Solution Action-Based Audio Routing : Introduce actions that allow users to switch audio destinations on-the-fly, similar to existing MIDI destination controls. MIDI Binding for Audio Destinations : Enable MIDI controllers to toggle or select audio destinations, facilitating hands-free control during performances. Widget Integration : Allow widgets to control audio routing paths, providing visual feedback and touch-based control within the user interface. Examples Live Instrument Switching : A guitarist uses a footswitch to reroute their signal from a clean amp setup to an effects-heavy chain during a solo. Dynamic Vocal Processing : A vocalist toggles between different vocal effect chains for verse and chorus sections using on-screen buttons. Studio Workflow Optimization : A producer quickly switches audio outputs between monitoring systems and recording devices without navigating through menus. Benefits Enhanced Performance Flexibility : Performers can adapt their audio routing in real-time, responding to the dynamics of a live show. Streamlined Workflow : Reduces the need for manual adjustments, allowing for more focus on creative aspects during both live and studio sessions. Consistent Control Experience : Aligns audio routing capabilities with existing MIDI routing features, providing a unified and intuitive control environment. This summary was automatically generated by ChatGPT-4 on 2025-05-25. Original Post: A setting to switch destinations for audio inputs on the fly available to gesture or widget. This setting is currently available for midi destinations but not audio Being able to solo a destination on the fly would avoid the current method of creating multiple inputs for same mic and soloing the input channel. Problem Having a mic input routed to multiple destinations means it is monitored through every destination which is problematic. Being able to solo destination would solve this problem.

In the bottom left screen, there are fixed ICONS to change the functional "view" of LP - see picture. I am going to mess up the functional names of the ICONS, but look at the attached picture. An ICON for UI Edit mode. An ICON for Mixer Mode. An ICON for Track View Mode..... all good stuff. These fixed ICONS on the bottom left put the software into what I have called here as "functional views". PLEASE - All clicking of these ICONS, or if you will, the action to change the view of LP into these different functional modes to happen via UI Widgets. SoooOOoooo.... I can create a button or step or dial or whatever widget, map or bind it to a MIDI foot switch and then change from Mixer Mode to Track View Mode, to whatever Mode - WITHOUT having to reach out to the screen and press these ICONs down on the bottom left. You can certainly leave the ICONs there and let function "as is" - for backwards compatibility. ALSO..... in a separate feature request, which I cannot find at the moment.... I asked for a new functional LP mode where ONLY the UI is visible, and by this I do not mean the UI to edit it, but the ENTIRE UI....with NO Mixer at all being shown. SooOOOoo.... if other functional views are created as suggested immediately above; then please allow those other functional views or modes to be accessed or changed via widget actions as well. Thanks Again for Great Software!!!

The idea is to store the state of the currently playing clips, so they can be used in a clip action later on for either start, stop, solo, clear, stretch, etc, even after multiple other actions have occurred. A simple way to do this would be to add "Currently playing clips" to the list of saved parameters, and add "previously playing clips" or "stored playing clips list", in the target of the actions on clips.

Would be nice to be able to group tracks together in the sequence. For grouped track we could have two modes: collapsed . A "read only mode" where you can all see the merged waves for midi in the timeline. I am guessing a blank rectangle is also fine expended mode : expose the tracks normally This would help the mixing in the sequencer, specially for several loops of the same instrument.

Description: Introduce the ability to assign pages to custom categories (e.g., “Content Pages”, “Widget Pages”, “Utility Pages”, etc.) and use this categorization to control both navigation behavior and visibility in different modes (e.g., Edit Mode vs. Normal Mode). Problem: Currently, all pages are treated the same in terms of navigation and visibility. However, many users structure their sessions with specific types of pages: Audio content pages (e.g. song sections) Widget/control pages Utility or setup pages There’s no way to group these or to define navigation behaviors or visibility based on page type. This makes it harder to: Navigate through relevant pages efficiently Hide non-performance pages during live sets Implement focused workflows Proposed Solution: Allow users to assign each page to a custom category (e.g., from a dropdown in Edit Mode) Enable actions to scroll/navigate only within a specified category (e.g., "Next Page in Category: Content Pages") Add a setting to hide certain categories in Normal Mode , but always show all in Edit Mode Benefits: Cleaner and more focused performance mode by hiding non-essential pages Faster navigation by limiting page scrolling to relevant sections Better organization of complex setups with many pages Enhanced flexibility for designing workflows tailored to live performance, studio use, or experimentation Examples: A performer could scroll only through "Content Pages" during a live set while keeping "Widget Pages" hidden in Normal Mode. An action like "Next Widget Page" could cycle through pages marked as widget pages without affecting content navigation. This summary was automatically generated by ChatGPT-4 on May 17, 2025.

Description: Users would like to have a built-in Low-Frequency Oscillator (LFO) or impulse generator within Loopy Pro to control various parameters dynamically. This would add movement and modulation capabilities to effects and controls, enhancing the creative potential of the software. Problem: Currently, Loopy Pro lacks built-in LFO or impulse generation, limiting users who want to automate parameter changes in a fluid and rhythmic way. This forces users to rely on external plugins or complex setups to achieve dynamic modulation. Proposed Solution: Integrate one or more LFOs that can be mapped to any parameter within Loopy Pro. Include common waveform types (sine, square, triangle, etc.) for versatile modulation. Add LFO settings to the binding menu, similar to press, double tap, long press, slide, or a new dedicated button. Allow users to set rate, depth, and phase for each LFO. Enable MIDI and automation support for LFO control. Benefits: Introduces dynamic control over parameters without needing external plugins. Expands creative possibilities, particularly in live performance and sound design. Provides an intuitive way to add modulation and movement to effects and instruments. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes the ability to convert an existing widget between Fader and Dial types without having to delete and recreate the widget. The goal is to streamline the UI customization workflow and preserve widget configurations during visual adjustments. Problems Redundant Workflow : Currently, if a user wants to switch a Fader widget to a Dial (or vice versa), they must manually delete the original and recreate the new widget from scratch. Loss of Configuration : This process risks losing existing bindings, parameter settings, styles, and actions tied to the original widget. Time-Consuming in Complex Layouts : In large or layered setups, replacing one widget type with another can disrupt the design and require manual re-alignment and reconfiguration. Proposed Solution Widget Type Switch Option : Add a toggle or dropdown in the widget settings to convert between Fader and Dial types. Preserve All Attributes : - Parameter bindings - MIDI/OSC mappings - Actions and behaviors - Size, styling, and position Optional Appearance Reset : Offer a checkbox to reset to default style for the new type, or retain the current styling where compatible. Examples Layout Tweaking : A performer wants to switch a vertical Fader to a compact Dial for better space usage, without redoing parameter assignments. Aesthetic Adjustments : A user redesigns a page layout and prefers Dials for consistency. With this feature, they can quickly convert all Faders without data loss. Iterative UI Design : During testing, a creator toggles between widget types to decide which feels best, without re-binding or repositioning every time. Benefits Faster UI Prototyping : Enables fluid workflow for experimenting with control layouts. Preserved Logic : Maintains all functional connections and behaviors. Better UX : Saves time, reduces error risk, and improves overall design flexibility in Loopy Pro’s UI system. This summary was automatically generated by ChatGPT-4 on 2025-05-16.