Add device orientation information to header information

[sbfkcel]

This is useful if need to draw the device appearance correctly.

Related Discussions

#5704
#3605
#925

#5894

---

CODEC    SESSION packet                         SESSION packet
[codec] [type|width|height|orient] […] […] […] [type|width|height|orient] […] […]
                                              ^
                                              rotation occurs

CODEC packet：

• codecId 4byte

SESSION packet:

• type 1byte, The SESSION packet type is 0xff
• width 4byte
• hegiht 4byte
• orient 3byte
  • isFlip 1byte
  • 180° 1byte
  • 90° 1byte

Orient format reference source

scrcpy/app/src/options.h

Lines 72 to 85 in 7998811

	// ,----- hflip (applied before the rotation)
	// | ,--- 180°
	// | | ,- 90° clockwise
	// | | |
	enum sc_orientation { // v v v
	SC_ORIENTATION_0, // 0 0 0
	SC_ORIENTATION_90, // 0 0 1
	SC_ORIENTATION_180, // 0 1 0
	SC_ORIENTATION_270, // 0 1 1
	SC_ORIENTATION_FLIP_0, // 1 0 0
	SC_ORIENTATION_FLIP_90, // 1 0 1
	SC_ORIENTATION_FLIP_180, // 1 1 0
	SC_ORIENTATION_FLIP_270, // 1 1 1
	};

Test run

meson setup x --buildtype=release --strip -Db_lto=true &&  ninja -Cx && ./run x

Output

INFO: Width=1920, Height=864, Flip=False, Direction=1

[sbfkcel]

The previous fork has too many redundant records, use the new pull.

@rom1v Please check again to see if there are any new suggestions.

[sbfkcel]

@rom1v Can this PR be merged in the next version? If it can be confirmed, I can't wait to update the Web client protocol parsing method.

[rom1v]

I just submitted #6159.

It introduces the protocol change to add a "session packet" (you're mentioned as co-author of that commit).

The session packet only includes the video resolution (since scrcpy currently does not use the device rotation), but the architecture is here, you can add the rotation on your branch with minimal changes I guess.

I adapted the client so that everything works correctly (as mentioned here: #5894 (comment)).

[sbfkcel]

Okay, future versions will align with the new protocol.
Adding different flags to distinguish data will not pollute the project.
look forward to merging it into the official branch after implementation.