Kalle Niemi
Description:
Improve the Loopy Pro preset manager by aligning it with 7-bit MIDI program change and bank change messages. This would include default MIDI mapping from 000 to 127 (AUV3 standard) and improve compatibility with external MIDI hardware and plugins.
Problem:
  • MIDI program and bank change support varies across AUV3 plugins.
  • There’s no consistent implementation, which complicates preset handling and controller integration.
  • Users have no easy way to map program changes to default AUV3 states or toggle numbering schemes.
Proposed Solution:
  • Add support for preset banks indexed 000–127 (7-bit MIDI spec) to match AUV3 default states.
  • Include options such as:
– Setting a custom “initial” patch.
– Global setting to toggle between numbering systems (e.g. 000→127 or 001→128) to match different hardware conventions.
  • Ensure smooth mapping between MIDI messages and plugin state recall.
Benefits:
  • Enhances interoperability with MIDI hardware and plugin standards.
  • Brings Loopy Pro closer to the experience of traditional hardware-based instruments.
  • Reduces confusion around patch numbering inconsistencies between devices.
Examples:
  • Use a MIDI controller to recall plugin presets 012, 045, or 099 by sending program change messages.
  • Match numbering between Loopy Pro and external synths or effect units.
  • Define a starting preset per project or session as an “initial” state.
This summary was automatically generated by ChatGPT-4 on 2025-07-12.
Original Post:
Midi program change and bank change messages are part of MIDI which is not always implemented in the Auv3, and when this is implemented the level of implementation varies greatly.
My suggestion is to update the Loopy Pro preset manager to match 7-bit midi messages, with numbered banks, filled with auv3 default state from 000 -> 127.
Extra features to this:
  • custom "initial" patch
  • system setting to toggle numbering from 000 -> 127 / 001 -> 128 ( as there is variance on how the program change messages are presented in different software / hardware)
Goal of my feature suggestion is to bring software to resemble the ease of use of hardware instrument and effect.