All Activity

New beta 4.10.0.23 seems promising! Did a quick handful of searches and so far they all came back within ~15 seconds, some near instantly! I've got much more in-depth testing I will do later, but would love to hear from others.

I released version 1.0.0.1 today https://github.com/encryptedcity/EmbyVision-Credits Feedback, testing, suggestions, and bug reports are very welcome!

EmbyVision Credits – Advanced End Credits Detection for Emby I’ve been working on EmbyVision Credits, an advanced end-credits detection plugin for Emby. It automatically detects where end credits begin and creates Emby chapter markers, allowing Emby’s Auto Skip functionality to skip credits. What it offers PaddleOCR support — CPU & NVIDIA GPU Black-frame detection Audio analysis & fingerprinting Character-density detection Video/scene pattern analysis Episode learning and comparison Fuzzy keyword matching Adaptive sampling and smart frame skipping Detection options specifically useful for anime Series, season, and episode processing Dry Run, Tracer, and debugging tools Marker backup & restore Scheduled automatic detection Per-series, tag, studio, and library rules External PaddleOCR service with CPU/GPU editions The OCR service runs separately from Emby, with CPU on port 8000 and GPU/CUDA on port 8001. The project is actively being developed, with a focus on making credit detection accurate, configurable, and practical for large Emby libraries. GitHub https://github.com/encryptedcity/EmbyVision-Credits Feedback, testing, suggestions, and bug reports are very welcome! EmbyVision Credits — Detect. Analyze. Learn. Mark. Skip. — EncryptedCity EmbyVision_video_1.5_00059_.mp4

@vurtHi, please see here and let us know if it helps get you squared away: Corrupt Database Thanks.

@vurtIt looks like DB has gone corrupt. SQLitePCL.pretty.SQLiteException: Corrupt: database disk image is malformed Here is a how to Corrupt Database | Emby Documentation Never had to use it, so can't help you with that.

Hi, my emby docker in unraid is shutting down randomly. This is the log. text error warn system array login Info App: Loading Emby.Webhooks, Version=1.0.38.0, Culture=neutral, PublicKeyToken=null from /config/plugins/Emby.Webhooks.dll Info App: Loading MusicBrainz, Version=1.0.28.0, Culture=neutral, PublicKeyToken=null from /config/plugins/MusicBrainz.dll Info App: Loading StudioImages, Version=1.0.3.0, Culture=neutral, PublicKeyToken=null from /config/plugins/StudioImages.dll Info App: Loading BlurayMounter, Version=1.0.5.0, Culture=neutral, PublicKeyToken=null from /config/plugins/BlurayMounter.dll Info App: Loading DvdMounter, Version=1.0.2.0, Culture=neutral, PublicKeyToken=null from /config/plugins/DvdMounter.dll Info SqliteUserRepository: Initializing PooledDatabaseConnectionManager with pool size: 3 Info SqliteUserRepository: Sqlite version: 3.49.2 Info SqliteUserRepository: Sqlite compiler options: ATOMIC_INTRINSICS=1,COMPILER=gcc-10.3.0,DEFAULT_AUTOVACUUM,DEFAULT_CACHE_SIZE=-2000,DEFAULT_FILE_FORMAT=4,DEFAULT_JOURNAL_SIZE_LIMIT=-1,DEFAULT_MMAP_SIZE=0,DEFAULT_PAGE_SIZE=4096,DEFAULT_PCACHE_INITSZ=20,DEFAULT_RECURSIVE_TRIGGERS,DEFAULT_SECTOR_SIZE=4096,DEFAULT_SYNCHRONOUS=2,DEFAULT_WAL_AUTOCHECKPOINT=1000,DEFAULT_WAL_SYNCHRONOUS=2,DEFAULT_WORKER_THREADS=0,DIRECT_OVERFLOW_READ,ENABLE_COLUMN_METADATA,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_MATH_FUNCTIONS,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MALLOC_SOFT_LIMIT=1024,MAX_ATTACHED=10,MAX_COLUMN=2000,MAX_COMPOUND_SELECT=500,MAX_DEFAULT_PAGE_SIZE=8192,MAX_EXPR_DEPTH=1000,MAX_FUNCTION_ARG=1000,MAX_LENGTH=1000000000,MAX_LIKE_PATTERN_LENGTH=50000,MAX_MMAP_SIZE=0x7fff0000,MAX_PAGE_COUNT=0xfffffffe,MAX_PAGE_SIZE=65536,MAX_SCHEMA_RETRY=25,MAX_SQL_LENGTH=1000000000,MAX_TRIGGER_DEPTH=1000,MAX_VARIABLE_NUMBER=250000,MAX_VDBE_OP=250000000,MAX_WORKER_THREADS=8,MUTEX_PTHREADS,OMIT_LOOKASIDE,OMIT_SHARED_CACHE,SYSTEM_MALLOC,TEMP_STORE=1,THREADSAFE=1 Info SqliteUserRepository: Sqlite ThreadSafe: 1 Info SqliteUserRepository: Sqlite ThreadingMode: MultiThreaded Info SqliteUserRepository: Opening sqlite connection to /config/data/users.db. isReadOnly: False Info SqliteUserRepository: Default journal_mode for /config/data/users.db is wal Info SqliteUserRepository: PRAGMA cache_size=-65536 Info SqliteUserRepository: PRAGMA page_size=4096 Info SqliteUserRepository: PRAGMA foreign_keys=1 Info SqliteUserRepository: PRAGMA SECURE_DELETE=0 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 Info SqliteUserRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 Info SqliteItemRepository: Initializing PooledDatabaseConnectionManager with pool size: 5 Info AuthenticationRepository: Initializing PooledDatabaseConnectionManager with pool size: 5 Info ActivityRepository: Initializing PooledDatabaseConnectionManager with pool size: 3 Info ActivityRepository: Opening sqlite connection to /config/data/activitylog.db. isReadOnly: False Info ActivityRepository: Default journal_mode for /config/data/activitylog.db is wal Info ActivityRepository: PRAGMA cache_size=-65536 Info ActivityRepository: PRAGMA page_size=4096 Info ActivityRepository: PRAGMA foreign_keys=1 Info ActivityRepository: PRAGMA SECURE_DELETE=0 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 Info ActivityRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 Info NetworkManager: Detecting local network addresses Info NetworkManager: networkInterface: Ethernet eth0, Speed: 10000000000, Description: eth0 Info NetworkManager: GatewayAddresses: 172.18.0.1 Info NetworkManager: UnicastAddresses: 172.18.0.13 Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo Info NetworkManager: GatewayAddresses: Info NetworkManager: UnicastAddresses: 127.0.0.1,::1 Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.18.0.13","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}] Info ServerConfigurationManager: Saving system configuration Debug XmlSerializer: Serializing to file /config/config/system.xml Info App: Begin vacuuming SqliteItemRepository Info SqliteItemRepository: Opening sqlite connection to /config/data/library.db. isReadOnly: False Info SqliteItemRepository: Default journal_mode for /config/data/library.db is wal Info SqliteItemRepository: PRAGMA cache_size=-131072 Info SqliteItemRepository: PRAGMA page_size=4096 Info SqliteItemRepository: PRAGMA foreign_keys=1 Info SqliteItemRepository: PRAGMA SECURE_DELETE=0 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 Info SqliteItemRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 Info App: Completed vacuuming SqliteItemRepository after 1712ms Info App: Begin vacuuming SqliteUserRepository Info App: Completed vacuuming SqliteUserRepository after 2ms Info App: Begin vacuuming AuthenticationRepository Info AuthenticationRepository: Opening sqlite connection to /config/data/authentication.db. isReadOnly: False Info AuthenticationRepository: Default journal_mode for /config/data/authentication.db is wal Info AuthenticationRepository: PRAGMA cache_size=-65536 Info AuthenticationRepository: PRAGMA page_size=4096 Info AuthenticationRepository: PRAGMA foreign_keys=1 Info AuthenticationRepository: PRAGMA SECURE_DELETE=0 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DDL to 0 is 0 Info AuthenticationRepository: Result of setting SQLITE_DBCONFIG_DQS_DML to 0 is 0 Info App: Completed vacuuming AuthenticationRepository after 23ms Info App: Begin vacuuming ActivityRepository Error Main: Error in appHost.Init *** Error Report *** Version: 4.9.5.0 Command line: /system/EmbyServer.dll -programdata /config -ffdetect /bin/ffdetect -ffmpeg /bin/ffmpeg -ffprobe /bin/ffprobe -restartexitcode 3 Operating system: Linux version 6.12.54-Unraid (root@Develop) (gcc (GCC) 15.2.0, GNU ld version 2.45-slack151) #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 OS/Process: x64/x64 Framework: .NET 8.0.25 Runtime: system/System.Private.CoreLib.dll Processor count: 4 Data path: /config Application path: /system SQLitePCL.pretty.SQLiteException: Corrupt: database disk image is malformed SQLitePCL.pretty.SQLiteException: Exception of type 'SQLitePCL.pretty.SQLiteException' was thrown. at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3 db, Int32 rc) at SQLitePCL.pretty.SQLiteException.CheckOk(sqlite3_stmt stmt, Int32 rc) at SQLitePCL.pretty.StatementImpl.MoveNext() at SQLitePCL.pretty.DatabaseConnection.Execute(IDatabaseConnection This, String sql) at Emby.Sqlite.BaseSqliteRepository.Vacuum() at Emby.Server.Implementations.ApplicationHost.VacuumDatabase(BaseSqliteRepository db) at Emby.Server.Implementations.ApplicationHost.VacuumDatabases() at Emby.Server.Implementations.ApplicationHost.RegisterResources() at Emby.Server.Implementations.ApplicationHost.Init() at EmbyServer.HostedService.StartAsync(CancellationToken cancellationToken) Source: SQLitePCL.pretty TargetSite: Void CheckOk(SQLitePCLEx.sqlite3, Int32) Info Main: Shutdown complete Info LogManager: Disposing Logger ** Press ANY KEY to close this window ** Does anyone know how to resolve this? TIA.

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

they already got my money why would they?

Trakt Air Dates — Beta Tester Guide Plugin version 5.0.0.0 · Updated 9 August 2026 This plugin has been rewritten from the ground up five times, because of how complex it turned out to be. What sounds simple — show the right date — runs into the fact that Emby, TMDB and Trakt each handle dates differently, and that the episodes most in need of fixing are the ones Emby knows least about. Each earlier version worked until it hit something Emby's plugin system doesn't allow; the last one broke outright when TheMovieDb provider changed how it stores data, and no amount of patching would have saved that approach. It isn't perfect. The limitations below are real, and most of them aren't things I can code around — they're the boundary of what a plugin is permitted to do inside Emby. Within those limits, this is the best I've been able to manage, and the parts that do work have been tested. If you tested an earlier version: this was previously called Air Date Fixer. Same project, renamed to Trakt Air Dates now that Trakt — not TMDB — is where the dates come from. It installs as a separate plugin, so remove any old EmbyAirDateFixer.dll before using this one. The plugin icon will still show the old name for now — that's expected, and the name in Emby's plugin list is the one to go by. Please read the Limitations section before installing. It lists the cases where this plugin will quietly do nothing — knowing them up front saves you chasing a problem that isn't a bug. What it fixes US and Canadian shows air in the evening Eastern time, which is already the next day across Europe and anywhere further east. TMDB stores those broadcast dates as a bare date with no time or timezone, so Emby shows the episodes on the wrong calendar day for those viewers. Trakt publishes each episode's air time as a true UTC instant, so it converts correctly for any timezone. This plugin uses Trakt as the reference and corrects Emby's dates to match. Only US and Canadian shows are touched. British, Australian and European shows are left exactly as they are. Two halves, and they're independent Already-downloaded episodes Upcoming (not yet downloaded) How it's fixed Corrected directly in your library Served with corrected dates by a built-in listener Setup needed Just two API keys Keys plus a port change Works on Every client, always Every client that reaches the listener You can stop after the first half. Library corrections need no port changes and carry no risk. The port swap is only needed if you want Upcoming fixed on TV apps and phones as well as the browser. Pros No extra container, no compose changes. One DLL. Everything runs inside Emby. Upcoming loads instantly. The list is cached in memory and refreshed in the background — typically well under a millisecond, versus Emby's own endpoint which is occasionally very slow. If Upcoming has ever failed to load in an app until you opened the web UI first, this fixes that. Corrections stick. If a later metadata refresh overwrites a corrected date, the plugin notices and puts it back. Immune to TheMovieDb provider updates. An earlier version of this plugin worked by editing that provider's cache files, and broke completely when the provider stopped using them. This design never touches them. Survives Emby updates. Nothing is injected into Emby's web files, so an update can't wipe it. Recovers from port conflicts on its own. If the port it needs is busy, it keeps retrying and starts the moment it's free — no restart, no intervention. Fails safe. If Trakt is unreachable, the plugin can't start, or Emby is being slow, you get uncorrected or slightly stale dates — never an empty screen or a dead server. Cons and trade-offs Upcoming corrections require moving Emby's own HTTP port. Not difficult, but it is a change to your server's configuration, and you should be comfortable doing it. The plugin sits in front of your server. With the listener enabled, all client traffic passes through it on its way to Emby. That's the only way to reach not-yet-downloaded episodes — Emby has no plugin hook that fires for them — but it does mean a bug here can affect more than air dates. Changing the listener port can lock you out of the settings page. If you're viewing the dashboard through the listener's port and you change that port, the page disappears mid-edit. The way back in is Emby's own port — e.g. http://YOUR-SERVER:8098/web/index.html. Worth noting before you touch that field, not after. The first Upcoming load after an Emby restart is slow. The cache is empty and has to be built. Everything after that is instant. Upcoming data can be up to about five minutes old. Irrelevant for air dates, but worth knowing. Limitations — where it will do nothing These aren't bugs. If you're in one of these situations, expect no corrections. HTTPS traffic bypasses the plugin entirely. The listener is HTTP-only. If your clients connect over HTTPS (commonly port 8920), they reach Emby directly and see uncorrected dates, with no error anywhere. There is currently no workaround other than using HTTP on your local network. Remote/WAN access bypasses it unless your router's port forward points at the listener's port rather than Emby's. Otherwise, away-from-home clients get uncorrected dates. The Android app may drift back to Emby's real port. Emby's apps trust the address the server reports about itself, and Android re-checks it — so even after you type the listener's address manually, it can revert to Emby's real port on a later restart. When it does, everything works normally except that Upcoming dates are uncorrected, with nothing to indicate anything changed. To check: in the app, look at the server address under its connection/server settings. If it shows Emby's real port (e.g. :8098) rather than the listener's (:8096), that's why. Re-adding the server manually fixes it until the next drift. I've requested a "lock custom server address" option in the app — somewhere to tell it to keep the address you typed and stop switching to the one the server reports. Realistically I don't expect it to be implemented; the response so far has been that it would cause more problems than it solves and affects very few people. There is no server-side fix available to me. The plugin already reports the correct address, but the app also learns the real one through network discovery, and a plugin can't intercept that. Realtime features are under observation. The plugin relays the apps' live-updates connection to Emby. This is working in testing, but some earlier connection drops aren't fully explained. It doesn't affect dates, browsing or playback — potentially things like remote control and instant library refresh. Please report anything odd. Only US and Canadian shows are adjusted, and only by one day. Shows from elsewhere are deliberately untouched. Tested on Emby 4.9.5.0, in Docker, on Linux. That's it. Other versions and platforms are untested — which is rather the point of a beta, but please mention your setup when reporting anything. What you'll need A Trakt Client ID — from trakt.tv/oauth/applications. Free and instant. Only the Client ID; no login, no OAuth, no tokens. A TMDB API Key (v3 auth) — from themoviedb.org/settings/api. Free and instant. The TMDB key is needed because Emby's own metadata doesn't reliably record which country a show comes from — on the library this was built against, that field was empty for every show. The plugin asks TMDB directly and caches the answer permanently, once per show. Setup Part 1 — library corrections (no risk, no port changes) Copy TraktAirDates.dll into your Emby plugins folder and restart Emby. Dashboard → Plugins → Trakt Air Dates. Paste in both keys. Turn on Enable corrections. Save. Downloaded episodes start being corrected within about 30 seconds. If you only use a web browser, you're done. Part 2 — Upcoming on TV apps and phones Emby apps request the upcoming list by a fixed address that plugins aren't allowed to answer. The workaround is to have the plugin answer on the port your devices already use, and move Emby itself to a different one. Your devices don't change. On the settings page, turn on Enable native app listener. Leave the port as the one your devices already use — usually 8096. Save. Dashboard → Networking → change Local HTTP port number to something free, e.g. 8098. Save and restart Emby. Existing devices keep working with the address they already have — nothing to do. Adding a device after the port swap: don't let the app find the server by itself. Emby's automatic discovery answers with Emby's real port (8098), which goes straight past the plugin — the app will connect and work perfectly, but Upcoming dates won't be corrected and nothing will indicate why. Choose the manual / "add server by address" option instead and type the listener's address in full, e.g. http://192.168.0.160:8096. The same applies if you ever sign out and back in, or reinstall an app. Check it worked: the Native App Listener box on the settings page should be green and read "Active — listening on port 8096, forwarding everything else to Emby on port 8098." If it's red, see below. You don't need to read a server log. Running Emby in Docker Nothing extra for network_mode: host. If you publish ports explicitly (-p 8096:8096), that mapping keeps working — the plugin answers on 8096 inside the container and reaches Emby on 8098 internally. You do not need to publish 8098. Running Emby on Windows Windows restricts which programs may listen on a port. Emby normally runs as your user account, which isn't allowed to claim a port for all addresses — so the listener may fail with "Access is denied". That's Windows policy, not a plugin fault. Either of these fixes it: Run Emby as Administrator — simplest, but you have to keep doing it. Grant a one-off permission (preferred). In an Administrator Command Prompt, replacing the name with your Windows account: netsh http add urlacl url=http://+:8096/ user=%USERNAME% Then restart Emby. This persists, and doesn't require running Emby elevated. To undo it later: netsh http delete urlacl url=http://+:8096/ Running Emby on macOS or native Linux No special permissions needed for port 8096. Ports below 1024 would need elevated rights, but there's no reason to use one. Both are untested — reports welcome. Troubleshooting Red box: "Could not start on port 8096 … Retrying automatically every 15s" No rush — it will start on its own the moment the port is free, and the attempt counter shows it's still trying. Causes, in order of likelihood: Emby hasn't actually moved off that port yet — do Part 2 step 2, and make sure Emby restarted. A second Emby or Jellyfin container is running. Easy to miss, and cost a full afternoon during development. Two Emby containers on host networking will silently fight over the same port. docker ps -a — if more than one Emby container is running, stop the one you don't use, and set it not to come back: docker update --restart=no <container_name>. Something unrelated holds the port. On Linux: sudo netstat -tlnp | grep :8096. Confirming it's genuinely working: sudo netstat -tlnp | grep -E ':(8096|8098)' should show one process ID holding both ports — the plugin runs inside Emby, so they share a process. Two different IDs means something else has taken the port. I can't reach the dashboard after changing the listener port Use Emby's own port: http://YOUR-SERVER:8098/web/index.html. Set the listener port back from there. Dates are right in the browser but wrong in an app The app is probably reaching Emby directly rather than through the listener. Check the server address saved in the app — it should use the listener's port (8096), not Emby's new one. See the Android note under Limitations. Nothing is being corrected at all Check the Last Refresh box. If it reports 0 of N series matched as US/Canada, the TMDB key is likely wrong or missing. Remember only US and Canadian shows are adjusted. Upcoming was slow once, then instant Expected — see Cons. If an app gave up on that first load, open it again; the result is kept even if the app stopped waiting. Reporting a problem If there are TV shows missing from your Upcoming listing, please let me know and I'll do my best to fix it.Missing shows are just as useful to hear about as wrong dates — the plugin merges its own data with Emby's, and a show disappearing means something didn't line up. Please include: The exact text of any red status box — it's generated live from what actually failed. Your Emby version, platform, and whether you're using Docker. Whether your clients connect over HTTP or HTTPS, and locally or remotely. For a wrong date: the show, season and episode number, the date shown, and the date you expected. If you send a server log, please check it for access tokens before sharing publicly. Uninstalling Remove the plugin DLL and restart Emby. If you did the port swap, set Emby's port back to 8096 in Dashboard → Networking first — otherwise your devices won't find the server. Dates already corrected in your library stay as they are. They're ordinary Emby metadata now. TraktAirDates.dll Trakt-Air-Dates-Beta-Tester-Guide.pdf

List of movie and TV aspect ratios used from my AR page. Perhaps useful to Emby dev so you don't have to dig through many sites to find AR sizes in use. There are also several calculators that can help find different pixel reduction sizes for all AR's for transcoding, if needed. https://www.producerelease.com/blu-ray/parcalc.htm#partable

Error processing type MediaBrowser.Providers.CoverArt.CoverArtAlbumEnhancer: System.ArgumentNullException: Value cannot be null. (Parameter 'source') at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source) ... Error processing type MediaBrowser.Providers.CoverArt.CoverArtBannerEnhancer: System.ArgumentNullException: Value cannot be null. (Parameter 'source') Error processing type MediaBrowser.Providers.CoverArt.CoverArtBoxsetEnhancer: System.ArgumentNullException: Value cannot be null. (Parameter 'source') Error processing type MediaBrowser.Providers.CoverArt.CoverArtCollectionEnhancer: System.ArgumentNullException: Value cannot be null. (Parameter 'source') Error processing type MediaBrowser.Providers.CoverArt.CoverArtEpisodeEnhancer: System.ArgumentNullException: Value cannot be null. (Parameter 'source') emby 4.10.0.23 beta

Hi, new build is up. Please let me know if this resolves the issue. Thanks.

Thanks. Yep - 23 assets listed followed by assets....Hang on thats not 23, click on assets button - oops.

Hi @arrbee99the files are in the assets area here, for android tv you can use Downloader code 3752238 (google hasnt approved it yet), for tvOS its already released in the app store, iOS should be following shortly

Moonfin 2.4.0 seems to be out, but not seeing anywhere to download it (on Github releases page) ? - Nevermind, found it 30 seconds after I typed the above...

Hi, where did you copy them to?

Certainly!

Thanks for sharing.

I just tried 3.5.42 and I still have gray bars on HDR content Emby displays the video as 4K Dolby Vision HEVC. MediaInfo shows it as HDR10/HDR10+ It plays in Emby ATV without grey bars.

The more I look into it, the more it seems like its a flaw in the google 4k streamer device. There are a handful of threads floating around that complain about persistent stutter problems on other apps as well. I didn't notice much on other apps until I really started testing, but I did find some content on the youtube app began stuttering as well. Seems like the device is just not well designed. Shame, because its not cheap and I'll need to start looking for an alternate android device. Thanks for trying to help me fix it Neminem!

Make sure to include the total duration when submitting. Different film versions are differentiated based on the duration, which allows you to submit multiple times.

Do you include video duration when submitting segments? Segments can overlap if the duration is different and that at least always worked for me.

@PasitheaI just wanted to let you know of a small flaw with the introdb submissions. When there is multiple versions of a movie I cant submit times for all versions. I get a message saying For example Terminator 2 has many versions. Specifically it has the Special Edition and the Ultimate Cut. With the difference in total length of the movie being around 3 mins between them. So the credits play in different spots. I cant add the timestamps for the Ultimate Cut because it seems to be too close in time to another submission I made. Hopefully I explained this well Thanks

@Luke I would love to see this improved

Is there a GitHub repo with the source code? I don't install plugins unless I can see the code.