Many years ago, Flash was essential in browsers to interact with the user media devices, such as a microphone and camera. Today, Web Real-Time Communication (WebRTC) technology has come to substitute the flash, so browsers do not need the flash to access media devices or establish their communication. However, WebRTC standards do not express precisely how browsers can record audios, videos or screen instead of describing getUserMedia API that enables a browser to access microphone and camera. The prime objective of this research is to create a new WebRTC recording mechanism to record audios, videos, and screen using Google Chrome, Firefox, and Opera. This experiment applied through Ethernet and Wireless of the Internet and 4G networks. Also, the recording mechanism of this research was obtained based on JavaScript Library for audio, video, screen (2D and 3D animation) recording. Besides, different audio and video codecs in Chrome, Firefox and Opera were utilised, such as VP8, VP9, and H264 for video, and Opus codec for audio. Not only but also, various bitrates (100 bytes bps, 1 Kbps, 100 Kbps, 1 MB bps, and 1 GB bps), different resolutions (1080p, 720p, 480p, and HD (3840* 2160)), and various frame-rates (fps) 5, 15, 24, 30 and 60 were considered and tested. Besides, an evaluation of recording mechanism, Quality of Experience (QoE) through actual users, resources, such as CPU performance was also done. In this paper, a novel implementation was accomplished over different networks, different browsers, various audio and video codecs, many peers, opening one or multi browsers at the same time, keep the streaming active as much as the user needs, save the record, using only audio and/or video recording as conferencing with full screen, etc.
展开▼
