When the imsdroid network environment is poor, mosaic is very serious. We can see that there is an option of Zero video artifacts, as the name suggests: Zero artifacts, that is, no camouflage image, the professional statement should be a software-compensated imaging algorithm. After setting, the mosaic is reduced a lot, but the network is poor, and the same is true if you try QQ. Take a look at this principle:
N a video processing system where motion vectors are estimated for a subset of the blocks of data forming a video frame, and motion vectors are interpolated for the remainder of the blocks of the frame, A method provided des determining, for at least one block of the current frame for which a motion vector is not estimated (204 ), whether a block to the left or right has an estimated Zero motion vector (206), determining whether the at least one block had an estimated Zero motion vector in a previous frame (206 ), and if both determinations are affirmative (208), providing a predetermined motion vector for the at least one block. the predetermined motion vector may be a zero motion vector (208 ).
(PS: I see Dizzy)
Https://groups.google.com/forum! Topic/doubango/tpdl3qepolicyq
Some Questions about the setting options:
This setting is (still ?) Hardcoded in tinymedia/src/tmedia_defaults.C Of The doubango source. To enable it change
Static tsk_bool_t _ video_zeroartifacts_enabled = tsk_false; // requires from remote parties to support avpf (RTCP-FIR/Nack/PLI)
To:
Static tsk_bool_t _ video_zeroartifacts_enabled = tsk_true; // requires from remote parties to support avpf (RTCP-FIR/Nack/PLI)
And recompile doubango and webrtc2sip.
There is a public API function to enable/disable this featureIt's not recommendedTo enable it on webrtc2sip as it's a relay and not a producer.
This feature shocould only be enabled on the clients or any endpoint acting as Video Producer (in opposite to video relay ).
Imsdroid video Mosaic