Being Able to Set a Project Key and Automatically Convert Melodic Loops to Current Key
planned
JP M
Description:
Loopy Pro users would benefit from a feature allowing them to set a project key and automatically convert imported melodic loops to the current key. This functionality is particularly useful for loops from external sources (e.g., BlocsWave), where pitch correction to match the project key is essential.
Problem:
Imported loops may not match the project key, requiring manual adjustment. This can be time-consuming and impractical when dealing with multiple samples. Current solutions like Launchpad can apply pitch shifting globally, per group, or per clip, but they rely on metadata (e.g., filename information) rather than analyzing the audio content itself.
Proposed Solution:
- Allow users to set a global project key in Loopy Pro.
- Provide automatic pitch detection for imported loops, adjusting them to the set key.
- Include options for common pitch modifications, such as:
- Current key ± 5th up/down
- Current key ± 1x and 2x octave up/down
- Enable a pitch wheel for manual adjustments, similar to Launchpad's functionality.
Benefits:
- Streamlined workflow when integrating external loops.
- Minimizes the need for manual pitch correction.
- Ensures harmonic consistency across the project.
This summary was automatically generated by ChatGPT-4 on 2025-05-07.
ultracello
Ideally plus:
– current key plus 5th up/down
– current key plus 1x and 2x oct up/down
Michael Tyson
planned
Michael Tyson
Launchpad app has this too, as a pitch wheel. Apply globally, per group or per clip. Automatically recognise current pitch and shift to target.
JP M
Michael Tyson: yes, I'm not at all sure but I think launchpad (and blocswave) use the info contained in the 'standard' samplefilename (bongobeat_Em_110.wav) and do not use detection/analysis of the wave itself.. (works fine if you use most commercially distributed (splice etc) samples though..)
Emil
Yeah man!
ultracello
under review