From c939c7e857d1f3be8f04e91b7ae37552856f208b Mon Sep 17 00:00:00 2001 From: ta264 Date: Thu, 6 Jun 2019 15:29:48 +0100 Subject: [PATCH] Updated Custom Post Processing Scripts (markdown) --- Custom-Post-Processing-Scripts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Custom-Post-Processing-Scripts.md b/Custom-Post-Processing-Scripts.md index 0183e19..cdbc6de 100644 --- a/Custom-Post-Processing-Scripts.md +++ b/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). 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 - `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