Feature Requests

Description This feature request proposes the implementation of flexible groove quantization options for MIDI recording in Loopy Pro. The goal is to provide users with advanced tools to adjust the timing and feel of MIDI recordings, enhancing musical expression and aligning with various rhythmic styles. Problems Rigid Quantization : Currently, Loopy Pro offers basic quantization settings that may not accommodate the nuanced timing required for different musical genres or personal playing styles. Limited Groove Customization : Users lack the ability to apply swing, shuffle, or custom groove templates to MIDI recordings, restricting creative possibilities. Inconsistent Timing Feel : Without flexible groove quantization, achieving a humanized or genre-specific rhythmic feel requires manual adjustments, which can be time-consuming and imprecise. Proposed Solution Advanced Quantization Options : Introduce a range of quantization settings, including swing percentages, shuffle rhythms, and customizable groove templates. Real-Time Groove Application : Allow users to apply and adjust groove settings in real-time during MIDI recording and playback. Groove Template Library : Provide a library of preset groove templates representing various musical styles (e.g., funk, jazz, hip-hop) and allow users to create and save custom templates. Visual Feedback : Implement visual indicators within the MIDI editor to display the applied groove adjustments, aiding in precise editing and alignment. Benefits Enhanced Musical Expression : Flexible groove quantization enables users to infuse their MIDI recordings with desired rhythmic feels, enhancing the musicality of their productions. Streamlined Workflow : Real-time groove application and visual feedback simplify the process of achieving the intended timing, reducing the need for manual corrections. Creative Versatility : A comprehensive set of groove options allows users to experiment with different rhythmic styles, fostering creativity and innovation in their music. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: Allow users to assign custom names to individual AUv3 effect instances within Loopy Pro, enhancing clarity and organization in complex projects. Problem: Currently, AUv3 effect instances in Loopy Pro are labeled with their default names, which can lead to confusion when multiple instances of the same effect are used. This lack of distinction makes it challenging to identify and manage specific effects, especially in intricate setups. Proposed Solution: – Enable renaming of each AUv3 effect instance directly within the Loopy Pro interface. – Display the custom names prominently in the mixer and effect lists. – Ensure that these custom names are saved with the project and persist across sessions. – When the custom label is deleted, the instance should automatically revert to showing the default AUv3 name. – Optionally, allow for color-coding or tagging of renamed instances for additional visual organization. Benefits: – Improves workflow efficiency by making effect instances easily identifiable. – Enhances project organization, particularly in complex or collaborative environments. – Reduces the likelihood of errors caused by misidentifying effects. – Aligns with standard practices in other DAWs, providing a familiar experience for users. This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Allow users to rename audio busses and optionally add visible notes or hints describing their function or purpose. Problem: Currently, busses in Loopy Pro are automatically named with letters (A, B, C...) upon creation, and users are unable to rename them. This makes it difficult to organize and recall bus functions, especially in complex projects with many busses. The default visual representation is also hard to distinguish from color groups, making the UI harder to parse quickly. Proposed Solution: – Allow users to rename busses at any time – Display the name prominently (e.g. at the top of the bus or next to the letter) – Optional: restore default letter-based name (e.g., "A") if custom label is deleted – Add support for a “hint” or “notes” field for each bus (shown e.g. on hover or toggle) – Consider visual improvements to further differentiate busses from color groups – Optional: provide a UI dialog showing an overview of a bus’s routing and settings, including name, balance, etc. Benefits: – Greatly improves clarity in complex routing setups – Reduces need for external “cheat sheets” – Helps identify and manage up to 24+ busses more efficiently – Enhances UI and UX, especially for live performance or sound design – Makes Loopy Pro more scalable and user-friendly for professional workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: The feature request proposes the ability to copy, move, or swap actions between two widgets within Loopy Pro. This would greatly streamline workflow, especially when working with complex setups. Currently, there is no efficient way to transfer actions between widgets without manually recreating them. Problem: When setting up multiple widgets, it can be tedious to replicate or transfer actions, especially in scenarios where similar actions need to be applied across multiple widgets. The lack of a copy, move, or swap function leads to redundant manual work. Proposed Solution: Introduce a feature to easily copy, move, or swap actions between two widgets. This could be implemented with a "Pin" function that allows the user to mark a widget, then switch to another widget and choose to copy, move, or swap the actions. Additionally, the feature should support replacing existing actions when moving actions from one widget to another. Benefits: Saves time when managing complex action setups. Reduces the need for manual copying and configuration of actions. Improves workflow efficiency by allowing users to quickly duplicate or transfer action sets. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Users want the ability to create custom effect chains in Loopy Pro, consisting of AUv3 and built-in effects, which can be saved and recalled as presets. This feature should include the ability to split signals based on frequency, volume, stereo (LR) or dual-split, and apply distinct effects to each split path, with the option to merge the processed signals back at the end. Problem: Currently, Loopy Pro only allows routing an audio signal directly to the next plugin, without flexible signal splitting or parallel processing. This limitation prevents more advanced audio setups, like multi-band processing or complex effect routing, which are common in multi-FX setups like Axe Fx III. Proposed Solution: Implement a modular grid system to route audio signals dynamically, similar to multi-FX processors. Allow users to split audio based on specific parameters (frequency, volume, stereo channels). Enable combining processed split signals at the end of the chain. Save and recall these custom effect chains as presets. Make it possible to integrate channel strip savings for easier project management. Benefits: Greatly enhanced audio processing flexibility. Efficient setup for advanced sound design and multi-effects. Simplifies workflow by allowing preset recall for complex signal chains. Facilitates creative sound manipulation during live performances. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Enable saving and recalling entire channel strips (including all plugins and optionally widgets) as presets. This allows fast loading of complex FX/instrument chains across different projects. Problem: Rebuilding plugin chains and settings for each project or channel type (input, color, bus, master) is time-consuming, especially in live setups or when consistent tone is needed across songs. Proposed Solution: – Add a feature to save a full channel (strip) as a reusable preset – Optionally include bound widgets and layout elements – Allow importing/exporting channel strip presets – Add "recall channel preset" and "save channel preset" actions – Allow presets for: – input channels – color channels – bus channels – master channel – Optional: grey out unloaded channels to free up RAM/CPU – Optional: preload (but inactive) channel strips for fast switching – Optional: include full widget configuration (position, behavior, etc.) – Add tags or labels to organize channel strip types (e.g. “Guitar FX”, “Vocal Bus”) Benefits: – Save time during project setup – Allows modular, reusable channel configurations – Supports consistent tone in live and studio workflows – Ideal for musicians switching instruments/effects between songs – Reduces CPU/memory load by offloading unused channels – Encourages structured and repeatable setups This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description This feature request proposes the implementation of a customizable metronome widget in Loopy Pro, offering enhanced control over its visibility and functionality. The widget should support actions to show, hide, or automatically hide after the first loop is recorded. Additional customization options include resizing, color adjustments, and shape selection. Proposed Solution Visibility Controls : Introduce actions to: - Show the metronome widget. - Hide the metronome widget. - Automatically hide the widget after the first loop is recorded. Customization Options : - Resizing : Allow users to adjust the size of the metronome widget to fit their workspace. - Color Adjustments : Enable color customization for: - The current beat/bar. - Already played beats/bars. - Upcoming beats/bars. - Shape Selection : Provide options to switch between rounded and square shapes for visual elements. - Beat/Bar Indicators : Option to display or hide the number of the beat/bar on each shape. Integration with MIDI/OSC : Ensure the metronome widget's visibility and actions can be controlled via MIDI or OSC messages. Synergy with Other Features : Consider integrating the metronome widget with the perennial progress bar feature, allowing measures of the metronome to be freely configured or linked to a certain loop. Problem Limited Control : Currently, users have minimal control over the metronome's visibility and appearance, which can be distracting during performances. Lack of Customization : The inability to resize or recolor the metronome limits its adaptability to different workflows and visual preferences. Integration Challenges : Without MIDI/OSC control, integrating the metronome widget into complex setups is cumbersome. Benefits Enhanced User Experience : Providing visibility controls and customization options allows users to tailor the metronome to their specific needs, improving focus and reducing distractions. Seamless Integration : MIDI/OSC support facilitates integration into advanced setups, enabling synchronized control across devices and software. Workflow Efficiency : Automatically hiding the metronome after the first loop helps maintain a clean workspace, allowing users to concentrate on their performance. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Introduce a complete set of clip region editing tools — including cropping, muting, navigation, snapping, and layer targeting — all accessible via Touch, MIDI, and Actions . The entire process should be usable flexibly with either direct interaction, external controllers, or programmable workflows. Problem: Currently, Loopy Pro requires touch interaction for detailed clip editing. There is no way to perform the full process — selecting a clip, defining a time region, and applying edits — via Actions or MIDI. This limits efficiency, prevents integration with hardware controllers, and interrupts creative or live performance workflows. Additionally, there's no way to toggle between snap-to-grid and free placement modes. Proposed Solution: Implement a fully parallel editing system where all functions can be used via: Direct Touch MIDI input Assignable Actions Feature Set: ✅ Clip Targeting: Open a specific clip Scroll/browse through clips on canvas or within groups (e.g. “next/previous clip”) Select clips via MIDI or widget actions ✅ Region Selection: Define editable region via bars, beats, %, samples, or milliseconds Use fixed-value actions (e.g. “crop bar 2 to 4.5”) Live “region cursor” control with MIDI or UI widgets – including during playback ✅ Editing Actions: Crop / Uncrop Mute / Unmute Apply to entire clip or individual overdub layers ✅ Snap Mode Toggle: Action to switch between Snap-to-Grid and Free editing modes Affects region selection precision (e.g. exact beats vs. free dragging or scrolling) ✅ Unified Access: Every step in the process is available via Touch, MIDI, and Actions — fully interchangeable Works with haptic controllers, footswitches, or touch-only setups No dependency on one specific input method Benefits: Maximum flexibility for performers, producers, and live users Enables complex, precise clip editing workflows without workflow interruptions Supports accessible and hands-free operation without limiting touch-based workflows Ideal for glitching, loop refinement, dynamic arrangement, or performance prep Examples: Touch to select a clip, then crop a bar with a two-finger gesture — or do the same using a mapped button Use MIDI to scroll through clips, define a time region with an encoder, and crop on beat 3 only Toggle Snap mode to align edits to bar grid or work freely with off-grid precision Mute overdub layer 2 from 1.5s to 2.2s using only widget buttons This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: I would love to be able to crop specific bars in a clip. Let’s say I record 16 bars of guitar and then decide that I want to keep bar 4-8. The editor makes it very hard to make the start/stop points fit perfectly to create a seamless loop. I can crop the clip perfectly in the sequencer, but I would like to be able to do the same at "donut level" :)

Description: Loopy Pro users would like the ability to create multiple timeline regions within the sequencer, allowing for more flexible arrangements and looping possibilities. Problem: Currently, the sequencer only allows for one continuous timeline looping region. This limitation makes it challenging for users who want to set up more dynamic and flexible arrangements, especially during live performances or when experimenting with song structures. Proposed Solution: Implement the ability to define multiple timeline regions that can loop independently or in sequence. These regions should be customizable, with options for setting different loop lengths and behaviors. Additionally, an arrangement widget that functions like a master timeline would allow for quick restructuring during performances. Benefits: Enhanced flexibility for live looping and performance. Ability to experiment with different song structures without stopping playback. Improved workflow for users who want to set up looping regions with minimal interaction during performance. This summary was automatically generated by ChatGPT-4 on 2025-05-07.