Closed jessetn closed 1 year ago
Imports are handled by Lidarr, this is not a bug with the lidarr-extended scripts but an issue with how upstream lidarr imports/matches releases. You can reach-out to Lidarr support channels for more information/support but there isn't anything I can do about it here....
On that note, if you can identify/prove it's a problem with one of the included scripts, I'll gladly investigate further. But this does not appear to be an issue with that....
There a Reddit post from Lidarr's support from January saying Lidarr does not require Release Group on import. I swear I also ran across the same statement on their Github but can't find atm. If I do I'll post
I only support the extended scripts, so your main issue is a lidarr issue, which means you need to use Lidarr support channels. Unless you can prove the extended scripts are causing the issue.
Edit:
@jessetn I'm assuming the files/import your showing is coming from the normal download methods? (torrent/usenet)
@RandomNinjaAtk I'm not @jessetn but having the same issue, and yes, the files are imported from the usual methods.
I'm having to manually import media that should otherwise have all necessary matching information for an automatic import with no errors, except for a missing "Release Group". I doesn't appear to have a switch in the settings for this requirement. I've noticed this for the past few releases but am now constantly having to manually import. Is this a bug or expected behavior? Version 1.1.3.2982 Package Version 1.1.3.2982-ls77 by linuxserver.io .NET Yes (6.0.7) Docker Yes DB Migration 63 Database Sqlite 3.40.1 AppData directory /config Startup directory /app/lidarr/bin Mode Console