FileBot

I have traditionally run Filebot x64 because that is what gets installed, however I wanted to take advantage of some of the bindings gathered using media info. I use Java x86 because I use Firefox x86 because some sites have problems with x64 browsers. I'd rather go x64 for everything, but that isn't going to happen anytime soon.

So, after reading several posts about why I couldn't access the bindings I found that it was because I was mixing my x86 and x64 environment. So I uninstalled Filebot 4.5 x64.

btw: The uninstall leaves behind a folder in my appdata\roaming folder, and the path environment is left with the path to filebot.

After cleaning up I rebooted.

I then downloaded the filebot x86 installer and installed it.

From that point on I can no longer use AVCHDCODER. I cannot drag/drop files into it, or manually add files.

So I uninstalled AVCHDCODER and associated tools and reloaded it. No go.

So I reinstalled windows from scratch. Installing AVCHDCODER first (I also use DVDFAB, Handbrake, AVStoDVD and tsMuxer). Then installed Filebot x86 clean (without having installed x64 version). Same problem.

I'd really prefer not to reload Windows again, it's very time consuming.

How do I get filebot x86 to happily coexist with AVCHDCoder?

btw: My java is 1.8u25 x86. Firefox is v31 x86, AVCHDCoder is using all x86 tools.

thanks

1.
Just install 64-bit Java in addition to the 32-bit one.

2.
I don't know AVCHDCODER. If you figure out what the problem is you can probably make them coexist. It's just files on a disk after all.


EDIT:

AVCHDCODER is a Java application so I suppose it might be using JNA, and erroneously loading native libraries from the FileBot install folder.

@see http://www.filebot.net/forums/viewtopic.php?f=8&t=1438

This is primarily a bug in AVCHDCODER but you can probably get around that by removing FileBot from the PATH.

Hi, thanks for your reply

1. Why would I want to install 64bit java? As much as I'd prefer to run x64 for everything, I'm trying to avoid a mixed mode environment because it just causes so many problems with so many things?

2. Removing the path seems to have worked. It took 3 tries to get rid of it (Took it out via regedit, but it kept getting added back in after a reboot, until the third try when it stayed deleted).

thanks for your help.

Tanya