No | Meta Name | Value |
1 | viewport | width=device-width |
No | Keyword | Website Count |
1 | Dailymotion | 7 |
2 | Vimeo | 11 |
3 | Wordpress plugin | 5 |
4 | Youtube | 101 |
5 | Predictions | 5 |
6 | Webrtc | 4 |
7 | Collaboration | 20 |
8 | Startup | 32 |
9 | Html5 | 62 |
10 | Node.js | 14 |
11 | Video | 379 |
12 | Conference | 27 |
13 | Presentation | 14 |
14 | Books | 98 |
15 | Html5 video | 2 |
16 | W3c | 5 |
17 | Accessibility | 5 |
18 | Captions | 3 |
19 | Subt**les | 20 |
20 | Standards | 8 |
No | Text |
1 | Ginger's thoughts |
2 | Annual release of external-videos plugin – we’ve hit v1.0 |
3 | Webrtc predictions for 2016 |
4 | My journey to coviu |
5 | Webvtt audio descriptions for elephants dream |
6 | Progress with rtc.io |
7 | Apprtc : google’s webrtc test app and its parameters |
8 | Use deck.js as a remote presentation tool |
9 | Webrtc books – a brief review |
10 | Webvtt discussions at foms |
11 | Webvtt as a w3c recommendation |
12 | Posts navigation |
No | Text |
1 | Silvia's blog |
No | Text |
1 | Advantages of a w3c recommendation |
2 | Choice of working group |
3 | The forthcoming process |
4 | Making the best of a complicated world |
5 | Categories |
6 | Archives |
7 | Meta |
No | Text |
1 | This is the annual release of my external-videos wordpress plugin and with the help of Andrew Nimmolo I’m proud to annouce we’ve reached version 1.0! |
2 | WebRTC Browser support |
3 | Codec Observations |
4 | The Enterprise Boundary |
5 | Summary |
6 | new video conferencing room |
7 | 640×480 resolution by default |
8 | Here are my favourite parameters: |
9 | UPDATE 12 May 2014 |
10 | Rob Manson’s awesome book “Getting Started with WebRTC” |
11 | 1. WebVTT Regions |
12 | enable |
13 | 2. Unify Rendering Approach |
14 | 3. Vertical Features |
15 | 4. Best Practices |
16 | 5. Non-caption use cases |
17 | 5.1 Preview Thumbnails |
18 | 5.2 Chapter markers |
19 | 5.3 Inband tracks for live video |
20 | 5.4 Cross-domain VTT loading |
21 | 6. Regions in live captioning |
22 | Given that Web browsers don’t need WebVTT to become a W3C standard, why then should we spend effort in moving the spec through the W3C process to become a W3C Recommendation? |
23 | So, a good process needs to be developed to allow everyone to contribute to the spec in the best way possible without requiring duplicate work. How can we do that? |
No | Text |
1 | hd=true |
2 | stereo=true |
3 | debug=loopback |
4 | tt=60 |
5 | https://apprtc.appspot.com/?r=82313387&hd=true&stereo=true&debug=loopback |
6 | ss=[stunserver] |
7 | ts=[turnserver] |
8 | tp=[pa***word] |
9 | audio=true&video=false |
10 | audio=false |
11 | audio=googEchoCancellation=false,googAutoGainControl=true |
12 | audio=googNoiseReduction=true |
13 | asc=ISAC/16000 |
14 | arc=opus/48000 |
15 | dtls=false |
16 | dscp=true |
17 | ipv6=true |
18 | arbr=[bitrate] |
19 | asbr=[bitrate] |
20 | vsbr=[bitrate] |
21 | vrbr=[bitrate] |
22 | https://apprtc.appspot.com/?r=&asbr=128&vsbr=4096&hd=true |
23 | BTW: somebody should really fix that print style sheet for deck.js – I’m only ever getting the one slide that is currently showing. 😉 |
Icon | Domain | IP | Alexa Rank |
Nationalcrimecheck.com.au | ![]() |
116.669 |