"instructions for using FXbench with VS10. The following info comes via email directly from the developer, Stefan Burger:
I just tested FXbench with the trial version of VideoStudio 10 and it works perfectly. The reason why the message �0 compatible Ulead product found� appears might be because you installed VS 10 not to the default directory. Usual the installation path of VS is like... C:\Programme\Ulead Systems\Ulead VideoStudio 10\vft_plug ...while 禅rogramme� is localized and can be different like 萪rogram Files�. However, the installer scans the path c:\\Ulead Systems for all subfolder with the name vft_plug and installs a copy of Fxbench.vft to them. If your installation path of VS 10 is totally different (maybe even on a different drive) this procedure will fail and you have to copy the Fxbench.vft file manually from your Fxbench installation folder to the vft_plug folder of your VS 10 installation. But this behaviour is not specific for VS 10, but is valid for all versions of VS. Regards, Stefan"
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2009-03-05 04:23 am (UTC)I just tested FXbench with the trial version of VideoStudio 10 and it works perfectly. The reason why the message �0 compatible Ulead product found� appears might be because you installed VS 10 not to the default directory. Usual the installation path of VS is like... C:\Programme\Ulead Systems\Ulead VideoStudio 10\vft_plug ...while 禅rogramme� is localized and can be different like 萪rogram Files�. However, the installer scans the path c:\\Ulead Systems for all subfolder with the name vft_plug and installs a copy of Fxbench.vft to them. If your installation path of VS 10 is totally different (maybe even on a different drive) this procedure will fail and you have to copy the Fxbench.vft file manually from your Fxbench installation folder to the vft_plug folder of your VS 10 installation. But this behaviour is not specific for VS 10, but is valid for all versions of VS.
Regards, Stefan"