Search results

attached

That case is clear. But the connections counter below does not make sense: -----Connection Stats----- connections=55 connections_rtmfp=0 connections_websocket=55 -----Port Stats----- ports_sip=0 ports_media=141 ports_rtsp=1 -----Stream Stats----- streams_webrtc_in=2 streams_webrtc_out=47...

I had two streams playing, one screen share and one audio and then I tried to stream one more screen share. Then I went to the player on IE I clicked start and then the server crashed, or some parts of the server crashed. I am attaching the crash log.

Thank you for the clarification and suggestions, all work fine

Check this out: -----Connection Stats----- connections=6 connections_rtmfp=0 connections_websocket=6 -----Port Stats----- ports_sip=0 ports_media=0 ports_rtsp=0 -----Stream Stats----- streams_webrtc_in=0 streams_webrtc_out=0 streams_rtmfp_in=0 streams_rtmfp_out=0 streams_rtmp_in=0...

According to the stats below: total connections=76 and streams_viewers=52+53=105, are these numbers correct? -----Connection Stats----- connections=76 connections_rtmfp=1 connections_websocket=75 -----Port Stats----- ports_sip=0 ports_media=163 ports_rtsp=1 -----Stream Stats-----...

I confirm that the problem is fixed, I tested on 2158.

Just fyi, Here are the stats without anybody connected on the server. When I use the player to play either 875960ccAudio or 875960cc it connects (but of course there is no connect). -----Connection Stats----- connections=237 connections_rtmfp=0 connections_websocket=237 -----Port Stats-----...

The first problem is that we cannot start a new stream at the same end point because it appears to be in use. And the second is that stats are wrong, we have to see and report how many users are connected but it appears that numbers are wrong. Attached are the logs.

The problem still persists. In fact it is like that right now. I see on the stats: streams_viewers=875960ccAudio/85,875960cc/89 There is nobody streaming or playing right now. I checked it with netstat, no connections at all. When I attempt to play the stream it says Connected. Can we debug...

I have noticed that after a couple of hours of connection to a screenshare stream and an audio stream the audio from the PC mutes!!! I mean that there is no sound at all, even from other apps. When I close the browser that plays the steams the sound comes back. Any clues?

What is the minimum chrome version that the player works? We have reports from chrome 55 user who does not work.

I added the above value and bandwidth events gone. So there is frame loss (I wonder why it occurs) we just limit the threshold the event will fire, correct? The above value makes the threshold 10%, right? What was the threshold before I manually set it?

We broadcast a stream to a few clients and I have noticed this line on the player: And we also see thousands of lines like this bellow on the flashphoner_manager.log How this NOT_ENOUGH_BANDWIDTH is triggered? Obviously it is wrong because the stream is like 300kb-2Mbit and every client is...

After a while it become like this:

Is this something to worry about?

Hi, i've done some work on REST methods based on this doc https://flashphoner.com/docs/wcs5/wcs_docs/html/en/wcs-rest-methods/ I successfully redirect all REST functions to my web app to achieve authentication for publishers/viewers. The whole app works like this: 1) When a user creates a...

The codes ordering fixed it, tt is perfect now. On the default config it was h264,vp8. Should I expect any side effects on any other browser by having vp8 before h264?

I am not sure if that setting affected anything. There are times that screen looks very good but when there is motion then it becomes very blurry. It feels to me that the problem is the encoding that chrome does but I do not have any solid evidence.

Screen sharing quality is very bad most of the times. There are a few times that things look crisp and good for a few seconds but then it is all blurry again. We use chrome and all the latest examples and WCS server. We have also added the googCpuOveruseDetection: false parameter. The CPU...