Hi,
So I had to open an old project from 2013, on my macbook pro..
It had some instances of Sylenth in it, but I notice some of them, from PluginGuru Bank were not sounding, when I looked at the interface, their oscillator volumes were at Zero..
Clearly they weren't at Zero when I used them in 2013...
Has this happened to anyone else with any patches?
Sylenth 3.073, Apple Mac Silicon 26.4.1, Cubendo 15.
https://www.dropbox.com/scl/fi/iyo1x6od ... jiv7t&dl=0
https://www.pluginguru.com/products/malicious-sylenth/
rsp
Some of my older patches no longer sound
-
- KVRian
- 1329 posts since 25 Sep, 2006
Try using the v2 engine:
Click MENU -> Open Data Folder, browse to Config and open Settings.xml with a text editor. Change the value useV2Engine to 1:
<Compatibility useV2Engine="1" displayCutoffInHz="0"/>
Then save and restart Sylenth1 and see if that helps. The v3 engine has some slight differences that could make it sound differently in some specific cases or even mute the sound if it uses negative volume modulation.
Click MENU -> Open Data Folder, browse to Config and open Settings.xml with a text editor. Change the value useV2Engine to 1:
<Compatibility useV2Engine="1" displayCutoffInHz="0"/>
Then save and restart Sylenth1 and see if that helps. The v3 engine has some slight differences that could make it sound differently in some specific cases or even mute the sound if it uses negative volume modulation.
-
- KVRAF
- Topic Starter
- 14435 posts since 16 Feb, 2005 from Planet Earth, Somewhere
That indeed does work...
What are the advantages of using the v3 engine on the whole?
rsp
edit:
I guess these:
Any quick ideas how to edit the patches so they sound the same way in the v3 engine?
rsp
What are the advantages of using the v3 engine on the whole?
rsp
edit:
I guess these:
26 March 2019
For this update we have revisited the audio engine and managed to improve overall sound quality of the oscillators and filters, without losing their cutting edge. We’ve also further optimized the code, so that it’s still as lean on the CPU as it was before! Optional oversampling for realtime playback and offline render modes have been added to the Settings file. A swing knob was added to the arpeggiator, a new skin by Scott Kane was included and several new presets were added, as well as many other improvements and bug fixes. This version is also fully compatible with Retina displays!
What's new in this version:
Improved oscillator sound quality (improved high frequency content, reduced aliasing).
Improved filter response and sound quality.
Further optimized CPU performance.
Added oversampling options for realtime playback and render mode.
Added Arpeggiator Swing knob.
Added master tuning frequency adjustment.
Improved pitch accuracy.
Added Nitro skin by Scott Kane.
Improved host automation for buttons and option controls.
Fixes compatibility issue on Linux.
Fixes high memory bug in 32bit version.
Fixes aupreset loading issue.
Added midi learn autoswitch control option.
Added 156 new presets to FactoryBank6.
Fixes offline installation bug on Windows.
Fixes problem with installation through script on Mac.
Added parameter highlighting for AAX version.
Added AAX page tables for Avid control surfaces.
Now fully compatible with Retina displays.
Added option to link AmpEnv A and B parameters.
Added locking options for all parameters and parts.
Any quick ideas how to edit the patches so they sound the same way in the v3 engine?
rsp
sound sculptist
-
- KVRAF
- Topic Starter
- 14435 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Though that work around is causing cubendo 15 to freeze when I go to a specific patch in that bank..(PAD Lost in the Light)
rsp
rsp
sound sculptist
-
- KVRian
- 1329 posts since 25 Sep, 2006
Ah right, there's a bug in v3.073 in the noise osc in the v2engine. It's fixed in v3.075 which should be available for Mac as well soon.
The v3 engine has a better overall sound quality and fixes some minor issues. If presets are using weird or randomized modulation values, the sound could mute if the volume modulation drops below zero. So try replacing those by positive modulation values and it should sound pretty much the same.
The v3 engine has a better overall sound quality and fixes some minor issues. If presets are using weird or randomized modulation values, the sound could mute if the volume modulation drops below zero. So try replacing those by positive modulation values and it should sound pretty much the same.
-
- KVRAF
- Topic Starter
- 14435 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Hi, It was actually the opposite.. the LFO was set to modulate AB Volume at 10, but the A and B volume were at zero... anyway setting LFO modulate to -10 works, and I am good again.
PS this synth really sounds good still in 2026.
thanks
rsp
PS this synth really sounds good still in 2026.
thanks
rsp
sound sculptist
-
- KVRian
- 1329 posts since 25 Sep, 2006
Interesting, could you maybe send that preset via email to support at lennardigital.com?
-
- KVRian
- 1329 posts since 25 Sep, 2006
Thanks. What's causing this is the same thing for both presets: The LFO offset is set to -10, which means the volume will modulate between -10 and 0 and never reach above 0, so indeed the output will be muted.
To fix this, just set the destination amount to -10 (as you did) to get the original sound, or set the LFO offset to +10 for regular polarity.
To fix this, just set the destination amount to -10 (as you did) to get the original sound, or set the LFO offset to +10 for regular polarity.
-
- KVRian
- 1329 posts since 25 Sep, 2006
In v2 the osc inverses the wave amplitude at negative volume, in v3 it will mute negative volume.
-
- KVRAF
- Topic Starter
- 14435 posts since 16 Feb, 2005 from Planet Earth, Somewhere
Got ya.. thanksLennard wrote: Wed May 06, 2026 2:07 pm In v2 the osc inverses the wave amplitude at negative volume, in v3 it will mute negative volume.
rsp
sound sculptist