Event - Firefox Live 2/meetings/2011-10-12
From MozillaWiki
- platform could be spun up this afternoon and ready today
- encoders were set up at the zoo
- mailed laptops
- ran flash media live encoders
- laptops still there?
- send stream to platform
- put that stream into the player
- front end,chrome is done by mozilla web dev
- moz doesn’t need to worry about infrastructure
- goes to ooyala, published through akami
- What are Ooyala changes since first campaign
- supports hls http streaming
- lots of new additions
- most significant new delivery
- HTML5 player for iOS
- HTML5 for desktop browser?
- challenge was there wasn’t player tag that was compatible
- No change since last campaign
- HTML5 tag is container; needs player that uses WebM as a protocol
- no way to encode live stream and then deliver into HTML5 player
- mobile player for android via RSS links
- Roku app to serve into android
- (Googles protocol)
- Ooyala might have Vp8 support in their player.
- don’t need to get creative with the player
- Mozilla will check out and send info on what encoders and protocols we’re using.
- IE crash box in player issue:
- Knoxville zoo ran VMs on his window machine which crashed. Should have used dedicated machines (mac minis or something)
- Ooyala, doesn’t use windows in any operations
- decision was made on client side
- need to send new machines. if webm need to find what encoders support it. significantly more expensive.
- Mozilla owns the platform. look at how many streams are left and whether we need to purchase more.
- Look at consumption.
- Who worked with the zoo? Ooyala was deeply involved. Account manager can help and someone from mozilla IT.
- One camera = one laptop multiple bit rate
- Ooyala suggests 3 bit rates per laptop.
- Full mobile/desktop support would require ~7 bit rates and at least 3 laptops
