See who is streaming your Eagle 3D Streaming apps right now, end a session that should not be running, and look at what your account has used.
Shows every active session on your account, live, and lets you remove a user from one. In the Control Panel it is called Running Streaming Sessions.
That matters for three reasons, and only the first is obvious:
Each row is one viewer's session, with these columns:
| Column | What it shows |
|---|---|
| App Name | The application being streamed. |
| Version | The build number, or Latest when the link always opens the newest build. |
| Port | The connection the session uses on the streaming machine. Needed to remove the viewer; nothing to act on otherwise. |
| Device | Desktop, smartphone, tablet and so on. |
| Browser | The viewer's browser, for example Chrome or Samsung Browser. |
| Country, City | Where the viewer is, from their internet address. Approximate. |
| Action | KICK PLAYER ends that viewer's session straight away. |
The Control Panel raises notifications about your account and applications — uploads finishing, and things needing attention. Worth checking after starting a large upload, since it tells you the app is ready without you watching the page.
The Analytics section shows how much you have streamed over time. Use it to answer the questions that decide a plan: when your peak actually is, how much of your allowance is used, and whether usage is growing.
Concurrent users and minutes are different limits and are hit for different reasons. Analytics tells you which one you are actually short of — upgrading for the other one costs money and changes nothing.
On the Minutes page, every session in the Sessions list has a What happened link. It opens that session told in plain words, in time order, in your own clock: when the link was opened and from where, how long it waited for a machine, how long the app took to start, when the picture appeared and at what size, and anything that went wrong along the way.
| Line you may see | What it means | What to do |
|---|---|---|
| Picture size changed from 1920 x 1080 to 1280 x 720 | The connection could not carry full size, so the picture was made smaller. | Usually the viewer's network. Check the bitrate settings if it happens to everyone. |
| Frame rate fell to 12 fps from 1:48 to 2:00 | The app or the machine could not keep up for those seconds (below 24 looks jerky). | Look at what the app was doing then: a heavy scene or a loading moment. |
| Slow connection (round trip about 250 ms) | The viewer was far away or on a busy network; controls feel delayed. | A streaming region nearer to your viewers helps. |
| About 600 video packets were lost | Part of the picture never arrived; it may have broken up or frozen. | Almost always the viewer's network (Wi-Fi, mobile data). |
| The connection dropped 1 time during the session | The stream was cut and reconnected. | If it happens often, contact support with the session time. |
Analytics → Video failed lists every visit where a machine was ready but the video never started on the visitor's screen, because the browser was waiting for the visitor. Each row is one visitor, so you can see how often it happens, on which app and on which devices.
| Reason shown | What happened | What helps |
|---|---|---|
| Play button not pressed | The browser does not start video with sound on its own. The page showed its play button and the visitor never pressed it. | Make the play button obvious on your page, or start muted. See why autoplay with sound is not natural. |
| Microphone request not answered | The app uses the microphone. The browser asked the visitor for permission and got no answer for 3 minutes, so the video never started. | Tell visitors before they open the link that the browser will ask for the microphone. Turn the microphone off if the app does not need it: microphone settings. |
Columns: when it happened, app, version, the page address the visitor opened, their city, browser and device.
The machine was held for the visitor while the page waited. A long list here means visitors are leaving before they see anything; fixing the cause is usually a change on your own page, not on the app.
What your allowance is, and the settings that stop it running out unnoticed.
Last updated