I consider myself fairly PC literate but I just can't seem to get FXBench to install for me where I can use it with VideoStudio9.
I received this message when I installed FXBench: (0 compatible Ulead products found).
I presume this is indicating my problem but I haven't been able to figure-out how to get FXBench to recognize my VideoStudio9.
I like to install my utilities (including VideoStudio & FXBench) into a Utilities folder on my "D" drive rather than the usual C:\Program Files folder. I've tried installing FXBench into its own folder and into the VideoStudio folder and neither of these attempts worked.
Does anybody have any suggestions?
Many Thanks!
Paul
Installing FXBench
Moderator: Ken Berry
- Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
Hi Paul, welcome to the forums..
After reading your post I inspected my own install of VS9, and found that I no longer had FX Bench or Burger's Transistions. I had to do a re-install of VS9 awhile back, so they were no longer available to me.
So what I just completed was a re-install of both. I uninstalled both FX Bench and Burgers Transistions via the Control Panel>Add/Remove Programs. Then reinstalled them. I just used the default install directories, and both recognized all 6 of my Ulead programs.
Just a suggestion, as you don't mention if you tried to reinstall and use the default setting. You might try letting them install to the default and see if they will recoginze or find your Ulead program. It may be that FX Bench just looks in the C:\Program Files directory for the Ulead Apps, and since you have VS installed to D: it may not be finding it there.
Ron P.
After reading your post I inspected my own install of VS9, and found that I no longer had FX Bench or Burger's Transistions. I had to do a re-install of VS9 awhile back, so they were no longer available to me.
So what I just completed was a re-install of both. I uninstalled both FX Bench and Burgers Transistions via the Control Panel>Add/Remove Programs. Then reinstalled them. I just used the default install directories, and both recognized all 6 of my Ulead programs.
Just a suggestion, as you don't mention if you tried to reinstall and use the default setting. You might try letting them install to the default and see if they will recoginze or find your Ulead program. It may be that FX Bench just looks in the C:\Program Files directory for the Ulead Apps, and since you have VS installed to D: it may not be finding it there.
Ron P.
Ron Petersen, Web Board Administrator
-
paulnapaca
Installing FXBench
Hi Ron:
First, a big THANK YOU for your response and help!
Apparently, FXBench is hard-coded to only look for VideoStudio in the C:\Program Files directory. This time the FXBench installation recognized that VideoStudio was installed.
Now, I find myself needing to trouble you for just a little further assistance. Unfortunately, there does not seem to be a FXBench manual to help me with this and the only postings I can find relating to FXBench were some old postings that you did which do not address this particular problem. In other words, I have truly tried looking around (e.g. web searches, Burger-FXBench website, etc.) for answers to this before troubling you again.
When I am in VideoStudio, I can find an icon for FXBench under the VideoFilters but that is all there is. I was expecting to see a list of the filters that FXBench has available. I've looked at Library Manager but there isn't anything in there that I can see.
Do I have to have FXBench up and running while I am in VideoStudio? How do I get VideoStudio to recognize the list of FXBench filters?
Thanks, once again, for your help!
Paul
First, a big THANK YOU for your response and help!
Apparently, FXBench is hard-coded to only look for VideoStudio in the C:\Program Files directory. This time the FXBench installation recognized that VideoStudio was installed.
Now, I find myself needing to trouble you for just a little further assistance. Unfortunately, there does not seem to be a FXBench manual to help me with this and the only postings I can find relating to FXBench were some old postings that you did which do not address this particular problem. In other words, I have truly tried looking around (e.g. web searches, Burger-FXBench website, etc.) for answers to this before troubling you again.
When I am in VideoStudio, I can find an icon for FXBench under the VideoFilters but that is all there is. I was expecting to see a list of the filters that FXBench has available. I've looked at Library Manager but there isn't anything in there that I can see.
Do I have to have FXBench up and running while I am in VideoStudio? How do I get VideoStudio to recognize the list of FXBench filters?
Thanks, once again, for your help!
Paul
- Ron P.
- Advisor
- Posts: 12002
- Joined: Tue May 10, 2005 12:45 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Hewlett-Packard 2AF3 1.0
- processor: 3.40 gigahertz Intel Core i7-4770
- ram: 16GB
- Video Card: NVIDIA GeForce GTX 645
- sound_card: NVIDIA High Definition Audio
- Hard_Drive_Capacity: 4TB
- Monitor/Display Make & Model: 1-HP 27" IPS, 1-Sanyo 21" TV/Monitor
- Corel programs: VS5,8.9,10-X5,PSP9-X8,CDGS-9,X4,Painter
- Location: Kansas, USA
- michaeltee
- Posts: 528
- Joined: Wed Aug 17, 2005 5:19 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: HP 82F1
- processor: Intel Core I5 7400 3 GHz
- ram: 16 GB DC
- Video Card: Intel HD Graphics 630
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 2TB Hybrid
- Monitor/Display Make & Model: Samsung S24D300
- Corel programs: Installed: PS Pro 2021, VS Ultimate 2020
- Location: California, USA
Hi All,
I thought I would post the 'official' 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 “Programme” is localized and can be different like ‘Program Files”. However, the installer scans the path c:\<default_programm_folder>\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
I thought I would post the 'official' 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 “Programme” is localized and can be different like ‘Program Files”. However, the installer scans the path c:\<default_programm_folder>\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
