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
Debugging voice issues is currently very difficult with Discore. It's pretty much impossible to determine why exactly audio-playback skips, speeds up, or freezes without modifying Discore itself.
Users should be able to opt-into receiving diagnostic information from voice connections. With this information, users should be able to determine:
If their application is sending voice data too slowly or too fast.
If their application is not sending voice data consistently (causing breaks in the playback).
If Discore is unable to send voice data consistently.
If Discore is sending voice data too slowly.
Information that needs to be exposed (note: this list is incomplete):
Frame send-rate (to determine consistency issues)
Whether the socket is trying to catch up (to determine consistency issues)
When the socket skips a frame (to determine if the application isn't giving Discore data quick enough)
The text was updated successfully, but these errors were encountered:
Debugging voice issues is currently very difficult with Discore. It's pretty much impossible to determine why exactly audio-playback skips, speeds up, or freezes without modifying Discore itself.
Users should be able to opt-into receiving diagnostic information from voice connections. With this information, users should be able to determine:
Information that needs to be exposed (note: this list is incomplete):
The text was updated successfully, but these errors were encountered: