[mythtv-users] What major features are planned for 0.27?
fatgerman at gmail.com
Sat Nov 24 13:48:55 UTC 2012
On Friday 23 Nov 2012 22:37:34 Michael T. Dean wrote:
> On 11/23/2012 10:02 PM, Preston Crow wrote:
> > On 11/23/12 21:58, Michael T. Dean wrote:
> >> On 11/21/2012 10:10 AM, Mark Greenwood wrote:
> >>> One thing that could be contributed though, and I don't know how
> >>> easy/hard this would be but with pointers I'd be prepared to look into
> >>> it, would be to make mythtv understand the multimedia keycodes sent by
> >>> IR remotes that are handled by the kernel's devinput interface (eg
> >>> KEY_PLAY, KEY_FASTFORWARD etc). Xbmc understands these natively and
> >>> means I didn't have to go through the trauma of setting up lirc.
> >> Pretty sure you just need to use mythfrontend's Edit Keys to set what
> >> you want each to do.
> > Yes, but the point is that this is something that should just work
> > without doing anything. There should be good default settings for all
> > those keycodes already. (This hasn't impacted me, but it sounds like
> > a simple and obvious improvement.)
> Of course, you do understand that there are both TV Playback|PLAY, and
> TV Playback|PAUSE (which is toggle play/pause).
> It's neither simple, nor obvious, to me which one the play button on
> Mark's remote should send... And the play button is the simplest of the
> multimedia ones... Does fast forward do a Global|RIGHT or TV
> Playback|SEEKFFWD or TV Playback|FFWDSTICKY or even TV Playback|JUMPFFWD?
Actually it's only complicated because mythtv makes things complicated by having too many choices. XBMC seems to take a much more pragmatic view. In a logical, simple world the Play key starts playback, the Pause key pauses and unpauses, and the Fast Forward button fast forwards - just like on any off-the-shelf PVR system made in the last 30 years, because people understand that. It's obvious what the default settings should be, and people can still customize if they want to.
The keys on my remote are already mapped by the kernel's ir-keytable interface - no need for LIRC. The mapping means that whatever your remote, the kernel sends something sensible - KEY_PLAY when you press Play, KEY_FASTFORWARD for FF etc, so assigning them to functions the average PVR should have should be simple. Of course there will alays be some that need tweaking by the user, but a sensible set of defaults that would work with any remote of this type wouldn't be hard to come up with. LIRC is pretty old hat these days, the latest kernel has mappings for most of the common remotes already.
> It's easy enough deciding which keys on a keyboard do what--because the
> user has them all available and can just hit the ones he wants. With a
> remote, though--where remotes don't even have standard layouts, let
> alone number and type of buttons--a "default for all remotes" mapping
> makes little sense.
> That said, once I finish the key binding "themes" patch (coming along
> with the overloaded key bindings fix), it will allow you all to decide
> what keys do what (and share those mappings with others).
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users