Forum Replies Created
-
Posts
-
Maybe try github pages?
https://help.github.com/categories/github-pages-basics/Using it with Jekyll is pretty sweet.
Hi there, and thanks for the reply. I hope I didn’t sound too grumpy in my last post!
Thing is, uiEnvelope is so close to what I need, and I was hoping to not get into looking into the innards of how the UI controls work. It’s great as-is, if there were methods for getting & setting the points via code, I think that’s all I really need.
Sorry if the thread resurrection is not appropriate…
I’ve been playing with CTRLR for a day or so, and have been having fun & making good progress. I’m working on an editor a Casio VZ series synth.
However lack of a usable envelope controller is going to massively ramp up the complexity of my project, is uiEnvelope still not workable? From doing a “what(myUiEnvelopeModulator)” I cannot see methods for getting points, although they can be added via the widget GUI. Also the Utility tab refuses to show XML for the widget.
I had a look at the panel by macrodx (earlier in this thread) and it looks awesome, although complex and I’m unsure how I would integrate that into an existing panel.
IMO the ability to link nodes is a “nice to have” (if I am understanding the requirement), whereas a workable envelope widget seems essential for a synth editor.
Plenty of synths allow an A = 100% with D, S & R = 0% for example and I don’t think generic code should make assumptions around this (even if illogical), as interesting things may happen when it hits the hardware. If it’s “bad interesting” not “good interesting” then it’s up to client code to test for and manage that. Similarly, this VZ synth allows for variable sustain points and up to 8-step envelopes, but I think that it should be left up to client code to manage device-specific weirdness rather than hacking weirdness into base classes.
I think that “all” I need are methods to get points as a list, set the X & Y max scaled values, and getters & setters for scaled values. My more annoying requirement is a Y axis from -63 to +63 for these DCO’s, so the root/0th point would be at (0, maxY/2) not (0,0) — but this is “just” a visual thing and would make no difference to how it sounds (also you’re only going to be transmitting positive hex numbers, so a “negative” Y value would always need transforming anyway).
Hope that makes sense, and thanks!
