14:58:22 RRSAgent has joined #me 14:58:26 logging to https://www.w3.org/2025/01/07-me-irc 14:58:26 Zakim has joined #me 15:00:16 igarashi has joined #me 15:01:05 Chair: Chris 15:01:15 Meeting: MEIG monthly meeting 15:01:19 agenda: https://lists.w3.org/Archives/Public/public-web-and-tv/2024Dec/0001.html 15:02:06 present+ 15:02:09 Present: Bernd_Czelhan, Chris_Needham, Kazuyuki_Ashimura, Tatsuya_Igarashi, Hisayuki_Ohmata, Louay_Bassbouss, Ryo_Yasuoka 15:02:18 Chair: Chris, Igarashi 15:02:56 rrsagent, make log public 15:02:59 rrsagent, draft minutes 15:03:00 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:03:36 present+ Francois_Daoust 15:04:56 present+ Rob_Smith 15:05:46 nhk_ryo has joined #me 15:05:57 scribe+ cpn 15:06:08 ohmata has joined #me 15:06:38 topic: Agenda 15:06:41 Louay has joined #me 15:06:54 present+ Louay_Bassbouss 15:06:57 cpn: (summarizes the agenda) 15:07:14 ... Sync on the Web CG, SVTA MSE issue review 15:07:25 ... anything else for today? 15:07:30 (none) 15:07:55 topic: Sync on th Web CG 15:07:59 s/th /the / 15:08:37 cpn: there was a breakout session during TPAC hosted by Kensaku Komatsu on media synchronization over QUIC 15:08:46 ... low latency media sync 15:09:23 i|summa|-> https://www.w3.org/2011/webtv/wiki/images/3/37/2025-01-07-W3C-MEIG.pdf slides| 15:09:44 i|there|[slide 3]| 15:09:48 rrsagent, draft minute 15:09:48 I'm logging. I don't understand 'draft minute', kaz. Try /msg RRSAgent help 15:09:54 s/rrsagent, draft minute// 15:09:55 rrsagent, draft minutes 15:09:57 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:10:07 ... a CG has been created 15:10:17 -> https://www.w3.org/community/sync-on-the-web/ Sync on the Web CG 15:10:25 cpn: planning to participate in the CG 15:11:13 ... not sure about the group's plan yet at the moment, but once they've got settled, can get more information 15:11:39 topic: MSE issues recap 15:11:44 [slide 4] 15:11:58 -> https://www.w3.org/2024/12/10-me-minutes.html Dec-10 minutes 15:12:26 cpn: continue discussion about MSE issues discussed on Dec 10 15:12:32 subtopic: Buffer capacity 15:12:39 [slide 5] 15:12:55 cpn: (revisits the topic around buffer capacity) 15:13:19 ... related to the MSE introspection API 15:13:32 ... several feature request proposals 15:13:57 -> https://github.com/w3c/media-source/issues/35 Issue 35 - Report buffer changes in update events 15:14:21 -> https://github.com/w3c/media-source/issues/40 Issue 40 - Needs event to notify when sourceBuffer needs more data 15:14:48 -> https://github.com/w3c/media-source/issues/172 Issue 172 - Consider adding API for app to know how much room is left in the SourceBuffer 15:15:16 -> https://github.com/w3c/media-source/issues/259 Issue 259 - Consider adding support for apps to get metadata about what is currently buffered 15:15:40 -> https://docs.google.com/document/d/1XBSu9x-z8gHwh0R_0Py7N8OuRz9QpNAld9AvQt8NSpY/edit?tab=t.0#heading=h.1wolj05z6ipg MSE SourceBuffer Introspection Proposal 15:15:57 cpn: we'd like to see solutions 15:16:17 ... would suggest we use the Issue 172 for that purpose 15:16:28 ... but we should also see the other related issues 15:16:56 ... then Managed MediaSource bufferedchange events 15:17:06 ... would be also helpful 15:17:11 ... another point raised is 15:17:25 ... requiring web apps to append mdat box structures 15:17:35 dsilhavy has joined #me 15:17:57 ... some implementations are more restricted 15:18:03 RobSmith has joined #me 15:18:07 present+ Daniel_Silhavy 15:18:12 ... not sure if we have this within the existing test suite 15:18:22 rrsagent, draft minutes 15:18:23 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:18:43 ... might be useful to have guide for implementations 15:18:54 ... for constrained devices 15:19:05 q? 15:19:52 ds: (gives comments) 15:20:09 ... all the legacy devices 15:20:32 ... don't need to import the mdat box structures 15:20:50 cpn: try to identify the device's capability 15:21:23 ds: thinking to add some buffer to improve the performance 15:22:06 lb: we're talking about two different test runners 15:22:13 ... we can have some test caes 15:22:20 ... to see the implementations 15:22:40 ...also prepared contents 15:23:14 ds: by position the box is closed 15:23:35 ... don't think we need a new test case 15:23:43 lb: need a piece of information 15:24:20 fd: not sure if the box parsing is equivalent 15:24:32 ... maybe some test case to be added 15:24:48 cpn: suggesting a test case for the Web platform? 15:24:49 fd: yeah 15:24:56 cpn: would make sense 15:25:11 lb: the question is always about the API 15:25:35 ... requires additional observation 15:25:45 ... in order to validate the data 15:25:59 ... the question is how to streamline the tests 15:26:13 ... also where to contribute 15:26:25 cpn: yeah, observation framework is a question 15:26:37 subtopic: Box parsing 15:26:42 [slide 6] 15:26:47 rrsagent, draft minutes 15:26:48 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:26:55 cpn: next is box parsing 15:27:24 -> https://github.com/w3c/media-source/issues/189 Issue 189 - Add Support for Media-Encoded Events 15:27:43 cpn: issue 189 adds support for media-encoded events 15:28:03 ... particular use case there 15:28:14 ... API proposal for DataCue 15:28:41 -> https://www.w3.org/TR/media-timed-events/ Requirements for Media Timed Events Note 15:29:04 -> https://github.com/WICG/datacue/blob/main/explainer.md DataCue proposal 15:29:39 -> https://wicg.github.io/datacue/ Draft DataCue API spec by WICG 15:30:00 cpn: very happy to support people who would like to work on that 15:30:18 ... think we mentioned this during TPAC 15:30:26 ... adding subtitles and captions in MSE 15:30:43 -> https://www.w3.org/2024/09/26-mediawg-minutes.html#t07 TPAC 2024 discussion 15:31:21 i|summarizes the agenda|scribenick: kaz| 15:31:31 rrsagent, draft minutes 15:31:32 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:31:56 cpn: questions about use case-specific APIs 15:32:05 ... for box parsing 15:32:16 ... there was a question around performance 15:32:22 ... about container parsing 15:32:55 -> https://github.com/w3c/webcodecs/issues/24 webcodecs Issue 24 - API for containers? 15:33:20 -> https://github.com/w3c/media-and-entertainment/issues/108 MEIG Issue 108 - Media Containers API 15:33:44 cpn: would be better to have native APIs rather than JavaScript 15:34:12 ... then WebCodecs and Canvas based player 15:34:39 -> https://github.com/w3c/webcodecs/issues/41 webcodecs Issue 41 - Support for content protection 15:35:03 cpn: buffering and rendering for delivering the data 15:35:24 ... to look at use cases again 15:35:36 ... e.g., timed metadata 15:36:23 ... need more investigation 15:36:35 ds: we have cases and workaround 15:36:59 ... just requirement for people's writing content 15:37:10 cpn: is this a particular one for starting? 15:37:34 ... or move boxes in general 15:37:56 ... this question comes back to the performance question 15:38:43 rs: to follow up the generic metadata discussion 15:38:59 ... found myself moving more generic metadata aspect 15:39:15 ... exposing the type filtering the design of the metadata 15:39:26 ... what you're interested in 15:39:48 ... the other problem is recently used datacue 15:39:56 ... specifically identify the timed text 15:40:30 ... rendering the timed text which is not relevant any more 15:40:46 ... it's more than parsing efficiency 15:41:06 ... I have the way I'm approaching 15:41:20 ... WebVTT aimed at spatial data 15:42:10 cpn: you're carrying the information using WebVTT 15:42:22 rs: yes, specifically, timed location 15:42:40 ... there are a number of use cases 15:42:56 ... e.g., monitoring collisions of vehicles 15:43:14 ... the scope of this is growing it quickly and handle metadata for specific use case 15:43:29 ... would be accessed by web apps 15:43:38 cpn: what kind of scope do you have? 15:43:54 ... this is an important capability, though 15:44:03 rs: looking at that 15:44:36 ... main focus is aimed at harmonizing multiple existing capabilities 15:44:57 ... in campuses 15:45:11 ... different levels of details from various scales 15:45:22 ... applications to online maps 15:45:44 ... aiming to do trying to harmonize and utilize the resources 15:45:59 rrsagent, draft minutes 15:46:00 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:46:07 ... can provide some link 15:46:11 cpn: would be helpful 15:46:46 ... you're proposal might be simpler 15:47:08 ... perhaps decoupling what we're proposing could be more productive 15:47:21 ... let's follow up that 15:47:44 subtopic: Codec information 15:47:49 [slide 7] 15:48:07 cpn: some more query API, e.g., codec information 15:48:21 ... related to MSI introspection API 15:48:36 OGC Testbed-20 GIMI aims: https://portal.ogc.org/files/108074#GIMI 15:48:41 -> https://github.com/w3c/media-source/issues/259 Issue 259 - Consider adding support for apps to get metadata about what is currently buffered 15:48:55 cpn: bundled issues there 15:49:09 ... related to buffer capacity and introspection capacity 15:49:28 subtopic: Dynamic addition/removal of Source Buffers 15:49:37 [slide 8] 15:50:26 -> https://github.com/w3c/media-source/issues/160 Issue 160 - Support playback through unbuffered ranges, and allow app to provide buffered gap tolerance 15:50:36 cpn: not sure if that covers all the issue around this 15:51:11 atai has joined #me 15:51:14 ... part of the API but not necessarily implemented 15:51:23 ds: one use case in my mind 15:51:36 ... sometimes multiple periods there 15:51:58 ... still need initial one to keep the playback 15:52:25 ... play audio and then video next 15:52:45 ... could fill in dummy data 15:52:57 ... then continue to play back 15:54:57 s|-> https://www.w3.org/2011/webtv/wiki/images/3/37/2025-01-07-W3C-MEIG.pdf slides|slideset: https://www.w3.org/2011/webtv/wiki/images/3/37/2025-01-07-W3C-MEIG.pdf| 15:55:14 cpn: media over QUICk vs DASH 15:55:20 rrsagent, draft minutes 15:55:21 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 15:55:49 ... continuing DASH playback 15:56:14 ... not sure if there is any written-down use case about multi-period 15:56:40 ds: try to create an issue 15:56:43 cpn: please do 15:57:07 ... something written down in the MSE issue tracker 15:57:16 subtopic: Multiple Source Buffers 15:57:20 [slide 9] 15:57:44 -> https://github.com/w3c/media-source/issues/357 Issue 357 - Proposal: Have a detachable MediaSource object 15:57:57 cpn: similarly, not sure the use case is covered 15:58:07 ds: segments might be overlapped 15:58:36 cpn: (goes through Issue 357) 15:59:09 ... detach a MediaSource from a media element 15:59:26 s/element/element temporarily/ 15:59:39 q+ 16:00:09 ... maybe a new Issue is needed for this point 16:00:32 ... didn't see another issue in the MSE repo around your use case 16:00:48 ack kaz 16:01:06 Kaz: Next steps? Create issues or comments on the existing issues is a key question 16:01:17 i/Next/scribenick: cpn/ 16:02:20 ... We can talk about additional issues next time 16:03:01 q- 16:03:05 rrsagent, draft minutes 16:03:07 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 16:03:41 cpn: would like to talk with Daniel about that 16:04:09 ... next meeting will be held on Feb 4 16:04:15 [adjourned] 16:04:22 i/would like/scribenick: kaz 16:04:26 rrsagent, draft minutes 16:04:28 I have made the request to generate https://www.w3.org/2025/01/07-me-minutes.html kaz 18:11:18 Zakim has left #me