[vlc-devel] [PATCH v5 00/24] Get rid of the control command API
robux4 at ycbcr.xyz
Mon Aug 31 09:32:37 CEST 2020
On 2020-08-27 16:43, Rémi Denis-Courmont wrote:
> Le torstaina 27. elokuuta 2020, 7.46.41 EEST Steve Lhomme a écrit :
>>> Why not? If your monitor resolution is 100x times that of the original
>>> video, it makes perfect sense that the speed is 100x if you measure video
>>> pixel speed. Indeed, until recently, hotkeys did not even care about
>>> mouse coordinates - only clicks. And the current rare usage (VR) has
>>> always been done with video coordinates.
>> This is wrong. If you mouse your mouse one pixel left, in VR, the video
>> should "rotate" by one pixel as well. It doesn't matter if your screen
>> is hidpi or you magnified the video 100x.
> AFAICT, VR is measured in angles. It does not matter if you move one pixel
> within the window resolution, or one sample within the video resolution. And
> if the video is upside down, then going up in the window coordinates should go
> down in the video coordinates and viewpoint angle.
I should have quoted "rotate one pixel". Of course you can't rotate one
pixel. What I am describing is that if you click on the 360 video and
move that mouse by one pixel, the video should rotate so that the pixel
under the mouse is still the same.
And so that means the DPI of your screen doesn't matter.
The magnification neither because the "rotation" is done in the display
module. It would be different if the rotation was done at the source
level or via a filter done before the magnification.
> At the input & itnterface levels, the window resolution is meaningless. In
> fact, it's neither known nor fixed.
> Certain things are broken. Most likely gestures for one. But adding events for
> cursor position in window coordinates fixes nothing.
> vlc-devel mailing list
> To unsubscribe or modify your subscription options:
More information about the vlc-devel