Zynewave's Forum Page

@rinxai wrote:

@ Frits – thanks for the changes, will check it out.

I haven’t released 0.26 yet.

Also, is there a way for me to upload the bank to Zynewave, I would like to maintain a single file, rather than uploaded multiple versions.

You can upload it to the wiki. Eventually I’ll create a wiki page for Nucleum, with a preset file library. Until then you can create your own rinxai page under user pages, and upload your file there.

Hi Per,

Thanks for the detailed report. Overall, I’m pleased to hear that the synth has a fair chance of being useful for a lot of people.

-The delay: I have no idea whether these are the default effects that come with SynthMaker or something of that ilk but I can say that chorus works a lot better than the delay and I’d honestly rather have no delay present than the one that is there. I’ve tried using some of it on my presets and I find myself wanting to use an external delay (basically any other delay) rather than deal with it.

The delay is the SM default “ping-pong delay”. I wouldn’t mind replacing it with a more useful delay implementation, if that can help with the creation of pad patches. I tried with the SM default reverb module, but to my ears it sounds terrible. Can you refer me to some examples of delays you find useful?

-ADSRs: Setting the ADSRs is a lot trickier than I am accustomed to in other synths for several reasons.
1) The ranges don’t seem to be ideal and the knobs quickly go past the “sweet spots” with little detail in the ranges I tend to favor. The range covered by 0.000 to 0.400 on the knobs would much more usefully be covered by 0.000 to 0.700. Not as much detail is required with really long settings (e.g. 2 seconds or more)

I agree with you here. The current formula for the ADR time in millisecs is: 8*x^3. So a max time of 8 seconds, and the knob at 0.5 gives a time of 1 second. I already increased the low end resolution in v0.24, but I can easily increase it further. Changing the formula to 8*x^4 gives a time of 500 millisecs at 0.5. Changing it to 8*x^5 gives 250 ms at 0.5. What seems reasonable to you?

3)The numerical readouts have no clear scale (not that I don’t encounter that elsewhere sometimes) meaning that time has to be invested initially on trial and error. If there is any way to replace the 0.00 to 1.00 scale with a seconds readout, that would be a big improvement.

I can easily add ms readouts in a later update. I just want to ensure the parameter scalings are settled before implementing this.

4)Curves/lines used in the envelope scaling by default seem “off”. I haven’t had luck using Shape 1 and Shape 2 in the Mod Matrix to correct this yet. Lots of experiments but no results. Maybe I am missing something obvious though so feel free to help fill in the blanks for me.

Do you mean the “AD Time” modulation targets? They apply a linear scaling of the AD times in milliseconds. If you think a different scaling is more appropriate, please let me know.

-LFOs: Similar issues to ADSRs. Almost unusable at low frequencies though quite fun at high frequenices. More detail at the low end would be great.

So an exponential scaling like the ADR times would perhaps be the solution. A formula of 20*x^2 gives a max of 20 Hz, and 5 Hz at center. Would that be reasonable?

@H-man wrote:

The CC assignments are working great with my BCF2000. I kinda worked out which was which by deduction and trial and error, not too hard but is there anywhere in Podium that I/we can view these?

No. If there is interest in this plugin on kvr, I’ll probably write a short manual, which could include a chart of the CC numbers.