This seems useful, let us know if it works for you
Was too curious and tired it. Does not work, the media scanner just quits/crashes.
But I set the scheduled maintenance to midnight, so its just an hour wait for me to see how the process goes 
The comment was meant in an affectionate wayâŠ
From what Iâve seen it really comes down to the initial scanning taking quite some time and Plex doing the scans sequentially. So you can easily run into episodes/seasons that have not yet been processed. Similarly you might experience that Plex isnât processing your manual action if itâs already processing shows.
Give it a moment.
I had the luck to play around with it for some days and itâs really a great addition. (of course you could have skipped ahead / fast forwarded manually⊠but itâs just so much more convenient
).
The usual⊠release has been pushed but not yet distributed to every connected client in that platform. I remember when Google took its time to pass those Plex for Android updates along.
Ah a shame. I will just set my scheduled task interval to run on a 23 hour interval so that it runs. Otherwise, on the default 3 hour interval, I think it would take over a year to go through my entire backlog as just a butler task.
I didnât throw your flowers in the trash - they went in a vase, you silly manâŠlol
Iâm just quietly looking up from my knitting to tell ya - it ainât workinâ.
⊠and I guess I can be glad itâs only not working, 'cause I guess it could be a LOT worseâŠ:
Iâm a firm believer in letting somebody know when something isnât working.
I wouldnât consider those guys to be âfear mongeringâ to report an unexpected behavior associated with this new feature (like when their server blows up), but maybe Iâm old fashioned.
Well, I went and took a nap, got up and itâs working for me now on both the
Roku and webapp. I didnât make any changes except walk away from it
for 2 hours. Maybe there is some additional internal record keeping that
PMS needs to do even after the progress circle starts spinning, I dunno.
I have a relatively fast CPU (8-Core AMD FX-8350) and the processing
of a 20+ episode season of âThe Wonder Yearsâ took just a couple of
minutes at most. Iâm letting the rest of my TV shows process normally
in the overnight updates.
Great feature, thanks Plex team.
So except for you, everybody else got it working. Itâs noticeable that you constantly draw conclusions from yourself to the general public.
Good idea with the 23 hour time window (Midnight to 11pm).
It seems to me that PMS can detect chapters in video files named âintroâ, âopâ and âopeningâ and such as markers, as some of my shows already started working without a long analysis phase. So I hope it does not have to spend several minutes for each show deep-scanning its files 
On âolderâ shows without these markers in the video file the server activity window showed a distinct âdetecting introâ activity and this took notably longer. This was notably missing in the above mentioned case (i.e., the analysis was just swiftly finished).
Iâve only seen mine running the Detecting Intros task. It roughly takes around 10 minutes per season, even on a Threadripper 2950x
I have been able to troubleshoot some of my issues down to folder structure/naming issues.
For example, for the HBO Rome series, I had a folder inside of Season 1 folder, which contained the season 1 files. It did not cause any issues within Plex; however, it effectively blocked the skip tv detection. As soon as I updated the folder structure to what Plex was expecting, bingo, skip tv detection worked.
This explains the hit or miss nature of the analysis going on. 
For real? For me it took about 2 mins per season on an old intel pentium j5005. ![]()
I am really surprised how well the feature works after a few small difficulties at the beginning. Top work!
The analysis complexity does seem to vary.
After I hit âanalyzeâ on the whole library, which currently does not trigger the deep intro analysis (took juts a few minutes), the âskip introâ started working for several shows. For other shows, even such with chapter markers in the MKV file, Plex needed a dedicated and longer âDetect introâ phase which takes a couple of minutes, before âskip introâ started working.
My tested shows also took between 1 and 4 minutes per show (Xeon E3-1225 V2).
EDIT: Maintenance and intro analysis has started. Some shows are finished in seconds time, while for other shows, the âPlexTranscoder.exeâ and âEasyAudioEncoder.exeâ start running during a longer âdetect intro phaseâ â maybe PMS needs to transcode/re-encode some files/shows into others formats before it can start detecting intro markers?
EDIT 2: The PMS analysis started at midnight and was completed by approximately 12 oâclock, so it took 12 hours to detect all intros. Overall, I find this implementation by Plex quite efficient (although CPU utilization during the heavy duty parts topped at ca 60%).
Not working for me either. Just crashes PMS and I have to restart it. Mine gets to about 90% I guess on the analyzing intros task under activity. Then PMS shuts down.
This is what happens every time my PMS starts the analyzation process. You can see it shows unreachable due to PMS Crashing.
is there any way we could manually add a timestamp for the skipping? for example in the metadata of the video.
Skipping only works on some content in my library. Personally I would just go ahead and add the rest manually.
Thanks!
You might want to check out the new update which contains fixes for the analysis/scanner crashing on old Windows machines
Thanks, will apply the update! Although I hope that the crash was more because I randomly tried to run the EXE file via command line. The server DID definitely do some extensive work without crash during last nights maintenance 
Make sure you are checking from the web app hosted by Plex by going to https://www.plex.tv and then clicking the launch button. If you check from the locally hosted web app on your server, you will not see this information even though it is there.
I verified this by checking a show I knew to have been analyzed and have the intro info and from the local web app the info was not there but when I checked from the hosted web app it appeared.
And for reference, this is what the tag will look like:
<Marker filter="theme=63505" type="intro" startTimeOffset="63509" endTimeOffset="152240"/>
-Shark2k
You edited that as I was typing.
You are also incorrect as I initially tested this on Full House, which has an opening segment before the intro and it properly identified intro for the show and the skip works as described.
-Shark2k
Dude, chill out. I was trying to help out with my response, no need for the attitude.
You could have easily said in your post, check out my edit for additional details.
Also, if I am not mistaken, the actual intro to 24 is fairly short.
Relevant info from the the support article:
- Short intros of less than 20 seconds are ignored.
Pretty sure that is why you are not seeing it for 24 hour.
-Shark2k
I removed that because it wasnât necessary for me to add, however RTFM has been used in the forum elsewhere.
And if you read the blog post about how it works, you would understand that the opening segment before the intro is not counted because it is not going to match the audio fingerprint they are looking for.
Plex made the decision to hard code ignoring shows that have an intro of less than 20 seconds for whatever reason. Maybe in the future they will make that changeable by the user, I donât know and canât say why.
However, there is also this relevant part in the support article:
- Intros ending more than 10 minutes into an episode will not be detected.
Which should cover most of what you are referring to in the edit.
-Shark2k
