PORTAL ENHANCEMENT 12

Using the Church Webcasting System, YouTube, etc. Including cameras and mixers.
Post Reply
User avatar
pete.arnett
Member
Posts: 257
Joined: Thu Dec 23, 2010 7:33 am
Location: Sunny South Florida, USA

PORTAL ENHANCEMENT 12

#1

Post by pete.arnett »

From the ​portal.ldswebcast.org site

"A small Portal enhancement for the new Streaming Player will be installed on 06NOV2015 between the hours of 10 a.m. and 12 p.m. MST. The enhancement will add an additional video player and give status updates on the new players."

Does this mean we will have HTML5 player on Friday p.m. ?
:D
rolandc
Member
Posts: 257
Joined: Tue May 15, 2012 8:20 pm

Re: PORTAL ENHANCEMENT 12

#2

Post by rolandc »

Yes and No
Roland
User avatar
shawndowler
New Member
Posts: 45
Joined: Thu Dec 11, 2008 4:12 pm
Location: Arizona, USA
Contact:

Re: PORTAL ENHANCEMENT 12

#3

Post by shawndowler »

This is more than confusing. The idea of a stable, standard HTML 5 video player is great. The idea of two doesn't make sense. They don't seem substantially different from the user perspective. Why make two available?

In my testing, the HTML 5 players are both much less resource-intensive than the Silverlight player. I could use old dual core machines to play the HTML 5 stream at the highest settings. This is not the case with the Silverlight player.

I would love more insight into the development process on these and why they are available to use, but not considered ready for prime time.
User avatar
pete.arnett
Member
Posts: 257
Joined: Thu Dec 23, 2010 7:33 am
Location: Sunny South Florida, USA

PORTAL ENHANCEMENT 12 HTML5 Players

#4

Post by pete.arnett »

It appears that the following are some of the changes, that we can see - Two new players are available that support HTML5
Have not seen any published information about what changed
--------------------------------------------------------------------
Early Access Program Test Events Only

Two new players are available that support HTML5 compatible browsers, however performance is still being optimized for various browsers (Chrome, Firefox, Internet Explorer 11, Edge, Safari). Event reporting statistics will not be available for this player at this time.

IMPORTANT: This player should only be used for testing or emergency playback.
Please use the “Feedback” link to report any problems. Thank you.

Early Access Receiving URL (A):
http://portal.ldswebcast.org/player/index.html?eid=.......

Early Access Receiving URL (B):
http://portal.ldswebcast.org/player/pla ... l?eid=eid=.......
User avatar
pete.arnett
Member
Posts: 257
Joined: Thu Dec 23, 2010 7:33 am
Location: Sunny South Florida, USA

PORTAL ENHANCEMENT 13

#5

Post by pete.arnett »

PORTAL ENHANCEMENT 13

The Portal will be undergoing an enhancement beginning 0900 MST, 13NOV2015 until 1300MST of the same day. The new player client will be released for general availability as well as a new alert for the Event Manager.
rannthal
Church Employee
Church Employee
Posts: 155
Joined: Mon Jun 09, 2014 2:41 pm

Re: PORTAL ENHANCEMENT 12

#6

Post by rannthal »

shawndowler wrote:This is more than confusing. The idea of a stable, standard HTML 5 video player is great. The idea of two doesn't make sense. They don't seem substantially different from the user perspective. Why make two available?
We are trying to decide which player works best and we put both of them out there for you to use and try and provide feedback on.
shawndowler wrote:I would love more insight into the development process on these and why they are available to use, but not considered ready for prime time.
Wish granted. We realize there are problems with the silverlight player. We need something better. But we also need a player that is able to provide all the stats so one will be able to see what is going on with it. Stats like what were available with the silverlight player: playback bandwidth, download bandwidth, buffer - audio and video, dropped frames, stall time, etc.
The reason is that they are not considered ready for prime time is that the decision on which player to use was not made and there was some trouble getting the needed stats from the players.
Once the decision has been made on what player to use, it needs to be developed and tested to be adaptive and have an auto reconnect, plus making sure all the stats needed are there.
Post Reply

Return to “Non-Interactive Webcasting”