No way to export wavetables from a patch #1341
Comments
|
Would this be in WAV format, 2048 points per frmae (regardless of how many points the original WT had)? |
|
No I was thinking you would export exactly what’s in the patch probably as a wav with surge tags This is successful if loading a patch exporting the wav and then reloading the wav is a complete noop. We could add a feature “export as 2048 samples” and do the interpolation. But that’s not the default I was also thinking - like you I suspect - of this being a good first issue |
|
Oh and it is not at all obvious how to best make a 2048 version of a 128 sample wavetable. I actually coded this up in python and even good interpolations like Lanczos have problems and introduce ringing in some cases in the library. |
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Dec 5, 2019
Given a Patch, it was impossible to save the wavetable as a .wav which you could use elsewhere. You could copy and paste but you couldn't extract. SO this adds code which exports the wav into your library for you and lets you know, including doing smart things with srge tags and the like so surge can use it in other contexts. Closes surge-synthesizer#1341
baconpaul
added a commit
that referenced
this issue
Dec 5, 2019
Given a Patch, it was impossible to save the wavetable as a .wav which you could use elsewhere. You could copy and paste but you couldn't extract. SO this adds code which exports the wav into your library for you and lets you know, including doing smart things with srge tags and the like so surge can use it in other contexts. Closes #1341
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pretty straight forward really. You load a patch and want the wt the synth makes it hard. You can copy and paste the osc but you can’t get it as a standalone
The text was updated successfully, but these errors were encountered: