"Starting Transcription server"

[Espanitaes]

Cannot do anything as the "Start Process" button keeps with the "Starting Transcription server" message.. and not possible to start the subtitles generation :(

Thx for the app. I tried it on my laptop and worked nice, but on my regular PC is giving me this problem

[tmoroney]

Not sure what is causing this, so can you follow these steps to help me debug:

1. Right click in AutoSubs and click "Inspect Element"
2. Click "Console" at the top of the new window.
3. Send a screenshot of what it says

[theoghn]

I have the same issue, here you can see the logs

[ihubgit]

i also have the same issue on ARM mac running Sequoia and DR studio 19.1.3, albeit with a different console error :

[TumaHD]

Same problem here

[TobiasWust]

I do have a clue. I think it's a problem, that I already had python installed before.
If I looked ad workspace->console and clicked on py3 I got the error, that python was not found.
I followed these instructions https://alexthecreative.com/python3-davinci-resolve-19-console-not-found/#:~:text=The%20Solution&text=If%20you%20didn't%20install,to%20your%20current%20python%20installation.
to symlink my python path ( in my case sudo ln -s /Users/wust/.pyenv/shims/python3 /usr/local/bin )
After that I can see in the python console, that a server is starting:

Operating System: OSX
Main App Path: /Applications/AutoSubs.app	
AutoSubs launched successfully.
AutoSubs server is listening on port: 55010	
Received request:{"func":"GetTimelineInfo"}	
[AutoSubs Server] Retrieving Timeline Info...

But the frontend still has problems connecting to it, even though it does get the PID at first, but then crashes (like in the screenshots from tumaHD
but exits with [Log] Transcription server exited with code 1 and signal null (index-RmK9l6ed.js, line 385)

thats all I found. @tmoroney let me know if I can help with any other information.

[tmoroney]

i also have the same issue on ARM mac running Sequoia and DR studio 19.1.3, albeit with a different console error :

Fixed now

[tmoroney]

Same problem here

Fixed now

[tmoroney]

I have the same issue, here you can see the logs

This issue is likely caused by something else already running on port 56001 so check what is running on it using this terminal command:

lsof -i :56001

You can kill that process by taking the PID from the output and putting it in this command where it says <PID>

kill -9 <PID>

[TobiasWust]

Thank you for the quick fix 🎉