Jump to content
Flirc Forums

ixian

Members
  • Content count

    24
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by ixian

  1. Adding support for Nvidia Shield TV

    Did you also add the Nvidia Shield preset itself to your Harmony profile? Don't just use the AT-163, use them both.
  2. Adding support for Nvidia Shield TV

    What Harmony are you using? What is assigned to power on/off?
  3. Adding support for Nvidia Shield TV

    Mine goes to sleep when I power off via Harmony like the rest of my devices. When in doubt completely delete the Shield profile from the Harmony, re-add it, and for good measure wipe the FLIRC and re-run setup for it too like I posted. Or just live with it - the Shield draws very little power at idle, will auto-sleep anyway as you discovered, and in general isn't a big deal. Question: If it's asleep (via auto) does it turn on with your profile? If so something is messed up in it and you should start over. Record in what app? Live Channels? If there's a keyboard shortcut for that then it's just a matter of mapping it to a discreet IR code (doesn't matter what device) in the Harmony app. If there are no keyboard shortcuts for record in the app in question then not much FLIRC can do.
  4. Adding support for Nvidia Shield TV

    Do those apps support keyboard shortcuts? I think Plex does (at least it does on other platforms). Check their forums for a list of keyboard shortcut keys. Then it's just a matter of following the standard FLIRC process to map buttons on your remote to those keys. See my earlier post in this thread for more guidance on that. I don't know if the Vue app supports keyboard shortcuts. I know Netflix and HBO Go, etc. don't. For those the standard Shield remote keys are all you can use (and need, really, since the apps are designed that way).
  5. Bluetooth capability to be added at v3?

    That may be anecdotal for you but is not an inherent flaw. I use WiFi integration with a hub and one of my Shields and have no issues with latency whatsoever. A lot of factors can cause latency issues. You might have misunderstood me; I was just using IR as an example "what if". To your point though, yes, decoding IR signals is easy and straightforward, BT is another matter entirely and understanding the inner workings of remote control there is hard.
  6. Bluetooth capability to be added at v3?

    Imagine if, back in the day when IR got traction, all the different manufacturers implemented it, used their own codes, and refused to share them. And if there was no way to easily intercept and decipher said codes. That's more or less what you have with BT today. BT also has limitations and as for how "fast" it is that is entirely up to how well it is implemented. Logitech worked directly with Sony on their PS4 implementation, for example. Doing the same thing for example with a HTPC is an entirely different problem. If anything, I see wifi remote control becoming more common. The Shield and a few other devices already offer it (the Harmony can control the Shield over Wifi today) and virtually every device including TVs today have wifi, whereas BT isn't as common. The FLIRC is an excellent supplement to devices like these. For example, having full keyboard shortcuts mapped to IR makes the Shield far more functional with apps like Kodi that support keyboard shortcuts.
  7. Adding support for Nvidia Shield TV

    Follow my instructions above. If you first configure FLIRC using the Shield preset "home" button functionality should work across apps. You can assign it to any button on your Harmony you want.
  8. Adding support for Nvidia Shield TV

    The basics of how it all works, just in case: Start with the Harmony config since this seems to be tripping you up. You only need to pick one device for your Shield profile, and (ironically enough) you don't want to pick "Shield TV" WITH the Harmony since that profile is for models that have IR (or WiFi/BT if you have the Harmony hub) and you don't want that since you are using a FLIRC. Just pick something that has a lot of buttons available (for flexibility) and won't interfere with any other devices you have. A lot of us here us the ViewTV AT-163 profile. Pick it and name it whatever you want, like "Shield TV" :) Now your Harmony is programmed to send IR signals for all (or at least most) of it's buttons. *It doesn't matter what those signals are* as long as they are each unique and don't accidentally trigger other equipment (which is why the AT-163 is a good choice....unless of course you have one :) ). All that matters is that when you press a button, a unique IR command is blasted out. The FLIRC will do the rest. Now, the FLIRC. The FLIRC dongle takes those discreet IR signals and translates them to commands the Shield TV understands. When you program the FLIRC via its application and assign IR commands to buttons you want to make sure you use the Shield layout first, for the basics, because Jason updated the software with the correct commands the Shield needs. Specifically, the "ok" button now functions correctly cross-app. So choose that profile and manually (don't click "Go" and have it do it automatically, that will map some commands you want for Kodi later twice) click each button, then press the corresponding button on your Harmony remote to map it. Basically, the 4 directions, the "ok" button, the back button, and the home button. Pick the buttons on your Harmony you want to do those functions (should be obvious) and have at it. Once you've done that, bring up the Kodi layout. Now you can program buttons for things like Play, Pause, ff/rw, etc. If you want even more control, skip the Kodi layout and use the full keyboard layout instead. Pull up (or print) this page for reference: http://kodi.wiki/view/Keyboard_controls . That's a complete list of keyboard shortcuts for Kodi. You can assign buttons to whatever keys on the keyboard you want. Don't forget that with most Harmony's you can also create custom buttons if you want to map advanced stuff, like for subtitles. Again, it doesn't matter what IR commands are assigned to the Harmony for each button, as long as it is discreet! The FLIRC is going to take whatever IR signal you sent it and translate that to the correct keyboard command. Doing this will give you: Basic Shield remote functionality across all applications (except voice control, since there's no mic on the Harmony.) Advanced keymap control for apps that support full keyboard commands - like Kodi. Get it?
  9. Adding support for Nvidia Shield TV

    No problem! You gave me a discount once before, I just found the new ones on Amazon and they appeared to be your official channel (is that correct?) so it was just easier to get them from there. I currently have 4 in use, with one spare I carry in my laptop bag when I travel - it's great for hooking up my laptop to hotel TVs, I just carry a very small IR remote that I had laying around with me as well and I can watch Kodi from my hotel bed at night :) For the Shield/FTV you should bundle these with a decent right-angle usb adapter (or maybe just link folks to them). I use VCZHS brand adapters off Amazon; they allow me to put the FLIRC in a position where the IR receiver just clears the top of the Shield in the back. Looks very clean, no extension cables to deal with, and works great. For Shield or FireTV it's as perfect an IR setup as could possibly be.
  10. Adding support for Nvidia Shield TV

    Protip for new Shield FLIRC users using a Harmony: Don't run "automated setup" with the new Shield layout unless you want to exactly duplicate how the Shield remote works (and maybe you do). I found this mapped several things in the background, like playback functions (stop, etc.) to the remote, which meant I had to erase them and do them over. It also resulted in double-presses for some keys. Again, this was only after I first ran the auto-setup, then went back and mapped keys for Kodi, etc. manually. If you are doing the latter, wipe the FLIRC settings, then do a manual setup for all keys. Use the Shield layout for basic transport (navigation, ok, home, back) and then use the Kodi keymap - or just the full keyboard - for whatever else you want to do. If you are using a Harmony and have custom buttons set up for stuff like subtitles this way is easier anyway. This will result in a setup that works perfectly with all non-Kodi Shield functions - including in apps like HBO Go, etc. - and also works great for Kodi-specific stuff. I prefer playback keys (discreet play and pause, stop, ff/rw, etc.) for Kodi since it supports them so well and they are a natural thing to use with a Harmony.
  11. Adding support for Nvidia Shield TV

    Thanks for the update! Working great on both my Shields. I have the 2015 and 2017 non-pro model. FLIRC in particular is a boon for the new non-Pro since there's no IR receiver; hopefully with these updates you find FLIRC becomes just as popular with those as it is now for the FireTV devices. I have 7 FLIRCs now - 4 original from back in the day and 3 new ones from Amazon. Great update all around.
  12. Adding support for Nvidia Shield TV

    So, just to be clear, in the FLIRC software, I should choose the FireTV layout and press my existing Harmony "OK" button to pair it with the FTV? Will that work? I thought it was the IR command being sent by the remote that mattered. Or do I need to use an actual FTV remote to program it? Just want to make sure.
  13. Adding support for Nvidia Shield TV

    Anyone figured out the "Enter" button not working in some apps, like HBO Go, yet? I've gotten everything else to work but that one is aggravating.
  14. Adding support for Nvidia Shield TV

    Hi all, Did this ever get resolved? I've been a multi-Flirc user for years but just got a Shield TV. It is an awesome little device and Flirc works fine with it when I'm in Kodi, but there's no back/home button support outside of it. Anything I can do to help?
  15. Windows 8

    Awesome, much appreciated. I will try these tonight and let you know how it works.
  16. Windows 8

    Yes, that's basically what we've been talking about. In fact that page more or less exactly replicates instructions earlier in this thread :) It's not a good solution. Not only will it throw of a lot of users - and now that Windows 8 is officially released, that will happen more often - but it's a huge security risk because you are disabling signature enforcement for all drivers. I understand it's more or less a one man show with volunteer help, and I've been supportive of the effort (and I've also bought 4 FLIRC modules) but the lack of updates on this and many other issues is really starting to bum me out where this product is concerned. At the end of the day it is a paid product.
  17. Windows 8

    2012 Server uses the same NT kernel as Windows 8 but is significantly different in most other aspects, including driver signing, so this isn't too surprising. It'd be nice to have an update. Despite all the drama around Windows 8 and Metro (and likely a lower adoption rate as a result in my opinion) the fact is in about a week it's going to be on a lot of computers, and move up from there. If anything, it's Kiosk mode is even better and easier to implement than Windows 7, meaning that for users that want (or need) a Windows-based XBMC box will flock to it.
  18. Windows 8

    Any update on this? Windows 8 is, of course, just around the corner - literally - and many of us have had it for a while thanks to MSDN. While the workaround in this post is serviceable - and thanks for that, TBS and others - it's hardly a long term solution. For that matter, it's been a long spell without an FLIRC update and there are several other issues that need addressing - what's the state of the new release?
  19. Long shot question... MCE?

    I've configured MCE dozens of times over the years and I've never had it refuse to continue because I didn't have an IR receiver. Something isn't right here - are you sure you can't just skip that step? You can control MCE with a keyboard, I know that, so FLIRC should work fine with it. Edit: Wait, are you trying to do this with analog capture/set top boxes by chance? I.e. not with a tuner?
×