Feature Requests

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.

I want to be able to create a midi bus and have the possibility to redirect the out of plugins and of buttons to it and from then send it to midi destinations For example currently in my template I have 8 buttons that sends note messages to digistix If I want to change the destination to another plugin I have to edit my template and change it to another plugin (16 times) Would be easier to have a midi bus in my project and send the output of the buttons to that bus and from the buss then add midi plugins into it so I can quickly switch between multiple applications fire example

Description: Allow users to freely reorder the items/options inside Stepper Dial and Radio List widgets via drag-and-drop (or Move Up/Down), without having to rebuild actions or rename items. Problem: Today, changing the order of items is only possible with a clumsy workaround: manually drag actions from one item to another and then rename each item. This is slow, error-prone, and especially painful when many items have nontrivial action stacks and labels. Proposed Solution: Drag & Drop Reorder: Reorder items with grab handles; support Move Up/Down, cut/copy/paste, and multi-select reordering. Action & Mapping Preservation: Actions, colors, icons, and bindings travel with the item as it moves. Stable Item IDs: Internally assign each item a persistent ID so expressions, feedback, and external mappings remain correct even if display order changes. Bulk Tools: Quick sort by name/index; “reverse,” “shuffle,” and “renumber” utilities; duplicate item with actions. Safety & Preview: Show before/after order, affected references, and offer Undo. Parity: Same capabilities for Stepper Dial and Radio List widgets. Benefits: Edit lists in seconds instead of rebuilding them. Eliminates mistakes from re-assigning actions by hand. Keeps controller mappings and expressions stable while improving UI order. Encourages iterative design (try new orders without fear). Examples: Rearrange a 16-step dial so “Scenes” appear in performance order; all step actions follow automatically. Sort a Radio List of fade-time presets by shortest→longest without breaking any targets. Duplicate a step (with actions) and drag it to a new position to create a variant. This summary was automatically generated by GPT-5 Thinking on 2025-08-25. Original Post: Ability to re-order stepper dial items (see screenshot) and radio lists Currently only doable with a workaround: you have to drag individual actions from item to item. Then rename the items. This is a bit ouchy, especially if you have a lot of actions.

Description: Add a built-in MIDI arpeggiator and/or step sequencer to Loopy Pro that can be used to send MIDI notes to instruments or plugins, either internally or externally. Problem: Currently, users who want arpeggiator or step sequencing functionality need to rely on external AUv3 plugins or external devices. This adds complexity, latency, and limits integration with Loopy Pro's internal action system and widget-based workflows. Proposed Solution: – Provide an internal MIDI arpeggiator with configurable note order, octave range, rhythm, gate length, and sync to clock – Add a step sequencer for MIDI notes with adjustable step count, note values, velocities, and per-step probability – Allow full widget and action system integration for triggering, pattern switching, parameter control, and sequencing automation – Optional AUv3-hosted UI or simplified grid editor for quick setup and live manipulation Benefits: ✅ Seamless integration with Loopy Pro’s interface and action system ✅ No need for third-party AUv3s, resulting in lower CPU usage and tighter sync ✅ Enables creative live performance setups including melodic looping and generative MIDI ✅ Opens new possibilities for Loopy Pro as a comprehensive live instrument and controller hub This summary was automatically generated by ChatGPT-4 on May 2, 2025.

Description: Add a native lyrics/lead-sheet module—Songbook Pro–style—with ChordPro support , PDF/text import, auto-scroll, teleprompter mode, chord transpose/capo, and tight sync to bars/beats/clips/scenes . Provide a canvas Lyrics Widget plus full-screen/Stage Display output and pedal/MIDI/OSC control. Problem: Singers and bands rely on external apps (e.g., Songbook Pro) for lyrics/charts, forcing app-switching and manual scrolling. Charts can’t sync to Loopy Pro’s transport, scenes, or follow actions, and per-song notes aren’t integrated with setlists and macros—risking missed cues on stage. Proposed Solution: Formats & Library: Import ChordPro (.pro/.cho) , TXT/RTF/Markdown , PDF , and images; per-song multi-document library (Lyrics, Lead Sheet, Stage Notes). Rendering: Chords inline ( [C] ), above-lyrics mode, section headers (Verse/Chorus/Bridge), annotations, custom fonts/sizes, theme/contrast presets, night mode. Transpose & Capo: Global/per-song transpose, capo display, Nashville numbers; instant refresh; per-instrument display (e.g., Bb/Eb). Sync & Cues: - Auto-scroll modes: time-based (mm:ss), bar/beat–based , follow Clip/Scene markers , or manual/pedal. - Markers: tie lines/sections to bar numbers , clip positions , or follow actions (“highlight Chorus at bar 33”). - Optional bouncing line /current-line highlight; pre-roll countdown. Control & I/O: - Pedal/D-pad: line/section up/down, next/prev song, start/stop auto-scroll, speed ±, jump to marker. - MIDI/OSC map for all controls; actions like Show/Hide Lyrics , Scroll to Section , Set Transpose . - Stage Display / external screen layout with big text and next-line preview. Lyrics Widget (Canvas): Resizable, lockable; quick zoom; picture-in-picture over clips; “safe area” so text never overlaps controls. Setlist Integration: Per-project library, per-item doc selection, quick edit, per-song scroll presets; export/share with project. Search & QoL: Global search, bookmarks, per-song notes, tap-to-zoom, pinch-to-resize, “fit to width/height,” keep-screen-awake. Performance & Safety: GPU text; caching; offline docs bundled with set; fallback to PDF if markup fails. Benefits: One app for loops + lyrics/charts , no app-switching. Bars/beats/clip-aware auto-scroll keeps eyes and hands free. Faster rehearsals with instant transpose/capo and consistent formatting. Reliable stage display with pedal/MIDI/OSC control and high-contrast themes. Examples: Map a footswitch: Section Down/Up ; auto-scroll engages at next bar and highlights the current line. Chorus marker at bar 49 triggers a highlight and a subtle screen pulse; a follow action also arms the harmony clip. Use Nashville numbers and set Capo +3 while the band’s keys track stays in concert pitch. On a second screen, show big teleprompter view ; the iPad keeps the compact Lyrics Widget beside transport and clips. Import a PDF lead sheet for the sax sub; switch to ChordPro lyrics for the singer with the same setlist item. This summary was automatically generated by GPT-5 Thinking on 2025-10-05. Original Post: Lyrics like songbook pro If you could connect to the amazing “songbook pro” app or simply copy some of their features that would be awesome!

Description: Add a new dropdown menu widget for selecting values or presets. This would offer an alternative to the current dial/stepper selector, providing better usability, especially with longer lists or precise selections. Problem: The dial widget is too fiddly for precise selection, especially with long lists (e.g., presets for AUv3 plugins). Users can’t see full label names, must scroll back and forth, and often select the wrong value. The lack of overview limits live usability and efficiency. Proposed Solution: – Introduce a new dropdown menu or matrix selector (e.g., 8×8 or 16×16 grid) – Allow full menu and individual entry customization (e.g., label line breaks, truncation options) – Auto-size width to longest label or allow manual width settings – Let users define how many entries above/below the cursor are shown while scrolling – Option to scroll with one control (dial/MIDI) and trigger with another (button) – Highlight active item visually (bold font, color, size) Benefits: ✅ Much better visibility of menu entries ✅ Faster and more reliable preset selection ✅ Frees up space on canvas by replacing multiple stepper widgets ✅ Ideal for live performance and AUv3 plugin integration ✅ More scalable UX for large value lists This summary was automatically generated by ChatGPT-4 on May 2, 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: Add a Page View / Picture-in-Picture (PiP) widget that embeds another page (or a region of it) directly on the current page—optionally interactive—so you can monitor and/or control clips, meters, and widgets from elsewhere without switching pages. Problem: Large shows spread controls across multiple pages (Drums, Vox, FX, Scenes). Jumping between them costs time, hides critical feedback (meters, armed status), and increases the chance of missed cues. Users need a compact, always-visible window into another page, with the option to interact when necessary. Proposed Solution: Widget Types: - Monitor (read-only, ultra-low CPU) and Interactive (tap/gesture passes through). - Page PiP (whole page scaled) and Region PiP (crop a group/area by selection). Scaling & Layout: - Fit/Cover/Pixel-perfect modes; min text size guard; safe-area padding; optional frame & label (source page name). - Presets: Thumbnail , Strip (x-wide) , Panel , Fullscreen Overlay . Interaction & Focus: - Tap-to-Focus sends MIDI/keyboard focus to the embedded page; long-press to Pop-Out a temporary full view; two-finger swipe to swap with the current page. - Interaction Filter: allow/block specific widget types (e.g., allow clip launches, block destructive edits). Transport & Quantize: - Cross-page triggers honor quantize/count-in rules; optional late-press guard toast (e.g., “deferred to next bar”). - Visual “in-sync” badge if the embedded page follows global transport/tempo. Audio & Safety: - Embedding does not duplicate audio; it’s a view/control layer. - “Performance Safe” mode throttles animations/meter FPS to protect CPU. - Lock Overlay to prevent accidental touches during shows. Multi-View & Routing: - Multiple PiPs per page; Multi-View Grid widget displays 2–9 sources with quick switch. - Assign a Follow Target (e.g., follow the currently selected page/scene). Actions & Variables: - Actions: Show/Hide PiP , Toggle Interactive , Pop-Out Fullscreen , Swap With Current Page , Set Source Page/Region , Cycle Sources . - Vars: pip.sourcePage , pip.isInteractive , pip.fps , pip.swapAvailable . Stage Display: - Send any PiP to external display as a Program/Preview pair (A/B) with safe margins and brightness cap. Benefits: Keep critical clips/meters always visible while performing elsewhere. Fewer page switches, faster cues, and safer live control. Modular layouts: build one master page with PiPs into specialist pages. CPU-aware and performance-safe with monitor/interactive modes. Examples: A Vocal page shows a PiP of Drums (meters + record buttons) to spot overloads; long-press pops it full-screen for quick fixes. A Master page hosts three PiPs (Pads, Bass, FX); taps launch clips on those pages bar-quantized without leaving the master view. A Scene Conductor PiP follows the selected page so the MD can glance/control whichever section the band is on. During a breakdown, Swap With Current Page promotes the FX PiP to full view; a second tap swaps back. This summary was automatically generated by GPT-5 Thinking on 2025-10-08. Original Post: Page-View (PIP view) Widget The ability to see the processing and activity from another page on the main page. AKA PIP mode of other pages on the main page.

Description: Add a host-level Frequency Crossover module that splits any audio source into multiple bands (e.g., Low/Mid/High, up to 5), routes each band to its own bus/FX chain, and then phase-aligned recombines them—or leaves them discrete for multibus workflows. Problem: Creating multiband processing in Loopy Pro currently requires awkward stacks of filters, manual routing, and ad-hoc phase compensation. That’s slow to set up, error-prone (level/phase holes at crossover points), and hard to manage live—especially when you need band mutes/solos, quick slope changes, or precise latency alignment. Proposed Solution: Crossover Module (Insert or Send Splitter): - Up to 5 bands with draggable crossover points (Hz) and filter types/slopes : Linkwitz–Riley, Butterworth, Bessel; 6–48 dB/oct . - Processing modes: - Zero-Latency — minimum-phase IIR, no added latency (no look-ahead), ideal for live monitoring and tight feel. - Minimum-Phase — classic IIR with negligible latency, musical phase response. - Linear-Phase — FIR with latency shown; perfect summing and no phase shift across bands. - Phase-safe summing with automatic latency compensation and per-band gain trim; global auto-gain to preserve loudness. - Per-band routing: send each band to a Bus , Channel , or Return FX ; optional internal Band Slots for inline FX. - Solo/Mute/Bypass per band; Band Link (adjust symmetric crossovers together); Oversampling option for HF integrity. - Metering: per-band peak/RMS/LU with correlation; global summed meter to verify null-safe recombine. Workflow & UX: - One-click templates: 3-Band (LR24) , 4-Band Mastering , Low-Split (Sub) , Top-Shimmer . - Snapshot A/B for crossover points & levels; copy/paste settings across instances. - Drag-to-assign: drop a bus or AU onto a band slot to route instantly. Actions & Variables: - Actions: Add Crossover , Set Band Count , Set Crossover Hz (band n) , Set Slope/Type , Solo/Mute Band , Route Band to Bus … , Toggle Linear-Phase , Toggle Zero-Latency , Recall Snapshot A/B . - Variables: xover.bandCount , xover.band[n].hz , xover.band[n].slope , xover.band[n].gainDb , xover.latencyMs , xover.isLinear , ** xover.isZeroLatency **, xover.sumDeltaDb . Safety & Performance: - Zero-Latency mode guarantees 0 ms added latency by avoiding look-ahead; linear-phase displays and compensates its latency. - CPU guard and latency readout; linear-phase warns when project quantize/count-in might need offset. - Auto-polarity checks ; soft clip/limit at recombine to prevent overs. - Fully undoable ; presets per project/page. Benefits: Fast, reliable multiband setups with correct phase and predictable gain. Zero-latency option for tight live performance , plus linear-phase for transparent studio work. Cleaner routing: lows to subs, mids to comps, highs to shimmer—without manual filter spaghetti. Reusable, readable templates that are easy to tweak under show conditions. Examples: Tri-band live mix (Zero-Latency): Lows (<120 Hz) → Sub Bus (Outputs 3–4), Mids (120–3.5 kHz) → glue comp, Highs (>3.5 kHz) → shimmer verb; LR24; summed meter shows −0.1 dB delta. Parallel distortion: High band (>2 kHz) to a fuzz AU; mids to clean delay; Linear-Phase with 48 dB/oct to keep crossover invisible on a studio bounce. Kick/bass management: Low band (<90 Hz) routed to a sidechain-controlled limiter on the bass bus; mids/highs remain unaffected for clarity— Zero-Latency keeps playing feel intact. This summary was automatically generated by GPT-5 Thinking on 2025-10-08. Original Post: I want the ability to route audio to separate paths based on frequency points. Ex. I play guitar and want all notes below 100 hz to go to channel with octave down fx, everything above to main guitar channel.

Description: Allow any widget-driven value change (buttons, steppers, faders, radios, menus) to be applied as a ramp instead of an instant jump—tempo-aware, quantized, and with selectable curves—so parameters glide musically to their targets. Problem: Instant value jumps can cause clicks, harsh transitions, and imprecise musical moves. Today, achieving smooth, time-synced changes requires multi-step macros or external automation, which is slow to build and fragile on stage. Proposed Solution: Ramp Options on “Set/Adjust Parameter”: - Duration units: ms/s, beats/bars , cycle of clip X , or combinations (e.g., 1 bar + 250 ms). - Curves: Linear, Exponential/Log, S-curve, Step, and Bezier (with shape %). - Targets: Absolute value, Add/Subtract , Multiply/Divide (e.g., ×1.5 dotted), clamp to min/max. - Start & Restart policy: From current value; Restart / Continue / Queue / Blend when a new ramp arrives. - Quantize start: None, Beat, Bar, Loop, or Cycle of clip X ; late-press guard to defer if too close to boundary. - Sync safety: Click-safe gain handling (auto microfade for very short ramps), sample-accurate scheduling. Controls & API: - Actions: Start Ramp (target, duration, curve, quantize) , Cancel Ramp , Pause/Resume , Resync to Boundary , Set Ramp Policy . - Variables: ramp.active , ramp.progress , ramp.remainingMs , ramp.target , ramp.curve , ramp.policy , ramp.sourceClipCycleBeats . - Inspector HUD: small progress ring/bar and resolved target/time readout. Batch & Mapping: - Ramp multiple parameters from one widget with independent curves or a shared timeline. - MIDI/OSC mappings can request a ramp per change (with throttle and delta threshold to prevent spam). Presets & QoL: - Quick chips: ×2 / ÷2 / dotted ×1.5 / triplet ×2/3 , “2 bars”, “500 ms”, “¾ cycle of Drums”. - Save ramp presets per widget/page; themeable success/queued feedback. Conflict Handling: - Per-parameter lane with policy for overlapping ramps; optional “kill others on start.” - Safe undo groups; ramps survive page switches unless flagged “local only.” Benefits: Smooth, musical transitions without macro sprawl. Reliable, bar/beat/clip-synced moves that land exactly on boundaries. Fewer clicks and level shocks; cleaner live operations. Reusable ramp presets speed up show programming. Examples: Delay Mix : ramp 0% → 35% over 2 bars with S-curve , quantized to bar; late press defers to the next bar. Filter Sweep : 200 Hz → 6 kHz over ¾ of the Drums clip’s cycle , exponential curve; Restart policy for retriggers. Master Duck : −12 dB over 120 ms , then Resume to 0 dB over 1 bar when talkback released. Morph Macro : one button ramps four synth params with different curves on a shared 4-bar timeline ; Multiply LFO rate by ×2/3 (triplet) mid-ramp. This summary was automatically generated by GPT-5 Thinking on 2025-10-14. Original Post: Apply ramp to value change action on widgets I am controlling my dials and faders using iPad touchscreen and I’d like to have an ability to apply ramp to value change action on widgets. So that when I press and slide to change the value, the value gets changed smoothly, not in spurts like it’s now. I.e. the desired behavior is: when press and slide a dial up very fast to get the highest value, the value changes smoothly within the configured ramp time, say, 8th note. It will help with life performance dramatically.