From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: VDR User <user.vdr@gmail.com>
Cc: Bastien Nocera <hadess@hadess.net>,
linux-input@vger.kernel.org, Sean Young <sean@mess.org>,
mchehab+samsung@kernel.org,
"mailing list: linux-media" <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2] Input: Add missing event codes for common IR remote buttons
Date: Thu, 24 Jan 2019 00:37:42 -0800 [thread overview]
Message-ID: <20190124083742.GB139904@dtor-ws> (raw)
In-Reply-To: <CAA7C2qiKOTKSWgmK_9ZyPC-JaBp+vW0nhoJMPJzHCmV_wsg8_A@mail.gmail.com>
On Tue, Jan 22, 2019 at 11:50:50PM -0800, VDR User wrote:
> > >
> > > KEY_DISPLAY_FORMAT doesn't open any menus and is used to cycle through
> > > how video is displayed on-screen to the user; full, zoomed,
> > > letterboxed, stretched, etc. KEY_CONTEXT_MENU would be for something
> > > like bringing up a playback menu where you'd set things like
> > > upscaling, deinterlacing, audio mixdown/mixup, etc.
> >
> > KEY_ASPECT_RATIO (formerly KEY_SCREEN).
>
> Physical displays have a single set aspect ratio (W/H). Images have
> their own aspect ratios. When the AR of the video to be display and
> the display itself are mismatched, you have to do something
> (letterbox, pillarbox, windowbox) to the video to maintain the correct
> video aspect ratio. You can't change the displays AR, and you aren't
> changing the videos AR so using KEY_ASPECT_RATIO makes no sense. AR
> isn't being touched/altered/manipulated, but how the video is being
> displayed is. Stretching and filling to match the display AR alters
> the video AR so there is makes sense, but then zooming may not. So,
> since "aspect ratio" kind of makes sense in a couple cases, and makes
> no sense in the rest, the more suitable KEY_DISPLAY_FORMAT is my
> suggestion.
No, we will not be renaming this key. We try to have parity with the
HUT, which has the following to say:
"Aspect OSC - Selects the next available supported aspect ratio option
on a device which outputs or displays video. For example, common
aspect ratio options are 4:3 (standard definition), 16:9 (often used
to stretch a standard definition source signal to a 16:9 video screen),
letter-box and anamorphic widescreen.The order in which the aspect
ratios are selected is implementation specific."
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-01-24 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 14:55 [PATCH v2] Input: Add missing event codes for common IR remote buttons Derek Kelly
2018-11-05 20:53 ` Sean Young
2018-11-13 13:04 ` Bastien Nocera
2018-11-13 16:20 ` VDR User
2019-01-19 8:52 ` Dmitry Torokhov
2019-01-23 7:50 ` VDR User
2019-01-23 10:18 ` Bastien Nocera
2019-01-23 16:07 ` VDR User
2019-01-24 8:37 ` Dmitry Torokhov [this message]
2019-01-24 16:21 ` VDR User
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190124083742.GB139904@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=sean@mess.org \
--cc=user.vdr@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox