-
Notifications
You must be signed in to change notification settings - Fork 189
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
Prismatik not lighting up the LEDs (No screens with widgets found) #611
Comments
I have had this working when I was on a 1080p monitor and I can see the LEDs sometimes lighting up as well but as soon as I switch to screen grabber mode now with the new monitor, something goes wrong and I can't make the other modes also work after that somehow. Not sure what is happening as soon as I shift to the grabbing mode. |
@psieg any inputs as to why this can occur? |
Does it work if you bulid from the 5.11.2.31 commit (5044e21)? I only have Windows available to test, what we are missing is fixing the coordinate system here: Lightpack/Software/grab/X11Grabber.cpp Line 75 in 97955fe
Can you try copying the logic from here: Lightpack/Software/grab/GrabberBase.cpp Line 180 in 97955fe
before comparing the widget rect with the screen rect? #574 has some more details, in particular https://doc.qt.io/qt-6/highdpi.html |
Or maybe X11 has an equivalent to what Desktop Duplication does, so we don't need to do coordinates math: Lightpack/Software/grab/DDuplGrabber.cpp Line 224 in 97955fe
|
The problem is first I want to understand that even if that doesn't work, why are the other methods also failing? ( The moodlamp one for e.g ) |
With the version you mentioned (5.11.2.31), I think things seem to work fine now, However, I have faced issues with that as well. Trying to understand why, so I had to delete the ~/.Prismatik directory as well somehow, don't know why but after doing that, it started working.. otherwise just changing the Prismatik binary hadn't working... do you know any reason as to how this could've happened? |
Your log contains these two lines: Possibly something screws up this field / the device configuration when running into this no screens found thing the first time, or this isn't a problem with scaling after all. My guess is that that also breaks Moodlight, because the Moodlight successfully writes an empty buffer to the device: To verify, it would help if you could upload the log when you run the master build for the first time (backup your config folder first ;) ) Please try the build from the |
How can I enabled the debug logs that time? I recall that I have to increase the debugLevel in ~/.Prismatik/main.conf to get the debug logs. |
|
I see some flaky results.. |
Indeed, not sure if core dump crashes are related or not. This looks like the stdout log, I think we'd need the log file to understand what exactly is happening (with the maximum debug level, 3 - there's indeed |
same issue. Any fix? |
This is built with latest master on git and tried with the specified tag as well but it doesn't seem to work
Attached Logs:
Prismatik.0.log
Screen resolution:
3440x1440
The text was updated successfully, but these errors were encountered: