binding no longer works
binding no longer works
I've had filebot installed for quite some time with the naming schemes set up. I decided to install androidsdk and it installed the jdk64 and jre64 versions and now filebot no longer names. I tried uninstalling both jdk and jre and repairing the 32bit version but its still not working. Any tips on how to fix this or to see what the problem is.
Re: binding no longer works
Call 'filebot' from cmdline and see if there is any error messages.
Re: binding no longer works
filebot opened ok but I caught this command in the faqs
filebot -script fn:sysinfo
Attached the screenshot to see if it helps any
filebot -script fn:sysinfo
Attached the screenshot to see if it helps any
Re: binding no longer works
How come you got 32-bit FileBot? The installer should automatically install 64-bit.
The output looks good. Have you tried starting FileBot via the FileBot (platform) launcher?
The output looks good. Have you tried starting FileBot via the FileBot (platform) launcher?
Re: binding no longer works
i have the 32bit because when I had the 64bit installed i had jre32 installed so it was easier to just keep filebot at 32..... not anymore. Same error with filebot(platform). I'll uninstall everything 32 and put 64 on to see if I get better results. Thanks for the quick replies.
Re: binding no longer works
Just run 'filebot' in cmd, that'll start the GUI and you still see any error output in the cmdline window.
Re: binding no longer works
thanks. the problem ended up being something stupid. Installed 64 everything and still had the error. Turns out the binding error was because I didn't choose a media file in format for the binding. It was still set to the serenity sample string. All is well nowrednoah wrote:Just run 'filebot' in cmd, that'll start the GUI and you still see any error output in the cmdline window.