Autoplay starts with muted video
Tried with default theme: Yes
Tried with all other plugins disabled: No
Browser version: Chrome 87.0.4280.88 (Official Build) (64-bit)
Shortcode/URL with the issue: [arve url="http://techslides.com/demos/sample-videos/small.mp4" muted="no"/]
Hi,
Probably I have just missed something, but I couldn’t find documentation for the autoplayed video. I’ve set autoplay for HTML5 video in settings, but when the video starts, it’s muted. That makes the plugin senseless to me. Is there something I have missed in documentation, or any way at all to make the sound in autoplay on by default?
found a line in php/functions-html-output.php:
‘muted’ => $autoplay ? ‘muted by ARVE because autoplay is on’ : $a[‘muted’],
changed to:
‘muted’ => $a[‘muted’],
So it works now as needed. Please add an option for this feature so this workaround could be changed back with native code. Thanks!
This is on purpose to make autoplay actually work in most cases.
What browser are you testing this on? To my knowledge Firefox desktop is the only browser allowing unmuted autoplay by default. All the mobile browsers prevent it meaning the video will NOT autoplay if you not also mute it at the same time. Chromium based desktop browsers do also prevent it by default as well AFAIK and the market share of Firefox (I still love it) is just to low to give it special treatment. Also autoplay with audio is generally frowned upon by users anyway, so I do not plan to change that.
I use Elementor Pro, opening video in a popup. This way, there’s no restriction by a browser to let the video play with sound (speaking about desktop). Tested in Chrome, as it’s written in the details in the top message. So for this scenario the feature to unmute auto played video could be very useful.
In my case, video is opened in a popup by a user clicking on the play button. Users are expecting video playback with sound, not muted. It’s important for good UX.
Also found this attribute in the player code: muted=”muted by ARVE because autoplay is on”
So my question changes: is there any option to fix this behavior of the plugin?