Media/WebRTC/2013-04-23
Tuesday, April 23, 2013, 9am Pacific:
Notes:
0) Work week for WebRTC:
- Definitely not around IETF. June 9 works best for everyone. Don't book flights yet.
1) PeerConnection, DataChannels blocking-webrtc+ bugs
- Nothing that needed to be discussed
2) Other development work for Fx 23/24
- jib - WebIDL: Making progress on bug 823512, filed bunch of webidl bugs (which are getting fixed fast. bz & mccr8 rock!) - commented out a few remaining lines so that it compiles, and am still working on hooking it up correctly to the build system to where it'll light up (unhooking xpidl in the process).
- Latency - how low can we set cubeb? Android 100ms; issues getting it lower on pre-4.1. MediaStreamGraph: using the callback to drive the graph. Issues especially on Windows.
- jesup, padenot, mreavy, and gcp to meet (targeting tomorrow)
3) Android development
- Skipped the update this week
4) B2G development
- New write up from ekr: https://wiki.mozilla.org/Media/WebRTC/WebRTCE10S
- Performance - need full perf info for audio-only calls, and of the video chain (especially once bjacob gets the fast-path YUV conversion fixed)
- figure out requirements and process for v1.2 (this is the requested target release)
- What are the perf targets?
- Facetime? Not likely - they have a faster processor and likely hardware support. Might roughly equal Facetime on older hardware, especially if resolution is limited by bandwidth not processing. They also have a low-latency audio stack.
5) Testing & Mochitests
- Notices
- Ted is nearly finished with having fake device support available for WebRTC automation
- Still running into issues on why media flow automation is failing - debug log analysis would be helpful
- Need assistance from gcp to find out why PeerConnection automation is failling to find the mozRTCPeerConnection API
- Working to get an explicit ETA from automation development team for automation delivery
- Initial testing of Android WebRTC - rough experience due to:
- Need clarity around the story with TURN testing and TURN server to be used for automation
- EKR has a TURN server stood up on EC2 (see https://bugzilla.mozilla.org/show_bug.cgi?id=860775 for credentials, which are security sensitive)
- currently, the C++ unit tests run on the ad hoc CI server with TURN.
- As soon as I figure out why the mochitests don't run on my CI server, I will run them too
- What about running TURN mochitests on rel eng infrastructure?
- This Week
- [jsmith] Continue debugging and fixing media flow automation
- [jsmith] Investigate call failure issue in bug 859395
- [jsmith] Work with gcp to diagnose Peer Connection automation failures on FxAndroid
- [jsmith] Misc exploratory testing on WebRTC patches landing
- [whimboo] Continued work on data channel automation
- [AaronMT] Begin working on an Android WebRTC platform test plan
- Last Week
- [jsmith] Kicked off try run with Android mochitest automation and analyzed results
- [jsmith] Debugging around bug 859195 to figure out media checking flow issue
- [jsmith] Misc exploratory testing around bugs needing QA involvement on Desktop
- [jsmith] Some security discussions around WebRTC story on B2G
- [jsmith] Investigated Galaxy S3 crash with getUserMedia on FxAndroid
- [AaronMT] Exploratory testing WebRTC functionality on FxAndroid
- [whimboo] Initial automation patch up for Data Only test awaiting feedback
- [ted] Nearly finished with adding fake device support in bug 815002
6) Discuss any current problems for people or issues that haven't been discussed -- or Any heads up for the group
- Reminders:
- Talkilla is having a work week in MV this week
- Doing a brown bag on WebRTC on Thurs, April 25.
- Documentation for developers
- higher level list of what have and don't have (important differences from the spec) -- perhaps link to bugs
- compiling this over the next few weeks at https://developer.mozilla.org/en-US/docs/WebRTC
- Talkilla is having a work week in MV this week
_________________
References:
- Proposal to target for Fx 23/24::
- Clean up of higher priority non-blockers bugs
- TURN support (ekr)
- State Machine Cleanup (abr)
- Better error reporting (abr)
- BUNDLE/RTP mux (ehugg)
- Conversion to WebIDL (jib)
- Better AEC (jesup)
- Persona integration (EKR)
- Improved latency (padenot with mreavy, jesup)
- Get C++ unit tests running on Windows (ehugg/ted)
Blocker List for releasing PeerConnection and DataChannels (the rest of WebRTC): https://bugzilla.mozilla.org/buglist.cgi?query_based_on=WebRTC%20blocking;status_whiteboard_type=anywordssubstr;query_format=advanced;status_whiteboard=blocking-webrtc%2B;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;known_name=WebRTC%20blocking
Blockers in Question for PeerConnection and DataChannels: https://bugzilla.mozilla.org/buglist.cgi?list_id=6168658&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=blocking-webrtc%3F
WebRTC Uplift Bugs: https://bugzilla.mozilla.org/buglist.cgi?list_id=6242297&resolution=FIXED&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=webrtc-uplift
Android gUM Blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=6371418&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=android-gum%2B
Android PeerConnection and DataChannels Blockers: https://bugzilla.mozilla.org/buglist.cgi?list_id=6371420&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=android-webrtc%2B
Turn Bugs: https://bugzilla.mozilla.org/buglist.cgi?list_id=6315579&resolution=---&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=turn Intermittent failures in WebRTC Automation: https://bugzilla.mozilla.org/buglist.cgi?keywords=intermittent-failure%2C%20&keywords_type=allwords&list_id=6167884&resolution=---&query_format=advanced&component=WebRTC&component=WebRTC%3A%20Audio%2FVideo&component=WebRTC%3A%20Networking&component=WebRTC%3A%20Signaling&product=Core
Android User Stories/Progress: https://webrtc-apps.etherpad.mozilla.org/4
