Feature Requests

Description: Enable moving or copying widgets to another page without rebuilding —preserving size/position, styling, actions, variables, and MIDI/OSC mappings. Offer Linked Instance (mirror-style) and Independent Copy modes, plus a Relink Wizard to adapt targets on the destination page. Problem: Recreating widgets on a different page is slow and error-prone: mappings break, actions must be rebuilt, and layouts drift. Duplicating by hand also risks conflicts (double-mapped MIDI, wrong targets). Users need a fast, reliable way to reuse existing UI across pages. Proposed Solution: Commands: Move to Page… and Copy to Page… (multi-select supported). Instance Modes: - Linked Instance (Mirror): shares logic/actions/parameters with the source; optional per-instance visual overrides (color/label). - Independent Copy: full duplicate; all bindings cloned with safe remapping. Relink Wizard (context-aware): - Auto-map targets by name/tag/color (e.g., reroute to local tracks/clips/groups). - Resolve MIDI/OSC conflicts (offer remap, scope, or disable). - Report dependencies (missing buses, AUv3, pages) with one-click fixes or placeholders. Layout Preservation: keep coordinates, size, z-order, anchors ; optional scale to destination grid and “keep safe text size”. Bundles & Library: save/load Widget Bundles (with assets/fonts/icons) and drop them onto any page. Cross-Page Links: show a small link badge on mirrored widgets; jump to Master ; command Make Independent / Re-link to… . Assets: carry embedded images/genmoji; de-duplicate on paste; warn on large assets. Safety & Undo: single undo step; late-press guard for widgets that trigger transport; dry-run preview. Actions & API: Move/Copy Widget(s) to Page , Create Linked Instance , Make Independent , Run Relink Wizard , Select Destination Page , Replace on Destination . - Vars: widget.instanceId , widget.linkGroupId , widget.isLinked , widget.pageName . Benefits: Build complex UIs faster—reuse proven widgets across pages without rebuilding. Fewer mapping mistakes; consistent behavior via linked instances . Clean migrations when reorganizing shows or making “performer vs. FOH” pages. Portable widget packs for teams and templates. Examples: Copy a Transport strip to a “Performer View” as a Linked Instance so one edit updates both pages. Move a Fader bank to a new FOH page; the Relink Wizard retargets sends/pans on that page. Duplicate a Scene Grid as an Independent Copy for the MD; MIDI inputs are auto-remapped to a different controller. Save a Looper Controls bundle (buttons + meters) and drop it onto new projects with all actions intact. This summary was automatically generated by GPT-5 Thinking on 2025-11-04. Original Post: Ability to Move Widgets to another page (without rebuilding after copying) Currently copying is the only options but it does not reserve and bindings or most of the linkings / connections of copied widget / Clips.

Description: Add a true dual-screen workflow where the iPad shows a Control Canvas (editing, buttons, faders) while an external monitor shows an Independent Stage Display (clips, big meters, lyrics/teleprompter, flashing BPM, scene cues). Support Mirror or Extended modes, per-screen pages/layouts, and one-tap actions to send widgets/pages to the external screen. Problem: With an external monitor attached, performers typically get mirroring or a single shared UI. This limits stage use (audience/camera view, MD screen, confidence monitor) and forces page switching during shows. Users need separate, purpose-built layouts on each screen—without rebuilding projects or compromising touch control on the iPad. Proposed Solution: Screen Modes - Mirror (current behavior) or Extended ( Control Canvas on iPad, Stage Display on external). - Per-project default mode ; quick toggle in the title bar. Per-Screen Pages & Layouts - Assign any Page to Screen A (iPad) or Screen B (External) ; optional Follow Page rules (e.g., external follows the selected group/scene). - Screen-Only Widgets (e.g., fullscreen clip grid, lyrics/ChordPro, flashing BPM, big clocks/meters) that don’t appear on the iPad. - PiP support to embed a region of one page into the other screen. Placement & Styling - Resolution-aware layout with Fit/Cover/Pixel-perfect scaling, safe margins/overscan controls, and min text size guards. - Brightness cap / Night mode , theme overrides, and “high-contrast stage” preset. Interaction & Safety - iPad remains the sole touch surface ; optional pointer control for external focus switching. - Performance-Safe mode (frame-rate throttle, reduced animations) for the external output. - Privacy filter prevents edit overlays or dialogs from appearing on the stage screen. Routing & Sync - Transport/tempo/scene are shared; screen-specific quantize for visual cues (downbeat flash, lyric advance). - Optional Program/Preview pair: preview next page/scene on external, Swap on cue. Actions & Variables - Actions: Set Screen Mode (Mirror/Extended) , Show Page on Screen (A/B) , Send Widget to Screen B (Fullscreen/Panel) , Swap Screens , Toggle Stage Display Preset , Set External Brightness/Theme . - Vars: screen.mode , screen.external.resolution , screen.external.fps , screen.external.isSafeMode , page.screen . Presets & Export - Save Stage Display presets (e.g., “Clips+Meters”, “Lyrics+Timer”); recall per setlist item. - External screen respects Genmoji , pictograms, and large-type fonts. Benefits: Run two optimized UIs at once : hands-on control on iPad, clear stage/audience view externally. Fewer page switches and safer shows with persistent meters/lyrics/cues. Camera- and FOH-friendly output (contrast, margins, brightness). Reusable presets speed setup across projects and venues. Examples: iPad shows your Control Canvas ; the HDMI screen shows Lyrics + Big BPM + Scene Countdown with high contrast. A Program/Preview layout on the external display previews the next scene; tap Swap at the bar boundary. Send a Fullscreen Clip Grid to Screen B while keeping detailed faders/FX on iPad; PiP a small Master meter back onto the iPad. For theatre, recall the “Confidence Monitor” preset (clock, next cue, current bar:beat, transport state) on the external screen. This summary was automatically generated by GPT-5 Thinking on 2025-11-04. Original Post: Loopy Pro working with two screens at the same time (Ipad and external screen) If i have my ipad conected via hdmi to second display, create and option so when I open an app AUv3 within Loopy Pro, I can view it on that second display while the Loopy Pro homepage remains active and visible in the screen option. This way i can have windows open on secondary/external screens as other apps have as VS Visual Synthesizer This way, I can use both options and screens at the same time. This is VERY usefull for working with Loopy pro.

Description: Allow any AUv3 instrument/effect to appear as a widget on the canvas—resizable, theme-aware, and mappable—so performers can tweak plugins directly without opening floating windows. Problem: AUv3s open in separate panels that obscure the layout, break flow on stage, and don’t persist well across pages. Users want always-visible, space-efficient plugin controls that live with their loops, faders, and macros. Proposed Solution: Widget Type: “AUv3 Widget” that hosts the plugin’s view inside a framed, resizable container (XS → Fullscreen). Layout & Views: Multiple view modes : Full UI , Compact UI (plugin-provided), and Mini Panel (user-selected parameters as knobs/faders + meters). Snap-to-grid, aspect locks, safe-area padding. Focus & Control: Optional Focus-Follow (hardware maps to the widget’s plugin when selected); Focus Lock to prevent steals. Parameter Mapping: Pick parameters into the Mini Panel, add per-control range/curve, and bi-directional feedback. Learn from gestures or MIDI. State & Presets: Per-widget Preset selector , A/B compare , and State recall with project; “Copy state to all instances of this plugin.” Performance: GPU-friendly compositing; Sleep when offscreen (optional), Auto-Suspend when silent; per-widget CPU meter and tail handling. Safety: Sandboxed; restore on crash; Safe Mode fallback to Mini Panel if the full UI fails to render. Actions & Variables: - Actions: Show/Hide AUv3 Widget , Toggle View Mode , Select Preset , Randomize Params , Bypass/Enable , Open Native Window . - Vars: au.name , au.preset , au.cpu , au.isBypassed , au.focused , au.param["Cutoff"] . Automation & Themes: Themeable frame (title, icon, color), title-bar shortcuts, and page-level visibility rules (only show on Page X). Benefits: Keep critical plugin controls in sight and integrated with the performance layout. Faster tweaks, fewer window toggles, less risk on stage. Consistent mappings and presets per page/project. Lower CPU surprises with suspend/sleep plus inline meters. Examples: Place a reverb AUv3 as a Mini Panel (Mix/Time/HP/LP) next to vocal loops; tap to expand to Full UI during soundcheck. Use Focus-Follow so an 8-knob controller always controls the selected AUv3 widget ; lock focus for precise edits. A synth AUv3 widget on the keys page shows macro knobs; a footswitch triggers Preset Next while the widget confirms the name. On dense pages, widgets default to Compact ; opening the editor temporarily pops the Full UI; closing returns to Compact automatically. This summary was automatically generated by GPT-5 Thinking on 2025-09-26. Original Post: AUv3 widget A widget acting as a place older for an AUv3 content, inside a page. This could be specially helpful for MIDI plugins, for things we cannot achieve with Loopy Pro widgets. Or to drop effect AUv3 in a page without having to remap anything.

Description: Introduce the ability to trigger actions at specific positions in a clip's playback cycle – most importantly, each time the clip reaches the start ("12 o'clock") or the end. These actions would fire repeatedly on every loop cycle, rather than just on initial playback. Problem: Currently, Loopy Pro can trigger actions like Play only once when playback begins. However, there's no way to automate events at the start or end of each loop cycle. This limits creative possibilities like synced effects, clip behavior changes, or layered automation tied precisely to clip looping. Proposed Solution: – Add a new action condition: “At Clip Start (Loop Point)” and optionally “At Clip End” – Actions can re-trigger every time the clip loops back to the beginning – Works similarly to Play-triggered actions, but executes on every cycle – Allows conditional behaviors, such as muting, effect toggles, or automation, to sync with clip looping – Integrate with clip quantization settings for tight sync Benefits: ✅ Enables loop-synced automation and effects ✅ Allows for creative, cyclic control of plugins and mix states ✅ Ideal for live performance where hands-free automation is needed ✅ Expands action timing options beyond one-shot triggers ✅ Helps align Loopy Pro with common looping workflows in other DAWs This summary was automatically generated by ChatGPT-4 on May 2, 2025.

Description: Add an option to hide all empty clips in the sequencer timeline for improved clarity and focus during editing and playback. Problem: Empty clips can clutter the sequencer view, especially in complex projects with many tracks and layers. This makes it harder to focus on the actual musical content and affects workflow speed and overview. Proposed Solution: – Add a toggle option (global or per-page) to hide all clips in the sequencer that currently contain no recorded material – Can be implemented as a visual filter (non-destructive) that does not delete clips – Could also include an "auto-hide when empty" mode – Optional keyboard shortcut or widget action to toggle visibility on/off – Ideally works dynamically: hidden when empty, shown when recording starts Benefits: – Cleaner and more focused sequencer view – Faster navigation and editing in dense projects – Useful for live performance setups with many unused placeholders – Reduces visual distractions and improves UX This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Allow duplicated/cloned AUv3 effect instances to have individually controllable bypass states, with a setting to choose between the current linked behavior (all clones toggle together) and independent control per instance. Provide fine-grained link options (bypass vs. parameters vs. presets) and clear UI to manage clone groups. Problem: Today, cloned instances typically share bypass —handy for global on/off, but it blocks A/B/C comparisons, per-branch mutes in parallel chains, scene-specific toggles, and CPU saving on a single instance. Users resort to duplicate chains or complex macros to emulate per-instance control. Proposed Solution: Link Modes (per clone group / per instance): - Linked (current): Bypass & parameters mirror the source. - Independent Bypass: Parameters may stay linked; bypass is per instance . - Fully Independent: Bypass and parameters are per instance. - Custom Links: Separate checkboxes: Bypass , Parameters , Preset , MIDI Map (choose what is linked). Controls & UI: - Clone Group badge (A/B/C…) with a quick “Link Bypass” toggle. - Per-instance Bypass , Solo , Mute (pre/post) buttons in the AU frame/title bar. - Context menu: Duplicate (Linked) / Duplicate (Independent) , Make Independent , Link to Group… - Visual indicator when an instance is bypass-linked (chain icon). Actions & Variables: - Actions: AUv3 → Toggle Bypass (This Instance) , Set Bypass (Group) , Link/Unlink Bypass , Link/Unlink Parameters , Duplicate as Independent/Linked , Solo Instance , Bypass Others in Group . - Vars: au.instanceId , au.groupId , au.isBypassed , au.link.bypass , au.link.params , au.cpu , au.presetName . Scenes & Follow Actions: - Scene recall targets instance or group scope; Follow Actions can toggle individual instance bypass at Beat/Bar/Loop with late-press guard. Performance & Safety: - Bypassed instances can sleep/suspend DSP (optional tail-safe release for reverbs/delays). - Micro-fade (5–20 ms) on bypass to prevent clicks; full undo/redo. Benefits: Choose workflow: one-switch global control or granular per-instance toggling. Easier A/B/C comparisons and scene-programming without duplicate chains. Better CPU management by sleeping unused clones. Cleaner templates; fewer workaround macros. Examples: Three cloned comps on vocals: parameters linked, bypass independent for fast flavor A/B/C in rehearsal. Parallel FX chain: keep Reverb linked & always on; toggle Chorus only on instance B during chorus. Scene 1 enables clone A , Scene 2 switches to C with tail-safe bypass to avoid cuts. This summary was automatically generated by GPT-5 Thinking on 2025-11-04. Original Post: Ability to Disable Individual Instances of FX Auv3 Duplicate (A,B,C…) When using Duplicates/ Clones of a Auv3 FX Instance, currently, enabling/disabling one of the duplicates will a enable/disable all of them. Individual control would mean much more flexibility and taking advantage of the duplicates feature.

Description: The mixer resize button enables a full-screen view, hiding the page select buttons and working across all views. Contrary to earlier statements, the mixer does not go full screen automatically when no objects are present on the page. Problem: Resizing the mixer to full screen hides the page selection buttons, which limits navigation and accessibility. Additionally, there's currently no fast way to access a dedicated full-size mixer without manual resizing. This can disrupt workflow and efficiency, especially in live performance or complex session contexts. Proposed Solution: Introduce the ability to add a dedicated page within a project that displays the full-size mixer. This page should be accessible with a single tap via an action. This would allow immediate access to the full mixer view without sacrificing navigation or requiring manual toggling. Benefits: Streamlined navigation with quick access to a full-size mixer. Preserves page-switching capabilities when using the full mixer. Enhances user workflow by minimizing manual UI adjustments. This summary was automatically generated by ChatGPT-4 on 2025-05-22.

Description: Let Text widgets show live or snapshot values from other widgets (faders, toggles, radios, menus, meters, clip/mixer props), triggered by On Press , On Select , On Change , On Release , or Timed Poll . Provide a simple templating syntax, formatting options, and safe cross-page references. Problem: Labels often need to mirror state elsewhere (e.g., show the value of a hidden fader or the currently selected radio item). Today this requires ad-hoc variables/macros and isn’t discoverable. There’s no direct way to say “when I press/select here, display that control’s value there,” with formatting, scope, and low latency. Proposed Solution: Binding & Templating: - Inline tokens: {widget:<nameOrId>.value} , {clip.selected.name} , {mixer.track[2].pan} , etc. - Multiple tokens per label with text, e.g., Delay: {widget:DelayMix.value|pct0} @ {tempo.bpm|0.0} . - Format pipes : |0 , |0.0 , |pct0 , |ms , |Hz , |signed , |pad2 , |upper , custom |map tables. Triggers (per Text widget): - On Press (of a target widget), On Release , On Select (radio/menu), On Change (value changed), Interval (e.g., 10 Hz), and Manual Refresh . - “ Snapshot vs. Live ” mode: one-off capture at trigger vs. continuous subscription until dismissed. - Debounce/Throttle to avoid spam during fast moves; hold/long-press variants. Targeting & Scope: - Reference by name, tag, color, or ID ; choose Nearest on Page , This Page , or Project-wide (cross-page safe). - Safe failure text (e.g., “—”) and warnings for missing/ambiguous targets; picker UI to resolve conflicts. Styling & Layout: - Auto-fit text, min/max font size, marquee for overflow, number alignment options, prefix/suffix units, conditional color (e.g., red when > −6 dB). - Optional icon/pictogram alongside value; supports Genmoji and embedded assets. Actions & Variables: - Actions: Text → Bind To Widget… , Set Template Text , Refresh Now , Start/Stop Live Subscription , Set Trigger (Press/Select/Change/Interval) . - Vars: text.boundTargets[] , text.lastValue , text.isLive , text.refreshHz , text.error . Debug & Safety: - Inspector shows resolved tokens and current values; “copy resolved text” for logs. - Sandboxed cross-page reads (read-only) with permission toggle; rate limit for background polling. Advanced: - Conditional templates : {if widget:Rec.state=="record"}● REC{else}idle{end} . - Aggregation : {avg widget:Band*.gainDb|0.0} dB , {max group:"Sends".value|pct0} . - Event queue : buffer last N changes for quick flick-through (“previous value” recall). Benefits: Clear, at-a-glance feedback without exposing the source controls. Faster programming—no fragile macro webs for simple readouts. Consistent, formatted labels across pages and projects. Performance-safe updates with throttling and subscriptions. Examples: A Text widget on the Master page shows Reverb {widget:RevMix.value|pct0} when the Reverb button is pressed , then stays live while held. A Radio for delay times updates a nearby label On Select : Delay: {widget:DelayTime.selectedLabel} . A compact header displays BPM {tempo.bpm|0} • Grid {edit.grid|note} with a 10 Hz interval trigger. Press a “Show Current Send” button: text snapshots {mixer.track[Vox].sendA|pct0} without subscribing. This summary was automatically generated by GPT-5 Thinking on 2025-11-04.

Description: Add dedicated Sustain Pedal (CC64) tools in the MIDI editor: a visual lane with pedal-down regions, smart functions to extend/merge notes under pedal , split at lifts , quantize/humanize pedal on/off , and support for half-pedaling . Include companion lanes for Sostenuto (CC66) and Soft (CC67) , plus one-click “bake/unbake” between pedal data and note lengths. Problem: Pedaled performances (piano, EP) record as short notes + CC64 holds. Editing or quantizing them is tedious: notes look staccato, pedal lifts get misplaced, and repedaling/half-pedal nuance gets lost. Fixing stuck notes, aligning lifts to the grid/groove, or converting pedal gestures into clean legato lengths currently requires time-consuming manual work. Proposed Solution: CC Lanes & Visualization - CC64 lane with pedal-down shading ; threshold & hysteresis to define “down” (e.g., ≥64 by default). - Half-pedal curve (map 0–127 to sustain amount), optional per-instrument response. - Optional lanes for CC66 (Sostenuto) and CC67 (Soft) with distinct shading. Smart Edit Operations - Pedal → Extend Notes: lengthen note-offs to the next pedal lift (legato merge across pedal). - Lift-Aware Split: cut sustained notes exactly at pedal lifts (with optional gap ms). - Render Sustain to Note Lengths / Extract Sustain from Overlaps (bake/unbake). - Quantize Pedal On/Off to grid or groove with feel %, and Humanize (±ticks) for natural lifts. - Repedaling handling: treat short lifts below N ms as continuous sustain. - Half-Pedal Scaling: compress/expand sustain amount by curve; clamp min hold. - Re-articulate after Lift: insert short release gaps or staccatissimo per setting. - Fix Stuck Notes: detect mismatched offs masked by pedal; generate/correct note-offs. Editing UX - Pencil/erase for pedal envelopes; box-edit multiple lifts; nudge on/off by ticks/beats. - Readouts while dragging: On @ 33.3.2 • Off @ 34.1.1 (Δ 0.6 beat) . - Chase state when starting playback mid-clip (reconstruct held notes from current pedal value). Actions & Variables - Actions: Extend Notes Under Sustain , Split at Pedal Lifts , Quantize Pedal On/Off , Bake Sustain to Lengths , Extract Sustain , Toggle Half-Pedal , Fix Stuck Notes . - Vars: cc64.down (bool), cc64.value , cc64.threshold , pedal.liftCount , pedal.halfAmount . Safety & Integration - Works with tempo/quantize changes and groove templates; fully undoable. - Per-track defaults for thresholds, repedal window, and half-pedal curve. Benefits: Clean, legible MIDI that reflects how pedaling actually sustains notes . Faster editing and musically correct quantization of pedal gestures. Preserves nuance (repedals, half-pedal) while fixing timing and stuck notes. Flexible workflows: keep CC64 live or bake into note lengths for export. Examples: Convert a recorded piano take: Bake Sustain to Lengths , quantize lifts to 1/4-groove , then Unbake to restore CC64 if needed. After a tempo change, Quantize Pedal On/Off and Repedal window = 80 ms to maintain natural legato. Use Lift-Aware Split to create re-articulations at each pedal up; add a 10 ms gap for clarity. Enable Half-Pedal with a gentle curve so values 50–90 produce partial sustain instead of binary holds. This summary was automatically generated by GPT-5 Thinking on 2025-10-14. Original Post: Midi editor: process sustain pedal messages Hi, I record piano into midi clip, the clip then has visible dots that mark places where I press and release the sustain pedal. However, I do not see the marks in the midi editor and hence cannot edit them. So loopy records midi messages for pressing and releasing the pedal, but doesn’t allow to process it.