Search results

I mean this shadow visible with the controls if the mouse is over the player. Thanks! Vico

Yep, there is something on weird on my end, as allways no problem with h264, but If I change my device to send Hevc I can´t find the proper settings to transmit this outside our server Thanks

I´d sent the ssh credentials and the rtsp video adress with the form. as allways... many thanks

Hi Max!, i`m trying to ingest MPG TS h265 from a rtsp to use the embed player. but no luck. The player is black. I followed the instrucions tu update, and updated one of our servers to the v.2.0.228-5.2.1579 The final goal is to publish the embed player and the latency is very important. Thanks...

Hi Max, we have a problem with the renovation of the Certbot, when we try to import the privkey we see a warning and deny the renovation, we need help. 4 servers are going to stop for this. Thanks in advance men!

Wow, really close to perfection. 24h testing and seems really reliable, maybe much more stable Thanks Max With an option for h265, we will touch the sky ;-) Thanks for your help men

Wow, seems to work super good, actually testing Max, there is a way to avoid the "FAILED: failed to connect to rtsp..." message, or to change the message. it´s on the client side and it´s hard to explain. Can´t find this thing in the Player.js Thanks

Yep, sorry mate, it´s ec2user This works suuuuper good, thanks a lot Max. The only thing is that I feel this embed like the old version, it´s the one from the 5.2.1555 version?

Thanks Max, I tried, overwrite the files in /embed_player, but this works like the old player and also no auto start after interuption. No password, I send the same like last time, instance runing. Thanks for your effort men, Vico

This works, it´s almost perfect for us. Max, last year or so you help us tweaking a bit the Player.js, we want that the player auto reconect if suddenly lost the feed, to avoid the "FAILED: Failed to connect to rtsp stream" on the client side. I try to do the same here copy pasting your old...

Ok, almost perfect. But, It´s possible to start Flashphoner when the instance start?, it´s not working like last version. Also, we stop the instance, start again and we get this trying to start WCS: [root@ip-172-31-20-102 ~]# sudo service webcallserver start Redirecting to /bin/systemctl start...

Yesss, actually working by far, thanks team. let us test this well, but looks super rock solid. Congrats.

you rule

Super!, thanks team. Max, what is the cleanest way to update?

Hi Max!, I´m testing this new version but can´t make it work. I´m listening to a rtsp feed and trying to generate a WebRTC player. Super happy with my actual servers running v.2.0.225-5.2.1482 super good for years, really happy. Anyway if you can help... SSH sent from support page. Thanks!

You rule men!!

Booooooooommmmm!!!, amazing Max. woks like a charm. How to propely update my other servers to the 2.0.189? Thaks for this men, Vico

Wow Max!, this looks like a dream to me, not kidding, this will save me But I can´t make this work, try in different servers and allways get a thinking circle but no work

Can you see something? I send the one from this folder...

I´m just using the embed from a WCS instance. So I´d paste the code on the: /usr/local/FlashphonerWebCallServer-5.2.944-XXXX/client2/examples/demo/streaming/embed_player/player.js But now I can´t play a thing, It´s like allways thinking... .-)