Speaking personally, I’m still predominantly using a bunch of classic old 32-bit VSTs that I simply cannot live without.
I cannot fix anything with the old Glitch 1.3, but maybe your feedback will help to reveal some other potential issue(s). I can tell you that Glitch 1.3.05 is working just fine for me as a bridged 32-bit -> 64-bit plugin within Renoise.Īs said, it would be great to know exactly what doesn’t work here for you, and what exactly happens when you try to use it. I’m running Renoise 3.2.1 here on Windows 10 Home edition (fully up to date, blah blah blah). For Mac I don’t know what problems there are. But it does not, supposedly because of the operating system. However, despite all this, Renoise 3.2 still supports 32bit plugins. It is desirable that any 32bit development disappear in the not too distant future, and all software programmers focus only on 64bit and move on. Renoise 3.2 is like a transition version. But serious programmers must focus on 64bit and abandon 32bit development at once. It is tragic to abandon some 32bit plugins. If so, be sure to name the operating system and the names and versions of the 32bit plugins. This is a known issue between Renoise and Windows 10, and supposedly, it is waiting for some solution.īut all of the above does not imply that you cannot load 32bit plugins.
Any additional window display while using the 32-bit window of any plugin will cause considerable delays in the Renoise GUI (pattern editor, main menu). Renoise 3.2.0 / 3.2.1 experiences performance problems when loading 32bit plugins. You should only disable scaling in the properties of the plugin ( Button). If you have any problems with 64bit add-ons, it will surely be due to automatic scaling. If you have 64bit add-ons, they should all work without problems. The main change of Renoise 3.2.0 / 3.2.1 is the GUI scaling.
0 kommentar(er)
