Curious about new option in Lidarr extended.conf #232
-
Noticed this line added to the extended.conf. Curious about configuration. Is this if I setup my Lidarr instance with SAB? Is there any particular mapping I need to do in my docker setup? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 3 replies
-
The change allows you to see the completed downloads in Lidarr web interface on the queue page. It shouldn’t interfere with sab |
Beta Was this translation helpful? Give feedback.
-
ok cool. Ill setup sab later. Quick question, did something change? Im redoing my server and I swear I had this setup previously without any download client configured in Lidarr. I only used the deezer/tidal setup, but now unless I add an import folder to the download client section things get downloaded but nothing gets imported to Lidarr when "LIDARR IMPORT NOTIFICATION SENT!" happens. |
Beta Was this translation helpful? Give feedback.
-
So a bug was introduced when attempting to resolve another request. I just pushed a fix for the bug... Restart (twice, first to pull the script, 2nd to run the script...) and pull the latest script and it should be resolved Reference: #233 |
Beta Was this translation helpful? Give feedback.
-
I set a new import path but Lidarr is not post processing the files it downloads to my root music folder how can i fix this or was this part of the bug |
Beta Was this translation helpful? Give feedback.
-
Its workingISH. What it is doing currently is downloading the albums, and not importing them YET. Once the script reaches the end of its current run and restarts in 15 minutes, then it is picking up the albums for import. The albums are remaining however in the import folder and not being removed. I am going to add an artist and let it run overnight to see if that corrects itself with cleanup |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
So a bug was introduced when attempting to resolve another request. I just pushed a fix for the bug... Restart (twice, first to pull the script, 2nd to run the script...) and pull the latest script and it should be resolved
Reference: #233