i need your help.
I'am on NAS synology DS 1817 with 8Go RAM ( it's a 32bits processor).
when i try to run filebot i have this error :
here is an example :
Code: Select all
Failed to read media characteristics: ExecuteException: [/volume1/@appstore/MediaServer/bin/ffprobe, -show_streams, -show_format, -print_format, json, -v, error, /volume1/Torrent/[ OxTorrent.com ] Batwoman.S01E01.SUBFRENCH.WEBRip.XviD-EXTREME.avi] failed (1)
Code: Select all
FileBot 4.9.0 (r7026)
JNA Native: 6.1.0
MediaInfo: 19.04
p7zip: p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
unrar: UNRAR 5.21 freeware
Chromaprint: 1.4.3
Extended Attributes: OK
Unicode Filesystem: OK
Script Bundle: 2019-12-07 (r610)
Groovy: 2.5.8
JRE: OpenJDK Runtime Environment 13.0.1-BellSoft
JVM: 32-bit OpenJDK Client VM
CPU/MEM: 4 Core / 259 MB Max Memory / 22 MB Used Memory
OS: Linux (arm)
HW: Linux XXXXX 3.10.105 #24922 SMP Tue Jul 9 18:27:19 CST 2019 armv7l GNU/Linux synology_alpine_ds1817
STORAGE: ext4 [/] @ 1.4 GB | ext4 [/volume1] @ 11 TB | ext4 [/opt] @ 11 TB
DATA: /volume1/@appstore/filebot/data/root
Package: SPK
License: FileBot License XXXXX (Valid-Until: 2020-11-06)
Done ヾ(@⌒ー⌒@)ノ

 What does the complete console output say? This is just a warning. If something else is not working, then it's most likely unrelated. Is there anything in particular that isn't working? Is FileBot not processing files correctly?
 What does the complete console output say? This is just a warning. If something else is not working, then it's most likely unrelated. Is there anything in particular that isn't working? Is FileBot not processing files correctly? On Synology NAS, FileBot is configured to use ffprobe to read basic media properties. Nice to have. But not strictly necessary information. FileBot will work fine without. Presumably, this particular file is corrupt, and so ffprobe can't parse it and fails.
 On Synology NAS, FileBot is configured to use ffprobe to read basic media properties. Nice to have. But not strictly necessary information. FileBot will work fine without. Presumably, this particular file is corrupt, and so ffprobe can't parse it and fails. 
 