Re: Scrolling as overlap avoidance (Re: Alternative approach to scrolling, with demos)

On Thu, May 8, 2014 at 6:22 AM, Christian Vogler <
christian.vogler@gallaudet.edu> wrote:

> The captions-follow-speaker use case is more complex than just simple
> left-right alignment. One example that occurs fairly frequently is having a
> group of multiple speakers all on-screen and they all respond to one
> particular question or statement with one or two words. Digging up actual
> video is harder, because one of the examples I remember most clearly I
> rented, but do not own.
>
> For this kind of use case, when we take possible font scaling into
> account, a horizontal center anchor , and a top vertical anchor almost
> always makes the most sense - i.e. when you scale the entire caption, you
> want it still to be centered below the speaker, and you want it to extend
> below the top margin, so that it does not obscure anything in the speaker
> itself.
>
There may be similar settings where it is desirable to position the text
over a speaker; in this case, lineAlign:bottom (or a suitable region anchor
point) would let the cue extend up as it grows.

> If I've been following you correctly, for the pop-on use case that is
> already handled for the cue box, and can be done irrespective of what
> happens with regions. Your question is only about regions themselves?
>
> Christian
>
> Sent from my mobile phone.  Please excuse any touchscreen-induced
> weirdness.
> On May 8, 2014 9:19 AM, "Philip Jägenstedt" <philipj@opera.com> wrote:
>
>> [I accidentally sent this reply off-list two days ago.]
>>
>> In the CPC demo, simple left and right alignment is used to follow the
>> speaker:
>> http://www.youtube.com/watch?v=BbqPe-IceP4
>>
>> Do you have an example where something more fancy than this is used?
>> Note that just by using the position, size and align setting you can
>> do fancier things, but an example would help determine if that's
>> enough or not.
>>
>> On Mon, May 5, 2014 at 6:31 PM, Christian Vogler
>> <christian.vogler@gallaudet.edu> wrote:
>> > To me, positioning for speaker identification makes the most sense in
>> terms
>> > of the anchor point - this point is the target for each speaker.
>> >
>> > Christian
>> >
>> >
>> > On Mon, May 5, 2014 at 12:27 PM, David Singer <singer@apple.com> wrote:
>> >>
>> >>
>> >> On May 5, 2014, at 5:00 , Philip Jägenstedt <philipj@opera.com> wrote:
>> >>
>> >> >> (2) the background color on the width and height of the rollup area
>> >> >> needs to be changeable
>> >> >
>> >> > Why? As I noted in the "background box tweaking" thread that's still
>> >> > possible with the sum of my suggestions, but I don't understand what
>> >> > the use case is.
>> >>
>> >> >> (4) move all the cues in the region as a group to another location
>> >> >
>> >> > This is also not handled by the current spec. I don't think it makes
>> >> > sense either, why not just end the cues and repeat them in a new
>> >> > position?
>> >> >
>> >>
>> >> I agree for these that if you want something ‘similar’ to appear as
>> what’s
>> >> already there, the clean thing to do is to re-draw it.  Same content
>> but in
>> >> a different region (with different position or colors), and so on.
>> >>
>> >> >
>> >> >> (3) font size changes on the region need to make the region go
>> bigger
>> >> >> centered out from the anchor point
>> >> >
>> >> > That's not handled by the current spec. We've talked about using
>> >> > font-relative units but that hasn't happened. I'd love to understand
>> >> > the use case for this though. Do you have an example video frame
>> where
>> >> > scaling around an anchor point is necessary as opposed to mode of
>> >> > scaling that happens with classical WebVTT?
>> >> >
>> >> >
>> >>
>> >> I also am curious
>> >>
>> >> David Singer
>> >> Manager, Software Standards, Apple Inc.
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Christian Vogler, PhD
>> > Director, Technology Access Program
>> > Department of Communication Studies
>> > SLCC 1116
>> > Gallaudet University
>> > http://tap.gallaudet.edu/
>> > VP: 202-250-2795
>>
>>

Received on Thursday, 8 May 2014 13:31:02 UTC