Context Navigation

#1360 closed defect (fixed)

Mobile devices can be rotated (the rotation angle can be detected), which may lead to wrong video orientation in rendering/playback.

The purpose is to allow video rendering in natural orientation (head/sky upside) or the preferred orientation of the capturer.

Common video codecs works in predefined allowed sizes/orientation, e.g: CIF, QCIF.
On iOS, capturing video to a file will store the video data in camera's native orientation, i.e: wide-oriented, the capture orientation info (the device/camera orientation when the capture/record process is done) is stored in video metadata, so in playing back the file, the stored capture orientation info (may be combined with current device orientation info) is used to calculate rotation angle to get natural orientation in video rendering/playback.

The orientation info is readable and read-only in capture.
The renderer will apply the orientation info provided by the capturer.
The orientation info is a rotation angle to be applied to a picture/video so it can be displayed naturally (or as the capturer preference).

SDP/SIP only offers limited support for orientation, and there is no way for sender to tell receiver about the video orientation of the capture device. The 'a=orient:x' in SDP is not really useful as this is receiver preference/capability, while in practice, the receiver can render any orientations and the capturer cannot really send portrait (codecs limitation, etc).

Based on the background above, the following API will be implemented by this ticket:

Add orientation capability to video device with the following specification:
- it is read-only for capture devices, and
- it is write-only for renderer devices
Add pjsua_vid_win_rotate(win, angle) API. The angle is a rotation angle to be applied to a picture/video so it can be displayed naturally (or as the capturer preference).