21:40:35 RRSAgent has joined #htmlav
21:40:35 logging to http://www.w3.org/2011/11/02-htmlav-irc
21:40:48 rrsagent, make log public
21:40:55 ryoichi_ has joined #htmlav
21:40:58 jallan has joined #htmlav
21:41:10 si-wei has joined #htmlav
21:41:12 TPAC11 Breakout Session: HTML5 AV Club
21:41:26 gang has joined #htmlav
21:41:35 classically television was a live real-time broadcast medium, many watching same thing at once, optimized for showing lots of things to people at once
21:41:37 noriya_ has joined #htmlav
21:41:48 Vincent has joined #htmlav
21:42:33 dvd players to ipods to personal video cameras - designed to help migrate to allow video to be shared with samller groups
21:42:39 frankolivier has joined #htmlav
21:42:46 Clarke has joined #htmlav
21:43:40 noriya_ has joined #htmlav
21:43:57 use cases: 1) minimize latency - built with assumption over internet, 2) misused to classic television use case to everyone at once
21:44:09 jeanne has joined #htmlav
21:44:54 mhakkinen has joined #htmlav
21:45:16 Kevin: ... missing the two-way component; 3) previously recorded and edited (YouTube case).
21:46:00 Kevin: classic - news - if you watch cable news, sequence of pre-cut stories; and repeat over time
21:46:19 kevin: speech/radio/music radio equivalent - same thing
21:47:04 Kevin: make transitions seamless- not at the script level but the browser level; buffer to hear, then play this, play this
21:47:41 Kevin: and then i would contend - movie, long form drama, are this case, because they have a scene structure
21:47:52 tpod has joined #htmlav
21:48:07 Kevin; so you could define them as a play list of sequences.
21:48:13 igarashi has joined #htmlav
21:48:25 JMR has joined #htmlav
21:49:05 mav has joined #htmlav
21:49:31 Kevin: The other one not attended to in HTML5 video space. Is user generated content, and keep it, archival model, small number of viewers, compressing down to fit in the network
21:50:07 Kevin: is this the right use case list and are they well represented in the HTML spec
21:50:51 Mark Vickers: 1) only one spec so it has to work for everyone. 2) web and tv interested in all use cases, and interested in gaps
21:51:38 Mark: play list is one we have on the list to talk about tomorrow
21:51:52 Mark: play this sequence when the next one is done. Another need...
21:52:35 JMR_ has joined #htmlav
21:53:21 Mark: ... is adaptive streaming
21:53:46 Kevin: the adaptive streaming, that is one of the specs almost there to satisfy legal worry not tech worry
21:54:32 Mark: it is on a shared internet connection, and you don't have sufficient bandwidth, you choose one a lower bandwidth stream
21:55:17 Kevin: download the damn thing and play it
21:55:42 Cyril_ has joined #htmlav
21:56:08 Mark Watson: choose a bit rate commensurate to the bandwidth you have, or lower that meansyou can start playing it right away, but ... asdaptive straming is about fast start up and low buffering
21:56:46 Kevin: doing at chapter chck points
21:57:06 Mark: but you need 2-3 second points to do adaptive streaming correctly
21:57:15 jnurthen has joined #htmlav
21:57:37 Mark Vickers: even when we have full right to download we use adaptive streaming, because it will starts quicker
21:57:53 Mark Vickers: techological leap ahead
21:59:52 Mark Vickers: full download and adaptive streaming are well supported
22:00:42 Eric: extremely difficultto the point of making it not always work well, adding the kind of API people are talking about...
22:01:06 to do all the media loading and switching to do adaptive streaming, technical issues to make that work well that it cannot be resolved
22:02:14 Eric: example, experimental API in Chrome to write javascript to load media and to the decoder, javascript that does all the adaptive stremaing, everything except decode the media
22:02:45 Eric: i argue that it will be very very difficult to make that work as well as we want it to work, because there are some difficultor implossible tech issues that cannot be solved in the javascript layer
22:03:03 Eric: for example, caching media, all the data that gets loaded by Javascript is stored in memory
22:03:38 Eric: because of security constraints, cannot give javascript arbitrary access to the harddrive, so don't think it will be possible for the javascript to do sufficient caching of the media
22:04:13 mark vickers; may not want to do everything in javscript.
22:05:01 Eric: using now, load media from the server, figure out what byte ranges, feed it down to the decoder, and as long as you don't care about looping, allowing the user to seek back into content ...
22:05:16 without going back to the server. I don't know how to make it more intelligent...
22:05:26 Mark Watson: why couldn't it hold onto what it is given?
22:06:02 Eric: doesn't have thelogic - which data is being loaded - how much should be kept in cache - the data is in Javascript
22:06:09 Mark Watson: what kind of data?
22:06:24 Eric: how user is viewing media, duration of the whole thing, likelihoo...
22:06:41 Eric: when a seek happens...
22:07:21 Mark: i see what you mean, are you assuming, w... a different model, provide the position in the global timeline, then it would have th emap of what media goes where...
22:08:08 Kevin: stream orientation .. classic MPEG TS model. ...
22:08:43 Mark W: the current experimental web kit model - i wouldn't propose as a product model, but question about what goes on in javascript and what goes on underneath
22:09:00 Mark W: i imagine there is a smart division between those layers.
22:09:51 Eric: don't doubt your sincerity, but we need to be careful about adding something here because you have something there (in existing adaptive streaming solutions)
22:10:48 Kevin: 2-way conversation - we hae a spec heading towards that (webRTC) and viewed as a different thing from adaptive streaming world.
22:11:49 Kevin: the other, distinct case, where i accept adaptive streaming makes more sense, near live, sports game, (1-way near live) that may be a case...
22:13:07 eric_carlson has joined #htmlav
22:13:18 Kevin: ... the key difference is a close enough ... 1 way near live, two hour phone-in type thing, want to be listening in near real-time
22:13:39 ryoichi__ has joined #htmlav
22:13:49 Clarke: tradeoff bandwidth and computational power
22:14:25 ryoichi__ has joined #htmlav
22:15:33 Mark K: inband is one way, also out of band multiple tracks, no way of saying which one is best...
22:15:44 Eric: handled by existing spec
22:16:46 Kevin: the archival case, interesting, one case we have had - how do we deal with codecs, patent things, hardware things, and what i am wondering...
22:17:45 Kevin: ... is there space for archival, non-patented, non-compressed, is it worth building up use cases for playing back lightly compressed video, as well as focusing on the 264/webM view ehere everhthing ...
22:17:52 kevin: ... is rather strongly compressed.
22:18:18 Eric: i have thought about it - two things - i don't think it is worht putting in the spec. i don't think i tis useful to take up space in the spec...
22:19:06 Eric: ... what i do think is useful... so... if not in the spec the right way to handle it is to put pressure on browser vendors to support it.
22:19:37 Kevin: the principle that once you have made the media we want to keep it around... somewhat related to that is the input side of things...
22:19:55 howard218 has joined #htmlav
22:20:10 Kevin: which is in the spec but no one spupports it, file, particularly on mobile, audio and video ... but the browsers cannot import them
22:20:34 Kevin: ... is it a matter of grumbling to people...
22:20:46 Eric: and it could imply give me an interface to take a new photo
22:20:52 howard has joined #htmlav
22:21:02 Frank O: quality of implementatino issue, not a matter of changing spec?
22:21:17 Kevin: at the moment the spec says you will get images...
22:21:33 Kevin: Write a test suite and grumble...
22:22:01 tpod has joined #htmlav
22:22:38 Kevin: what else would be nice to do with AV that we cannot do now?
22:23:00 Mark Watson: protection of UGC - you want your family to view in the cloud, and have them be able to play it back
22:23:33 Eric: as people outside this room, save it like an image. Conrol key, audio or video and save it to the local system. if we enable that, some way for content owners to opt out of that
22:23:53 Kevin: saveable flag that defaults to YES
22:24:08 Kevin: and then you need to be able to set it
22:24:22 Kevin: user editability - ask for at all?
22:24:33 Kevin: once i can capture, can i trim it.
22:24:44 Mark: there is a media fragment API?
22:25:06 Eric; not the same thing. only attributes on the URL, to change it you have to change the source
22:25:28 Mark V: URL to point into a fragment, but it doesn't allow you to play from this point to that point because each is a separae URL
22:27:12 Kevin: ... plays into the editing question as well.
22:28:00 Mark Watson: tiny one. presently, you can find out from media element how much was buffered, but if the player is inteliignet enough to stop playback, it knows how much...
22:28:33 mark: needs to buffer, so it could show a progress bar, which is a better user experience than a spinning "wait" symbol.
22:29:01 Mark: right now, i cannot do a progress bar.
22:30:03 Kevin: scrubbing (dragging through to find where you want because there are no chapters)
22:30:13 Kevin is that a diff mode or payers problem
22:30:45 Mark: if VOD rather than live stream, knows how long and whatis available and get pull only those things to create whatever user interface you want
22:31:13 rrsagent, make log public
22:31:38 rrsagent, make minutes
22:31:38 I have made the request to generate http://www.w3.org/2011/11/02-htmlav-minutes.html marie
22:34:35 KevinMarks has joined #htmlav
22:35:10 tedleung has left #htmlav
22:36:22 Vincent has joined #htmlav
22:36:56 Vincent has left #htmlav
22:38:26 jun has left #htmlav
22:43:15 jeanne has joined #htmlav
22:46:58 si-wei has joined #htmlav
22:47:18 si-wei has left #htmlav
23:31:27 KevinMarks has joined #htmlav
23:32:01 jeanne has joined #htmlav
23:41:28 Zakim has left #htmlav