Question about 'markers' and manipulating them

Hi, so I understand there are skip markers for intro and credits. And also there is a module for commercial skipping too.

I noticed in the recent API docs that there are ways to set custom “markers” with timestamps. Can these custom markers be skipped by the user? If not what exactly are they for?

https://developer.plex.tv/pms/#tag/Library/operation/libraryMetadataPostMarker

I was wanting to try and build a bot for fun that analyses Jeopardy episodes and generates a skip marker for the interview segment (ideally with a custom button of “skip chit-chat”). The analyser component could use the same pattern matching software as what Plex uses for commercials, intros and credits, or perhaps AI recognition.

If you set the markers at intro, they can be skipped like the Plex generated intros.

Plex actuality scans for these using separate tricks, not sure AI is good enough yet to know what is “chit-chat”.

Ok so I need to hijack the intro marker, I can’t create custom ones?

Oh yep I also intend to use tricks/heuristics. I have some ideas on how to bookend the interviews programmatically without requiring a bot to literally understand the speech as chit-chat.

Just to add to this. There appears to be 5 “marker” types total:
“intro”, “commercial”, “bookmark”, “resume”, and “credit”.

Intro, credit and commercial all seem simple enough, but does anyone know what “bookmark” and “resume” do? I added a random “bookmark” marker to an episode and nothing seems to have changed.

Thanks Finn for testing. So close! Would’ve been almost perfect for it to show a “Skip Bookmark” button. Perhaps its just a non functional placeholder value.

Might have to settle with a commercial marker for my purposes.

Hopefully also if “Analyse” is ever run, it doesnt remove custom marlers. Ill have to test.

The Plex API has some stuff that was merely “envisioned” when it was put together, but was never fleshed out as a feature. Bookmarks are one such instance. You can put them into the server database alright using the API. But to actually use them, they would need clients supporting them as well.