Feature Requests

Description: Introduce a DJ- or sampler-style “Slicer” mode that divides a clip into rhythmic slices and allows instant triggering of those slices — either via a grid, MIDI controller, or touch input — similar to features found in tools like the Korg Volca Sample, Roland SP-series, or Serato-style slicers. Problem: Loopy Pro currently lacks a dedicated slicer interface for rhythmic or pitch-based clip triggering. While clips can be manually trimmed or edited, there’s no native way to divide a loop into steps or beat slices and jump between them in real time. This limits live remixing, finger drumming, and creative beat manipulation — especially for users coming from DJ or sampler hardware. Proposed Solution: Add a Slicer Mode or Slicer Widget with the following capabilities: ✅ Core Features: Divide a clip into N slices (based on grid: 1/4, 1/8, 1/16, custom) Trigger slices manually via: - Touch (grid layout) - MIDI pad controller - Key or widget-based input Slices can either: - Jump playback instantly - Retrigger as one-shots - Sustain while held ("Hold-to-Play") ✅ Volca Sample–Style “Step Jump” Mode: Hold a step to jump playback instantly to that slice Release returns to original timeline (optional) Behavior: momentary jump vs. latch Compatible with looping playback or free-running ✅ Additional Options (as requested in comments): Slice-to-MIDI (assign slices to specific MIDI notes) Per-slice FX, reverse, or pitch control Sequence slices in the Step Sequencer Map slices to individual AUv3 chains (optional advanced use) Benefits: Enables performance styles like beat juggling, stuttering, slice remixing Opens new creative workflows for DJs, finger drummers, loop-based performers Bridges the gap between clip looping and classic sampler-style triggering Makes Loopy Pro more competitive with hardware samplers and iOS tools like Koala, Samplr, Blocs Wave Examples: Load a breakbeat, slice into 8 steps, trigger each slice live via MIDI pads Use a Volca-style jump to step 5, then release to resume loop from original timeline Play a sliced vocal phrase chromatically via MIDI mapping Trigger rapid-fire slices in sync with quantization for glitchy textures This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Slicer version that mashes up features from a DJ style slicer (as in Serato or Djay Pro) and Volca Sample's step jump feature. – Retrigger selected slice at adjustable timings (1, 1/2, 1/4, 1/8, etc) – Retrigger selected slices in sequence (as in Volca Sample Step Jump) – Hold function to keep slices selected after fingers lift off

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 This feature request proposes the implementation of an action within Loopy Pro that enables users to record directly into the next available clip of a specified color. The goal is to streamline the recording process, especially during live performances, by allowing for efficient and organized clip management based on color coding. Problems Limited Visual Feedback : On certain MIDI controllers, such as the APC40, it can be challenging to distinguish between clips that contain content and those that are empty, as the brightness levels are similar. This ambiguity can lead to recording over existing clips unintentionally. Workflow Inefficiency : Currently, users must manually select the next available clip for recording, which can be time-consuming and prone to errors, particularly in complex projects with multiple colors and pages. Limited MIDI Controller Integration : Users with MIDI foot controllers that have a limited number of buttons face challenges in assigning specific controls for each clip, restricting their ability to manage recordings efficiently. Proposed Solution "Record to Next Clip in Color" Action : Introduce an action that, when triggered, records into the next available (empty) clip of a specified color. This action can be assigned to on-screen buttons or MIDI controller inputs. Color-Based Clip Selection : Allow users to define the color context for the action, ensuring that recordings are directed to the appropriate set of clips. Integration with Existing Systems : Ensure compatibility with Loopy Pro's current action and MIDI control systems, allowing for seamless integration into existing workflows. Examples APC40 Integration : A user assigns the "Record to Next Clip in Color" action to the buttons beneath each column on the APC40. Pressing a button records into the next available clip of the corresponding color, simplifying the recording process during live performances. Multi-Page Template Management : A user has a template with multiple pages, each containing clips of different colors. By assigning the action to color-coded buttons on a dedicated page, the user can efficiently record into the appropriate clips across various pages without navigating through each one manually. MIDI Foot Controller Usage : A performer with a MIDI foot controller assigns the action to a limited number of footswitches. This setup allows for hands-free recording into designated clip colors, enhancing live performance capabilities. Benefits Enhanced Live Performance Flexibility : Enables performers to manage recordings efficiently, reducing the risk of overwriting existing clips and minimizing the need for manual navigation. Improved Workflow Efficiency : Streamlines the recording process by automating clip selection based on color, saving time and reducing the potential for errors. Expanded MIDI Controller Integration : Provides users with limited-button MIDI controllers the ability to manage recordings effectively, maximizing the utility of their hardware. This summary was automatically generated by ChatGPT-4 on 2025-05-09.

Description This feature request proposes redesigning the Send FX and Panorama encoders to visually resemble dials, aligning them with other control elements within the application. The goal is to enhance visual consistency and improve user experience by providing a more intuitive interface for adjusting these parameters. Problems Visual Inconsistency : Currently, the Send FX and Panorama encoders differ in appearance from other control elements, potentially causing confusion and disrupting workflow. Limited Readability : When multiple sends are added to a single channel, it becomes challenging to discern the current value states, hindering precise adjustments. User Interface Clutter : The existing design may contribute to a cluttered interface, especially in complex projects with numerous sends and panorama adjustments. Proposed Solution Dial-Based Design : Redesign the Send FX and Panorama encoders to adopt a dial-like appearance, consistent with other control elements in the application. Enhanced Visual Indicators : Implement clear visual cues, such as color coding or value markers, to indicate current settings and facilitate quick adjustments. Customizable Controls : Allow users to choose between different control styles (e.g., dials or sliders) based on personal preference and workflow requirements. Examples Mixing Multiple Sends : A user working on a complex mix with several sends per channel can more easily identify and adjust send levels using the redesigned dial interface. Stereo Imaging Adjustments : A producer fine-tuning the stereo field of various tracks benefits from the intuitive dial representation of panorama controls. Live Performance Tweaks : During a live set, a performer quickly adjusts send effects and panning using the visually consistent and easily accessible dials. Benefits Improved User Experience : A consistent visual design across control elements enhances usability and reduces the learning curve for new users. Increased Efficiency : Clearer visual indicators and intuitive controls enable faster and more accurate adjustments during mixing and performance. Enhanced Aesthetic Appeal : A cohesive interface design contributes to a more professional and polished appearance of the application. This summary was automatically generated by ChatGPT-4 on 2025-05-09.

Description: Introduce an optional echo cancellation feature in Loopy Pro to reduce feedback and echo when using external speakers and microphones in the same environment. Problem: When using Loopy Pro with external audio gear (e.g. microphones routed through Loopy and output via speakers), feedback and echo artifacts are common, especially in live or rehearsal settings. Currently, users have to manage this manually with gain staging, mic placement, or external hardware/software — which is not always practical or effective. Proposed Solution: Add a built-in echo cancellation option that: Actively analyzes the output signal and suppresses its re-entry via the input Works similarly to echo cancellation in video conferencing apps, but optimized for musical use Can be enabled per input channel or globally Includes adjustable parameters for fine-tuning (e.g. cancellation strength, latency tolerance) Benefits: Reduces risk of feedback in live performance or rehearsal setups Makes it easier to use Loopy Pro with open speakers and microphones Enhances experience for vocalists, acoustic instrumentalists, and loop-based performers without needing in-ear monitoring Lowers technical barrier for mobile setups in public or small room environments Examples: Singing live into a mic with Loopy Pro effects and output through nearby PA speakers Looping acoustic instruments without headphones in a controlled feedback-safe setup Using Loopy Pro in classroom or workshop settings with ambient mics and speakers This summary was automatically generated by ChatGPT-4 on 2025-05-17.

Description: Expand the list of project-level actions that can be assigned to buttons, widgets, or MIDI triggers within Loopy Pro. Problem: Currently, only a limited set of project-wide actions can be triggered via assignable controls. Users working with complex live setups often need quick access to deeper project-level functions (e.g. opening specific panels, toggling metronome, changing clock settings, or modifying project routing), but these are not currently assignable. Proposed Solution: Extend the Action system to include more project-wide options such as: Toggle metronome Show/hide mixer, clips view, or routing view Change tempo or time signature Trigger project-level automation or scene transitions Load a specific scene or reset project state Start/stop all clips globally These options should be available in the same Actions menu used for widgets and MIDI bindings. Benefits: Offers more control flexibility for live performers and power users Reduces reliance on manual navigation during performance Enables complex workflows with fewer taps or gestures Enhances accessibility for hands-free or MIDI-only control setups Examples: A footswitch that toggles the metronome or opens the routing matrix A MIDI pad that instantly jumps to a specific scene or resets project tempo A widget that shows/hides all FX chains or mixer view This summary was automatically generated by ChatGPT-4 on 2025-05-17.

Description: Loopy Pro users would benefit from the ability to enable or disable specific actions and follow action entries via checkboxes. This feature would streamline live setups by allowing users to quickly toggle actions without needing to delete them entirely. Problem: Currently, to deactivate an action or MIDI binding, users must delete it. This makes it cumbersome to experiment with different setups or quickly make adjustments during a performance. Additionally, there is no visual indication of which bindings are active or inactive. Proposed Solution: Introduce checkboxes next to each action and MIDI binding for quick enable/disable functionality. Inactive bindings should be visually greyed out for better clarity. Display a summary of total actions, showing both active and inactive counts, with a clear distinction (e.g., green for active, red for inactive). Allow toggling of follow actions globally or per project/color/clip. Include a widget for quick control over enabling/disabling actions and follow actions. Benefits: Faster and more intuitive control over action setups. Improved usability for live performance adjustments. Reduced risk of accidentally deleting important setups. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description This feature request proposes enhancing the MIDI routing interface in Loopy Pro by displaying the track name and icon within the MIDI destinations boxes. The goal is to improve clarity and usability when assigning MIDI outputs, especially in complex projects with multiple tracks and destinations. Problems Lack of Visual Identification : Currently, MIDI destinations are listed without accompanying track names or icons, making it difficult to quickly identify the target track, especially when multiple tracks are involved. Workflow Inefficiency : Users must rely on memory or trial-and-error to determine the correct MIDI destination, which can slow down the setup process and increase the likelihood of routing errors. Limited Scalability : As projects grow in complexity, the absence of clear identifiers in MIDI destinations hampers efficient management and scalability. Proposed Solution Display Track Names : Modify the MIDI destinations interface to include the name of each track, providing immediate textual identification. Include Track Icons : Alongside track names, display the associated track icon or color, offering a visual cue to further aid in quick identification. Consistent UI Integration : Ensure that these enhancements are consistently applied across all areas where MIDI destinations are selected or displayed, maintaining a uniform user experience. Examples Live Performance Setup : A performer sets up multiple MIDI tracks to control different instruments. With track names and icons visible in the MIDI destinations, they can quickly assign outputs without confusion, ensuring a smooth performance. Complex Project Management : In a project with numerous tracks, a producer can efficiently route MIDI signals by visually identifying tracks through their names and icons, streamlining the workflow. Educational Use : In a teaching environment, instructors can demonstrate MIDI routing more effectively, as students can easily follow along by recognizing track identifiers in the interface. Benefits Enhanced Usability : Provides clear visual and textual cues, making MIDI routing more intuitive and reducing the learning curve for new users. Improved Efficiency : Speeds up the process of assigning and managing MIDI destinations, particularly in large or complex projects. Reduced Errors : Minimizes the risk of routing mistakes by allowing users to easily confirm the correct destination through recognizable identifiers. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Description: A MIDI keyboard widget that can be added to a layout in Loopy Pro, similar to the existing pads widget. This widget would facilitate a cohesive layout without the need to reposition or toggle the keyboard during a jam session. Problem: Currently, users rely on the Velocity Keyboard AU for most projects, but it lacks integration with Loopy Pro’s layout. Additionally, mapping a range of MIDI notes to multiple buttons is cumbersome, as each note must be assigned individually. There is also no simple way to transpose all keys together, such as using octave up/down buttons. Proposed Solution: Develop a built-in MIDI keyboard widget for Loopy Pro that offers: Velocity-sensitive key input similar to the Velocity Keyboard AU. Integrated octave up/down transposition for quick access to a broader note range. Flexibility to add, reposition, or hide the keyboard easily within a layout. Customizable layouts to accommodate different use cases, like live performance or studio setup. Benefits: Simplifies live setups by integrating a keyboard directly into the Loopy Pro interface. Reduces dependency on external AUs for basic MIDI input. Offers a more intuitive and flexible solution for MIDI control. Facilitates live looping by allowing quick transposition and note access. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Allow users to defer project tempo detection to a loop other than the first — enabling Loopy Pro to set the project tempo based on a later, user-selected loop. Problem: Currently, Loopy Pro determines and locks the project tempo based on the very first recorded loop. This limits flexibility in sessions where the first loop is not rhythmically relevant or is intended to be free-tempo (e.g. ambient texture, drone, or vocal swell). Users have no option to tell Loopy Pro to wait and derive the tempo from a different, later loop that better represents the intended timing. Proposed Solution: Add a feature that allows users to: Bypass tempo detection from the first loop Optionally choose which loop (e.g. second, third, or any later one) should define the project tempo Or let Loopy Pro auto-detect tempo from the first rhythmically meaningful loop This could be implemented as a toggle or dropdown in the project/session settings. Benefits: Greater control over when and how project tempo is set Enables free-form intros and ambient starts without locking the grid too early Better suited for complex arrangements and live workflows where rhythm develops gradually Improves compatibility with creative, non-linear loop layering Examples: First loop: ambient pad (no timing) → ignored Second loop: rhythmic guitar riff → sets tempo Third loop: beatbox loop → sets tempo while earlier ones remain unquantized This summary was automatically generated by ChatGPT-4 on 2025-05-17. Original Post: Currently, LP fix the project tempo thanks to the first loop recorded. The aim of this new feature is for LP to fix the project tempo thanks to the detection of the tempo of a loop other than the first one (or first ones pre-chosen).