Custom size in mapper and virtual screen sizes not consistent.
-
There seems to be an issue using the custom size in the mapper with virtual outputs.
I was using some large NDI outputs, and no screens, and needed to use the mapper on these screens. As I am not using actual screens using virtual stages seems appropriate as I don't want this to reflect a screen size or be associated with a screen. I set my virtual stage size to 5120 * 720, but when I opened the mapper the output size at the bottom right says 1920 * 1080, nothing to do with the stage size I have made. Is this what resolution processing will happen at? Also why can I change this at all? The mapper sends things to stages, shouldn't it always have the resolution of the stage (virtual or real) it is associated with?
Anyway, after inputting the correct values of my stage size, the grey mapping area on the output was correct, but did not reflect the output I could see projected, to be on the stage half of my output had to be outside of the designated area.
I feel like the custom stage size entry on the mapper is redundant and confusing, stage sizes should be changed in the stage setup and everything that reflects them should be updated automatically.
Here is a screenshot of the issue - the images here were actually lined up correctly on my projecjton, filling the whole thing from left to right, but not in the mapper.
-
I just did some testing. I generally agree with you about the grid settings. But I understand it only as a helper to position a new slice.
First of all, I didn't have any issues with your virtual stage values. Set the grid division to the virtual stage numbers, it represents the exact boundaries as the stage output.
Testing around, I recognized the following; Changing the grid values, after adding slices, doesn't change anything regarding the output scaling. It only sets a frame around the stages center, where new slices are fitted in, when added. It is more kind of an orientation to help put slices into position.
I agree, it is some very limited helper. And it is confusing as it works on pixel basis. It would make more sense, if it would be represented as an aspect. E.g. 16:9, 16:10, 2,35:1 etc. and would not change the zoom in the output view, which could be confused as an actual scaling.
-
There is one more function for this settings. It sets the reference system for positioning the single manipulation point and therefor the values range for the point adjust settings.
-
@dillthekraut I am not sure what you mean by grid settings, but changing these values does change the output sent to the stage as well as the guide frame. It is unclear exactly what is happening here when I change these values - how do these settings interact with the stage size?
There are a few things happening. I feel like the value set here should be updated when the size of the stage is changed - this is why I changed it in the first place. I made a virtual stage and connected a few things. Then I went to the mapper and noticed the frame guide was nothing like what my stage output was. I then changed this to reflect my stage output and the frame guide was the correct shape but not at all accurate.
I get that if there is a custom value set here that if you then change the stage size there is now an issue of which size to use, but I am still trying to understand the use case of changing the output size in the mapper. It does seem to change the output (recording attached below). If it was just for referencing numeric values that seems like an edge use case. If you are using numeric values it would seem that you would want to use the exact pixel positions, this is what that precision seems most useful for.
WIthout a clear understanding of what this adjustment is for, I do feel like it should not be there, or should initially be the stage size, and if the stage size is changed it should update to that.
Fred
-
Ok, I see now what you mean. It is very confusing as the scaling only happens sometimes. It seems to only scale in some extreme aspect deviations or the horizontal numbers exceeding the actual stage size.
When typing in the custom values, you automatically go through those extremes (19 x 1080, 192 x 1080, 1920 x 1080). But switching between the presets only sometimes changes the real scaling. When the Stage output is very wide, like your virtual stage, non of the presets seem to have an effect.
I agree with you, that this feature is, if not inconsistent, very unclear and confusing.| I am not sure what you mean by grid settings
If you hover with the mouse over the custom size values, it say 'horizontal / vertical grid devision', which I guessed is the name of the feature and therefor called it grid settings.
