You can place your slogan here.
This would also be a great spot for a top product pitch.
Some VST effects won't run on SynthFont
Some VST effects (or instruments) may display error messages like these when you try to use them in versions of SynthFont later than 1.557.
and other tools for Midi and SoundFonts
These messages are not originated in SynthFont, but in the DLL library of the VST. The reason for this behavior is as follows: Many VST effects/instruments are created using the SynthEdit tool. SynthEdit has a major flaw: when the effect is initiated it wants to save a number of module files in a subfolder to the folder where the effect is situated (usually the "C:\Program Files\VSTPlugins" folder), and on Windows 7 this folder ("C:\Program Files (x86)\VSTPlugins") is normally protected. Nothing can be written there without administrator rights. What probably happens is that the modules are written into a hidden virtual folder (see image below), but the effect can't find them there.
A VirtualStore is a place where Windows stores data files that programs create while running and try to write into any "Program Files" folder, which is strictly forbidden on Windows 7. Thus the files are written into a VirtualStore folder in the users local folder:
Windows 7 treats the VirtualStore folders differently from how Vista does. Thus the problem does not always appear on Vista computers.
For some odd reason, all versions of SynthFont since 1.558 will not allow loaded DLL libraries access to virtual folders. Version 1.558 was the first to be compiled with a newer Delphi compiler, version 11 (2007), while version 1.600 was the first to be compiled with the even newer Delphi version 14 (2010) compiler, but the issue still remains.
There are two solutions to this problems and the first one is to take ownership of the VST folder.
The first - and recommended - solution is the start by downloading the file TakeOwnership.zip (originally from How-To Geek). Just unzip and run the InstallTakeOwnership.reg file to add a right-click menu item to the Explorer menu. Explore your way to the VST folder (e.g. The C:\Program Files (x86)\VSTPlugins folder), and right click on it. Select "Take Ownership". After that, SynthFont should work as before.
The second approach is this: Download the file VSTDummyHost.exe. Run the program and open the VST file you want to use. The program will not do anything more than let the VST effect dump its modules, either into the VirtualStore folder as above or into the VSTPlugins folder. If you find them in the VirtualStore, then copy the folder into the VSTPlugins folder (you may need administrator rights to do that). That's it for this particular VST effect! But you need to repeat this for all your effects that have this problem! Therefore the preferred solution is to take ownership, as describe above.