Zynewave's Forum Page

@Conquistador wrote:

A. Crash when using the “Move Effect Track” command.

I managed to reproduce a crash. I’ll look into this.

B. Deleting tracks and strange behavior.
If you have an instrument mapping on track it appears you cannot delete the track. Certainly I cannot use the Delete Track command it just does not work but the Eraser tool works.

I can’t reproduce this. I have no problems deleting a track with an instrument on it. Please give more details.

C. Dragging mappings within a track panel will create a copy. Unless I missed the implementation of drag and drop support within a track panel (in compact mode), I will have to assume this behavior is not as intended?

Support for drag-reordering tracks within a group panel is not yet implemented.

@Per Lichtman wrote:

Would it be possible to extend the maximum ADR times (say to 20 seconds or at least to 10) without losing the recently acquired detail in the early part of the knob?

I can’t make this change without affecting all existing presets, so I think I prefer to let it stay at 8 seconds max.

-Master Level (Volume) ADSR: I know, there are already several envelopes but here is an issue as I see it. If I am going to tweak the release times of the different oscillators to use them to change the sound of the release, then sometimes I need to have them be longer than the length of the sound itself. If I use them with such long release times while playing a pad right now, then all voices are rapidly eaten up. Also, I can tell you from my early experience with synths that having a master ADSR makes it much easier to design your first patch if you are a newbie, even if you aren’t worrying about the complexities I mentioned. Depending on what is easiest to deal with, it might also be made to only attenuate relative to the current level position just so that the level won’t blast your ears if something goes wrong in the modulation, but that really isn’t necessary.

I assume you mean the case where you use an osc as a pure modulator, and set the release to longer than the actual sound output. I see your point, but it would require a rework of the synth design to fit in an extra amp envelope. One of the challenges I set myself with this synth was to find a ballance between flexibility and using as few parameters as possible.

As far as the chorus, is the pre-delay currently in ms? If so, labeling it would be helpful. Ditto for LFO 1 and 2 speed and the rate on chorus.

I’ve added real value readouts in v0.26. The chorus effect is the default component that comes with SM. I had a look in the chorus code and it turns out the values for delay and depth were in “samples”. The equivalent ms times are less than 5 ms, which is way too low for a proper chorus. I’ll spend some time improving the chorus in the coming days.

In terms of pad sounds, what would help a lot (given the fact that you already helped a lot with the last update) would really be if you could set a panning dial below each of the oscillators for filter 1 and 2 so that the oscillators could be panned right before they hit each filter. That’s assuming that each filter has a stereo input. If each filter has a mono input, I suppose that the best that could be done would be to pan the output of each of the mono filters. Right now, Nucleum is really starting to gain strength in creating the timbral evolution of a pad or atmosphere but it can’t create the space of one (at least not without external effects).

The filters are mono, but I could add two panners for the two filter outputs. Those should of course be modulatable as well. From one of your previous recommendations, I was considering removing the delay, and add the two panner dials instead. But I see that a lot of the user-made presets are already using the delay, so I’m afraid we’re stuck with the delay. I’ll look at ways to improve the delay later on.

@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.