Save IntroSkip Metadata inside NFO

[Cheesegeezer 3102]

@ebr

Eric, do you mind if make this an emby premium plugin? I would like to keep our intros and credits info inside the emby eco system.

cheers

[rbjtech 5000]

2 hours ago, Cheesegeezer said:

So just to keep you lot in the loop.

Waiting on some final testing before i release this to the catalogue.

Cheers

Restore looks to be fine (on my test system) and the NFO data has been successfully written to my main TV library (33K episodes) - took about 8 mins.  Spot testing looks good.

Nice work - I can now use the marker info in the NFO stored with the media to restore the Intro data into a new test instances, rebuild etc without having a dependency on the media Internal Id, thus no re-detection is now necessary.

Multi-versions work great (ie each NFO is updated).

Brilliant plugin ! 

Edited October 25, 2022 by rbjtech

[Cheesegeezer 3102]

Peeps, just found a fairly epic bug earlier which I've eraddicated, however waiting on a couple of testers to confirm that the bug is fixed and I will release the beast.

Standby to standby...... you lovely lovely people, beautiful british people

 

Edited October 26, 2022 by Cheesegeezer

[adminExitium 295]

Wonderful work, thanks a lot @Cheesegeezer.

 

Just to confirm, will it always do a full restore from the NFO to the DB or will it only restore the changed or added data automatically when Emby detects any changes to the NFO file?

[Cheesegeezer 3102]

13 minutes ago, adminExitium said:

Wonderful work, thanks a lot @Cheesegeezer.

 

Just to confirm, will it always do a full restore from the NFO to the DB or will it only restore the changed or added data automatically when Emby detects any changes to the NFO file?

It doesn’t monitor changes at all, its purely a full backup and full restore utility. 
 

at the time of backup it will find all episode that have intro and credits skip markers from the episode’s chapter table and writes them to json file in a user defined backup folder and/or to the episode’s nfo if it is saved in the media folders.

restore will use json OR nfo restore method. Not both and write the markers back to the chapter table overwriting any existing markers.

 

 

 

[adminExitium 295]

Got it, thanks. Looking forward to trying it out.

[Cheesegeezer 3102]

12 minutes ago, adminExitium said:

Got it, thanks. Looking forward to trying it out.

Just waiting on one tester to confirm all is good with restoring and it will be released 

[rbjtech 5000]

11 hours ago, Cheesegeezer said:

It doesn’t monitor changes at all, its purely a full backup and full restore utility. 
 

at the time of backup it will find all episode that have intro and credits skip markers from the episode’s chapter table and writes them to json file in a user defined backup folder and/or to the episode’s nfo if it is saved in the media folders.

restore will use json OR nfo restore method. Not both and write the markers back to the chapter table overwriting any existing markers.

 

 

 

Hopefully, the core will follow suit and use the same NFO section to read/write in core functions, making it a 'real-time' backup solution - allowing a full restore at any time as the data is independent from the database. 

Awesome job @Cheesegeezer 

@Luke - FYI

tail of the NFO file ......

  </fileinfo>
  <markers>
    <introstart>626303072</introstart>
    <introend>801518812</introend>
    <creditstart>0</creditstart>
  </markers>
</episodedetails>

 

[Cheesegeezer 3102]

Thanks Rich!

we are ready for release… but might package this with the TVCreditsSkip Plugin if i can get the damn UI to behave itself. As it makes sense to package it all in a single plugin. Also the database would act as a live backup for intro and credit skip markers and store these in the database that could just then be extracted by usin the chapter Insert task.

i dunno! 
what does the community feel? 

[Cheesegeezer 3102]

Launched in the plugin Catalogue.

Can be found under Metadata Section.  I will set up a Plugin thread shortly. 

Thanks all and enjoy.

 

 

Plugin Support Thread is located here

 

Edited October 28, 2022 by Cheesegeezer

[Cheesegeezer 3102]

@CBers @FrostByte 

not sure if you want to update the first post with my post above.

Upto you fellas.... Cheers

[FrostByte 5258]

2 hours ago, Cheesegeezer said:

@CBers @FrostByte 

not sure if you want to update the first post with my post above.

Upto you fellas.... Cheers

Updated the thread message to include a link to the plugin

[Monkolf 3]

On 10/21/2022 at 8:53 AM, Luke said:

HI, yes some sort of edit and backup process for this is planned for future updates. Thanks.

I save as much data alongside the media as I can, to make importing into the library as quick and painless as possible, should the need ever arise. This includes the .nfo metadata, the scraped images, and video thumbnail preview (.bif) files. This becomes proportionately more important as the library size grows.
I'm still looking into the root cause (perhaps a loose/bad SATA cable), but I had one of my TV media drives recently go offline overnight. After getting things back up, it seems emby is having to go back through and regenerate the fingerprint files and run the intro detection for each episode. There are thousands, so I'm about 36 hours in and still going...

@Luke, a couple of (hopefully) quick questions:
1) As it's been a while since the quoted reply was posted, just to confirm; is backing up the detected intro data still something that we can expect to be added? For cases like my above situation, this is something that would have been a tremendous boon to getting things up and going again.

2) This Feature Request is marked as being solved by a plugin. It's my understanding that this plugin is no longer supported and doesn't function properly on recent builds. Would the preference be to open a new Feature Request, in this case? I'm just looking for the devs' preferred route to bring visibility to this topic.

Thanks!

[Luke 40115]

4 hours ago, Monkolf said:

I save as much data alongside the media as I can, to make importing into the library as quick and painless as possible, should the need ever arise. This includes the .nfo metadata, the scraped images, and video thumbnail preview (.bif) files. This becomes proportionately more important as the library size grows.
I'm still looking into the root cause (perhaps a loose/bad SATA cable), but I had one of my TV media drives recently go offline overnight. After getting things back up, it seems emby is having to go back through and regenerate the fingerprint files and run the intro detection for each episode. There are thousands, so I'm about 36 hours in and still going...

@Luke, a couple of (hopefully) quick questions:
1) As it's been a while since the quoted reply was posted, just to confirm; is backing up the detected intro data still something that we can expect to be added? For cases like my above situation, this is something that would have been a tremendous boon to getting things up and going again.

2) This Feature Request is marked as being solved by a plugin. It's my understanding that this plugin is no longer supported and doesn't function properly on recent builds. Would the preference be to open a new Feature Request, in this case? I'm just looking for the devs' preferred route to bring visibility to this topic.

Thanks!

Hi, yes, and no, let's keep this feature request.

[Clackdor 92]

I'm also going to voice my support for this since I also prefer to keep all supporting files in media folders as well. I also have several emby instances pointing at those folders (only one of which has write permissions to update metadata, images, etc.)

I'm actually generating preview images after not having them for a while. I'm realizing the situation is still messy with any emby generated detection or chapter data and images. It's far from portable as it is right now. Ideally we should have a way to store all of this information next to the media considering how valuable it is. It should be easy to reimport in the event of a fresh server reinstall. 

[te5s3rakt 3]

On 04/05/2025 at 18:53, Monkolf said:

2) This Feature Request is marked as being solved by a plugin. It's my understanding that this plugin is no longer supported and doesn't function properly on recent builds. Would the preference be to open a new Feature Request, in this case? I'm just looking for the devs' preferred route to bring visibility to this topic.

On 04/05/2025 at 23:14, Luke said:

Hi, yes, and no, let's keep this feature request.

Then based on @Monkolf‘s original point, this request should be unflagged as “solved by a plugin”, if that is in fact not the case anymore.

My 2C. Mission critical items such as key metadata should really be handled by an official solution, rather than a third party one. No offence to the original plugin author, they did a tremendous job in the absence of one. But the drop in support perfectly illustrates the need for a first party solution.

From my experience, I wouldn’t ever trust something, that was not first party developed, to d!ck around in production database. I don’t at work. I sure as hell wouldn’t at home.

It’s +1 from me for this feature. There’s not a feature the competition could introduce to match Emby if Emby cracked intro-ship metadata in nfo. It’d be an absolute game changer.

[TMCsw 180]

I really think this is necessary as over the years I’ve accumulated about 8000+ recordings that until recently they are saved in a .ts container (lately I use ScripterX to convert them (in parallel) to .mkv (for nearly instant FF/REW) and strip all unnecessary tracks and add an AAC stereo track (so I can easily speed up playback).

Now I’m converting the old files in the same way but the intro’s are slightly off because of this. (so is comskip)

If the intro skip was saved in the .nfo, I could easily strip it out with the same script that is converting the files and then emby would see this (.nfo change) and run into skip accordingly.

As it is now intro skip is the most time consuming part of scanning in media (assuming that everything else is saved beside the media (Yes I delay intro skip and .bif file generation for quick scanning) as I have to remove this files from the lib then put them back to get a intro skip rescan.