John C
Description:
Introduce the ability to export and import individual widgets (or groups of widgets) for reuse across different projects, including their internal mappings, curated lists, and logic.
Problem:
Currently, widgets can only be duplicated within the same project or copied via clipboard, which often leads to broken references (“NA” or “#REF”) when taken out of context. Complex or curated widgets, such as preset selectors, are difficult and time-consuming to recreate in new projects.
Proposed Solution:
Provide an export/import mechanism for widgets that preserves their structure, curated lists, and mappings. This could include a way to debug or gracefully handle missing references when importing into a different project, ensuring maximum portability.
Benefits:
  • Save time by reusing complex widgets across multiple projects.
  • Avoid tedious manual recreation of curated or elaborate widgets.
  • Ensure consistency in setup, especially when debugging or sharing.
  • Enable a personal library of frequently used widgets.
Examples:
  • Export a preset selector widget curated to 20 out of 100 plugin presets, then import it into a new project without rebuilding the list.
  • Share a custom MIDI-mapping widget with collaborators for consistent performance setups.
  • Maintain a library of debugging widgets to test signal flows across projects.
This summary was automatically generated by GPT-5 Thinking on 2025-08-20.
Original Post:
Ability to export Widgets. I have had some issues using clipboard, and I understand that there are major issues with handling undefined things for out of context widgets, but some elaborate widgets are a real pain to recreate in a new project. It would be great to export/import and debug stuff that’s “NA” or “#REF”.
For example a preset selecting widget I have is curated to 20 of the 100 presets on a plugin. Nice to keep that for other projects.