Classic ZynAddSubFX VST download

[jackoo]

like I said... "architectural" issue...
This one needs more brain power.... and another day!

Thanks so much for your feedback!
Cheers!

[jackoo]

After 3 days of work...
Please test the new MIDI implementation!
======================================

ZynAddSubFX VST
ver. 2.4.1.512beta VST VDX version (June 3rd, 2020)

- Fixed "again" right/left panning
- Major change in the Midi implementation (adapted architecture more to the VST standard)
- Midi sync fix with large buffer sizes
- Fixed another preset browser bug (which allowed to cfg file to pile up)
- Properly fixed interaction between 'max_voices' and Virtual Keyboard
- Should in theory work well now with any buffer size (doesn't require fixed buffers anymore).
- Added the option to change the default state of the mod-wheel via the cfg file.
- 30 new quality patches by VDX (Blade Runner, Floyd Diamond, The Unknown Man, and more)

ZynAddSubFX VST v2.4.1.512beta (direct link)

[Iu Gob]

Everything I've tried has worked well. Thanks Jackoo. I am happy with classic ZynAddSubFX VST. Thank you once again for keeping it up to date and alive. New presets are also appreciated.
A big hug!!

[cyrb]

Nice work!

At first the new version didn't seem to fix my issue in FL. But I took a second look at the "Processing" tab and found out it happened due to "Process maximum size buffers" option being enabled. Disabling that fixed the stuttering.

[jackoo]

Hi, thanks very much for trying it out.

Actually, in this latest version (512) I think I've solved what I had already known from this old report here:
viewtopic.php?f=47&t=499348&p=7002032

What I hope to have decoupled is the connection between the buffer size asked by the host to be filled - and - the internal buffer size (cfg file).

The accuracy of the MIDI rendering still depends on the internal buffer size (from the cfg file) - but only on that.
The lower this buffer, the higher the MIDI accuracy.
However, if you make this internal buffer very low, there is some additional CPU hit.
This number should be a power of 2 also for CPU performance reasons.

For extreme MIDI accuracy, I would set the internal buffer to 32. Testing this, I could not tell the difference between Zyn and other plugins playing very very very fast MIDI notes. See for yourself if the CPU usage increase is negligible or not. I did not test 16 . If you don't need that kind of accuracy a value of 128 or 256 for the cfg buffer relaxes a bit the CPU.


I was a little surprised that it stutters with the FL "Process maximum buffers".
I'm not sure how FL implements that.
I don't know now if ZynFusion had the same issue *because* of this setting (or otherwise it just works fine).

Anyway, unless you see other issues, I would recommend to use default settings for buffers now in FL (processing options).



I'll also write this here once more, because it seems this is not very clear:

How to automate ZynAddSubFX?

- In the MIDI window, acquire some controls (adds them to the list)
- Instead of a CC number write the star (*) character
- Press Apply

If you check the parameters in the host, it should see now the controls in the MIDI window list, instead of the 'unused' label.

Cheers!

[jackoo]

ZynAddSubFX VST
ver. 2.4.1.515beta VST VDX version (June 14th, 2020)

- Optimize note stealing (implemented fade-out)
- Removed clicks when number of voices is close to max_voices
- Bug fix: Reduced overall latency by 1 buffer (now has zero latency when used as FX)
- updated recommended settings in cfg

ZynAddSubFX VST v2.4.1.515beta (direct link)

[Iu Gob]

Thank you!
Regards

[IsakHG]

Great vst!

[per99]

Hello jackoo,

I wonder if it matters what the sample rate is in the preference settings? I tried to change from 44.100 to 48.000, since this is the sample rate I normally use, but if I close and reopen, the 44.100 is back. Not that I can hear that this affects the sound quality, but it seems natural to use the same rate as in REAPER. So is it possible to somehow change zynaddsubfx's sample rate, or is it better to not care about it?

Cheers

[per99]

And BTW: The Zyn keeps forgetting the directories I add to favorites when loading an instrument or a xmz-file (save all paramters). If I exit REAPER and then open again, the favorites are gone. This definitely isn't a big deal, it's a matter of 10 seconds extra to get to the right folder. I just can't see why this kind of stuff works in a different way in REAPER compared to Cubase, where it worked as expected. (I didn't know about the * when doing automation. But I guess cc numbers still will do if I have my graphs within the midi-tracks? Can't try it out right now, everything's a mess.)

[jackoo]

Hello jackoo,

I wonder if it matters what the sample rate is in the preference settings? I tried to change from 44.100 to 48.000, since this is the sample rate I normally use, but if I close and reopen, the 44.100 is back. Not that I can hear that this affects the sound quality, but it seems natural to use the same rate eas in REAPER. So is it possible to somehow change zynaddsubfx's sample rate, or is it better to not care about it?

Cheers

The plugin always uses the sample rate provided by the host. Just ignore the 44.1 reading. It's probably not updated in the UI.

[per99]

The plugin always uses the sample rate provided by the host. Just ignore the 44.1 reading. It's probably not updated in the UI.

So I shouldn't manually change the .cfg file and type 48.000? (Normally I guess changed settings are reflected in the .cfg document, I mean that this is an automatic process?)

[jackoo]

No. All values for sample rate in all locations are ignored.
Host sample rate is interrogated and that will be used, even if not displayed. Completely automatic.

[jackoo]

I tried to change from 44.100 to 48.000, since this is the sample rate I normally use, but if I close and reopen, the 44.100 is back.

I decided to fix also visually the thing above.
Also, I'm posting an "experimental" update:

I noticed that doing abrupt Pitch Bends, or when sweeping the cutoff frequency via Midi CC, the performance is not so good. So I tried to add some interpolation at the cost of a little latency when sending PB and midi CCs.

So here it is:

==> ZynAddSubFX VST v2.4.1.517beta

- Attempted to make PitchBend and CC transitions via Midi (esp. cutoff freq) smoother by adding some intermediate points to the "staircase" input.
Try to assign a controller CC to the global filter cutoff frequency. The control should be smoother.

- Added cfg option "cc_latency" in milliseconds, for smoothing purposes.
Set this to 1 to have the same behavior as in a previous release
Recommended value: 52ms
- Settings window now correctly displays host sample rate


I did my own tests, but If anyone could test this, I'd be really grateful.
There should be an noticeable improvement, though not really perfect due to other architectural limitations.
Cheers!

[per99]

So I tried to add some interpolation at the cost of a little latency when sending PB and midi CCs /.../ Recommended value: 52ms.

Yeah, sooner och later I'm gonna try this out. But 52 milliseconds latency, thats 0.052 seconds. Rather much, but what does it mean in this context? Does the whole tone get delayed with 52 milliseconds extra, when you use midi automation (to controll cutoff frequency)? But if you dont't use PB or midi CC:s, then it's the ordinary latency?

And if you export/render - then you normally don't have to care about latency - right?