Re: [TOOLS-DEVELOPMENT] Meetecho Thoughts

Alexa Morris <amorris@amsl.com> Fri, 12 April 2019 21:16 UTC

Return-Path: <amorris@amsl.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D9B1200EC for <tools-development@ietfa.amsl.com>; Fri, 12 Apr 2019 14:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2CX9RblRaaG for <tools-development@ietfa.amsl.com>; Fri, 12 Apr 2019 14:16:32 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DF8412009A for <tools-development@ietf.org>; Fri, 12 Apr 2019 14:16:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9FD271C1E55; Fri, 12 Apr 2019 14:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrI0Aov97pLU; Fri, 12 Apr 2019 14:16:17 -0700 (PDT)
Received: from [IPv6:2601:647:4200:85ab:4528:455a:315:b407] (unknown [IPv6:2601:647:4200:85ab:4528:455a:315:b407]) by c8a.amsl.com (Postfix) with ESMTPSA id 6143E1C1888; Fri, 12 Apr 2019 14:16:17 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Message-Id: <7320BDB6-1FD7-449D-83EE-A19966FB14EF@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_69235152-F851-4D41-BCE6-FC97F4957CAC"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 12 Apr 2019 14:16:14 -0700
In-Reply-To: <576f3104-9936-7fb1-127b-c59e960fcc51@nostrum.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, IETF Tools Development <tools-development@ietf.org>
To: Adam Roach <adam@nostrum.com>
References: <9D205B0A-7A1B-4E63-B0E3-D597B966D254@bangj.com> <6199636f-1ddc-6ae3-9907-53ad5ecf7bf5@nostrum.com> <a966b86e-0530-8a00-6d8a-1bf0ea3b366f@nostrum.com> <74fb0dba-d1a1-ab1c-686e-56f2502a0a39@nostrum.com> <576f3104-9936-7fb1-127b-c59e960fcc51@nostrum.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/VZOW0FwYQ6z6wvYsgiShzFl9j4o>
Subject: Re: [TOOLS-DEVELOPMENT] Meetecho Thoughts
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2019 21:16:36 -0000

Just to provide an update here, Robert and I are going to have a call with Tom and the Meetecho team in a couple of weeks, with the goal of better understanding what changes would be involved from the Meetecho side. We will report back on what we learn.

Alexa

> On Apr 2, 2019, at 2:21 PM, Adam Roach <adam@nostrum.com> wrote:
> 
> I suspect it's mostly a matter of asking the MeetEcho folks for pointers to their formats. For example, the Jabber transcripts can be seen in an easy-to-use JSON format here:
> 
> https://play.conf.meetecho.com/Playout/session/IETF104-DOH-20190326-1120 <https://play.conf.meetecho.com/Playout/session/IETF104-DOH-20190326-1120>
> 
> And the timestamped transcript is here:
> 
> https://play.conf.meetecho.com/Playout/resources/IETF104-DOH-20190326-1120 <https://play.conf.meetecho.com/Playout/resources/IETF104-DOH-20190326-1120>
> 
> /a
> 
> 
> On 4/2/19 4:03 PM, Robert Sparks wrote:
>> Yes, but Tom's looking for something using an open format that he can integrate into things like his app.
>> On 4/2/19 4:01 PM, Adam Roach wrote:
>>> FWIW, Meetecho already produces a playback application that gets you several of the features that Tom has described. See, e.g.:
>>> 
>>> https://play.conf.meetecho.com/Playout/?session=IETF104-DOH-20190326-1120 <https://play.conf.meetecho.com/Playout/?session=IETF104-DOH-20190326-1120>
>>> 
>>> You can find these on the IETF HTML Agenda by clicking on the "M" meetecho button.
>>> 
>>> /a
>>> 
>>> 
>>> On 4/2/19 12:50 PM, Robert Sparks wrote:
>>>> Tools team:
>>>> 
>>>> Below is a short conversation with Tom Pusateri (the creator of the IETFers iOS app) about the usability of the current youtube videos and what we might strive for that's better.
>>>> 
>>>> Do any of you know people who could help us do better than we are currently?
>>>> Should we ask Meetecho what they think they could do to get closer to what Tom describes?
>>>> RjS
>>>> 
>>>> -------- Forwarded Message --------
>>>> Subject:	Re: Meetecho Thoughts
>>>> Date:	Tue, 2 Apr 2019 12:02:41 -0400
>>>> From:	Tom Pusateri <pusateri@bangj.com> <mailto:pusateri@bangj.com>
>>>> To:	Robert Sparks <rjsparks@nostrum.com> <mailto:rjsparks@nostrum.com>
>>>> 
>>>> Certainly. The more awareness the better.
>>>> 
>>>> Tom
>>>> 
>>>> 
>>>>> On Apr 2, 2019, at 11:22 AM, Robert Sparks <rjsparks@nostrum.com> <mailto:rjsparks@nostrum.com> wrote:
>>>>> 
>>>>> Got it.
>>>>> 
>>>>> May I forward the thread so far to the tools team (or at least to Russ)?
>>>>> 
>>>>> RjS
>>>>> 
>>>>> On 4/1/19 4:23 PM, Tom Pusateri wrote:
>>>>>> Robert,
>>>>>> I probably shouldn’t have mentioned SMIL because that’s a solution not a problem. I’m not trying to dictate a solution, only an open format that we can experiment with the streams to combine them in more useful ways. I’ve parsed the jabber logs in the past and that’s doable but there’s very little information in them anymore.
>>>>>> 
>>>>>> I think the slide change info can be done in real time by looking at the video (that will take some code) or using a custom presenter.
>>>>>> 
>>>>>> My purpose is mainly to try to get people thinking in a way and have a goal to shoot for instead of just continuing in the current mode which is difficult to integrate and is not a great user experience. Youtube videos don’t play well with mobile data plans when mostly what you want is audio and synchronized slides.
>>>>>> 
>>>>>> Thanks,
>>>>>> Tom
>>>>>> 
>>>>>> 
>>>>>>> On Apr 1, 2019, at 4:50 PM, Robert Sparks <rjsparks@nostrum.com> <mailto:rjsparks@nostrum.com> wrote:
>>>>>>> 
>>>>>>> Hi Tom -
>>>>>>> 
>>>>>>> If memory serves, SMIL is still quite difficult to create, and capturing the events you detail below will be labor intensive (particularly the speaker switches). I can bring this up with the tools team, but unless I'm mis-remembering, your ask here is quite large.
>>>>>>> 
>>>>>>> RjS
>>>>>>> 
>>>>>>> On 4/1/19 2:14 PM, Tom Pusateri wrote:
>>>>>>>> Robert,
>>>>>>>> I sent this summary below to Portia and Alexa based on a quick meeting in Prague. I would like to see the deliverables from Meetecho be more open than a youtube video and an mp3 file per session. They suggested I talk with you first to see how my goals align with the datatracker futures. Can we talk some time about this?
>>>>>>>> 
>>>>>>>> I find the youtube replays to be a poor user experience and I would like to do something better and think if we could get separate output streams synced together with SMIL descriptions, we might be able to experiment a bit.
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> Tom
>>>>>>>> 
>>>>>>>> 
>>>>>>>> IETF produces lots of media at main meetings, side meetings, remote participation meetings, etc.
>>>>>>>> 
>>>>>>>> Audio
>>>>>>>> Slides
>>>>>>>> Video
>>>>>>>> Jabber comments
>>>>>>>> Events
>>>>>>>> • Each speaker at the front of the room
>>>>>>>> • Each person coming to the microphone in the audience
>>>>>>>> • Slide changes
>>>>>>>> 
>>>>>>>> All media for a single session can be brought together in SMIL
>>>>>>>> 
>>>>>>>> https://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language <https://en.wikipedia.org/wiki/Synchronized_Multimedia_Integration_Language>
>>>>>>>> 
>>>>>>>> Then, many outputs can be generated from combinations of media and events.
>>>>>>>> 
>>>>>>>> Examples:
>>>>>>>> Audio only for low bandwidth consumption
>>>>>>>> Combination audio/slides with automatic slide changes (mp4)
>>>>>>>> Overlay jabber messages synchronized
>>>>>>>> Overlay Speaker identification with profile pics
>>>>>>>> 
>>>>>>>> One size fits all Youtube output format is not flexible enough for best user experience in app integration
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> TOOLS-DEVELOPMENT mailing list
>>>> TOOLS-DEVELOPMENT@ietf.org <mailto:TOOLS-DEVELOPMENT@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/tools-development <https://www.ietf.org/mailman/listinfo/tools-development>
>>> 
> 
> _______________________________________________
> TOOLS-DEVELOPMENT mailing list
> TOOLS-DEVELOPMENT@ietf.org
> https://www.ietf.org/mailman/listinfo/tools-development