Reads MUSICBRAINZ_ALBUMID from FLAC (vorbis block type 4) and MP3 (ID3v2 TXXX) files, matches against Lidarr's known releases, switches monitored=true to the correct one, and queues RefreshArtist. Runs before lidarr_cleanup.sh in the daily job list so the strike system doesn't act on files that just needed a release correction.
126 lines
5.0 KiB
Markdown
Executable File
126 lines
5.0 KiB
Markdown
Executable File
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
|
||
source ~/.bashrc
|
||
claude
|
||
|
||
|
||
|
||
need a script that check file locations. like if a kids movie is in movies. it needs to detect this and update the location in the arrs. so it would tell radarr to move shrek from movies to kids movies and trck the new file
|
||
|
||
|
||
look at a way to better determine when a container was manually shutdown for docker watchdog
|
||
|
||
|
||
|
||
we may need to add this to our preflight before lidarr cleanup. check if lidarr need corrected before
|
||
removal. since we have a strike list we can save results of previous scan then run this script then
|
||
continue. lidarr has been wierd for the last year. maybe we
|
||
────────────────────────────────────────────────────────────────
|
||
|
||
|
||
|
||
|
||
❯ now we should be able to allow or have other host be able to start a shared srvice if desired using
|
||
shared auth stack, maybe a container array in host*.conf folder that can add the container to the other
|
||
servers, just thinkig of future design
|
||
|
||
|
||
|
||
|
||
|
||
. fix fallback strike list timing, maybe 30 seconds. them a t 90 seconds 3 stike triggers. just gotta test buffer. never had the strike system
|
||
. verify silent toggle switches back on good notifications
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Saved. Here's where we land and what to pick up:
|
||
|
||
What happened: Lidarr was silently discarding valid files because it selected the wrong MusicBrainz release edition (Brazil CD, Japan Digital, etc.) while your files were tagged for a different one (US CD, Vinyl). The track IDs don't match across editions, so RescanFolders always returned "Importing 0 tracks." Not a file problem — a database mismatch. The 5GB threshold in lidarr_cleanup.sh was doing exactly what it should.
|
||
|
||
Fixed this session: 123 albums bulk-corrected (read MUSICBRAINZ_ALBUMID from FLAC tags, switched Lidarr's release selection, RefreshArtist). Full root rescan still running in the background.
|
||
|
||
Next session — pick up here:
|
||
1. Design the daily fixer script (Media/lidarr_release_fixer.sh) — FLAC + MP3 (ID3 TXXX) tag reading, same bulk-fix logic, runs from daily orchestrator. Strike system in lidarr_cleanup.sh already provides the protection window.
|
||
2. 42 albums where file MBID isn't in Lidarr at all (unofficial/re-tagged) — manual import or ignore.
|
||
3. 217 MP3 albums — need ID3 TXXX frame reader added to the fixer.
|
||
4. Check the full root rescan completed and see if zero-file count dropped further below 927.
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
WAY LATER
|
||
|
||
now we should be able to allow or have other host be able to start a shared srvice if desired using
|
||
shared auth stack, maybe a container array in host*.conf folder that can add the container to the other
|
||
servers, just thinkig of future design
|
||
|
||
|
||
when a owner offboards and there is more than 1 server left, one needs to become the owner, we could do this in multiple ways or a combination, strongest server and BANDWIDTH,whos contributing more.... maybe we just promt and ask them
|
||
|
||
|
||
|
||
|
||
|
||
look into an overall, setup script, pull as many vars as possible without user having to add. like docker names, and so on.
|
||
|
||
|
||
|
||
|
||
|
||
|
||
fallback, should partnership be authoritive. like no partners fallback fails and after x amount of time dissables untill a new remote is found
|
||
|
||
|
||
|
||
|
||
|
||
|
||
i need a way to get rid of git. the apllication becomes the source for each mesh cluster... so it gets dl from github, or ca. i need the app layer to be able to open and edit settings, like open conf first. things have to filled out for it to work. , and partnership deploy to second server, third server........... and push the correct host.conf. and only update that file if new things are added or completely wiped....... cant mod a var nut can rearrang the script if structure changes again......... even if git it used as a core and is auto set from the start..... the app layer is king moving forward, and scipts are cores that just get called. i have all the flexabiliy in the world being able to change things and the app layers call and use it............
|
||
|
||
we may need a startup guide.. first launch, open master.conf. then host1.
|
||
|
||
|
||
we need to updata the folder Unraid_Scripts to Varaverk every where and update git script, and update all traces and scripts that call it and update the user script plugin......
|
||
with this app layer i think we modle the user script to our system and no longer user facing..... maybe
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
uide. owner sets up first.. establishes himself in master.conf as host1.... sets up the rest of master.conf.. little changes may be needed.. then fills out host1.conf.... then makes sure machines are shared in tail scale.. start onboard.......... then host2, host3, what ever is in master.conf it will reachout, uinstall correct containers,and leave the state file... install varaverk on host 2 and host 3. on install it sees the state file and defuaults to mirror. they fill out their setting and all should start working.......
|
||
|
||
working on getting this down to just web ui. on intitial no state file opens master.conf, locks you out of enabling any orchs untill set up.....
|