I have installed both the Filebot and Filebot Node applications on my Synology DS718+. I have also installed the Java Installer app, as well as the Node JS v4 app. When I run the System Info on the Filebot Node app I get the following error:
filebot -script 'fn:sysinfo'
------------------------------------------
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v7.Java7$1 (file:/volume1/@appstore/filebot/jar/groovy.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class,int)
WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v7.Java7$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
BUG! exception in phase 'semantic analysis' in source unit 'Script1.groovy' Unsupported class file major version 57
BUG! exception in phase 'semantic analysis' in source unit 'Script1.groovy' Unsupported class file major version 57
at net.filebot.cli.ScriptShell.evaluate(ScriptShell.java:64)
at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:74)
at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:163)
at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:37)
at net.filebot.Main.main(Main.java:132)
Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 57
at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:184)
at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:166)
at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:152)
at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:273)
... 5 more
Error (o_O)
------------------------------------------
[Process error]
This makes me think Java is not installed, yet your Java Installer app should have taken care of this?
Please read Optional Features in the Synology Installation Guide: viewtopic.php?t=1802
The SPK package does package generic libmediainfo builds, but those may not always be compatible with your specific platform, so it's best to install MediaInfo via packages for your specific Synology platform.
You can also forward the issue to Synology Support to see if they can improve compatibility with generic Linux binaries.