Feature Requests

Description: Add a portable presets system with two layers: (1) structural templates for buses/instruments/routings (including AUv3 chains and MIDI mappings), and (2) preconfigured widget templates (buttons/faders/knobs) that already target common parameters or global actions. Templates can be saved to a personal library and inserted via drag-and-drop into any project. Problem: Across projects, users repeatedly rebuild the same setups: specific bus chains, instrument routings with MIDI color/channel mappings, and widgets that control basics like “Bus B volume,” “Master volume,” or “FX toggle.” Recreating these from scratch is slow, disrupts creative flow, and results in inconsistent control layouts. Proposed Solution: Structural Templates: Save buses/instruments with their AUv3 chains, routings, sends, colors, and MIDI mappings. Option to include/exclude audio/midi clips. Widget Templates: Save ready-to-use controls (buttons/faders/knobs/grids) prebound to targets (e.g., bus volumes, effect parameters, global actions). Library & Browser: Project + user library with tags, favorites, search, preview, and versioning. Smart Insert: Conflict-aware import that remaps colors/channels, resolves name clashes, and prompts to create missing buses or reuse existing ones. Dependencies: Detect missing AUv3s and offer placeholders or alternative device mappings; show a summary report post-import. Scope Options: Insert as new, or Apply Template to Selection (update an existing bus/instrument). Share/Export: Pack templates (with optional assets) into a sharable file for collaborators; support drag-in to install. Shortcuts & Actions: “Save Selection as Template,” “Insert Template,” and “Replace With Template” actions for rapid workflow and controller mapping. Benefits: Huge time savings for both complex chains and simple, frequently used controls. Consistency of mappings and UI across projects, lowering on-stage errors. Encourages experimentation—drop in a complete chain + control surface in seconds. Easier collaboration and onboarding via shareable, versioned template packs. Examples: Save a Guitar Bus (Input 2 → Bus B → AUv3 FX chain) plus a pre-mapped fader; reuse it across multiple projects instantly. Insert a Ravenscroft275 instrument template mapped to a MIDI color with a sustain toggle button already wired. Drop a Master Utilities widget set (Master fader, Reverb Send, Mute/Panic) onto any page; targets auto-bind to the current project’s buses. Share a Live Vocals Chain pack (preamp → de-esser → comp → delay send) with a labeled control strip for a touring rig. This summary was automatically generated by GPT-5 Thinking on 2025-08-25.

Description: Add a tag-based browser for Instruments & Effects (genre/name/favorites), a small header clock, support for background images on buttons, groove accent controls, and mixer usability upgrades: collapse/expand from anywhere and swipe navigation that preserves access to key controls (sends/pan). Problem: Large device lists are hard to browse without tags, favorites, and flexible sorting. Performers often want a discreet time-of-day clock on the header. Visual identification of buttons is limited to text/emoji; custom images would improve recognition. Groove/metronome accents aren’t easily adjustable to emphasize feel. Mixer sections collapse only from the left, slowing layout management. Horizontal swiping can hide essential controls (sends/pan), increasing errors mid-performance. Proposed Solution: Tagged Browser: User-defined tags (e.g., Bass, Keys, Ambient ), star/favorite, multi-sort (A–Z, tag, last used), and filters; “Collections” (saved filters) for quick recall. Header Clock: Optional, minimal, theme-aware time-of-day readout with 12/24h and show/hide toggle. Button Background Images: Per-widget image fill (PNG/WebP/SVG), fit/cover modes, tint/opacity, nine-slice safe text area, theme-contrast warnings. Groove Accent Controls: Accent strength (0–100%), per-beat pattern editor (e.g., 1 e & a), swing/feel presets; expose variables for labels/LEDs. Mixer Collapse Anywhere: Collapse/expand controls on each section/group; double-tap to toggle; remember state per page. Swipe-Safe Mixer: Sticky column option for pan/sends (stay visible while scrolling), plus a “Quick Controls” overlay (press-and-hold) to adjust pan/sends without losing position. Benefits: Faster device selection with meaningful organization and favorites. Clear, unobtrusive timekeeping during shows. More legible, personalized UIs with image-backed buttons. Tighter rhythmic feel via adjustable accents and patterns. Quicker mixer housekeeping and fewer accidental changes while swiping. Better live reliability: key controls remain accessible at all times. Examples: Filter effects by tags Modulation + Favorites to build a chain in seconds; save as a “Collection.” Header shows a small 21:30 clock during a set. Drum pad buttons use background images (kick/snare/hats) with high-contrast labels. Set accent to 70% on beats 2 & 4 with light swing for a laid-back groove. Collapse FX groups from their own headers; swipe across the mixer while pan and Send A stay pinned on screen. This summary was automatically generated by GPT-5 Thinking on 2025-08-25. Original Post: I would like to be able to organize instruments & Effects by genre, name and favorite. See the time of the day (clock) on the header. Be able to add background image on buttons. Control the accent of the groove. Be able to minimize and maximize some part of the Mixer at any place, not only from the left on the mixer. Be able to swipe left and right in the mixers without missing the sends levels and pan while doing it.

Description: Add context-aware actions to move to the next/previous project in the currently active setlist , so a single mapping (e.g., a footswitch) works regardless of which setlist is loaded. Problem: Today, navigation buttons can target “next/previous project” only within a specific setlist. Reusing the same projects across multiple setlists forces users to reconfigure buttons for every occurrence, creating duplicated work and increasing the risk of errors in live situations. Proposed Solution: New actions: Setlist › Next Project (Active Setlist) and Setlist › Previous Project (Active Setlist) . Options per action: - Wrap-around (stop at ends or loop). - Skip disabled/hidden items. - Mode: Cue (preload and wait) vs Load now (immediate switch). Additional actions/variables: - Jump to Project by Offset/Index within the active setlist. - Expose currentProjectIndex , projectCount , isFirst/isLast , currentProjectName for labels/LEDs/logic. - OnProjectChanged event for updating UI and resetting per-project state. Backward compatible; existing setlist-specific mappings continue to work. Benefits: One reusable mapping works across all setlists—no per-setlist reconfiguration. Faster, safer set navigation on stage (ideal for foot controllers). Clear feedback (index/name) for performers and techs. Less template duplication and fewer chances for mismatched buttons. Examples: A dual-footswitch: left = Previous Project (Active Setlist) , right = Next Project (Active Setlist) ; HUD shows “3/12 • Ambient Drone B ”. Use Cue mode to preload the next project silently; a second press (or Load Now ) commits the switch without dropouts. Bind a “Jump by Offset -2/+2” for skipping interludes while keeping mappings identical across different setlists. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: Select the next/previous projet in current setlist Currently, it’s possible to assign a button to move to the next/previous project in a specific setlist. However, it would be much more useful if we could assign a button to switch to the next/previous project within the active setlist. I often reuse the same projects in different setlists, and each time I have to reconfigure the buttons for every project involved.

Description: Introduce the ability to export and import individual widgets (or groups of widgets) for reuse across different projects, including their internal mappings, curated lists, and logic. Problem: Currently, widgets can only be duplicated within the same project or copied via clipboard, which often leads to broken references (“NA” or “#REF”) when taken out of context. Complex or curated widgets, such as preset selectors, are difficult and time-consuming to recreate in new projects. Proposed Solution: Provide an export/import mechanism for widgets that preserves their structure, curated lists, and mappings. This could include a way to debug or gracefully handle missing references when importing into a different project, ensuring maximum portability. Benefits: Save time by reusing complex widgets across multiple projects. Avoid tedious manual recreation of curated or elaborate widgets. Ensure consistency in setup, especially when debugging or sharing. Enable a personal library of frequently used widgets. Examples: Export a preset selector widget curated to 20 out of 100 plugin presets, then import it into a new project without rebuilding the list. Share a custom MIDI-mapping widget with collaborators for consistent performance setups. Maintain a library of debugging widgets to test signal flows across projects. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: Ability to export Widgets. I have had some issues using clipboard, and I understand that there are major issues with handling undefined things for out of context widgets, but some elaborate widgets are a real pain to recreate in a new project. It would be great to export/import and debug stuff that’s “NA” or “#REF”. For example a preset selecting widget I have is curated to 20 of the 100 presets on a plugin. Nice to keep that for other projects.

Description: Introduce a family of UI actions to dynamically modify widget appearance and labels at runtime—e.g., set text, background/foreground color, icon, opacity, visibility, and style “class”—based on actions, conditions, or feedback. Problem: Performers often send program changes/CCs or trigger actions where the UI does not reflect the true state afterward. Grids that fire patches can’t highlight which patch is active, and buttons that send CC toggles provide no “on/off” confirmation. Large widgets (e.g., stepdials) consume valuable screen space when only their current value needs to be shown elsewhere. Proposed Solution: Provide UI Alteration Actions and bindings with low-latency, GPU-friendly updates: Set Text / Format Text: Update a label or button text from constants, variables, expressions, or another widget’s value; support formatting (units, padding, precision). Set Color: Background/foreground/tint; support theme tokens and expressions (e.g., color by state). Set Icon / Emoji / Glyph: Swap icon assets based on state. Set Visibility / Enablement / Opacity: Show/hide or enable/disable widgets; optional fade duration. Add/Remove Class: Apply named style classes (e.g., selected , warning , armed ) for bulk style changes. Pulse/Blink: Temporary highlight with duration/easing; optional repeat while condition true. Group Selection: Radio-group semantics for grids (one selected item highlighted, auto-unselect others). Watchers: Bind alterations to MIDI/Keyboard/OSC feedback, clip/track states, or arbitrary expressions. Scopes: Target a specific widget, all widgets with a tag/class, or a page/global HUD element. Safety/UX: Undo-aware; reset to template defaults on project load (configurable). Backward-compatible. Benefits: Clear, trustworthy visual feedback after actions and external MIDI changes. Frees screen real estate by showing values in compact labels rather than large controls. Faster programming: fewer helper widgets and workarounds. Consistent, themeable look via classes and tokens; easier maintenance across pages. Examples: A patch grid highlights the currently active patch and dims others; a quick “pulse” confirms selection. Buttons that send CC toggles change text to “On/Off” and background color to reflect hardware state returned via MIDI feedback. A compact label on the main page mirrors a stepdial’s selected value (e.g., “Step: 11 • 73%”), letting the dial live on a secondary page. When a track arms for record, class armed applies globally: buttons turn red and an icon switches to a REC glyph. Show a warning banner ( visible = true ) if input level exceeds a threshold; fade out after 1 s. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: I’d love to see a family of UI actions that allow doing things like dynamically setting the Text of a button or label as a result of an action, setting the background colors to simulate state changes. For example, I have some buttons then send an action as a CC, but I can’t tell if I turned it on or not afterwards. Also I gave a grid of buttons that send patches, but I can’t highlight the one that is currently on.

Description: Enable user-defined stickers (small graphics/icons/symbols) that can be used anywhere text labels can appear, as inline icons or as positioned overlays on widgets/pages. Provide a simple project-level sticker library with fast import (paste, Files, Photos, iOS sticker picker) and consistent rendering. Problem: Emojis are too limited to express many musical concepts (articulations, pedal states, controller brands, custom symbols). Currently, users can insert emojis but not custom sticker graphics, making it harder to label controls, reduce ambiguity, or create highly legible live UIs—especially in complex or collaborative templates. Proposed Solution: Sticker Library (per Project + User Library): Manage named assets; support PNG/WebP/SVG (static), with automatic sizing variants and texture atlasing for performance. Inline Stickers in Text: Insert by name (e.g., [:violin:] ), or via a small picker next to label fields; baseline-aligned and tintable (where appropriate). Overlay Stickers: Add stickers as visual elements anchored to a widget (inside/outside, corners/edges, absolute or percent offsets). Snap, rotate, scale; lock to maintain layout. State-Aware Swaps: Map sticker variants to widget states (default/active/disabled/armed) and to expressions or feedback (e.g., program number → icon). Import Paths: Paste from clipboard; browse Files/Photos; optional iOS system Sticker picker where supported, converting to a static asset on import for reliability. Packaging & Exchange: Embed sticker assets in project bundles and template exports; provide placeholders + warnings for missing assets; optional “Replace Asset” tool. Accessibility & Themes: Alt text for screen readers; adhere to theme contrast rules; allow tint/opacity to match themes. Performance/Safety: GPU-friendly atlases; size caps; no remote fetching at runtime; licenses noted in metadata. Benefits: Faster visual recognition on stage (clear icons > cryptic text). Fewer errors from misidentifying channels/controls. Cleaner, denser layouts by replacing large text with compact symbols. Highly personalized, brandable templates that are still portable and reliable. Collaborative projects retain consistent visual language via bundled assets. Examples: Mixer channels labeled with instrument logos (cello, vox, drums) as inline icons and small corner overlays on faders. Keyboard page shows scale degrees or articulation markings as stickers placed along keys. Patch grid highlights the currently active patch with a state-swapped sticker (e.g., filled vs. outline). Effects rack uses standardized stickers for “pre/post,” “mono/stereo,” and “sidechain” to reduce label clutter. Shared band template exports with its sticker set embedded; another device opens it with all icons intact. This summary was automatically generated by GPT-5 Thinking on 2025-08-20.

Description: Loopy Pro users would like an optional action that allows double-tapping or long-pressing on an XY pad to reset it to predefined specific values. Problem: Currently, resetting the XY pad to a default or specific value requires manual adjustment, which can be time-consuming, especially during live performances. There is no quick way to revert the XY pad to a specific state without manually dragging it back. Proposed Solution: Implement an optional feature where users can assign a double-tap or long-press action to the XY pad, allowing it to instantly reset to predefined coordinates. This setting could be configured per XY pad within the widget options. Benefits: Quicker resetting of the XY pad during live performances. Enhanced usability and efficiency, particularly in dynamic setups. Reduces the risk of manual errors when needing to return to a specific setting. This summary was automatically generated by ChatGPT-4 on 2025-05-07.

Description: Add an option to load a new project without tearing down active Inter-App Audio (IAA) sessions, so external apps (e.g., Novation Launchpad) keep playing while the project switches. Problem: When a project is loaded—especially via a button widget—the audio engine and IAA graph are typically rebuilt. Many IAA apps stop or lose transport/clock during this transition, breaking continuity in live sets and forcing manual restarts. Proposed Solution: Introduce a “Preserve IAA on Project Load” mode with the following behavior: Background Load: Prepare the new project while keeping the current audio engine and IAA nodes alive until the switch point. IAA Session Persistence: Maintain existing IAA connections; if the same IAA app exists in the target project, auto-rebind to the new project’s routing. Transport/Clock Options: Choose whether to keep sending MIDI Clock/Link/transport (Start/Continue) to IAA apps during the transition. Routing Fallbacks: If an IAA source isn’t present in the target project, route it to a safe bus or default input until user mapping is ready. Switch Style: Hard cut or timed crossfade at commit; optional “pre-cue then commit” action pair. Safety/Compatibility: Detect sample-rate/buffer changes that would force an engine restart and warn or defer until safe; timeout and revert if reconnection fails. Benefits: Seamless song/project changes without stopping external IAA playback. Fewer on-stage hiccups; no manual relaunch of companion apps. Flexible handover (cue/crossfade) that fits live performance workflows. Backward-compatible; projects that don’t use IAA are unaffected. Examples: While Novation Launchpad (IAA) performs a loop, trigger Load Project (Preserve IAA) ; Launchpad keeps playing, the new project preloads, then a second press commits the switch with a 500 ms crossfade. An IAA drone app continues output to a fallback bus during the load, then auto-rebinds to the target project’s FX chain when the switch completes. Keep MIDI Clock running to an external IAA rhythm app so tempo stays locked across project changes. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: load project keep inter app audio apps going it would be great if the novation launchpad app keeps going as interapp audio when a new project is loaded via a button widget.

Description: Add an “Any” option to Widget State Feedback (alongside “First” and “All”) that evaluates to true if any matched widget satisfies the chosen condition, and exposes that result for feedback, expressions, actions, and styling. Problem: Current aggregation options are limited to “First” (use only the first match) and “All” (require every match). Many real-world setups need a logical OR across a set—e.g., show a light if any button is active, display “REC” if any track is recording, or trigger an action if any pad is held. Achieving this today requires clumsy workarounds (duplicate checks, extra helper widgets, complex expressions), which are brittle and time-consuming. Proposed Solution: Introduce an “Any” aggregation mode for Widget State Feedback sources. UI: simple selector with First / Any / All . Semantics: returns true when ≥1 target matches the condition; empty set returns false. Expose the boolean (and optionally the count of matches) as a variable for labels, colors, automation, and OSC. Backward-compatible; no change to existing projects. Benefits: Dramatically simpler templates and fewer helper widgets. Clearer logic (explicit OR) and easier maintenance. More robust feedback in performance contexts. Potentially lower CPU/overhead by removing workaround chains. Examples: Light a single LED if any of a bank’s toggle buttons is ON. Show a big “REC” badge when any clip/track is recording. Trigger a “Panic/Mute All” action if any channel clips (via state threshold). Display “Solo Active” when any mixer channel is soloed. Enable a “Next Scene” button when any pad in a group is pressed. This summary was automatically generated by GPT-5 Thinking on 2025-08-20. Original Post: Widget State Feedback - add “Any” to the current “First” and “All”. Some edge cases where this is handy.

When using a single button for more than one action for better visual feedback state. Example. Using a press action on a single button widget with a green colour to play a clip and a long press action to record the clip on the same button.the button's colour should turn green when the press action is triggered and red when the long press is triggered.that way we can have a better visual feedback state on the button.The option could be placed on the action menu near the action to open the colour menu.