[mythtv-users] First time NVidia Shield + Remote Setup
Michael
mythtv at blandford.net
Wed Jan 23 17:47:57 UTC 2019
On 1/23/19 10:31 AM, A D wrote:
>
>
> On Wed, Jan 23, 2019 at 11:13 AM Greg Oliver <oliver.greg at gmail.com
> <mailto:oliver.greg at gmail.com>> wrote:
>
> On Wed, Jan 23, 2019 at 10:39 AM A D <ashu.desai at gmail.com
> <mailto:ashu.desai at gmail.com>> wrote:
>
>
>
> On Wed, Jan 23, 2019 at 10:34 AM Greg Oliver
> <oliver.greg at gmail.com <mailto:oliver.greg at gmail.com>> wrote:
>
> On Wed, Jan 23, 2019 at 10:05 AM A D <ashu.desai at gmail.com
> <mailto:ashu.desai at gmail.com>> wrote:
>
> Hello all
> I wanted to start a fresh chain so as to not mix up my
> initial email for help.
>
> I just bought NVidia Shield 4K gaming edition. Reading
> here from past emails, I know a lot of people said
> there were certain gotchas, especially setting up the
> remote the "right" way.
>
> Can someone please give me the 'best' practices on
> setting up the nVidia as a Frontend?
>
> Not sure if this matters, but I do not have TV
> recording on my backend. I am only doing this for
> Music/Photos/Videos (on my storage - NOT recordings)
>
>
> If you are not recording TV (or from a STB), then MythTV
> should not be your choice. There are way better suited
> media slingers out there with apps for most devices
> already available.
>
>
> I am sorry but don't agree with that - I have been using Myth
> for 12 odd years. When Comcast/Xfinity started encrypting TV
> channels, I stopped the TV recording on my end. However, I
> love Myth platform and even though there may be million other
> offerings that can do something better, I prefer keeping my
> bond with Myth.
>
> Appreciate the input, though.
>
> Reason I mention this is there were some emails about
> commercial skip and that doesn't affect me and didn't
> want someone to waste their time for me on it.
>
> Appreciate all the help you guys give, as always.
>
> Thank you!
>
> Ash
>
>
> No worries - I can appreciate that. The remote for the shield is
> pretty nice to use, but the new LONGPRESS entries in MythTV are
> non-intuitive, so I gave up trying to make them work. Every time
> I tried to train one in MythTV, the short button press kicked in
> and MythTV acted on it. I am unsure how to get them working, but
> since I have the Harmony stuff, I did not dwell on it too long and
> just use my harmony mapped to my keys as always. If you are going
> to use multiple Shields, I recommend upon first cofig of the
> frontend to make a unique identifier you can distinguish so MythTV
> does no make them all seem similar (in case you want to copy the
> keymappings from one Shield to the other in the database without
> having to go through it all over again).
>
> -Greg
>
>
> I honestly don't see myself getting multiple Shields - however, if the
> "right" way is to make a unique identifier - I guess I should do it
> that way? Is there a step by step somewhere on setting up the remote?
> Or should I search it online? I am asking here on our forums since
> need to customize it for my Myth
>
Even if you only use 1 shield, you should create a unique identifier.
Peter has indicated that the default identifier will change when new
packages are issued ( I think it was when new signing certs were used,
but I don't remember for sure). if you don't want to lose your
settings down the road, you should create a unique identifier from the
start.
There are multiple ways of managing the remote and they have been
discussed a fair amount of the last few months on the list. The most
common seem to be:
1) Using the long press entries
2) Use the harmony hub to bind using bluetooth and send keypresses from
the virtual keyboard
3) Use the USB flirc device + any remote (including harmony)
4) Use a remote that emulates a keyboard + USB dongle
5) Use a bluetooth keyboard/mouse
I am personally using #2 and #3 for my two shields.
Michael
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190123/c89bf903/attachment.html>
More information about the mythtv-users
mailing list