Intro/Credits Backup & Restore (New Plugin)

[crusher11 1243]

I deleted the JSON files from the Fanny and Alexander folder, and now it works.

[guilty57 11]

6 hours ago, crusher11 said:

I deleted the JSON files from the Fanny and Alexander folder, and now it works.

That confirms the diagnosis - thanks for testing it. Deleting the JSON forced restore to read the NFO directly, and the NFO had the right data all along.

That's obviously not something you should have to do by hand every time, so the actual fix is what we talked about above: restore will merge JSON and NFO together field by field instead of stopping at the first JSON match. Once that ships, you can put your JSON backups back and it'll pick whichever source actually has a value for each field (Intro/Credits independently), rather than an old or partial JSON blocking a more complete NFO. Will post here once that's out.

[crusher11 1243]

Yeah, once I confirmed it fixed the issue I just disabled “save JSON with metadata” and ran another restore, and everything seems to be working now. Re-enabled it afterwards, so it should overwrite the bad JSON files with the correct data on the next backup.

Edited Thursday at 02:37 PM by crusher11

[crusher11 1243]

Might be worth letting users choose whether to restore from NFO or JSON. Auto-detect has completely screwed up all the Alfred Hitchcock Presents intros, and they're all the first 30 seconds of each episode. A simple bulk find-and-replace in the NFOs will fix that, whereas using ChapterAPI or the like would take ages.

[guilty57 11]

v1.9.0 is out - a full config page redesign plus a reliability fix.

Config page redesign. Instead of one flat list of checkboxes, there are now two clearly separated modes:

• Custom: pick your own folder(s). Independent JSON and standalone-NFO toggles (the standalone NFO is the plugin's own file, just a <markers> tag - not Emby's scraper NFO), separately controllable for Backup and Restore.
• Automatic (Media Folder): backups live next to each video, like before. Backup now has independent JSON and NFO toggles (no more "Both" - just check one or both) plus a new "just-in-case" JSON safety copy option that writes to a folder of your choosing, completely separate from what's happening next to your videos. Restore stays NFO / JSON / "let the plugin choose" (recommended).

Picking one mode now properly hides the other's section. The separate "Auto-restore" / "Auto-backup on manual edit" toggles are gone too - those background watchers are now on automatically based on whichever sources you've actually configured, instead of a switch you had to remember to flip.

Reliability fix: Auto-restore occasionally missed restoring right after a Refresh Metadata, because Emby's own NFO scraper isn't always atomic about writing the file - a read could catch it mid-write. Added a short retry for that specific case; confirmed fixed across multiple shows in testing.

If you're upgrading, take a look at the config page - the layout changed, worth double-checking your settings landed where you expect.

Release with prebuilt DLL:

https://github.com/guilty57/credits-intros-backup-restore/releases/tag/v1.9.0

 

Custom Selection

 

Auto Selection

Edited 1 hour ago by guilty57
Screenshots added.

[Ferwin29 10]

Hi @guilty57, I've got a question about plugin's compatibility. I don't have the plugin in Emby Server 4.10.22, it's not compatible with ?

[guilty57 11]

14 minutes ago, Ferwin29 said:

Hi @guilty57, I've got a question about plugin's compatibility. I don't have the plugin in Emby Server 4.10.22, it's not compatible with ?

I've only built and tested this against 4.10.0.20 so far, haven't had a chance to try it on 4.10.22 specifically. I don't have a reason to expect it wouldn't work - nothing in the plugin depends on anything version-specific that I'm aware of - but "should work" isn't the same as "confirmed working."

Would you be up for testing it and letting us know what happens? If it doesn't load, the first thing to check is embyserver.txt right after startup for any error mentioning IntrosBackupReplacement - that'll tell us whether it's a real incompatibility or something else. Appreciate you flagging this either way - if it does turn out to need a fix for 4.10.22, better to know now than have others hit it silently.