You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe!
I'm experimenting with creating new synths programmatically, that involve inserting custom wavetables. However, it is not clear how to do this in Surge.
Describe the solution you'd like:
Ideally, there would be an XML format that captures the complete state of the synthesizer, nothing missing (Update patch file format to not use .fxp #6627)
The test suite for this could have scripts to roundtrip from FXP to XML and back, to make sure they are identical. I would be happy to contribute.
The Python API could be extended. If it is incomplete, an XML solution would be preferable.
Describe alternatives you've considered:
IDK.
Additional context:
I've made a lot of progress in getting AI to program synths, which I'll be sharing with the community soon, but wavetables is a missing link.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe!
I'm experimenting with creating new synths programmatically, that involve inserting custom wavetables. However, it is not clear how to do this in Surge.
Describe the solution you'd like:
The test suite for this could have scripts to roundtrip from FXP to XML and back, to make sure they are identical. I would be happy to contribute.
Describe alternatives you've considered:
IDK.
Additional context:
I've made a lot of progress in getting AI to program synths, which I'll be sharing with the community soon, but wavetables is a missing link.
The text was updated successfully, but these errors were encountered: