Feature Requests

The text inside widgets (such as rotary dials) appears blurry due to the inner color blending with the outer border. Please consider using a solid background color and providing an option to customize the text color for better visibility.

Description: Allow Loopy Pro to use the internal microphones of iOS devices (e.g., top and front mics) as a stereo input source, enabling true stereo recording directly from the device without needing external hardware. Problem: Currently, Loopy Pro does not offer stereo input from built-in microphones, even though other apps (e.g. AUM by Kymatica) can access and utilize them. Users are limited to mono recordings, which restricts spatial realism and depth in acoustic recordings or field sampling. This creates a disparity between Loopy Pro and other iOS apps that offer advanced input routing. Proposed Solution: Add support for stereo mic configuration using available internal microphone channels (e.g., front = Left, top = Right). Make stereo input available as an input option in the routing matrix and Audio Input Devices menu. Clearly label internal mic channels so users can assign or disable individual sides as needed. Benefits: Unlocks the full potential of iOS devices for stereo field recording and live looping. Enables immersive soundscapes, realistic instrument capture, and spatial stereo effects. Eliminates the need for external stereo mic hardware in many situations. Examples: Record a stereo loop with natural room ambiance using only the iPad/iPhone’s built-in mics. Use stereo mic input for voice layering or binaural field recordings. Combine with panning and spatial FX in Loopy Pro’s mixer for dynamic performance setups. This summary was automatically generated by ChatGPT-4 on 2025-07-12. Original Post: In other apps, it is possible to create stereo recordings using the front and top microphones. Please enable this capability.

Problem: Text in Loopy Pro widgets is static – there’s no way to display live values like AUv3 or MIDI, or to show dynamic status feedback. Users can’t show the value of a fader or knob, nor adapt text visibility, size or content dynamically. Proposed Solution: Text binding to controls: Let text widgets display live MIDI values from bound faders or knobs Placeholder system with support for: - $project.name$ , $bar.current$ , $channel_name_1$ , $AUv3_post_3$ - Current/total clip layers, named layers - Clip colors, groups, AUv3 plugin parameters User-defined labels for value ranges , e.g. 30–155 Hz = “Rumble”, 1000–3000 Hz = “Medium” Conditional formatting & visibility - Show exact value only while knob/fader is touched - After a delay, return to label display (e.g. "Range name") Text resizing logic - Auto-scale font size with widget/canvas changes - Manual ± font size per widget Formula-based expressions , like SWITCH(...) Text changes via actions , e.g. “Set label to: VERSE” Benefit: Real-time, intelligent feedback in the UI itself No need for extra screens or MIDI displays Clear overview of dynamic values, actions and playback states Great for live performance, section navigation, parameter feedback and more Customizable and responsive interface that adapts to user interaction Extension: Define Dynamic Behavior for Each Placeholder Ideally, each placeholder should have its own display logic – controlling when and how it appears. Examples: Always visible (default) Only visible during interaction , e.g. while a fader or knob is being moved Visible for a short time after interaction , e.g. 1 second after release Conditionally visible , e.g. only when a clip is playing or a value is in a certain range Toggle visibility via actions or logic This would allow for highly adaptive and context-aware UIs – showing the right info at the right moment without visual overload. It would give Loopy Pro a unique edge as a flexible, user-definable performance environment. This summary was automatically generated by ChatGPT-4 on April 30, 2025.

Currently the “Cancel Count-Ins/Outs” action does not have any targeting options, so it cancels all count-ins/outs. Sometimes users might only want to cancel some of the count-ins/outs. For example, after triggering a mutually exclusive play group to play in order to switch from one section of a song to another, I might then want to cancel the count-in for some of the clips that are about to play (for a breakdown section) while letting the other count-ins/outs continue. Or anytime I trigger multiple clips to play, stop, or record, and one or more but not all was by mistake, I could fix my mistake while still allowing the other actions that were on purpose to continue. This action should have all the targeting options that other actions have. Targeting “this clip” is the option I most want to have because I could set a gesture that cancels count-ins/outs for whichever clip that gesture is performed on. But I can see uses for other targeting options as well.

Description This feature request proposes the implementation of 14-bit MIDI support within Loopy Pro to enable high-resolution control over internal parameters as well as those of hosted AUv3 plugins. Supporting 14-bit MIDI would dramatically increase the resolution of parameter adjustments—from 128 steps to 16,384—making Loopy Pro suitable for precision-critical use cases in live performance, sound design, and professional production environments. Problems Insufficient Resolution with 7-bit MIDI : Current MIDI support is limited to 7-bit (0–127) messages, which causes stepping artifacts when controlling parameters like filter cutoff, reverb amount, or pitch, particularly on high-quality AUv3 instruments and FX. Limited Expressiveness and Control : Power users and live performers using expressive hardware struggle to achieve the desired smoothness and nuance, especially when dealing with fine-tuned parameters like EQ bands, compressor thresholds, or pitch bends. Underutilized Hardware Capabilities : Many modern MIDI controllers (e.g. Electra One, Faderfox EC4, BomeBox) already support sending 14-bit high-resolution CC (including NRPN and RPN). Without support in Loopy Pro, these devices can't be fully utilized. Proposed Solution Full 14-bit MIDI Support : - Recognize and respond to 14-bit high-resolution MIDI Control Change messages (using MSB/LSB pairs). - Support both NRPN and RPN-based control messages. Enhanced MIDI Learn Engine : - Extend the MIDI Learn system to detect 14-bit CC pairs and assign them as high-resolution parameter sources. Visual Feedback for High-Res Bindings : - Clearly indicate when a parameter is being controlled via 14-bit resolution (e.g., with a visual tag or tooltip in the UI). AUv3 Integration : - Ensure that high-resolution control is passed through to hosted AUv3 plugin parameters that natively support fine resolution. Examples Precise Filter Sweeps : A performer uses an Electra One to send 14-bit CC data to control a synth’s cutoff frequency inside Loopy Pro, achieving silky-smooth filter movements with no audible stepping. Plugin Automation : A producer records high-resolution automation into Loopy Pro using a Faderfox EC4, adjusting reverb decay and EQ gain curves with surgical precision. Cross-Platform Consistency : A user coming from Bitwig or Logic Pro wants the same level of resolution with their MIDI controller when using Loopy Pro live on iPad or macOS. Device-Specific Expectations : Controllers like the Electra One , Faderfox EC4 , and setups using BomeBox or Axoloti expect 14-bit support and already send such data. Without support, Loopy Pro remains the weak link in an otherwise high-res control chain. Benefits Professional-Grade Precision : Ensures Loopy Pro is capable of delivering the same level of detailed automation and live control as top-tier desktop DAWs. Expanded Hardware Compatibility : Allows seamless integration with hardware that sends 14-bit MIDI—common in studio and touring-grade MIDI setups. Improved Sound Design and Live Control : Enables smoother real-time parameter morphing, better modulation routing, and more expressive performances. This summary was automatically generated by ChatGPT-4 on 2025-05-17.

Under project-wide follow actions, there should be an option to trigger actions whenever a certain play group starts playing or stops playing.

A Default RGB Pad Color Syncing Mode would allow smaller controller manufacturers and individual users to implement RGB color syncing on newer or niche controllers like the Exquis midi controller. It is unrealistic to expect Loopy Pro to support every midi controller past, present and future, unless there is an A.I for that😊. With a default mode, larger manufacturers could bake in support for Loopy Pro and smaller manufacturers and individual users could use midi effects plugins such as Plugdata, Pd and Midifire to implement RGB color syncing. If that is not possible, please support the Exquis midi controller directly.

Description This feature request proposes the implementation of a radial (pie-style) pop-up menu within Loopy Pro's gesture system. The goal is to provide users with a more efficient and visually organized method to access multiple actions or presets through a single gesture or button, enhancing the user interface and workflow. Problems Inefficient Navigation : Currently, navigating through step dials or radio grids to select a specific action or preset can trigger unintended actions for each intermediate step, leading to workflow disruptions. Screen Real Estate Constraints : Limited screen space, especially on smaller devices, makes it challenging to display multiple controls simultaneously without cluttering the interface. Limited Gesture Integration : The existing gesture system lacks a dynamic menu that can present multiple action options in a compact and accessible manner. Proposed Solution Radial Menu Integration : Introduce a radial pop-up menu that can be triggered via gestures or button presses, displaying multiple action options in a circular layout. Deferred Action Execution : Ensure that actions within the radial menu are only executed upon final selection, preventing unintended triggers during navigation. Customizable Menu Items : Allow users to customize the actions or presets available within the radial menu to suit their specific workflow needs. Visual Feedback : Provide clear visual cues within the radial menu to indicate the currently highlighted option and confirm selection upon release. Benefits Enhanced Workflow Efficiency : Users can quickly access and execute desired actions without navigating through multiple menus or triggering unintended actions. Optimized Interface : The radial menu offers a compact and organized method to present multiple options, conserving screen space and reducing clutter. Improved Gesture Utilization : Integrating the radial menu into the gesture system expands the functionality of gestures, allowing for more complex and efficient control schemes. This summary was automatically generated by ChatGPT-4 on 2025-05-08.

Currently a slider cannot be used to trigger a button. This could be useful for triggering macro as suggested in the wiki. Example: I want to trigger a bunch of action already registered in buttons before to run my slider effect.

When I configure a slider to send MIDI messages, I cannot send a CC with a range 0 to 0. If you select 0-0, the value is set to 0-127. Example: I want to: Send always 0 to channel 1 Send from 0 to 127 to channel 2