EmbyVision OCR GPU Edition, CPU Edition Credits Detector new plugin: Beta

[EncryptedCity 18]

Hello Everyone, I am happy to announce that there is now a Beta version plugin that will detect credits in TV Shows. I originally posted in tools and utilities however since then I have made several improvements to the plugin. The plugins I posted in the tools and utilities were very early versions of EmbyVision OCR. They do support H264 and HEVC files but the latest version of this plugin now supports AV1 as well with CPU and GPU. I developed the software mostly for myself because of my large av1 library and limited tools available that will detect AV1 files for credits. I decided to share it because it is such a cool development.

I realize that this may not be the only credits detector plugin and you are probably wondering, why you should install my version and test it vs the other? Because watching end credits is boring for most!

The original docker containers for the tool are on GitHub. Pease see the posts in tools and utilities for information on installation and also there is installation instructions inside the plugin for the CPU and GPU docker containers. They use the same plugin.

I have also used them with the original in store plugin for OCR detection. They are on GitHub and they do work with the plugin in the Emby forum however it is recommended to use them with my new plugin as it has been designed to work efficiently with them. This image is the OCR Detection working on AV1 files which is mostly what my library is composed of due to my transcoding them to AV1 with my Tdarr and handbrake method.

It's easy to get started. I quite busy and I am not sure how much support I can offer for this plugin but you can find help in the debug logs and they will help you configure the plugin. it  runs on Default settings for most servers. You will need docker for this. 

Feel free to leave comments and post your experiences with the plugin or ask for help,  if I can't get to answering in time surely other people will be able to help you if you have questions. There is lots of documentation. Please read through it. The software also works well on Unraid.

Thank you. Please watch the video. I uploaded one.

EmbyVisionCredits.dll

Edited Thursday at 03:00 AM by EncryptedCity
video

[yocker 1784]

That looks like a reskinned EmbyCredits?
Not that i mind, would just like to know for clarification sake.

Edited Thursday at 03:27 AM by yocker

[EncryptedCity 18]

It’s a fair question. It may look similar because it started from the same general idea and builds on the EmbyCredits concept, but it has been heavily modified and expanded. There are new components, including the OCR service, GPU/CPU OCR support, different detection options, new configuration, and a lot of changes under the hood. The detection engines have also been designed and developed from scratch rather than simply being copied over or rebranded.

I’m a little surprised you were able to reach that conclusion only 23 minutes after the post went up though, since the documentation and changes are fairly extensive. I’d be interested to know which parts you looked at that made it appear to be just a reskin.

[EncryptedCity 18]

EmbyVision OCR GPU Edition, CPU Edition can also be installed alongside the original EmbyCredits plugin, so users can run both independently if they want to compare functionality or migrate at their own pace. You can also install both the CPU and GPU containers simultaneously. 

[EncryptedCity 18]

I wanted to share a quick demonstration of the progress so far. The credits detection is working extremely well and is detecting credits across my library with a very high success rate.

In this video, you can see the detection process running and finding credits successfully. The only ones being skipped are items that already had credits markers detected previously, which is expected behavior.

This is a huge step forward, and I’m excited to keep improving it with more testing, optimizations, and additional features.

 

 

[yocker 1784]

47 minutes ago, EncryptedCity said:

I’m a little surprised you were able to reach that conclusion only 23 minutes after the post went up though, since the documentation and changes are fairly extensive. I’d be interested to know which parts you looked at that made it appear to be just a reskin.

Because it's not really hard to spot the similarities.
Many of the UI elementals are precisely the same. Even the tracer feature which i gave that name because i thought it would be a fun and original name to give it.


This is from EmbyCredits.
Plus many more examples.

As said, i don't mind. Just want clarification if it's EmbyCredits underneath.
 

[EncryptedCity 18]

Thanks for clarifying. I understand why some similarities stood out, especially with the UI elements and the tracer naming.

To answer your question: yes, it started from the EmbyCredits foundation, and I should have been clearer about that relationship. The goal was never to present it as if the original concept came from nowhere or to hide the connection. It was developed as an extension/evolution of the idea, while also remaining compatible with the original plugin.

A lot has changed since then. The OCR service, CPU/GPU OCR support, detection engines, processing logic, configuration system, and many other components have been redesigned, rebuilt, or expanded. The detection engines themselves were developed from scratch rather than simply being copied over.

The backend is also completely different in terms of architecture. It now uses dedicated Docker OCR services:

• CPU OCR Edition: ~1.89 GB container image

• GPU OCR Edition: ~8.34 GB container image

• Separate CPU and GPU endpoints

• GPU edition uses CUDA acceleration with PaddleOCR

• Dedicated OCR microservice architecture instead of relying only on the plugin process

It was also listed under Tools & Utilities because these services are designed to work with EmbyCredits as well. Users can use the OCR services with the existing plugin or use the expanded project alongside it. Both can be installed simultaneously.

The tracer naming similarity is a fair point — I should have picked a more unique name there to avoid confusion.

I appreciate you bringing it up. Hopefully this clarifies that this is not simply a reskin, but an expanded implementation built from the original concept with a significantly different backend and additional functionality.

https://github.com/encryptedcity/embyvision-ocr

https://github.com/encryptedcity/embyvision-ocr-gpu

[yocker 1784]

2 minutes ago, EncryptedCity said:

Thanks for clarifying. I understand why some similarities stood out, especially with the UI elements and the tracer naming.

To answer your question: yes, it started from the EmbyCredits foundation, and I should have been clearer about that relationship. The goal was never to present it as if the original concept came from nowhere or to hide the connection. It was developed as an extension/evolution of the idea, while also remaining compatible with the original plugin.

As said i don't mind, EmbyCredits is made under the MIT license so you can basically do with it what you want. I just wanted to know if it was at least originally EmbyCredits.
Open Source would have been good though.
 

[EncryptedCity 18]

Progress so far after running about an hour.

[EncryptedCity 18]

6 minutes ago, yocker said:

As said i don't mind, EmbyCredits is made under the MIT license so you can basically do with it what you want. I just wanted to know if it was at least originally EmbyCredits.
Open Source would have been good though.
 

To be fair, I probably wouldn't have started this project if it had already met the needs I was trying to solve. I wanted reliable OCR support, dedicated CPU/GPU services, improved detection, and a different architecture, so I ended up building those pieces myself. It wasn't about replacing EmbyCredits for everyone—it was about solving the problems I was running into and then sharing the result with the community.

[Neminem 1819]

Copy Cat

[EncryptedCity 18]

To everyone following this discussion,

I want to address the recent comments and explain why I've decided to stop posting plugin updates on this forum.

Recently, I've been accused of being a "copycat" and of simply reskinning someone else's plugin or software. I strongly disagree with those accusations. If someone believes there are technical similarities, they should provide evidence and discuss the matter respectfully instead of making repeated public accusations.

I've been a member of this community since November 2021 and have shared my work here in good faith. My goal has always been to contribute, learn, and improve my projects based on constructive feedback. Unfortunately, the discussion has shifted away from technical topics and toward personal attacks, which isn't productive for anyone.

I'm always open to bug reports, feature suggestions, and technical criticism. Those conversations help developers improve their work. What I won't continue to engage with are repeated accusations and attempts to discredit my work without clear supporting evidence.

Because of how this situation has unfolded, I've decided that I will no longer be posting updates for my plugin on this forum. This wasn't a decision I wanted to make, but I no longer feel that continuing to contribute here is worthwhile under these circumstances.

I want to sincerely thank everyone who has downloaded my plugin, tested it, reported issues, suggested improvements, or offered encouragement. Your support has been greatly appreciated.

I hope future discussions on this forum remain respectful and focused on technical collaboration rather than personal disputes.

Thank you, and I wish the community all the best.

Edited Thursday at 04:54 PM by EncryptedCity

[RedNo7 6]

@EncryptedCity

I read  @yocker's questions as being polite and respectful; I honestly didn't read it as an accusation (which implies a level of impropriety) but more as a fair question given they're the dev behind EmbyCredits and there are similarities to both.  I also think that @Neminemwas just being playful.

I'm new here, don't know anyone, and am looking forward to trying both plugins out.

[crusher11 1245]

3 hours ago, EncryptedCity said:

 If someone believes there are technical similarities, they should provide evidence 

 

Here's evidence:
 

15 hours ago, EncryptedCity said:

To answer your question: yes, it started from the EmbyCredits foundation

 

[yocker 1784]

Just to be 110% clear!!
People can do what ever they want with my plugins, they can even call it their own and start taking money for it if they want.
I was just curious if it was based on EmbyCredits, nothing else!

I know @Neminemdoes nothing but help people on this forum, he just made a miscalculated joke.

@EncryptedCityNot that you need it, but you have my permission to build upon EmbyCredits. It's also MIT license so everyone can do what ever they want.
I'm extremely happy when something i made can be used by others in what ever way they like.
My TimeMarkEdit is also build upon a nother plugin (ChapterAPI) so i know how it feels to want to improve something.

That should hopefully clear everything up.  

[EncryptedCity 18]

I appreciate the clarification from everyone. To be clear, yes, EmbyCredits was the starting point in the sense that it was the existing project I wanted to remain compatible with. That was the reason for using it as a reference point — so the new services could work alongside it and be useful to existing users, including users who may want to migrate slowly to another solution if they have AV1 content or other specific needs like I do.

It was never intended to imply that the entire concept of credit detection belongs to one project. Detecting credits in media is a general problem, and different implementations can approach it in different ways.

The reason I created this was to build a different architecture with the features I wanted: dedicated OCR services, CPU/GPU editions, Docker-based backend services, new detection engines, expanded configuration, and a more flexible workflow.

I also want to emphasize that compatibility was part of the goal from the beginning. The OCR services can be used with EmbyCredits, and users can run both projects side-by-side if they choose.

I appreciate the questions because it gives me a chance to clarify the relationship properly. That said, I think I have explained the history and intentions clearly, so I will be stepping back from further discussion on this thread. I’ll continue focusing on development and supporting users through the appropriate channels.

[EncryptedCity 18]

EmbyVision Credits – OCR Edition | Major New Release!
I’m excited to release a brand-new version of EmbyVision Credits, with some pretty major advancements under the hood! This release has been heavily reworked to deliver extremely reliable credit detection, with testing achieving close to 100% successful detection, while combining multiple detection methods to make the results smarter and more accurate. The plugin now uses advanced PaddleOCR detection, keyword matching, character-density analysis, episode-to-episode comparison, black-frame detection, audio fingerprinting, automatic episode learning, confidence scoring, and intelligent timestamp refinement to determine where credits actually begin. It also learns from previously processed episodes to improve detection across an entire series. On top of the detection improvements, the UI has received a huge overhaul, with a cleaner, more modern interface, organized collapsible settings, improved library/show/episode selection, detailed detection results, confidence percentages, playback previews, editable timestamps, chapter-marker support, API tools, tracing, notifications, Auto Skip, OCR enhancements, and much more. The goal is simple: make credit detection something that just works, without constantly having to babysit it. Honestly, after fighting with this thing for a long time, I think I've finally built one that actually works properly and works nicely . This is a completely different level from the earlier versions, and there is a lot going on behind the scenes that isn't immediately visible from the UI. If anyone has questions, runs into an issue, or wants to know how any of the detection systems work, feel free to reply to this post!  

I’ve decided not to post the new DLL just yet.

The new version of EmbyVision Credits has undergone some major improvements under the hood, including significant improvements to credit detection reliability and a much more refined user interface. I’m very proud of the progress and want to make sure the release is properly tested before I put it out there.

That said, some of the recent comments have taken the enjoyment out of sharing the work, so I’m going to take a step back and release it when I’m ready rather than rushing it.

The project isn’t abandoned, and development is continuing. I simply want the next release to be something I’m happy to put my name on.

Thanks to everyone who has provided constructive feedback and supported the project. It is genuinely appreciated.

I am happy to provide a video demonstration for the community showing results, it will be posted below. 

[EncryptedCity 18]

On 8/6/2026 at 1:42 PM, RedNo7 said:

@EncryptedCity

I read  @yocker's questions as being polite and respectful; I honestly didn't read it as an accusation (which implies a level of impropriety) but more as a fair question given they're the dev behind EmbyCredits and there are similarities to both.  I also think that @Neminemwas just being playful.

I'm new here, don't know anyone, and am looking forward to trying both plugins out.

I appreciate you taking the time to explain how you interpreted the comments, and I understand that you’re new here and may not have the same context surrounding the discussion.

That said, I think it’s important to distinguish between how a comment was intended and how it was actually received. From my perspective, the combination of the questions and comments directed at me did not come across as playful or simply curious. It felt personal and targeted, particularly given the wording and the context in which the comments were made.

I have no issue with someone asking whether EmbyVision Credits is based on EmbyCredits. That is a perfectly reasonable question, and I’ve already answered it. What bothered me was the way the discussion developed afterward.

I also appreciate that Yocker has clarified that he was simply curious and that he considers Neminem’s comment to have been a miscalculated joke. I can accept that clarification. At the same time, I think I’m entitled to say that I didn’t find the joke funny and that the overall exchange left me feeling singled out.

I’m not looking to start an argument with anyone. I’ve put a tremendous amount of time into developing EmbyVision Credits, including the new OCR version and the substantial improvements in the upcoming release. I simply want the work to be discussed on its technical merits rather than turning the conversation into something personal.

No hard feelings toward you personally, and I appreciate you sharing your perspective. I just wanted to explain why I reacted the way I did.

I also want to clear up one other point, because I think there may be a misunderstanding here.

Nobody is taking Yocker’s plugin, repackaging it, or trying to sell it under a different name. EmbyVision Credits is my own project, and I have been developing it independently with my own approach, code, features, detection methods, OCR integration, and user interface.

There are certainly similarities in the overall purpose because both plugins are designed to deal with credits detection, but that doesn't mean one is simply a copy of the other. I have made a lot of deliberate design choices of my own as well. For example, I chose not to include a prominent donation button in the interface. That's simply my preference for how I want my plugin's UI to look and function.

I have no problem with people comparing the two projects or asking reasonable questions about their origins. What I don't want is for people to assume that similarities in purpose automatically mean that one project is copying the other.

I'm happy to let the software itself demonstrate what EmbyVision Credits is and what I've put into it.

[RedNo7 6]

2 hours ago, EncryptedCity said:

That said, I think it’s important to distinguish between how a comment was intended and how it was actually received.

Totally understand - that's why I was trying to offer another perspective.  I only stated that I'm new to show that I do not have a personal connection with anyone in this thread i.e. my take was independent.

I was genuinely looking forward to trying out your plugin so hope you decide to release it at some point.

[yocker 1784]

@EncryptedCityI have tried to write a private message to you as i want to avoid any escalation of this issue but either i'm blocked or you have disabled being sent new messages.

Either way.
I suggest changing the 32 character GuID of the plugin as other wise running this plugin will clash with mine and cause problems if installed simultaneously.
Something that can be a problem troubleshooting as it's usually not the first thing that comes to mind.