Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terrorform Feature Request: Deeper than 64 waves & a new effect #76

Open
VegaDeftwing opened this issue Jan 31, 2022 · 1 comment
Open

Comments

@VegaDeftwing
Copy link

I'm trying to migrate old patches from V1 with XFX wave to V2 with Terrorform, and my go-to wavetable, "Viking.wav" from XFX's wave's folder is 2048 samples per cycles and 256(?) cycles. I'd very much appreciate the ability to load these bigger wavetables. I do see that VCV's WT VCO can load the bigger wave file fine, so it might be possible to yoink some of that code?

Further, XFX Wave had a really neat effect labeled as "Juno" which simply zero'd out the wave starting from the first and middle samples, and turning up the effect zero'd out more samples, as you can see in these screenshots as I turn the effect up. If you could add this as well that would be amazing!

image
image
image
image

@VegaDeftwing VegaDeftwing changed the title Terrorform: Deeper than 64 waves & a new effect Terrorform Feature Request: Deeper than 64 waves & a new effect Jan 31, 2022
@ValleyAudio
Copy link
Owner

ValleyAudio commented Feb 19, 2022

Hiya, unfortunately I've capped Terrorform's 2048 sample-per-cycle mode to 8 due to the autosave feature in Rack. You see, if you load your own tables, to maintain portability and to have those recalled when re-opening a patch, Terrorform writes its user wavetable data to the patch file. The more slots filled, the bigger the patch file. To strike a balance between usability and file size when Terrorform is fully laden, the wavetable maximum size is capped to a suitable value. I remember from testing during development of Terrorform, filling out the user slots with larger tables dramatically increased patch file size.

As for the Juno mode, that seems pretty interesting, it's similar to the Pulse modes of the Shaper feature. I'll see if I can add that down the line :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants