Why a streamed video, on Eagle 3D Streaming or anywhere else on the web, may start by itself but its sound may not, why a sound button and a play button are both still needed, and what Eagle 3D Streaming does on every device.
It is past midnight. Someone is lying in bed next to a sleeping partner, scrolling on their phone. A friend has sent a link, and they open it.
If the video started by itself with its sound, the room would fill with noise at full volume, and the partner would wake up. The person only wanted to see the video, not to hear it, and they were given no chance to choose.
Now picture the same thing in a quiet office, on a train, in a library, or in a meeting. Or a video whose sound is simply unpleasant: a scream, an accident, an argument. The viewer may well want to watch it, but not to hear it, or not yet.
And picture the worst case: a pop-up window from a website you did not mean to visit, with a video in it, and a loud voice shouting "Your computer is infected! Call this number now!". If sound could start on its own, every such pop-up would become a loudspeaker the moment it opened.
People usually say "autoplay" as if it were one thing. For a browser it is two:
To stop the bedroom, the office and the pop-up from ever happening, every major browser (Chrome, Edge, Firefox and Safari) adopted the same rule: the picture may start by itself, the sound may not. Sound is allowed only after the viewer has done something on the page: a click, a tap, or a key press.
One detail surprises almost everyone. If a page asks the browser to start a video with its sound before the viewer has done anything, the browser does not quietly play it without sound. It refuses the whole request, and the video does not start at all. A page that insists on sound gets a frozen first frame.
So a page for which autoplay matters has to accept one fact: to start by itself every time, the video has to start muted.
That raises the next question. If the video starts silently, how does the viewer know there is sound at all, and how do they turn it on?
Turning it on is not up to the page alone. A browser lets a muted video start its sound only once its own condition has been met: something that shows a real person is sitting in front of the screen. Chrome's condition is that the viewer has interacted with the page: a click, a tap or a key press. Safari, and the browsers on the iPhone, have the same kind of condition with their own definition of what counts. Until that condition is met, a page that tries to turn the sound on is refused.
So the industry's answer is to let the viewer decide when the sound comes on. The page shows a sound button, the familiar speaker icon with a cross through it, which says "the sound is off". The page's programmer makes a press on that button try to start the sound. The press itself is the interaction the browser was waiting for, so the condition is met at that very moment, and the sound starts. That is how the sound comes back on a video that started by itself, muted.
That is why, wherever you see a video start by itself (social media feeds, news websites, product pages) you also see a small speaker icon in a corner. It is not decoration. It is the other half of the same browser rule.
With the video starting muted and a sound button on screen, it is tempting to think the play button is no longer needed. It is still needed, because not every device allows even muted autoplay.
On these devices the video cannot start until the viewer presses something. A page without a play button simply shows a still picture, and the viewer has no idea that anything is wrong or what to do about it.
So the play button must stay. It should not be on screen all the time, only when autoplay was refused, and it must appear by itself at that moment, without the viewer having to guess.
Eagle 3D Streaming's position is simple: if picture and sound can start together, they should. So it uses smart autoplay: it assumes, to begin with, that the browser will allow both, tries that first, and only steps down when the browser says no. Each step down happens by itself, and fast.
| where the viewer is | what they see |
|---|---|
| Clicked or tapped on the page before the stream was ready | The stream starts with sound. |
| Chrome, Edge, Firefox or Safari, no click yet | The stream starts muted, with the sound button in the bottom-right corner. |
| iPhone or iPad in Low Power Mode | The play button. Pressing it starts picture and sound. |
| Safari "Never Auto-Play" or Firefox "Block Audio and Video" | The play button. Pressing it starts picture and sound. |
| A rule that refuses the sound even after the play button | A short pause, then the stream plays muted, with the sound button. |
All of this happens with the Autoplay setting switched on. With it off, the viewer always presses a button to start; see Streaming interface.
Last updated