POSTBUCKET - where random posts in unrelated topics go
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
I've update the FileBot Node docker container to FileBot Node 0.2.8.4. Please try the latest container and let me know if you encounter any problems.
-
- Posts: 11
- Joined: 12 Apr 2019, 06:20
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
Works great. Thank you! Two questions though:
1, Is it possible to somehow un-schedule a task? Can not find that option.
2, Is there any way to also schedule it to run at a specified time? Currently only a API call seems possible.
1, Is it possible to somehow un-schedule a task? Can not find that option.
2, Is there any way to also schedule it to run at a specified time? Currently only a API call seems possible.
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
1.
Yes, but only by directly modifying the FileBot Node application data files, which are stored in /data/.filebot-node (container-point-of-view).
2.
FileBot Node does not include a scheduler. The scheduling of commands is best done with the built-in facilities of the platform, i.e. cron if you're using a generic Linux system.
But at that point, why would you be using FileBot Node in the first place? You could just use cron to schedule docker filebot amc script calls directly, without having FileBot Node running at all.
Yes, but only by directly modifying the FileBot Node application data files, which are stored in /data/.filebot-node (container-point-of-view).
2.
FileBot Node does not include a scheduler. The scheduling of commands is best done with the built-in facilities of the platform, i.e. cron if you're using a generic Linux system.

-
- Posts: 11
- Joined: 12 Apr 2019, 06:20
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
1, Got it.
2, Just because Node makes it much more convenient to rapidly test different iterations of a command and schedule it when it finally does the right thing. (I am just bad at writing shell scripts. Always some typo / unescaped character / etc....
). The API Is all I currently really need.
2, Just because Node makes it much more convenient to rapidly test different iterations of a command and schedule it when it finally does the right thing. (I am just bad at writing shell scripts. Always some typo / unescaped character / etc....

Re: [JDownloader] Setup for Windows, Linux and Mac OS X
I see. Yes, FileBot Node certainly has value in generating CLI commands. You could always use the WebUI to generate commands and the copy & paste that into your scheduled shell script.OutrageousGem wrote: ↑17 Jun 2019, 09:37 Just because Node makes it much more convenient to rapidly test different iterations of a command and schedule it when it finally does the right thing. (I am just bad at writing shell scripts. Always some typo / unescaped character / etc....). The API Is all I currently really need.


-
- Posts: 8
- Joined: 13 Jul 2014, 18:10
Re: [EVAL] Split code into external *.groovy script files
I've tried using a few different things, but even having something as simple as:
test.groovy=>
{n}
and then doing movieFormat="{include 'test.groovy'}"
also tested movieFormat="{evaluate('test.groovy' as File)}"
results in an empty name..am I missing something? I may not have understood what should be in the groovy file, but from what I can see it should just be the same expression as we can already use in a one liner format?
*edit 2* updated to 4.8.6, but still getting empty file name
test.groovy=>
{n}
and then doing movieFormat="{include 'test.groovy'}"
also tested movieFormat="{evaluate('test.groovy' as File)}"
results in an empty name..am I missing something? I may not have understood what should be in the groovy file, but from what I can see it should just be the same expression as we can already use in a one liner format?
*edit 2* updated to 4.8.6, but still getting empty file name
Re: [EVAL] Split code into external *.groovy script files
test.groovy
We're including Groovy code here, as opposed to FileBot Format Expression code, which interprets {...} delimited expressions as Groovy code. If we include Groovy code from within Groovy code, like in the example above, then Groovy code is expected.
YES:
Same as {n}
NO:
Same as {{n}}
Code: Select all
n

YES:
Code: Select all
{evaluate 'n'}

NO:
Code: Select all
{evaluate '{n}'}

-
- Posts: 8
- Joined: 13 Jul 2014, 18:10
Re: [EVAL] Split code into external *.groovy script files
Oh, I see, I always was under the impression that the format expressions were just plain groovy. Shame on me.
Yeah, getting results now. Thanks!
Yeah, getting results now. Thanks!
Re: [EVAL] Split code into external *.groovy script files
No worries. It’s a common misconception, since Groovy Code itself may also contain {} for close blocks or closures. So the semantics depend on the context.
-
- Posts: 8
- Joined: 13 Jul 2014, 18:10
Re: [EVAL] Split code into external *.groovy script files
After playing around a bit this is awesome.
However:
Trying to break out certain helpers as separate scripts it seems that there is an issue with loading external scripts unless everything is placed and run from the filebot portable folder (which I'd like to avoid since I have all my scripts backuped to a gdrive synced folder).
If I have a
tags.groovy file that grabs my preferred tag format, I can't seem to get it to load.
I've tried:
include 'getEditions.groovy' // this works fine if I place my groovy files in the lib, but if I run it from where I actually have my files it tries to load it from $CWD
After googling the recommended way is to do:
However, that blows up with
I've tried granting access to all apps for that permission, but it doesn't seem to work.
Even doing:
Doesn't work.
Is there some additional arguments I can give filebot to figure out which path to load files from, or is it all handled by the JVM?
However:
Trying to break out certain helpers as separate scripts it seems that there is an issue with loading external scripts unless everything is placed and run from the filebot portable folder (which I'd like to avoid since I have all my scripts backuped to a gdrive synced folder).
If I have a
tags.groovy file that grabs my preferred tag format, I can't seem to get it to load.
I've tried:
include 'getEditions.groovy' // this works fine if I place my groovy files in the lib, but if I run it from where I actually have my files it tries to load it from $CWD
After googling the recommended way is to do:
Code: Select all
def scriptDir = getClass().protectionDomain.codeSource.location.path
include '$scriptDir/getEditions.groovy'
Code: Select all
AccessControlException: access denied ("java.lang.RuntimePermission" "getProtectionDomain")
Even doing:
Code: Select all
grant {
permission java.security.AllPermission;
};
Is there some additional arguments I can give filebot to figure out which path to load files from, or is it all handled by the JVM?
Re: [EVAL] Split code into external *.groovy script files
1.
Your code just doesn't do what you think it does:
http://groovy-lang.org/syntax.html#_str ... erpolation
2.
I'd use environment variables if I wanted to pass in some common folder paths for use in custom scripts:
or via --def name=value if you need it in the format engine:
Your code just doesn't do what you think it does:
Code: Select all
def x = 1
println '$x = 1' // $x = 1
println "$x = 1" // 1 = 1

2.
I'd use environment variables if I wanted to pass in some common folder paths for use in custom scripts:
Code: Select all
export FILEBOT_FORMAT_D="$HOME/.gdrive/FileBot Formats"
Code: Select all
_environment.FILEBOT_FORMAT_D
Code: Select all
filebot ... --def FormatFolder="$FILEBOT_FORMAT_D"
Code: Select all
{defines.FormatFolder}
Re: [EVAL] Split code into external *.groovy script files
FileBot r6524 will now resolve include("files.groovy") relatively to the current script file by default.
-
- Posts: 8
- Joined: 13 Jul 2014, 18:10
Re: [EVAL] Split code into external *.groovy script files
Great!
Thanks for pointing out that string interpolation thing, completely missed the single quotes difference (still threw the security exception but that's irrelevant now I guess).
The --def was exactly what I was thinking of as a workaround.
Thanks for the help!
Re: Metadata and Extended Attributes
Hi,
is there any option to add filebot xattr to already sorted files?
eg, i have multiple series where on some seasons the xattr from filebot are missing, so ne the " filebot missing script" does not work correct and think the season is missing.
is there any option to add filebot xattr to already sorted files?
eg, i have multiple series where on some seasons the xattr from filebot are missing, so ne the " filebot missing script" does not work correct and think the season is missing.
Re: Metadata and Extended Attributes
You'll have to process files through FileBot again to ensure that xattr are set this time.
You can find files without xattr metadata like so:
You can find files without xattr metadata like so:
Code: Select all
filebot -mediainfo . --filter '!f.metadata' --format {f}
Re: Metadata and Extended Attributes
thanks for your fast reply!
thats the first thing i did, but filebot says "Skipped, already exists".
thats the first thing i did, but filebot says "Skipped, already exists".

Re: Metadata and Extended Attributes
1.
You can move all untagged files elsewhere first:
2.
However, the general smart approach is to never touch files in your Media folder, and only ever move files there via FileBot. That way you can ensure that everything is always in perfect order.
i.e. just process all your files into a new folder, and then remove the old one if you're happy with the new one
You can move all untagged files elsewhere first:
Code: Select all
filebot -mediainfo . --filter '!f.metadata' -exec mv -v {f} /path/to/untagged/files/{f.name}
2.
However, the general smart approach is to never touch files in your Media folder, and only ever move files there via FileBot. That way you can ensure that everything is always in perfect order.
i.e. just process all your files into a new folder, and then remove the old one if you're happy with the new one
Code: Select all
--format /path/to/new/folder/{plex}
-
- Posts: 9
- Joined: 21 Jun 2019, 23:05
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
I followed your steps in post #1 and it works very well I just can't change any of the downloaded files because I have no permission.
How can I get filebot to create files/folders with correct permissions?
On my Media Drive all my files have:
Owner: 1000
Group: 100
Permissions: 775
Files renamed and moved from Filebot have:
Owner: 0
Group: 0
Permissions: 775
How can I get filebot to create files/folders with correct permissions?
On my Media Drive all my files have:
Owner: 1000
Group: 100
Permissions: 775
Files renamed and moved from Filebot have:
Owner: 0
Group: 0
Permissions: 775
Re: [JDownloader] Setup for Windows, Linux and Mac OS X
FileBot does not set or change permissions in any way. It does whatever the OS does by default.
The amc script does have the --def exec option though, which allows you to run your own post-processing commands on newly processed files:
The amc script does have the --def exec option though, which allows you to run your own post-processing commands on newly processed files:
Code: Select all
--def "exec=chmod -R 775 {quote folder} && chown -R admin:administrators {quote folder}"
-
- 402
- Posts: 157
- Joined: 16 Dec 2014, 01:39
Re: [DOCS] Use --mapper expressions for AniDB / TheTVDB cross-entity matching
Any idea when 4.8.6 is coming to the windows store?
Re: [DOCS] Use --mapper expressions for AniDB / TheTVDB cross-entity matching
The Microsoft Store package will be submitted to the Store on release day. Microsoft will then take a few days to test and publish.
4.8.6 has not been released yet. It's ready when it's ready. Probably sometime in September. You can help speed things up by trying the latest beta and providing feedback.
4.8.6 has not been released yet. It's ready when it's ready. Probably sometime in September. You can help speed things up by trying the latest beta and providing feedback.
Re: Choose Java Swing Look-and-Feel (e.g. Dark Mode)
This works great. Any chance of this being an option within the application? Maybe under Preferences?rednoah wrote: ↑25 Feb 2019, 19:23
- Open Start Menu and search for Set Environment Variables
- Click on New
Name:Value:Code: Select all
FILEBOT_OPTS
Code: Select all
-Dnet.filebot.theme=Darcula
- Click OK and then relaunch FileBot.
Note that you'll need the latest revision (i.e. r6135 or higher) for any of this to work. The FileBot (platform) launcher is using the Darcula theme by default now as well.
Re: [DOCS] --apply post-processing features
Will this replace scripts ?
any future plans to ?
where is this in the Docs ?
https://www.filebot.net/docs/api/
what does this use to fetch stuff ?
any future plans to ?
where is this in the Docs ?
https://www.filebot.net/docs/api/
what does this use to fetch stuff ?
Re: [DOCS] --apply post-processing features
Not at all. It's just a variety of frequently requested features that more or less fall under the same umbrella. The future plan is to add selected post-processing features to the GUI and allow users to apply some of them as part of the rename process.
A public API is not planned. It doesn't do anything that isn't already implemented in the htpc.groovy script or otherwise commonly handled via -exec calls.

It's doing more or less the same as the artwork.* scripts, using TheMovieDB / TheTVDB / FanartTV as the source of image files.
Re: [PLEX] FileBot Xattr Metadata Scanners & Plug-ins
Do the PLug-ins and Scanners folders go into the Plug-in directory on the PMS?