This repository was archived by the owner on Jul 12, 2023. It is now read-only.
Timeouts/Resilience for loudness-analysis? #19
Locked
RandomUser345
started this conversation in
Ideas
Replies: 2 comments 1 reply
-
|
I've thought about making the feature optional, this may provide the push to make that change. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Latest version should give you some options to disable it, see the updated readme |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Works like a charm! Thank you! |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm quite a noob when it comes to bash-scripting so I don't know if this is even feasible, but on my hardware (Raspberry Pi 4 with Ubuntu 20.04) I sometimes download files from deezer/tidal which cause the loudness-analysis to crash, bringing down the whole box. Is there a way to make this more resilient? Since I cant login anymore to the machine and have to reset it I'm not able to get to much info, I just see the last lines in the docker logs after the restart and its always on the loudness-check.
Fortunately the same files won't be downloaded again since they are already in the list, still this can be quite annoying if the downloader is idling for a day before I see the issue.
Beta Was this translation helpful? Give feedback.
All reactions