How does scanning episode intros work?

[GeneralTsoSo 5]

Over the past two weeks, I've been trying to understand how the scanning episode intro function works.

When I run the process manually, it seems that it begins scanning all of my library again. I've tested this multiple ways and I can't seem to wrap my head around how it works. I would think that it would detect episode intros already processed and just worry about the newly added content. And I swear that this is how episode intros functioned about 2-3 versions ago.

Tests:

1. This is the first scanning attempt after adding a few pieces of content. This first initial scan (since I haven't done it in a while) took about 3-3.5 days. Once complete, I did a metadata backup, and ran the scan once more. Expecting the scan to finish quickly because it already ran once, it completes another scan in 3-3.5 days.

2. No new added content and manually enabled scan episode intros. Again, another 3-3.5 days of scanning.

3. One new piece of added content. Manually enabled intro scanning which again took another 3-3.5 days.

4. After the third test, I decided run test two again, and same result. The scanning took an equal amount of time as the previous tests.

What am I not understanding about this function? Why does it seem do a full scan, and not just detect what has been newly changed and work on those?

Thank you!

[Happy2Play 9780]

Without logs it is hard to say as I know all my daily scans take about a minute.  But don't have the Detect Intros task run during library scans.

New/Clean install probably about 3-5 days as you will be throttled per provider.

But as for episode intros it can be an extremely long process depending on how much media you have.

But if every scan is taking the same about of time there is something going on with your specific setup.  May have to elaborate on your library setup also.

 

 

[GeneralTsoSo 5]

I have attached a log for anyone to review. I am seeing many errors that seem to be related to the intro scanning function. However, I'm not super sure.

Would this potentially require a rebuild of Emby, something I can review in Ubuntu, or something else?

Thank you!

embyserver-63886320000.txt

[GeneralTsoSo 5]

I have reviewed my logs further and searched "Info FfmpegManager: ProcessRun". It seems that it references which shows/episodes are experiencing the error.

Am I understanding this correctly? If so, any thoughts on a potential solution? Removing the problematic file, or changing something about the file?

Thank you. 

Edited June 25, 2025 by GeneralTsoSo

[GeneralTsoSo 5]

I have resolved my issue.

There were a few problematic shows that were getting hung up in processing intros when reviewing the logs with debugging.

I removed the shows, and the intro scan now scans in seconds, confirming that other episode intros have been completed.

@LukeApologies for tagging you. But I have a quick question about my solution. 

Is it possible to have content excluded from a scan, namely the problematic content found in logs?

Thank you.

Edited June 25, 2025 by GeneralTsoSo

[Luke 42078]

HI, yes we can look at improving this. Thanks.