JNA Native & MediaInfo errors...

[ZeroByDivide]

Dunno really how long this has been going on for to be honest but I just noticed it today while running a sysinfo for filebot to check some stuff..

Code: Select all

FileBot 4.7.5 (r4649)
JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll) not found in resource path ([file:/C:/Users/JourneyOver/Dropbox/Public/Folders/Filebot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load amd64 (64-bit) native library MediaInfo.dll: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: 9.20
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_111
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 6 Core / 1 GB Max Memory / 15 MB Used Memory
OS: Windows 10 (amd64)
Package: PORTABLE
Data: C:\Users\JourneyOver\Dropbox\Public\Folders\Filebot
Done ヾ(＠⌒ー⌒＠)ノ

notably these are the two errors that seem to be popping up

Code: Select all

JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86-64/jnidispatch.dll) not found in resource path ([file:/C:/Users/JourneyOver/Dropbox/Public/Folders/Filebot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load amd64 (64-bit) native library MediaInfo.dll: Could not initialize class com.sun.jna.Native

and then in the normal logs that filebot produces whenever it does it's processing stuff --

Code: Select all

{duration} => Expression yields empty value: Binding "duration": Native library (com/sun/jna/win32-x86-64/jnidispatch.dll) not found in resource path ([file:/C:/Users/JourneyOver/Dropbox/Public/Folders/Filebot/FileBot.jar])

Running the latest version of java 64 bit, running the portable version of filebot and using the 64 bit versions of MediaInfo and 7-Zip native libraries.
http://i.imgur.com/CpYYpdu.png

have uninstalled and re-installed java and deleted and brought back the portable version of filebot already as a measure to see if either of them was a problem or not.
everything seems to work just fine regardless other than just those errors.

[rednoah]

You may be missing the correct jnidispatch.dll native library:
https://github.com/filebot/filebot/tree ... /win32-x64

Older revisions of FileBot accidentally packaged jnidispatch.dll for all platforms in the jar, which is no longer the case in the latest revision.

The startup config may need to be adjusted as well, to make sure jnidispatch.dll is loaded from the portable application folder.

GUI config:
https://github.com/filebot/filebot/blob ... ot.l4j.ini

CLI config:
https://github.com/filebot/filebot/blob ... ilebot.cmd

[ZeroByDivide]

You may be missing the correct jnidispatch.dll native library:
https://github.com/filebot/filebot/tree ... /win32-x64

Older revisions of FileBot accidentally packaged jnidispatch.dll for all platforms in the jar, which is no longer the case in the latest revision.

The startup config may need to be adjusted as well, to make sure jnidispatch.dll is loaded from the portable application folder.

GUI config:
https://github.com/filebot/filebot/blob ... ot.l4j.ini

CLI config:
https://github.com/filebot/filebot/blob ... ilebot.cmd

Ah it was to do with the startup config I believe, was super out of date compared to the two above, so I replaced both [and well just redid the whole filebot folder as well] and it stopped erroring out

Code: Select all

FileBot 4.7.5 (r4649)
JNA Native: 4.0.1
MediaInfo: 0.7.88
7-Zip-JBinding: 9.20
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_112
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 6 Core / 1 GB Max Memory / 24 MB Used Memory
OS: Windows 10 (amd64)
Package: PORTABLE
Data: C:\Users\JourneyOver\Dropbox\Public\Folders\Filebot\data
Done ヾ(＠⌒ー⌒＠)ノ

[rednoah]

Yeah, sorry, most of the time it's only the code that changes, but occasionally I may need to change the startup config as well.

[ZeroByDivide]

It's all good, least this was a quick and easy fix