Sylenth1 v3.02 font problem
-
- KVRist
- 40 posts since 7 Apr, 2016
The new version of Sylenth1, v 3.021, 64-bit, Windows version does not work properly in Studio One v 3.2 on Windows 10: I can not read any menus as shown in the attached screengrab.
Sylenth1 version 3 works in Reaper though, so maybe this is a bug in Studio One?
Still, I had no problem with Sylenth1 *version 2* in Studio One...
Sylenth1 version 3 works in Reaper though, so maybe this is a bug in Studio One?
Still, I had no problem with Sylenth1 *version 2* in Studio One...
You do not have the required permissions to view the files attached to this post.
-
- KVRian
- 1330 posts since 25 Sep, 2006
This is caused by a bug in Sylenth1 v3.021 in combination with Windows 10. We're already working on a fix. Please use Sylenth1 v3.020 instead until the problem is fixed. You can contact us here if you don't have the download link for that version.
-
- KVRist
- 138 posts since 16 May, 2007
Lennard, I have emailed you about a Psylenth1 bank im working on also? it has allot of old and new sounds in it aswell, could you possibly email me back about this?
DJBenniboy - (Soundcloud) http://www.soundcloud.com/benniboyproductions 
(Youtube) - http://www.youtube.com/DJBenniboyOfficial
(Twitter)
@djbenniboy
check my patches out @ www.u-he.com/PatchLib/zebra.html
(Youtube) - http://www.youtube.com/DJBenniboyOfficial
(Twitter)
@djbenniboy
check my patches out @ www.u-he.com/PatchLib/zebra.html
-
- KVRist
- Topic Starter
- 40 posts since 7 Apr, 2016
-
- KVRist
- Topic Starter
- 40 posts since 7 Apr, 2016
I have to correct myself. It seems like it was only working temporarily. Today the problem reappeared with v3.020. I was told by Presonus support to turn off high dpi mode and that workaround works. I don't know if this is a bug in Studio One or in Sylenth1.
-
- KVRian
- 1330 posts since 25 Sep, 2006
Are you sure the problem appeared in v3.020 on the popup menu's? Or did the problem appear somewhere else, on a messagebox for example?svenh wrote:I have to correct myself. It seems like it was only working temporarily. Today the problem reappeared with v3.020. I was told by Presonus support to turn off high dpi mode and that workaround works. I don't know if this is a bug in Studio One or in Sylenth1.
Because v3.021 is using a different method to render the text on the popup menu's, which is causing the bug. So I'd say it's nearly impossible that it occured in the popupmenu's of v3.020.
-
- KVRist
- Topic Starter
- 40 posts since 7 Apr, 2016
Maybe you are right, since I can not reproduce the problem now. If the problem reappear with v3.020, I will be quick to make a screendump including the version number before it disappears again 
Anyway, overall very happy with the update! I love that I can resize the GUI for my big monitor. And I love that the integration with Nektar Panorama now is EVEN BETTER than before! And the sound is of course still great!
All the best,
Sven
Anyway, overall very happy with the update! I love that I can resize the GUI for my big monitor. And I love that the integration with Nektar Panorama now is EVEN BETTER than before! And the sound is of course still great!
All the best,
Sven
-
twolegstoneworks twolegstoneworks https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7585
- KVRian
- 1426 posts since 12 Jun, 2003 from Denmark
It's an issue with Cubase 8.5 as well..
-
- KVRian
- 1330 posts since 25 Sep, 2006
-
- KVRist
- 460 posts since 14 Mar, 2004 from Colorado, USA
Lennard, I guess I bought Sylenth after 3.021 came out and the only download I have available in my customer area is the 3.021 dated 4/6/2016. How can I download 3.020 to workaround until the fix is released?
Core i9-7940X | Asus Prime X299-A | 64GB DDR4-3200 | Samsung 950 Pro 2TB Sys, 860 Evo 4TB Data | Steinberg UR824 & CC121 | Virus TI Desktop | Roli Seabord Rise 2 | Nektar Panorama P6 | Nektar Aura | Roland VG-99 | Win10 Pro x64 | Cubase Pro 12
-
- KVRAF
- 15135 posts since 7 Sep, 2008
Omniphonix wrote:Lennard, I guess I bought Sylenth after 3.021 came out and the only download I have available in my customer area is the 3.021 dated 4/6/2016. How can I download 3.020 to workaround until the fix is released?
Lennard wrote:This is caused by a bug in Sylenth1 v3.021 in combination with Windows 10. We're already working on a fix. Please use Sylenth1 v3.020 instead until the problem is fixed. You can contact us here if you don't have the download link for that version.
"I was wondering if you'd like to try Magic Mushrooms"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"
"Oooh I dont know. Sounds a bit scary"
"It's not scary. You just lose a sense of who you are and all that sh!t"
-
- KVRist
- 460 posts since 14 Mar, 2004 from Colorado, USA
I am still having this problem with Sylenth1 3.020 (DLL dated 4/4/2016). I did a complete deactivate, uninstall, install older version, reactivate process when deleting the DLL and then running the older installer didn't work. It still has the issue with menu text...


Core i9-7940X | Asus Prime X299-A | 64GB DDR4-3200 | Samsung 950 Pro 2TB Sys, 860 Evo 4TB Data | Steinberg UR824 & CC121 | Virus TI Desktop | Roli Seabord Rise 2 | Nektar Panorama P6 | Nektar Aura | Roland VG-99 | Win10 Pro x64 | Cubase Pro 12
-
- KVRian
- 1330 posts since 25 Sep, 2006
-
- KVRist
- 460 posts since 14 Mar, 2004 from Colorado, USA
It's strange, after booting up and trying again today (having made no changes), I can't reproduce the issue. Anyway, will you post here when an update to 3.021 is released that fixes this issue?Lennard wrote:Can you please click MENU -> About in Sylenth1 to doublecheck that that is actually the same version that is being loade (v3.020)?
Core i9-7940X | Asus Prime X299-A | 64GB DDR4-3200 | Samsung 950 Pro 2TB Sys, 860 Evo 4TB Data | Steinberg UR824 & CC121 | Virus TI Desktop | Roli Seabord Rise 2 | Nektar Panorama P6 | Nektar Aura | Roland VG-99 | Win10 Pro x64 | Cubase Pro 12
- KVRAF
- 5913 posts since 17 Aug, 2004 from Berlin, Germany
I can confirm that this problem is also with 3.0.20 but only under some circumstances I cannot reproduce. Actually I've started a new project and this font bug is gone (hopefully)
Maybe the problem is more often with 3.0.21 and that's why we have seen it after a short time of testing.
Maybe the problem is more often with 3.0.21 and that's why we have seen it after a short time of testing.
| Links
