Archive | W3C ORTC RSS for this section

Vancouver WebRTC – Meetup 2 @PlentyofFish

With more than 40 members and growing, Vancouver WebRTC now has a new venue! Chris Simpson from PoF rallied to get us into their new presentation lounge, the “Aquarium”, thanks Chris!

IMG_4459-1 IMG_4456-1IMG_4458-1

Our next event is on June 25th from 6-8pm and we have a great evening planned with Omnistream and Perch presenting!

Come check it out!

W3C ORCT CG Meeting 9 – June 24, 10am PDT

We are holding our ninth CG meeting on the 24th of June…

https://www.w3.org/community/ortc/

Where: Online (TBD)

When: June 24, 2015 10am PDT

Agenda

Review action items from last meeting:

– RTCIceCandidateComplete dictionary
https://github.com/openpeer/ortc/issues/207

– RTCIceGatherer.close affect on RTCIceTransport / RTCDtlsTransport
https://github.com/openpeer/ortc/issues/208

– Comments added to #200
Incoming media prior to Remote Fingerprint Verification
https://github.com/openpeer/ortc/issues/200

– Comments added to #170, Peter to send fuller proposal to list
Response to connectivity checks prior to calling iceTransport.start()?
https://github.com/openpeer/ortc/issues/170#issuecomment-105629219

– Original #188 – Priority Calculation, new bug #209
Trying to remove RTCIceTransport.createAssociatedTransport(component)
https://github.com/openpeer/ortc/issues/209

– Philipp Hancke’s Review Comments
https://github.com/openpeer/ortc/issues/198

Review open issues: https://github.com/openpeer/ortc/issues?q=is%3Aopen

Review current draft: http://ortc.org (upper right hand side)

Review implementation progress: ORTC Lib, MS Edge, Google ?

Review ORTC CG alignment with WebRTC WG and 1.0 spec.

Questions, comments?

Plan next meeting.

WebRTC Update from Justin Uberti, WebTorrent talk by Feross Aboukhadijeh & John Hiesey

Fresh out of Google IO, Justin Uberti provides a WebRTC update via WebRTC Meetup in SFO at the Twilio HQ. Slides and demos are not visible, I am attempting to get a copy of the slides. UPDATE: Most of the slides were captured via photos.

Justin talking points:
– Renewed focus on mobile
– HD bitrates and bandwidth estimation
– Goal H.264 coming to Chrome 45 via Cisco’s OpenH264 (whoa!)
– VP9 & hardware support
– Demo on Nexus 6 using VP9 and hardware encoder

What’s coming next..
– Mobile performance
– Complete call setup should be 500ms
– Encryption (we don’t hold the keys)
– ECDSA coming soon!
– HW encode on android capable of 1080p
– New Echo Cancellation via DAEC (Delay Agnostic Echo Canceller)
– Mobile Networks
– Network Handoff
– Scaling Quality
– Better performance on lossy networks
New domain for “WebRTC and Web Audio resources”
Appr.tc
g.co/webrtc

Q&A

Q What’s the story on spec deviation?
A We want to make sure we add promises to the spec.

Q Get Stats?
A Working on it

Q Unified plan support
A Organizationally challenged and taking back seat to encoding performance and other “on fire” must fix immediately

Q What is going to evolve in screen sharing in spec and Chrome?
A Things work “ok” for screen sharing but not great for some things like scrolling, people are also interested in using in tabs versus window. Screen refresh is not as fast as we would like but we think we have fixed that.

Q Changing framerate and resolution mid-call?
A RTPSender gives you some of these knobs (Note: Object from ORTC Spec!), which is on its way.

Q Battery life for hw encoded apps?
A 3 categories, voice only, video on sw, video on hw. Video demo was on hw at 1080p at 30% of CPU. HW video will compete with a baseband voice call on wifi.

Feross Aboukhadijeh & John Hiesey (creators of PeerCDN

Talking points:

https://github.com/feross/webtorrent
– Using WebRTC DataChannel to stream content
– Demo: can’t see the screen
– Hosting websites in Browsers via WebTorrent
– NAT traversal via regular STUN / TURN

Q&A

Q Justin asks, what will it take to have this work with existing bittorrent clients
A They need to add WebRTC, then it will work

W3C ORTC CG Meeting 8

ORTC CG Meeting 8 will be held on May 13 at 10am – Pacific Daylight Time.

Where: Online WebRTC Enable Meeting via Jitsi (https://jitsi.tools.ietf.org/ortc) Reverted to Google Hangouts

Agenda:

WebRTC Meetup – Vancouver

Vancouver is one of the hotbeds for IP communication technology and is home to many developers. With the advent of WebRTC, integration of voice and video chat into almost any application is within reach but as always, there are always pitfalls. Sounds like a great reason to start a WebRTC meetup in Vancouver!

As of today Vancouver now has its own WebRTC meetup group. If you are interested in linking up and talking to like-minded RTC geeks implementing real time comm using WebRTC please join and let’s get together. We will also be looking for meetup facilities & sponsors (snacks, drinks etc.).

I am thinking our first meetup will be in May sometime, not sure on exact dates yet.

Agenda and topic for the first meeting is wide open. Topics like, “WebRTC 101” or “Dos and Don’ts” come to mind, but we can decide on that when we have heard from some active members.

We will also be bringing in some live guests from time to time via what else, WebRTC!

Hope to see you soon!

/Erik

ORTC and WebRTC Consulting

  

Hookflash is now providing WebRTC and ORTC Consulting services.

Professional Services Pack

For organizations looking for an expert ORTC / WebRTC developer to provide assistance or become a part of their teams for specific projects. Depending on your needs, the Hookflash subject matter expert can help with any aspect of your project, including consulting, design, development, and QA. The PSP (Professional Services Pack) is available in increments of 40 hours. We have streamlined the engagement process for the PSP to enable a quick start.

Complete Project Development

For companies needing specific development expertise or staff augmentation, we offer complete life cycle development services, including use-case definition, requirements specification, estimates, project planning, design, development, QA, and app store deployment.

Where we shine: C++ (low level, client and server), Assembler (eg. CODEC enhancement), Mobile development: Objective-C (iOS) , Java (android) and Server: Node.js

For more information please visit Hookflash or call 1.855.HOOKFLASH (466.5352) ext.2

W3C ORTC CG Meeting 7

22 January 2015 Editor’s draft:
http://ortc.org/wp-content/uploads/2015/01/ortc.html

Changes from the October 14 Editor’s Draft:

WebRTC 1.0 compatibility

  • Statistics API Update (Issue 85)
  • H.264 parameters update (Issue 158)
  • Support for maxptime (Issue 160)
  • RTCRtpUnhandledEvent update (Issue 163)
  • Support for RTCIceGatherer.state (Issue 164)
%d bloggers like this: