Welcome @white notch!
Someone from <@&938443185347244033> will assist when they're available.
Including the meta.log from the beginning is a huge help, type !logs for more information.
#Libraries Help - @Mr Carrot
zenith obsidianBOT
You can press the "Close Post" button above or type /close at any time to close this post.
zenith obsidianBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
lyric nexus
Can you drag the whole config in here? I'd like to see how those anchors are defined.
white notch
To break this down a little bit.
*radarr, radarr_2160, and radarr_1080 all perform different things, to they are called upon to do different things.
zenith obsidianBOT
The following was shared by @white notch and was automatically redacted by Luma as it may have contained sensitive information.
If you feel this message should not have been redacted, resend it with !noredact in your message to avoid redaction.
white notch
it is a mess. I know. that is why i am looking to clean it up a lot.
lyric nexus
I guess I can sort of see why you have this set up like this but to me it seems insanely granular. Is there really enough going on that you need separate reports for every individual thing rather than just a single report by library, for example?
then you've got some 4K libraries feeding a 1080 radarr?
white notch
not really.
the reason i broke it up into so many sections, was because back with 1.31 of plex, i found PMM would run craze slow. I have since rolled back (12 months ago) back to 1.29 where it acts faster, but i havent looked at recombining everything again.
my radarr instances are setup that all my 4k will add to my radarr 1080 instance because i want the movies in 1080, but it will set the profile to 4k where my 4k instance automatically picks it up.
again, it was done to resolve an issue many moons ago, and i am sure the issue is fixed now, but never got around to addressing or testing it out since.
lyric nexus
Well, some thoughts:
These radarr entries:
Actor 2160:
schedule: weekly(Saturday)
library_name: Movies
report_path: config/Report/Actor2160_Report.yml
collection_files: *actor
radarr: *radarr_1080
Actor 1080:
schedule: weekly(Saturday)
library_name: Movies - 1080p
report_path: config/Report/Actor1080_Report.yml
collection_files: *actor
radarr: *radarr
Are pointless. The actor collections are based on the casts of the movies in Plex, so there will never be anything to add to radarr.
white notch
ok, taken them out.
lyric nexus
If you were to push the schedule down into the actor section, these four could be combined into two, assuming you can do without the default-level report:
Actor 2160:
Actor 1080:
Seasonal 2160:
Seasonal 1080:
Can i move the schedule to the actor handle now? and then combine some libs?
lyric nexus
You could also add the meta section into those two, and probably some others.
white notch
schedule: weekly(Saturday)
- pmm: actor
template_variables:
collection_section: '002'
use_separator: false
style: signature
name_format: 🎂 Happy Birthday <<key_name>>
translation_key: birthday
sort_by: audience_rating.desc
title_format: <<key_name>>'s Birthday
data:
depth: 20
limit: 100
tmdb_birthday:
this_month: true
before: 0
after: 0
radarr_add_missing: false```?or after the - pmm line?
lyric nexus
to start
Common: &common
- pmm: actor
schedule: weekly(Saturday)
template_variables:
collection_section: '002'
...
- pmm: seasonal
template_variables:
collection_section: '001'
...
libraries:
Movies:
report_path: config/Report/Movies.yml
collection_files: *common
radarr: *radarr_1080
Movies - 1080p:
report_path: config/Report/Movies-1080.yml
collection_files: *common
radarr: *radarr
Can't really bring meta in since you want to run those on different schedules.
white notch
I just noticed my radarr and radar_1080 are the same besides add missing. so ill reemove one of those and update too.
lyric nexus
I guess you can't really combine much more given the scheduling requirements you have.
white notch
ok. how about this, the issue i have been having is everytime it hits a new library request, it wants to scan my several thousand movie catalogue again. so it was scanning 3 or 4 times each day cycle.
taht would be the largest time consumtion of my generally 1hour long daily process. would removing the day blocks from each, and combining the libs prove faster?
lyric nexus
You could lighten up all the radarr/sonarr by only specifying what's different from a base radarr/sonarr.
lyric nexus
taht would be the largest time consumtion of my generally 1hour long daily proce...
Depending on how much time it takes to load the library, probably. By splitting these up into separate "libraries", if you're not defeating the cache you're not making the most of it.
white notch
Common: &common
- pmm: actor
...
- pmm: seasonal
...
Libraries:
Movies 2160:
library_name: Movies
report_path: config/Report/Movies2160_Report.yml
collection_files: *common
radarr: *radarr_1080
Movies 1080:
library_name: Movies - 1080p
report_path: config/Report/Movies1080_Report.yml
collection_files: *common
radarr: *radarr_1080```For example:
Radarr: &radarr
url: http://192.168.0.102:7878
token: (redacted by Luma)
add_missing: false
add_existing: false
upgrade_existing: false
root_folder_path: /data/media/movies/1080
monitor: true
availability: announced
quality_profile: 1080p
language_profile: English
tag: pmm
search: true
ignore_cache: false
radarr_path: None
plex_path: None
Radarr_1080: &radarr_1080
add_missing: true
Radarr_2160: &radarr_2160
url: http://192.168.0.102:7877
token: (redacted by Luma)
add_missing: true
root_folder_path: /data/media/movies/2160
quality_profile: 2160p
can i drop radarr: *radarr_1080 from the libraries, and put it into the - PMM: seasonal section instead?
lyric nexus
can i drop radarr: *radarr_1080 from the libraries, and put it into the - PMM: s...
No, that's a library-level thing.
white notch
ok.
but i can drop out the duplicate bits of radarr from the 1080 and 2160 radarr anchors?
lyric nexus
Yes. PMM will go to the base-level "radarr" then apply the delta settings that you specify.
So in the above, radarr_1080 is everything from radarr but add_missing is changed.
white notch
awesome.
because in the Meta 2160: library, i want it to rely on the radarr_2160, i have to keep that library separate to the others?
lyric nexus
If you wanted to do give up on the day, you could push the may(X-Y) schedules down into meta and universe and then add those to "common"
lyric nexus
because in the Meta 2160: library, i want it to rely on the radarr_2160, i have ...
Yep
white notch
If you wanted to do give up on the day, you could push the may(X-Y) schedules do...
how so? and yes.
so, *meta doesnt get added to my radarr_2160, but *universe does. so these need to remain separate still for that reason right?
lyric nexus
Common: &common
- pmm: actor
template_variables:
collection_section: '002'
use_separator: false
...
- pmm: seasonal
template_variables:
collection_section: '001'
visible_library: false
visible_home: true
...
- pmm: basic
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '003'
...
- pmm: imdb
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '003'
use_separator: false
...
- pmm: tmdb
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '003'
use_airing: false
...
- pmm: trakt
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '003'
use_collected: false
...
- file: config/Movie Collections.yml
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '003'
use_separator: false
...
- pmm: universe
schedule:
- range(05/04-05/06)
template_variables:
collection_section: '004'
visible_library: false
...
I guess universe uses that oddball radarr so you can't combine that.
but you're calling the universe default in two of those anchors (meta and universe)
white notch
are you certain there is no way to define that in the handle and not the library? I already have radarr options in the handles for &seasonal (&common)
item_radarr_tag: pmm, <<key_name>>```There are some radarr options that can be defined there, but some things can't be. If the things that you are changing can be set there, sure, you can put them down there. The URL and token can't be set there, however, for example, so you can't replace radarr_2160 with template_variables.
white notch
wait,, i just saw that. why am i calling upon universe in meta and on its own? damn it.
ive just dropped &meta and combined it with &common. I didnt worry about the date ranges as the only thing that needed the date range was Starwars day (someone requested it be added) that means I could also remove the Meta_2160/1080 libraries too.
and i removed Universe_1080 from the library as it doesnt need to run again when it is already assigned to run in &common
lyric nexus
Hopefully that gives you a start on things.
white notch
one more thing regarding the &universe handle.
can I get it so that it wont re-run the collections portion as it is being done daily, but in the Universe_2160 library it adds what is already in the library to radarr_2160?
because that is essentially the only reason for that.
lyric nexus
adds what is already in the library to radarr_2160?
You want to add universe things that have been added to Plex outside of Radarr to Radarr? Does that happen often?
white notch
well, PMM is adding the items from &meta that are missing in the &universe collections to Radarr_1080 at the moment, but the &universe section was only setup to re-add the same collection to 2160 radarr and tag it appropriately. double handling, but i couldnt think of a better way to do that.
see, i dont want everything added to 4k, just some manually selected things, and the things in the Universe section.
in my head that makes sense, but i am assuming you think i am nuts.
lyric nexus
right, but if something is "already in the library" isn't it already in Radarr?
white notch
it is in 1 instance of radarr, not in the second. so essentially &universe wasnt setup to create the Collection in plex, because that was already being done in &meta, its function was to tag the already existing universe collections so that Radarr_2160 would add it to the second instance of radarr instead.
and I think I just worked out a way to do that anyway.
lyric nexus
So by "library" you don't mean the Plex library.
white notch
I think I will just have to add the radarr_tag: 2160p and then assign my second instance of radarr to impost anything with that tag.
lyric nexus
That's probably simplest and was what I was about to suggest.
white notch
in the handles can i add radarr_quality?
lyric nexus
Nope. Available settings at the template_variable level listed here:
https://metamanager.wiki/en/nightly/defaults/collection_variables/