Skip to content
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

Closed
meltiso opened this issue Sep 27, 2024 · 4 comments
Closed

Vision Module in "Stale" Mode Due to Mismatched Monitor IDs #369

meltiso opened this issue Sep 27, 2024 · 4 comments

Comments

@meltiso
Copy link

meltiso commented Sep 27, 2024

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:

2024-09-27T10:47:16.683910Z ERROR screenpipe_vision::core: Failed to get monitor with id: 330083. Exiting continuous_capture.    
2024-09-27T10:47:16.683956Z ERROR screenpipe_vision::core: Failed to get monitor with id: 20580179. Exiting continuous_capture. 

In the app settings under the monitors section, I see:

79825613. \\.\DISPLAY1 (default) - 1920x1080
63768545. \\.\DISPLAY2 - 1920x1080

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:

  1. Launch the Screenpipe app on Windows 11.
  2. Close Screenpipe completely
  3. Disconnect and reconnect an HDMI cable for one of the monitors (I don't know if this step matters).
  4. Relaunch Screenpipe.
  5. Go to settings -> monitors, and notice one of the monitor IDs have changed.
  6. Click update to restart the Vision and Audio modules.
  7. Open the logs and observe errors related to monitor IDs.
  8. Check that the Vision module is in "stale" mode, failing on both screens due to mismatched monitor IDs.

Expected Behavior:

  • The Vision module should be able to capture frames using the detected monitors.
  • The monitor IDs in the logs should match the IDs of the detected screens, allowing the Vision module to function correctly.

Actual Behavior:

  • The Vision module enters "stale" mode, failing to capture frames.
  • The logs show errors for monitor IDs that do not exist in the list of detected displays.

Environment:

  • App Version: 0.2.72
  • OS: Windows 11
  • Monitor Configuration: Dual monitors, both 1920x1080 resolution. One in HDMI.
Copy link

linear bot commented Sep 27, 2024

@meltiso
Copy link
Author

meltiso commented Sep 27, 2024

I realized that even though only two screens show up in the list, Screenpipe is counting a total of four screens. I didn’t select the two screens I mentioned in my original issue, which I just noticed.

After selecting those two screens, the total reaches four, and the Vision module status changes to ok. However, we still see errors in the logs related to the screens that aren’t in the list but are included in the total count.
{A49EE733-8860-4995-BDEB-53CD2822185A}
{B947CDD5-B9D1-46D7-B856-CA13A1A0CA65}

@louis030195
Copy link
Collaborator

@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

@meltiso
Copy link
Author

meltiso commented Sep 27, 2024

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants