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 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: 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 Users should be able to rotate/offset the playback phase of clips, groups or overdub layers, either after recording or already before recording. The following two modes should be available: • Rotation starting from the original phase zero (default clip start) • Rotation relative to current position (i.e., continue shifting from already rotated point) Implementation should be available both via Actions and Clip Detail Window. Functionality • Offset/rotation for individual clips • Offset/rotation for: • selected clips (regardless of color) • all clips of a specific color • first overdub layer • last overdub layer • overdub layers marked as Reverse • overdub layers not marked as Reverse • Option to predefine an offset before recording (clip is recorded normally but played back shifted) • Resetting phase should also support ramping Offset Units • Multiple formats: • Degrees (e.g. 90°, 180°, 270°) • Percent (e.g. 67.20%) • Milliseconds (e.g. 71 ms) = Micro steps • Samples (e.g. 228 samples) • Beats, bars or fractional clip units (e.g. 1/8 bar, 1/16 beat, 1/8 clip) • Combine quantized values with micro steps (e.g. 1 bar + 71 ms) • Nudge offsets by bars, beats or ms Offset Triggers • Immediately • At next clip cycle • Relative to current playhead (e.g. now + x ms) • Relative to clip start (0° + x ms) Special – Trigger Follow Action When Offset Position Reached Allow triggering a specific follow action when a defined offset position of a certain overdub (or overdub layer) is reached. The user should be able to choose: • Trigger once on the first cycle only • Trigger every time the playhead passes the offset position • Trigger on the last cycle before stop or count-out Additional Options • Undo/Redo support for offset operations • Snap-based or quantized shift (e.g. snap to 1/16, 1/8, etc.) • Reset to original phase via action or gesture • Offset logic defined via formulas (e.g. Offset = overdub number × 1/16) Benefits • Musical precision and expressive performance tweaks • Ideal for latency correction, live improvisation, structured rhythm shifts • Great for drum programming or glitch effects This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Improve control settings and preset management by adding undo/redo, search, filter, and advanced sorting options for MIDI bindings, actions, OSC directions, and plugin presets. Problem: Currently, managing large sets of mappings and actions is tedious and prone to error. Deleting entries in bulk is not possible. Labels can remain even after deletion due to bugs. There's also no way to recover deleted entries or track changes without undo/redo functionality. Proposed Solution: – Add Undo/Redo buttons scoped per section (e.g., MIDI bindings, actions, OSC, plugin presets) – Make list entries deletable via swipe (e.g., after accidental import) – Fix bug where labels don’t disappear after full deletion – Add search with auto-focus – Enable filtering – Support drag & drop sorting by: • Global profiles • Project settings • MIDI bindings • Actions • OSC directions • Plugin presets • Control Settings categories – All list items should support: • Reorder • Move between categories • Copy to category • Delete • Copy/paste • Move to another profile • Move up/down • One-click top/bottom move Benefits: ✅ Massively improved efficiency when editing bindings or presets ✅ Prevents accidental loss of work ✅ Much better clarity and control over large setups ✅ Brings consistency to all control-setting areas ✅ Saves time by avoiding full rebuilds of profiles This summary was automatically generated by ChatGPT-4 on April 30, 2025.

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.

Description: Improve the readability of UI elements like list widgets, stepped dials, and radio buttons by offering customizable or larger font size options. Problem: For many users, especially in live performance or low-light situations, the current text size in list-based or selection-based widgets is too small to read comfortably and quickly. This limits usability and increases the chance of errors. Proposed Solution: – Add adjustable font size settings for: - List widgets - Stepped dials - Radio button groups – Allow bold/high-contrast modes for better visibility – Possibly include UI scaling presets or per-widget overrides Benefits: ✅ Better accessibility for users with impaired vision or on small screens ✅ Faster and more accurate navigation in live contexts ✅ Less eye strain, more focus on performance ✅ Aligns with UX expectations of modern touchscreen apps This summary was automatically generated by ChatGPT-4 on May 2, 2025.

Description: Enable advanced comping and multi-take recording workflows by allowing users to record loops in continuous overdub mode, where each overdub is treated as a separate "take". Provide an interface to select, preview, and combine takes after recording. Useful for songwriting, refining loops, and selecting the best performance. Problem: Currently, Loopy Pro doesn’t offer a dedicated take management system. Users cannot easily select from past overdubs or compile a composite loop from multiple takes. There's no support for comping workflows as seen in DAWs, which limits its use in detailed arrangement or songwriting sessions. Proposed Solution: – Allow continuous overdubbing where each layer is saved as an individual take – Provide a “loop re-record until tap” mode with last-take selection – Add a clip context menu or hold gesture to open a “Take Selection” window – Integrate zoom and grid snap for precise part selection (similar to AudioShare) – Enable MIDI-assignable switching between takes or random playback of takes – Allow replacing or inserting specific takes with velocity/FX presets (e.g., fade, stutter, LFO) – Option to play newly recorded overdubs in reverse – Quantized insert/replace options – Add support for slice-based comping (e.g., select bar 1 from take A, bar 2 from take B...) – MIDI long/short press behavior to control insert/replace start and stop – Append-before/after actions for looping logic – Temporal “takes” timeline overlay or pop-up to drag/select preferred versions – Enable randomized take playback for generative loop evolution Benefits: ✅ Unlocks powerful songwriting and loop refinement workflows ✅ Makes Loopy Pro more DAW-like for structured clip editing ✅ Adds creative options like reversed overdubs and stuttered inserts ✅ Great for live performance and recording multiple takes without stopping ✅ Brings best of “multitaking” and “comping” to Loopy Pro in an intuitive way ✅ Enables precise control and creative decision-making post-recording ✅ Makes Loopy Pro more competitive with DAWs like Logic and Cubasis for clip-based workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable pinch-to-zoom functionality in the canvas edit screen to allow users to zoom in and out while editing widgets and layout elements. Problem: Editing small elements or navigating dense canvases with many rows and columns can be cumbersome, especially on smaller screens like iPhones. Precise placement and alignment become difficult without zoom support. Proposed Solution: – Implement standard pinch-to-zoom gestures in the canvas edit mode – Allow zooming in for detailed work and zooming out for overview navigation – Maintain full interaction with elements while zoomed (drag, resize, etc.) – Optionally display current zoom level for orientation Benefits: – Improves precision and usability when working with complex layouts – Makes editing possible and pleasant even on small screen devices – Speeds up UI creation and editing by reducing scrolling and repositioning – Aligns with user expectations for standard gesture support This summary was automatically generated by ChatGPT-4 on April 30, 2025.