You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forgive my inquiry if this has already been discussed...
Does the overhead of implementing this server/client/web sockets scenario show degradation in overall "real-time" consumption/transcribe/translation/display performance compared to a solution that contains all functionality in one script base?
This solution is terrific, but for "single client" needs, is this overkill and potentially slower?
The text was updated successfully, but these errors were encountered:
Hello, if you run everything locally the extra latency is negligible (maximum 10ms), most of the latency is consumed by the actual transcription process.
Forgive my inquiry if this has already been discussed...
Does the overhead of implementing this server/client/web sockets scenario show degradation in overall "real-time" consumption/transcribe/translation/display performance compared to a solution that contains all functionality in one script base?
This solution is terrific, but for "single client" needs, is this overkill and potentially slower?
The text was updated successfully, but these errors were encountered: