AutoSubs does not open inside DaVinci Resolve Studio

[Suyash-Pokharel]

Currently I am uisng DaVinci ReIsolve Studio Version: 19.0.0.0069 and i have installed AutoSubs in my D drive inside Davinci Resolve so that I could find it when needed. But when I open AutoSubs from Workspace > Script > AutoSubs V2 it does not open at all.
And when I opened the console, it says:
"Operating System: Windows
...i Resolve\Support\Fusion\Scripts\Utility\AutoSubs V2.lua:626: An attempt was made to access a socket in a way forbidden by its access permissions."
When I open OpenSubs.exe file, it says "Failed to connect to Resolve"
What should I do?

[steveroot]

I'm new here and just came across the same problem.
Potentially we could solve this by going back to DaVinci 18, hinted by this reddit post:
https://www.reddit.com/r/davinciresolve/comments/1gpo20i/191_broken_scripts_megathread/?rdt=40553

Key words from that post:
_In the last 24 hours, BMD announced Resolve 19.1. (release notes thread)

This had the unfortunate side effect of breaking UI functionality for scripts in the free version - including Reactor. At the moment, it appears to be intentional, but I'm waiting to hear from another source to confirm.

From Andrew Hazelden at WSL:

Service Notice: BMD has decided in Resolve (Free) v19.1 to remove access to the UI Manager GUI scripting library from Lua and Python scripting. UI Manager access is now a paid feature that is part of Resolve Studio/Fusion Studio v19.1 only.
Hint: The Reactor Package Manager is a UI Manager based Lua script that will no longer run in Resolve (Free) v19.1_

I'm travelling with low bandwidth so can't try reverting to Resolve version 18 for another week

[steveroot]

Home early!
So I've just bought Resolve Studio, installed it, and now AutoSubs is working perfectly

Therefore, I think the issue is v19.1 removing access to UI manager in the free version of Resolve.

[vadyxac]

search for apps which use ports 56001 and 56002 by command:
Get-Process -Id (Get-NetTCPConnection -LocalPort 56001).OwningProcess
it will tell you process which you have to kill or give error if there is no such
and close them

[YourAverageMo]

this solution worked for me:

#316 (comment)

[tmoroney]

This issue was opened against an older version of AutoSubs. The project has been completely rewritten since then — please update to the latest version as this is very likely already fixed. If you're still experiencing this on the latest version, please open a new issue with updated logs.

---

Generated by Claude Code