Home › Forums › Products › Vsig and Preset Development › VSIG Requests
- This topic has 3 replies, 2 voices, and was last updated 3 months, 2 weeks ago by
ndeshpandeEventide Staff.
-
AuthorPosts
-
-
September 1, 2023 at 4:47 am #173960
PuppeteerParticipant1) Would it be possible to adjust the c_graph object so that a precise number can be typed into an individual point?
I’m trying to use this as a compact frequency selector for 32 bands, but on Emote, you can only adjust each band with a mouse, which is not precise enough. An option to have tapers included would be awesome.
2) Can we get a mtaperknob object, so we can make bulk taper knobs. Again, thinking frequency or dB selectors here?
3) Preset Table. An object that can accept a control signal integer (with say a range of 32), with an arbitary number of outputs (maybe 32).
For each input integer each all of the outputs is set to a preset value. Basically a big look up table. where the input determines which set of outputs gets set. The idea is to use this to have a number of different defaults for mknob. Basically it would be like a stack of c_switch where all the inputs are constants.
4) An upgrade to Curve (the audio rate one) to allow 1024 points, rather than 32. Basically an audio rate c_tablen
-
September 5, 2023 at 1:09 pm #174027
Howdy, we’ve taken note of these and have added feature requests to our backlog, though there definitely isn’t a timeline for us getting to this workload.
If you could give us a few specific examples of your needs for these modules, it might give us more insight into building specific modules to solve your problems that can’t be solved with what’s already in vsig (your examples for 1 and 4 already help us out a bit). Off the top of my head, a few follow ups though these are without the context of the specific problem you’re trying to solve, so I admit they may be naive suggestions…
2) Take a look at c_master_taper. I frequently use it to map input knobs. Frequency selection tapering can be done with the c_master_taper, and for dB/amplitude conversion either take 10.0 * log10 of the squared value for going amplitude -> dB, or 10^(in/20) to go from dB -> amplitude. dB conversions inherently throw out phase, since the logarithm is undefined (well, imaginary) for negative values and the dB value itself contains no phase information for amplitude conversion.
3) A c_quantize hooked up to a c_table_n might be able to help you in the short term.
4) You could put a bridge on the output of c_table_n by connecting a c_fltr_a to it. I like 20 ms as a baseline time constant for parameter smoothing.
-
September 6, 2023 at 5:41 am #174043PuppeteerParticipant
Howdy, we’ve taken note of these and have added feature requests to our backlog, though there definitely isn’t a timeline for us getting to this workload. If you could give us a few specific examples of your needs for these modules, it might give us more insight into building specific modules to solve your problems that can’t be solved with what’s already in vsig (your examples for 1 and 4 already help us out a bit). Off the top of my head, a few follow ups though these are without the context of the specific problem you’re trying to solve, so I admit they may be naive suggestions… 2) Take a look at c_master_taper. I frequently use it to map input knobs. Frequency selection tapering can be done with the c_master_taper, and for dB/amplitude conversion either take 10.0 * log10 of the squared value for going amplitude -> dB, or 10^(in/20) to go from dB -> amplitude. dB conversions inherently throw out phase, since the logarithm is undefined (well, imaginary) for negative values and the dB value itself contains no phase information for amplitude conversion.
Thanks for the feedback. The application I’m looking at right now is a 32 band vocoder where I want to set the input filter frequency and output filter frequency using knobs. Two 32 output mknob would need 64 x c_master_tapers wired back into the inputs to achieve this, or I’d need 64 taperknobs. An mtaperknob would be a much more elegant way to do this, and this would also be useful for things like amplitude on graphic eq’s, multibank delays etc.
3) A c_quantize hooked up to a c_table_n might be able to help you in the short term.
For this example, I’d need to get the c_table_n to trigger 32 further c_table_n’s I was looking at building a bunch of presets for different vocoders with their bandwidths, and filter frequencies, where selecting say Moog Vocoder, or Ensoniq Vocoder, or Korg Vocoder, would set each of the 32 bands to some preset frequency, and turning on and off bands as needed, as well as adjusting the bandwidths of the filters.
I’ll get around this by just building a bunch of presets, but it would have been nice to have a menu on the UI to select a model to emulate.
4) You could put a bridge on the output of c_table_n by connecting a c_fltr_a to it. I like 20 ms as a baseline time constant for parameter smoothing.
Yeah, I tried that. I’m building a complex waveshaper with repeating shapes. It needs to be 1:1 at audio rate for the input to get correctly mapped. 32 nodes isn’t enough if you have discontinuities in it.
I may be able to get around this last one by using the max ~gen export, but I need to get hold of a Max license and then get my hands dirty.
-
September 12, 2023 at 11:23 am #174149
Got it, understood. Yeah, your needs here are pretty specialized though certainly valid – each band needs unique output mappings from unique user input values.
I’ve forwarded your requests here to our product specialists for VSig and H9000, feature requests will be filed if they have not already been logged in our system. I can tell you we would not be getting to these customized modules any time in the immediate future, and if you need solutions in the short term then gen~ integration is your best bet.
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.
