A couple of my patches sounded different once I ugraded to Sylenth 2.0. What I discovered is that this was due to the new version of sylenth thinking the notes were overlapping each other when in reality they were painted as whole notes in sonar in the paino roll view. If I took the note back one tick then sylenth saw them as not overlapping and the beahvior was as in sylenth 1.
Not sure why this is happeining. I am thinking that the new version is reading the notes as overlapping when it should not.
Heads up for other sonar users.
Good news is all stuttering problems are gone except for one stutter when starting a song with Sonar 7. After that I do not get any stutters at all on my projects.
This is a great synth! Period.
Lance
Sylenth 2.0 and Sonar 7
-
- KVRer
- 21 posts since 3 Feb, 2006
-
- KVRian
- 1330 posts since 25 Sep, 2006
I've tried this, but it works just fine here. Notes snapped to the grid will not overlap. Same goes for other hosts.stoutlyric wrote:A couple of my patches sounded different once I ugraded to Sylenth 2.0. What I discovered is that this was due to the new version of sylenth thinking the notes were overlapping each other when in reality they were painted as whole notes in sonar in the paino roll view. If I took the note back one tick then sylenth saw them as not overlapping and the beahvior was as in sylenth 1.
Any specific preset this happens to maybe? Have you tried the same presets in a new empty project? And what exactly makes you think they overlap? Does the portamento kick in while it's set to Normal mode (and not Slide mode)?
-
Oliver Schmitt Oliver Schmitt https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=109283
- KVRist
- 306 posts since 2 Jun, 2006 from Germany
what a great sounding vst synth.... one of the best u can get....
go ahead lennar - great job !
greets,
olli
go ahead lennar - great job !
greets,
olli
SOR Ultimate Bundle updated!
https://www.sounds-of-revolution.com/po ... te-bundle/
https://www.sounds-of-revolution.com/po ... te-bundle/
-
- KVRer
- Topic Starter
- 21 posts since 3 Feb, 2006
The first note has these properties in Sonar:
Time - 11:01:000
Duration - 1:000
The second Note has these:
Time - 11:02:000
Duration - 1:000
If the duration of the first note is changed to 959 then the patch sounds like Sylenth 1 original version.
After more research this is what I found:
The LFO1 (triangle) is modulating Cutoff AB on the second note differently (slower rise)on the second note than the first. I thought it was overlapping notes because ticking the note back to 959 fixed this? Portamento is set to 0 and it does not matter what mode you are in "N" or "S" the behavior is the same.
I tried saving the patch in a brand new project and got the same result.
Your help is very appreciated. Thanks.
Time - 11:01:000
Duration - 1:000
The second Note has these:
Time - 11:02:000
Duration - 1:000
If the duration of the first note is changed to 959 then the patch sounds like Sylenth 1 original version.
After more research this is what I found:
The LFO1 (triangle) is modulating Cutoff AB on the second note differently (slower rise)on the second note than the first. I thought it was overlapping notes because ticking the note back to 959 fixed this? Portamento is set to 0 and it does not matter what mode you are in "N" or "S" the behavior is the same.
I tried saving the patch in a brand new project and got the same result.
Your help is very appreciated. Thanks.
-
- KVRian
- 1330 posts since 25 Sep, 2006
Is the LFO running in Free mode maybe? In that case it will not be retriggered at all. The preset may sound different than in v1.21, because the LFO free mode is tempo-independent in v2.0 (it wasn't before!). If you need the LFO synced, you should turn Free mode off, or adjust the rate manually.stoutlyric wrote:After more research this is what I found:
The LFO1 (triangle) is modulating Cutoff AB on the second note differently (slower rise)on the second note than the first. I thought it was overlapping notes because ticking the note back to 959 fixed this? Portamento is set to 0 and it does not matter what mode you are in "N" or "S" the behavior is the same.
If that doesn't solve the problem, please send me the problematic patch and I'll have a closer look.

