mirror/Lidarr
1
0
Fork 0
mirror of https://github.com/lidarr/Lidarr synced 2024-12-22 15:53:23 +00:00
Code Issues Releases Wiki Activity

Updated Custom Post Processing Scripts (markdown)

ta264 2019-06-06 15:29:48 +01:00
parent d924e60a9d
commit c939c7e857
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Custom-Post-Processing-Scripts.md

@ -106,7 +106,7 @@ Sample script using the Lidarr environment variables to create EDL files for all
An example script to trigger beets is [here](https://gist.github.com/ta264/77443a3de790babbd4f5ce6b9af64f4d). You need to have your beets config file setup correctly. An example is [here](https://gist.github.com/ta264/2cb2de25755976bf3f5e7901835209d5). An example script to trigger beets is [here](https://gist.github.com/ta264/77443a3de790babbd4f5ce6b9af64f4d). You need to have your beets config file setup correctly. An example is [here](https://gist.github.com/ta264/2cb2de25755976bf3f5e7901835209d5).
Key points: Key points:
- This will not work on Lidarr `0.5.0.583`. It requires nightly or a (yet to be released) `0.6.0` build. - This will not work on Lidarr `0.5.0.583`. It requires nightly or a `0.6.0` build.
- `directory` must be your (only) root directory in Lidarr - `directory` must be your (only) root directory in Lidarr
- `import\copy` must be `no` to prevent beets moving files - `import\copy` must be `no` to prevent beets moving files
- You should configure beets file naming to match your lidarr file naming to avoid nasty surprises - You should configure beets file naming to match your lidarr file naming to avoid nasty surprises