Feature Requests

Description: Allow recording on a target clip to be queued while another clip is playing, so capture begins exactly at the next musical boundary (beat/bar/loop/cycle of clip X) without stopping or disrupting current playback. Supports pre-roll/count-in, visual cues, and cancel. Problem: Pressing Record during playback can start mid-cycle or force awkward stops. Performers need a way to pre-arm recording and have it fire cleanly at the next boundary , keeping the current material running until the handoff. Proposed Solution: Record Queue State: Per clip/track Queued to Record state with HUD countdown and ring badge; optional soundless pre-roll. Quantize Targets: Next Beat / Next Bar / Next Loop / Cycle of Clip … with ± offset (beats/ms); respects global quantize and time signature. Count-In & Guard: Per-action count-in (bars/beats) and late-press guard to defer if the press is too close to a boundary. Modes: Record New , Overdub Existing , Replace , or Record into Empty Only ; choose after-queue behavior for the currently playing clip (keep, stop at boundary, crossfade). Groups & Colors: Queue for color groups (e.g., next empty in Blue) or for selected clip ; exclusive/choke options for one-shot lanes. Actions & Bindings: Queue Record (target, boundary, offset, mode) , Queue Overdub , Queue Replace , Cancel Record Queue , Record Now (bypass) . Safety & Recovery: Quantized, sample-accurate start; cancel on clip delete or page change (optional); full undo. Feedback & Variables: HUD (“Recording in 1 bar”), ring flashes on the final beat; vars clip.isQueuedToRecord , queue.boundary , queue.etaMs . Benefits: Clean, musical entries—no half-starts or chopped first transients. Keep performance flowing by recording exactly when the loop turns over . Fewer footswitch taps and error-prone timing; safer live capture. Works across colors/groups to build structured arrangements on the fly. Examples: While a Verse loop plays, press a pedal to Queue Record the Chorus clip at the next bar with a 1-bar count-in ; Verse keeps playing until the handoff. Queue Overdub on a drum clip for the next loop cycle; current take keeps running, overdub starts precisely on turnover. In a one-shot group, queue a new FX hit to record at the next bar + 1/8 ; the previous one-shot stops at that boundary. Use Queue Record (Cycle of “Drums”) so a bass clip starts recording on the drums’ cycle even in a 3:2 polymeter. This summary was automatically generated by GPT-5 Thinking on 2025-10-08. Original Post: Queuing record while another clip is playing Hey! My setup got to complicated! It’s really not though, I just want to do simple things. Queue recording for clip 2 for when clip 1 has ended. Here, I made a short video about it https://youtu.be/ksgolvIOkYs?si=fV89G3Cm6SApfsSG Please come back to me if I’m wrong I can say my master is at 1 bar for important settings. -> I record as long clips as I want to then count out with 1 bar, temporarily overiding other loop settings. This is the meat of the template but I also want potatoes, and sauce. Thanx @Michael!

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: Enable support for AUv3 plugins with multiple audio inputs, including standard sidechain inputs on FX and instruments (e.g. FabFilter Twin 3), and allow flexible audio routing between tracks to use this functionality. Problem: Loopy Pro currently doesn’t support AUv3 sidechain inputs or multi-input routing. This limits its use as a fully capable DAW for those relying on dynamics control or complex routing setups (e.g. ducking via sidechain compression). Proposed Solution: – Implement routing of audio from one track to the sidechain input of a plugin on another track – Support AUv3 FX plugins with standard sidechain inputs – Support instrument AUv3 plugins that also include sidechain inputs (e.g. FabFilter Twin 3) – Allow use of multi-output AUv3 instruments with flexible routing to Loopy tracks or groups – Provide clear UI elements to manage input/output routing between tracks and plugins Benefits: – Makes Loopy Pro viable as a standalone DAW for advanced users – Enables mixing techniques like ducking, pumping, spectral sidechaining – Makes full use of AUv3 plugins that already support these features – Greatly enhances creative potential in sound design, live setups and dynamic control workflows This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Description: Enable Loopy Pro to access and route individual outputs from multi-output AUv3 plugins. This would allow users to handle complex signal routing within Loopy itself, without needing to rely on external hosts like AUM. Problem: Currently, Loopy Pro does not expose the individual outputs of multi-output AUv3 plugins. As a result, users cannot route separate channels (e.g., drum parts or stems) to different buses, apply individual effects, or send them to discrete hardware outputs. This makes advanced mixing setups cumbersome and forces users to rely on external apps. Proposed Solution: – Detect and expose multiple output channels from AUv3 plugins – Allow routing of each AUv3 output to a different Loopy Pro bus or track – Enable per-output effect chains (e.g., reverb on snare, delay on hi-hats) – Permit discrete outputs to be routed to specific physical outputs on an audio interface – Maintain compatibility with AUv3 instruments like Digistix, Hammerhead, FAC Drumkit, Loopy AU (backing tracks), etc. – Provide clear UI to manage output-channel mapping within Loopy Pro’s mixer or plugin settings Benefits: ✅ Gives users full control over plugin output routing inside Loopy Pro ✅ Eliminates the need to use AUM or other routing apps for multi-output AUv3s ✅ Supports pro-level mixing setups with buses, FX, and separate audio interface outputs ✅ Makes Loopy Pro a more complete AUv3 host, especially for beatmakers and live performers ✅ Enhances flexibility for handling multi-part instruments and complex backing tracks This summary was automatically generated by ChatGPT-4 on April 30, 2025.

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: 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.

Issue: With 2.0 and the addition of midi, routing and configuration is more powerful, but also slower to set up for spontaneous jams (often requiring multiple mixer-canvas-popup-submenu interactions for a single input->output result). Plus, the growing mixer becomes a bit overwhelming to navigate the more things are added, even with folding. Proposed solution: Wizards for typical scenarios, that guide through each step, creating or connecting the desired combination in the background (inputs, colors, outputs, widgets).

Description: Add optional MIDI stem capture to Session Recording so Loopy Pro records MIDI alongside audio—per track/color and at user-defined tap-points (input, post-FX, or outgoing). Export as Standard MIDI Files (Type 1), aligned to the session’s tempo map, time signature, and bar starts. Problem: Session Recording excels at audio stems, but many users also need the exact MIDI that was played or generated (notes, CC/PC, pitch bend, aftertouch, MPE) for later editing, re-instrumentation, or re-rendering. Without MIDI stems, you must re-perform or guess from audio, which kills flexibility and slows post-production. Proposed Solution: Capture Matrix (choose any): - Per-Track Input (Pre) — raw incoming MIDI to that track (pre quantize/FX). - Per-Track Post-FX (Post) — after MIDI plugins/transformers. - Global Out — the consolidated MIDI Loopy Pro sends out (to AUv3/hardware). - Per-Clip Playback (Optional) — MIDI emitted by playing clips on that track. Data & Fidelity: Notes, CC (7-bit & 14-bit), Pitch Bend (14-bit), Poly/Channel Aftertouch, Program Change, RPN/NRPN, MPE (per-channel). Optional SysEx (size-limited). Timing & Alignment: Sample/clock-accurate timestamps; embeds tempo map & time-signature ; respects count-in/out, latency/MIDI offset, and quantize settings. Quantize Options (per capture): Raw , Post-Quantize , or Both (write two lanes/files). File Layout & Naming: One SMF per selected scope (e.g., Keys-Track (Post).mid , Drums-GlobalOut.mid ); color/track names included; bar-aligned starts. Session Export Integration: New “MIDI Stems” toggle alongside audio stems; bundle with audio in the session export folder/zip. Recovery & Safety: Works with Auto-Save/Recovery; warns on missing tempo; clamps negative offsets beyond look-ahead. Actions & API: Toggle MIDI Stem Capture , Set Capture Tap-Point , Include/Exclude Clip Playback , Export Now . Vars: midiCaptureEnabled , tapPoint , midiEventsRecorded , mpeEnabled . Benefits: Full creative freedom post-show: re-voice, re-mix, or re-render tracks from exact performance data. Accurate archival of controller moves (CC/Bend/AT) and program changes. Faster collaboration—send compact MIDI + a reference mix instead of giant multitracks. Reliable synchronization with audio stems for tight DAW workflows. Examples: Capture Keys (Post-FX) to keep chord voicings + sustain CC exactly as performed; later swap pianos in a DAW. Record Global Out to preserve program changes and automation sent to an external synth—then re-render via the same rig. For an MPE controller, save per-track Post MIDI to retain per-note bends/pressure; export audio stems + .mid for detailed editing. Enable Both (Raw + Post-Quantize) on Drums to choose between human feel and grid-tight editing later. This summary was automatically generated by GPT-5 Thinking on 2025-09-14. ``` Original Post: Have the option of the midi performance/loops be captured and exported as midi files along with the audio stems.

Description: Add display controls for the mixer’s dashed decibel reference lines, plus clearer level readouts on the fader itself. Problem: Always-visible dB guide lines add visual noise, eat vertical space, and can be ambiguous at a glance because their values must be traced to the side. Each fader already shows a numeric dB readout nearby, so many users prefer a cleaner view—especially on dense performance layouts. Proposed Solution: Visibility Controls: Per-project (with per-page override) options: Show , Dim , Auto (show while adjusting) , and Hide . Density & Style: Choose Major ticks only (0 dB, −6 dB) , Major + minor , or None ; optional 0 dB emphasis line. Handle Readout: Optional numeric dB (or %/linear) displayed inside the fader cap while adjusting (or always), with high-contrast bubble. Quick Toggle: Action/shortcut to cycle visibility states; variable exposes current mode for labels/LEDs. Accessibility: Larger readout mode, color-blind/contrast-safe styling; snap-to-0 dB option with press-and-hold to bypass. Persistence: Settings saved with themes/templates; defaults in Preferences. Benefits: Cleaner mixer during performance; less cognitive load. Clearer metering: focus on the value that matters (in-handle readout or side label). Flexible for both precision editing and live use. Consistent visual language across templates and pages. Examples: Live set: set guide lines to Auto so lines appear only while you move a fader; 0 dB line remains emphasized. Editing session: enable Major + minor ticks and always-on handle readout for precise balancing. Map a controller button to Toggle Mixer dB Lines to declutter the screen mid-show. This summary was automatically generated by GPT-5 Thinking on 2025-08-25. Original Post: Allow hiding decibel reference lines in the mixer The dashed line indicators for decibel levels in the mixer are currently always shown where they add unnecessary visual noise and take up a lot of screen space for little to no benefit (at the position of each slider it's unclear what each line represents without tracing it to the side), and the db value is shown next to each fader aswell already. I would even suggest moving this value into the slider handle itself (making that round or square to contain it) so it's prominently visible and cannot be mistaken for something else. But allowing to hide the lines would already be an improvement.

Description: Improve Loopy Pro’s audio engine by enabling true multi-core (multi-threaded) CPU processing for audio rendering, especially useful with multiple AUv3 plugins and parallel signal paths. Problem: Currently, Loopy Pro does not seem to fully utilize multi-core CPU processing for audio tasks. This can quickly lead to CPU overloads in complex projects with several AUv3 plugins, effects, or multiple audio channels – even on high-end iPads. Proposed Solution: – Implement multi-threaded audio rendering – Distribute AUv3 plugin processing across available CPU cores – Prioritize per-track or per-plugin parallelization – Dynamically allocate threads based on system load – Add CPU usage per-core display (optional) Benefits: – Much better performance on modern multi-core CPUs – Lower risk of audio glitches and dropouts – Enables more complex, creative setups with more plugins – Extends device longevity by improving resource efficiency – Makes Loopy Pro more competitive as a DAW alternative This summary was automatically generated by ChatGPT-4 on April 30, 2025.