@renan When you plan to upgrade WebRTC
@renan When you plan to upgrade WebRTC Stream from Beta to production-ready full integrated stream service?
14 Replies
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
WebRTC isn’t fully usable because:
- it doesn’t load in iframe integrated player
- no stream statistics / analytics
- audio issues, already reported, the audio track is sometimes not available and loads after a while e.g. 30 seconds
- missing auto VoD
The audio issue is the reason why we dropped the WebRTC, everything else we already have implemented replacements
btw, the live counter within your iframe player is broken. I already reported this also. The issue wasn’t existing before 2 weeks.
Look at the counter in our Livechat and compare with the number from the player. It was equal before 2 weeks.
And yes I double checked the validity of ours and yours
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
I noticed the live watch counter issue today. I have an idea whats going wrong, possibly it will help to go in the right direction. Look at the screenshot. We have streams where the counter is constantly equal and we have stream where the counter constantly differs. I assume that this has something to do with the input stream specification, because we have different streamer with different setup. When the input stream is matching a “low profile” criteria CF doesn’t recode this specific stream within the adaptive concept. It will just use it as it is. And therefore my assumption is that the live watch counter is populated around this processing. That would be a solid reason for such an issue.
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
Ok, at least it was a guess 😁
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
We have 20+ streamer, never has this issue and since a couple of weeks it occurs on multiple (always same) streamer. That’s something which does not fit into a “pause” situation, especially when the differences is such huge.
That’s not a big deal for us, since we capture our own live watch counter (originally as a WebRTC replacement). But what really would be an issue is when the “streamer minutes” analytics is related to the same strategy. Because we use Stream Analytics as a base of our pricing model. It is actually mandatory for us that this value (delivered minutes from analytics) is almost trustful.
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
I think it doen't need further explanation, reporting a broken watch counter in livestream overlay should be enough.
Also CF statistic says 22000 minutes delivered, our own measure expects 12000 minutes delivered. That's a plus of almost 100% from our to yours? And please don't tell me anything about "behind the live edge". That couln't be true. In 3 hours of video length the 22000 minutes would require 122 viewers per minute. But we have round about 60-65 viewers per stream. So our own measurement is by far more close to the real value. As far as I know your payment is based on your measured minutes, and that is simply not acceptable for us.