-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vision Module in "Stale" Mode Due to Mismatched Monitor IDs #369
Comments
@meltiso one of the known issue is that when you have for example 2 monitors and disconnect one it will still show 2 instead of 1 this shouldn't affect the program, just one thread will fail to capture this missing monitor and rest of the program keep going i will try to solve this soon |
@louis030195 Didn't know it was an ongoing issue. Thanks! 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
At app launch, the Vision module enters "stale" mode with the status
frame: stale, audio: ok
. Upon checking the logs, the following errors appear:In the app settings under the monitors section, I see:
The monitor IDs in the logs don't match the ones detected in the settings, which seems to be causing the Vision module to go stale, as it can't use the detected monitors.
Steps to Reproduce:
Expected Behavior:
Actual Behavior:
Environment:
The text was updated successfully, but these errors were encountered: