Feature Requests

Description: Add multiplicative operators to parameters and actions so you can change a value relative to its current value (×, ÷) instead of only setting an absolute number—perfect for tempo (BPM), rates, grid lengths, delays, and other musical ratios. Problem: Many musical changes are proportional (double-time/half-time, dotted = ×1.5, triplet = ×2/3). Today this usually requires manual math, separate presets, or multiple actions. There’s no single, reusable way to say “multiply the current value by N”—especially across multiple targets at once. Proposed Solution: New math modes in “Adjust Parameter / Set Value”: Set / Add / Subtract / Multiply / Divide . Factor input: number, percentage, or expression (e.g., × 2 , × 1.5 , ÷ 3 , × (swingEnabled ? 1.5 : 1.0) ). Musical helpers: quick chips for ×2 (double) , ÷2 (half) , ×1.5 (dotted) , ×2/3 (triplet) , ×4/3 , ×3/2 , etc. Scope: works for BPM , grid/subdivision , quantize interval , LFO/rate , delay time , envelope times , loop length (musical units) , metronome/groove cycle , and any parameter with numeric/tempo timebase. Constraints & safety: min/max clamps, unit rounding (e.g., BPM to 0.1), optional snap to musical steps; preview of resolved value before commit. Batch apply: select multiple targets (e.g., BPM + delay + LFO rate) and apply one ratio; optional link so future changes propagate. Actions & mappings: new actions Multiply Parameter by … and Divide Parameter by … ; MIDI bindings can call them directly. Variables: prevValue , newValue , appliedFactor , clamped exposed for labels/logic. Benefits: One-tap double/half-time and dotted/triplet conversions—no calculator, no duplicate presets. Consistent musical transformations across different parameters and devices. Faster experimentation and live morphs with safe limits and clear feedback. Examples: Tempo: BPM × 2 to jump into double-time; later BPM ÷ 2 to return. Rhythmic FX: Delay Time × 1.5 to toggle dotted echoes; LFO Rate × 2/3 for triplet modulation. Grid/Quantize: Grid Length × 2 for halftime editing; Quantize Interval × 3/2 for swingy grids. Macro morph: One button applies ×0.5 to envelope attack/decay while ×2 to arpeggiator rate for a tighter feel, all in sync. Expression-driven: parameter × (transport.isPlaying ? 1.5 : 1.0) —only dotted while playing. This summary was automatically generated by GPT-5 Thinking on 2025-09-16. ``` Original Post: Multiply Values(I.e. BPM) Specifically, I use ClyphX Pro in Ableton to multiply the current bpm(with variable ramping, but that’s already implemented globally in LP) to allow for transposing keys alongside tempo by varispeed loopers, it’s about the only thing I can’t do in loopy to transfer my workflow I.e. a perfect fifth up with equal temperament would be Bpm *1.498299124718113 Chromatic bpm modulation would do me but I imagine versus the present nudge value (addition), multipliers all round has broad use cases others could think of, I know nothing of the implementation but would hope it’s relatively similar to nudge being basic maths applied to a value I’ve attached my bpm transpose scripts but yeah they’re literally just dividing one note Hz by another to determine intervals

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 a complete set of clip-group actions to control groups during performance—launch all, stop all, choke/exclusive start, round-robin/next/previous/random selection, set current member by index/tag, synchronous quantized triggers, fades/crossfades inside the group, and quick group-level mute/solo/clear. Problem: Groups are great for organizing variations (fills, bass lines, one-shots), but live control still requires drilling into clips or manual selection. Performers need one-press, group-aware actions (e.g., “play the next fill in this group at the next bar,” “choke hats,” “randomize a new layer now”) without leaving the canvas or touching individual clips. Proposed Solution: Core Playback Actions (target by Group Name/ID/Color/Tag): - Group Launch (All / Selected / Current Member) — bar/beat/loop quantize, optional “arm now, fire at boundary.” - Group Stop (All / Current / Others) ; Group Clear ; Group Mute/Solo/Unmute . - Exclusive Start (Choke) — start one member and stop others in the group. - Select Member Next / Previous / First / Last / nth / by Tag , with wrap or clamp. - Trigger & Advance — fire current member and automatically advance (round-robin). - Random Member with no-repeat / weighted options. Timing & Mix: - Per-action Launch/Stop Quantize (None/Beat/Bar/Loop/Custom), Fade In/Out (ms or beats), and In-group Crossfade (equal-power/S-curve) when switching members. - Pre-roll guard (late-toggle safety) and ±offset (beats/ms) relative to boundary. Modes & Policies: - Group Mode switchers: Free / Exclusive / Round-Robin / Random / Cycle (action-settable in real time). - Voice Limit (N) — limit simultaneous members; oldest/newest cut policy. Selection & Routing Helpers: - Set Group Record Target (new recordings auto-join), Apply Color/Tags to Group Members . - Follow-Action Scope — enable/disable FAs for a group (ties into global FA controls). Variables & Feedback: - group.memberCount , group.selectedIndex , group.playingCount , group.mode , group.voiceLimit , group.name/color/tags , group.lastChosenId . - HUD/badge showing the current member and the next rule (e.g., “RR → 3/5”). Safety & Undo: - Quantized state changes; full undo; “panic” Stop Group Now . - Works across pages; ignores hidden/disabled members unless flagged. Benefits: Perform variation management from a single control—no clip hunting. Faster musical choreography: rotate fills, choke hats, swap bass lines, randomize textures— in time and crossfaded . Cleaner templates (one widget per group) and fewer duplicated actions. Clear feedback for controllers/labels using exposed group variables. Examples: Hats group set to Exclusive + Voice Limit 1 ; a footswitch runs Exclusive Start so closed hats immediately choke open hats. Drum Fills group: Trigger & Advance (Bar-quantized, 120 ms crossfade) —each press launches the next fill, cycling through 5 clips. Pads group: Random Member (no-repeat, weighted) to texture-shift every 8 bars; Group Mute toggles the whole layer. During live capture, press Set Group Record Target = “Perc FX” so new one-shots automatically belong to (and are controlled by) that group. A “Variations” button Selects nth=3 of the Bass Lines group for the chorus, then Group Stop at outro with 250 ms fade. This summary was automatically generated by GPT-5 Thinking on 2025-09-16. Original Post: Allow actions for Clip Group or Playgroups (NOT color group) IF and only IF - the user has or makes clip groups. The actions apply as a whole to all the clips in the group WITHOUT the annoyance of individual clip settings such as record if empty. EXAMPLE: A user has 24 clips and groups them into 4 groups of 6. The user has a song with 4 parts, and wants to start one group whenever they press a button (footswitch).... and stop all the other groups so that ONLY that group plays (aka mutually exclusive). IF... the user tries to accomplish this functionality via a clip action - knowing that if I start/stop a specific clip then ALL of the clips in that group will start/stop with the "respect play groups" functionality - well the problem is that if the clip they select to start/stop is empty; it will start recording, when you didn't want or indicate by your actions to record. It's senseless to allow users to create clip groups - and then the ONLY way to control the group is via a clip in the group. C'mon.... keep the functionality at the proper grain. Allow users to start /stop clip playgroups as whole via an action WITHOUT the action pointing to a specific clip. Thanks

Description: Make widget text rendering in Edit mode scale-aware and responsive so labels always fit their widgets at any canvas zoom or screen size. Provide per-widget options for auto-sizing, wrapping, truncation (ellipsis), and min/max font sizes—so what you see while editing accurately reflects performance mode. Problem: In Edit mode, widget text does not re-adjust when the canvas is zoomed or when the AU/preview frame is resized. Labels can spill outside their widgets, overlap neighbors, or clip unpredictably. This looks odd, makes alignment hard, and can mislead users about what will appear on stage. Proposed Solution: Auto-Fit Engine: Shrink-to-fit with configurable min/max font size , optional character/word wrapping , and ellipsis for single-line modes. Scale-Aware Layout: Recompute text metrics whenever canvas zoom, window scale, or widget size changes; cache results for performance. Per-Widget Controls: - Mode: Auto-fit / Wrap / Single-line + Ellipsis / Clip . - Padding & Safe Area (keep text away from rounded corners/icons). - Alignment (H/V), line height , letter spacing , icon+text layout . Edit-Time Diagnostics: Optional overflow guides (red outline), “Text fits” indicator, live preview of resolved font size/lines. Parity Preview: “Preview @ scale” toggle to simulate performance rendering exactly inside Edit mode. Actions/Variables: Set Widget Label , Set Font Size , Toggle Auto-fit ; expose textFits , resolvedFontSize , lineCount , isTruncated for labels/logic. Benefits: Clean, accurate canvas while editing—no more text spilling over widgets. Faster layout work; fewer surprises switching between edit and performance. Better accessibility and localization (long strings/languages fit gracefully). Consistent look across iPad models, orientations, and AU windows. Examples: A compact button grid with long labels (“Emphasis”, “Contour”) shrinks to fit within each button at 70% canvas zoom; ellipsis engages only if the label exceeds the min font size. A two-line wrap mode for descriptive buttons keeps typography readable in portrait and landscape. During authoring, overflow guides show which widgets would truncate; a one-tap “Fix to Auto-fit” resolves them project-wide. This summary was automatically generated by GPT-5 Thinking on 2025-09-07. It would be great it textboxes re-adjusted to screen size! :) Maybe when they are locked to a widget?

Description: Provide precise MIDI latency compensation for both incoming and outgoing MIDI with positive (delay) and negative (advance) offsets. Offer scopes at Global , Device/Port , Channel , Track/Instrument , and Mapping levels, with units in ms and musical ticks/beats . Problem: External gear, AUv3s, and networks introduce variable MIDI and audio latency/jitter. Without per-path compensation, notes, CCs, and clocks can feel late or early relative to audio, causing flams with drums, sloppy tightness, and misaligned automation. Current workarounds (manual clip nudge, quantize) don’t help live output or real-time controller mappings. Proposed Solution: Scopes & Units: - Global → Device/Port → Channel → Track/Instrument → individual Mapping. - Offsets in milliseconds or ticks/beats (tempo-aware). Directions: - Input Offset (record/learn): Shift captured MIDI timestamps (pre-quantize) to de-jitter playing feel. - Output Offset (live send): Schedule outgoing Note/CC/PC/Clock earlier (negative) or later (positive) relative to the engine timeline. Message Coverage: Notes, CC, Program Change, Aftertouch, Pitch Bend, MIDI Clock/Start/Stop, MPE (per-channel). Scheduling & Safety: Sample/buffer-aware timing; guard rails when negative offset exceeds look-ahead (auto-clamp, warn). Works with plugin delay compensation and project quantization. Calibration Wizard: - Loopback mode: send test bursts → measure round-trip → propose offsets per port. - Audio probe mode: send MIDI to a device that emits audio transients; detect via input to estimate device path latency. - Store per-rig profiles (studio/live). Per-Mapping Overrides: Action-level “Apply MIDI Offset” toggle/amount for critical macros (e.g., tight mutes, scene calls). Monitoring & UI: - Inspector shows resolved offset per path (ms & beats), recent jitter (ms p95), and active profile. - Status badges on tracks/ports when non-zero offsets are applied. Automation & API: Actions to Set/Cycle MIDI Offset at any scope; variables midiOffsetMs , midiOffsetBeats , jitterMs for labels/logic/OSC. Presets: Tight Drums , External Synth , Wireless Controller . Benefits: Tighter groove with external drum machines and synths. Reliable alignment of MIDI automation with audio events and clip boundaries. Portable, profile-based setups for different rigs/venues. Less manual nudging; better live feel and reduced flams. Examples: Set −7 ms output offset on Port: TR-8S so its kicks land exactly with internal audio. Apply +3 ms input offset to a Bluetooth controller to stabilize recorded timing before quantize. Give the Bass Instrument Track a −1/64 note offset (tempo-scaled) to feel ahead without changing audio latency. For show control, per-mapping offset −12 ms on a “Mute Bus” CC ensures mutes hit precisely on scene boundaries despite device lag. This summary was automatically generated by GPT-5 Thinking on 2025-09-07.

When dragging menu items the blur effect actually does look a bit distracting on older device (old ipad pro). Tbh it doesn't contribute to my experience and I'd be happy if i could turn it off.

I wanted to create a simple halftime and double time button. I assumed this would be easy - but widgets only allow specific BPM info - not concepts like divide and multiply BPM.

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

Description: Add 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 This feature request proposes the implementation of flexible groove quantization options for MIDI recording in Loopy Pro. The goal is to provide users with advanced tools to adjust the timing and feel of MIDI recordings, enhancing musical expression and aligning with various rhythmic styles. Problems Rigid Quantization : Currently, Loopy Pro offers basic quantization settings that may not accommodate the nuanced timing required for different musical genres or personal playing styles. Limited Groove Customization : Users lack the ability to apply swing, shuffle, or custom groove templates to MIDI recordings, restricting creative possibilities. Inconsistent Timing Feel : Without flexible groove quantization, achieving a humanized or genre-specific rhythmic feel requires manual adjustments, which can be time-consuming and imprecise. Proposed Solution Advanced Quantization Options : Introduce a range of quantization settings, including swing percentages, shuffle rhythms, and customizable groove templates. Real-Time Groove Application : Allow users to apply and adjust groove settings in real-time during MIDI recording and playback. Groove Template Library : Provide a library of preset groove templates representing various musical styles (e.g., funk, jazz, hip-hop) and allow users to create and save custom templates. Visual Feedback : Implement visual indicators within the MIDI editor to display the applied groove adjustments, aiding in precise editing and alignment. Benefits Enhanced Musical Expression : Flexible groove quantization enables users to infuse their MIDI recordings with desired rhythmic feels, enhancing the musicality of their productions. Streamlined Workflow : Real-time groove application and visual feedback simplify the process of achieving the intended timing, reducing the need for manual corrections. Creative Versatility : A comprehensive set of groove options allows users to experiment with different rhythmic styles, fostering creativity and innovation in their music. This summary was automatically generated by ChatGPT-4 on 2025-05-08.