I would be interested in this as well

You’re not running the latest build. You might need to uninstall and then reinstall FileBot to make sure you’re running the latest build. Is that for Filebot Node, Filebot or both? /Edit: All good now 8-) Just a FYI for others, you don't need to uninstall and reinstall on a Synology. I just downloa...

Heya, I had installed the license on my Synology just over a week ago and all was good but now I'm getting: No such property: license for class: Script1 groovy.lang.MissingPropertyException: No such property: license for class: Script1 at Script1.run(Script1.groovy:14) at net.filebot.cli.ScriptShell...

plittlefield wrote: ↑20 Jul 2018, 16:33 OK, I am ready to buy the annual licence... where do I go?

https://www.filebot.net/purchase.html

I've been using Filebot for a while now, donated beer money to @rednoah for his help on here to getting my setup working and at $6 a year I would be stupid to not had over the cash.

Excellently priced and the least you deserve for the amount FileBot has benefited loads and loads of people.

Hi, I've had my setup automated for quite some time now and last week this happened: Run script [dev:amc] at [Tue May 29 03:00:17 IST 2018] Parameter: ut_label = tv Parameter: music = y Parameter: unsorted = y Parameter: clean = y Parameter: deleteAfterExtract = y Parameter: minFileSize = 1000000 Pa...

Did you ever figure this out?

rednoah wrote:Logs?

The videos are either smaller than 50 MB or shorter than 10 minutes. You can pass in your own minFileSize and minLengthMS if you don't like the defaults. Set these options to 0 to disable them.

Cheers! Adding minLengthMS=0 did the trick

I just searched the internet for this issue and came across this thread. I am getting the same "skip short video message" on some files less than 50MB in size. I did have a minimum file size option in my command line so I changed that to "10" and it still does the same thing. Eve...

Curious about this... my FileBot stopped working after a recent DSM update. The FileBot Node wouldn't run so I thought I would try a reboot. In Package Centre the Node is still showing as Stopped, but the logs indicate it is started and it is actually processing my files.

Can anyone explain this?

Friends4U wrote:Not working here... with the test version (0.2.0)

In what sense? What do you see?

rednoah wrote:I've uploaded a test package that should work on DSM 6.

Please try and give me feedback:
https://sourceforge.net/projects/filebo ... ebot/HEAD/

What do I need to install/copy?


/Edit: Ignore me, the file wasn't showing up when I clicked the link but I've just refreshed and it is there.

I have been tinkering and have made some progress. This is what I have done: 1) Updated the node path in start.sh to: /usr/local/bin/node --max_executable_size=16 --use_idle_notification "server/app.js" 2) Updated the paths in start.sh to: export FILEBOT_NODE_HTTPS_KEY="/usr/syno/etc/...

And sorted! Had to run as root and specify the full path of /volume1/@appstore/filebot/filebot.sh

for all who have the DSM 6 Beta 1 or Beta 2 installed Filebot Node does not work. Some path or certificates has been changed. And the authenticate.cgi will not be supportet via Beta1 and2. I installed DSM 6 RC1 where the authenticate.cgi is supportet. Filebot Node itself works but the gui didn't st...

As per the other thread, mine is kind of working on the new Synology beta. However, whilst manually clicking on Run on the task works, the automatic execution gives: find: cannot get current directory: Permission denied /Edit: Instead of running it as admin I tried as my own user and now I get: sh: ...

I may have spoken too soon. For some reason the schedule doesn't do anything, but when I click run manually it works fine. Strange

The changes to start.sh make it work. It is only the UI that doesn't work, which most people won't care about once their setup is done

Did a manual run of the tasks I had set up and it all seems to work fine: # created on Sun Mar 06 2016 03:16:16 GMT+0000 (GMT) Run script [fn:amc] at [Sun Mar 06 03:36:25 GMT 2016] Parameter: ut_label = tv Parameter: music = y Parameter: unsorted = y Parameter: clean = y Parameter: deleteAfterExtrac...

I changed my start.sh as per the above recommendations and my Filebot NodeStarts: ENVIRONMENT { SYNOPKG_DSM_LANGUAGE: 'enu', FILEBOT_NODE_HTTPS_KEY: '/usr/syno/etc/certificate/system/default/privkey.pem', TERM: 'vt102', FILEBOT_CMD_UID: '1024', SYNOPKG_TEMP_LOGFILE: '/tmp/synopkgmgr.log-filebot-node...

rednoah wrote:viewtopic.php?f=13&t=3418

Cheers!

Ok so I added that and just now a PROPER release of Better Call Saul came out, it just skipped it

/Edit: Don't worry, set conflict to override

If it is already there for whatever reason then I would like to be able to take any action myself.

Banned from where?

Bah, for some reason when a file already exists it moves it the Unsorted folder. I'm assuming if I use the overwrite option it will just replace it, but what if I wanted to leave it in the EpisodesTEMP folder?