-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Unexpected Behavior with QT Screen Capture Multi Monitor Capture & LED Frame Position Limitation #1320
Comments
OK I've tested with the development build, looks like the region capture with QT issue is fixed in my use case, which is great news, thank you @Lord-Grey. I've attached an image of the new builds LED Visualization window. However, the second (more minor) issue I mentioned in the initial post is still present, where I cannot set the vertical offset to more than 40% from the top or less than 60% from the bottom, this seems like an arbitrary limit, especially after hiding these configuration options in the context of "Advanced Settings", to me it would make sense to not impose limits on "advanced" users, and present at the most a warning dialogue, that can be ignored would be ideal. I'd appreciate this fix to allow the software to support stacked monitor configurations of the same vertical resolution. |
@ImAvix Thanks for testing and feedback. Seems I have missed the % issue before. I guess you finally would like to get something like the following, correct? I have a look on the percentages to see what makes sense in cross field validations.... |
I've been setting my options with the "Classic Layout (LED Frame)" option in the LED Layout tab, there I am presented with a limit of 40% (even in expert settings mode), I can manually overwrite that in the "Generated/Current LED Configuration" JSON editing panel, where I can lower the top edge to 0,5 or 50%, however the top of the left and right sides are still at the old limit, which generates an LED frame that looks like this: Then I encounter the issue of setting a uniform height for the left and right side pixels, which requires some arithmetic ("% vert" divided by "vertical LED count" = proportional pixel row height) and then more importantly manually editing the JSON file, again in my opinion, this should be done through the software, ideally through the GUI. I could get the result I want by manually adjusting the JSON file, but I have a vertical LED resolution of 22, across both monitors, I'd have to edit 88 values, adjusting in increments of 0.0227... Not my ideal weekend. The solutions I see here are either:
There is already a JSON viewer, which is handy, and while this is fine for editing setups with fewer LEDs, when the number of LEDs starts to get higher, this becomes tedious quickly. I have no problem with combining the two JSON configs for weird shapes (again like my monitor configuration), but manually adjusting these proportional arguments is not the best user experience. |
@ImAvix Maybe I was not clear with my last post. I removed the vertical and horizontal limitations and provided a link to the updated build for you to test. Edit
I did the "stiched" ayout completely via the UI. No manual number editing. You just do two configuration steps. Note: remove the [] from the clipboard config and put a comma between the two configs to get a valid JSON. |
Success! @Lord-Grey Sorry for the confusion, I didn't see your second comment with the newer build version before posting my comment. You can ignore my comments about manually creating JSON files. That second build addresses both my issues with the software. Following those two configuration steps you outlined was the most ideal process for creating the LED layout I desire, I appreciate you taking a look at this issue, and I'm glad we could reach a resolution. |
Fixed via #1421 |
For a bit of context, my setup is probably a bit unusual, but I see no reason why it shouldn't work. I have 2 stacked monitors, a 3440x1440 ultrawide, and a 2560x1440 monitor on top, both centered horizonally. Image attached for reference.
Bug report
I have the QT capture selected, Device Resolution is correct, but in the live video the bottom half is completely black, and the top half is the bottom monitor. This is when the ultrawide is the "main display" in the windows settings, which is how I normally have it and would like to keep it. Setting is shown here:
Setting is found in System -> Display -> Multiple displays -> "Make this my main display" Checkbox.
Screenshot of LED Visualization "Live Video" Window shown here:
When I change the main display to the top monitor though the capture almost correctly captures both monitors, there's black padding on the right hand side that extends to a resolution about 450 pixels to the right, which when you work out horizontal resolution difference between the two monitors (3440-2560) and center it (divide by 2) you get 440px. So again shown below:
Finally, since the vertical resolution of my monitors is the same, I cannot vertically align the top LED frame line with the top of the monitor since the max allowed is a 40% vertical crop (found in the advanced settings), seen below.
I'm no expert, but my guess for the "bottom half black video output" bug mentioned is that the "origin" point where capture on the main display starts is based off the main displays top left pixel, which doesn't allow for monitors above or to the left of it, because of the limitation to positive integers on the crop. I've visualised both scenarios, where the red box is the combined resolution of the two monitors, but the misconfiguration of the "origin" point causes these errors.
Scenario 1: Bottom Half Black Screen
Here you can see the origin point is in the top left of the ultrawide display, and the combined desktop resolution is correct, but the capture region is wrong.
Scenario 2: Both Screens Incorrectly Captured
Again here the origin point is in the top left of the top monitor, and the combined desktop resolution is still correct, but the capture region is still wrong.
Finally, removing the 40% limit on the LED frame vertical offset should hopefully be an easy fix 🤞
Steps to reproduce
What is expected?
What is actually happening?
System
Hyperion Server:
Hyperion Server OS:
Debug Logs
Just in case they are useful.
https://pastebin.com/vQELk501
The text was updated successfully, but these errors were encountered: