Jump to content
Flirc Forums

daniel87

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

1 Neutral

About daniel87

  • Rank
    Curious Flirc-er
  1. +1 for this function: would be super useful for my setup.
  2. I ended up buy Flirc and followed this guide: Works great. Solved: Problem 1 - programmed Flirc keystrokes as CTRL-ALT-SHIFT-<some key>. Odd enough combination to not conflict with anything else. (If this does conflict and becomes annoying, will contact you about your HID solution, yawor ;) ) Then I mapped these keys in Event Ghost to correspond to XBMC commands through the Event Ghost plugin. Problem 2 - Programmed my Netflix remote button to tell Event Ghost to disable the XBMC events. When I switch back to HDMI input on my TV (i.e., PC running XBMC), I just have to press record on my remote (unused otherwise) to re-enable XBMC events. Problem 3 - haven't walked through the solution here yet, but it should be possible to solve this in a similar manner. Extra - pressing another unused button on my remote launches XBMC, and/or brings it to the foreground, and/or maximizes it (all the states in which I might leave XBMC when walking away from my PC). Next up is programming another remote button to launch Steam in Big Picture mode and switch default audio output to HDMI (shortcoming of Steam, unfortunately, but I have a script ready for this), and I'll be all set :) Only negative feedback I have for Flirc is that it wasn't exactly plug n play. When I first plugged it in I was able to program it okay, but it wouldn't forward any events to Windows (Windows 7, x64) afterwards. Looked around a bit on the forums and someone suggested unplugging the regular keyboard and Flirc, then plugging in Flirc followed by the regular keyboard. That fixed things, and Flirc worked smoothly afterwards. The range on it is great too... really an great device.
  3. This guide is the primary factor that convinced me that Flirc is the best solution for my setup. Fantastic guide, fully automated my entertainment :P
  4. Found a solution that "locks" the PC from responding to any keyboard presses until a specific key combination is pressed. Will work perfectly here.
  5. @rowsdower: this is *perfect*. I'm facing an almost identical situation (). Thank you for sharing your solution.
  6. Thanks for taking the time to go walk me through the problem. Here are a couple of follow up questions in an attempt to work around the issues you described: Regarding problem 1: a ) Can I set up Flirc such that pressing a button runs a script in addition to pressing a keyboard button? What I'm thinking is that in addition to forwarding "left", "right", as keyboard events, Flirc also runs a script (AutoIt, AutoHotkey, etc.) first to change focus to XBMC if that isn't already the case. The overhead from running the script should be small enough. b ) If it's not possible for Flirc to associate 2 actions with 1 button press: --> Can I train Flirc to associate a button press with *just* running a script? Either directly or through Windows global hotkeys? --> If the above is true, then I see 2 options: 1) Dedicate a single remote button to running the focus-shifting script, or 2) do the focus change *and* the action button press ("left", "right", etc.) in the script, which is triggered by Flirc. Think any of this is doable? Regarding problem 2: Is there a way to associate a button press with enabling/disabling Flirc? What I'm thinking is using the Netflix button on my remote to tell Flirc "ignore any further button presses", and a second dedicated button on my remote to tell it "resume forwarding remote presses". If that's not possible then I can get fancier and wrap all the keyboard press actions in scripts, and associate button presses with those scripts through Flirc (if possible, see above). Then use 2 buttons on the remote to tell the scripts (instead of Flirc) to allow/disallow button presses. Maybe I'm trying too hard and there's an easier single-remote solution (other then CEC-USB adapter, which is $50, or a dedicated CEC-enabled XBMC host), let me know.
  7. Hi, I came across Flirc by chance on the interwebz and I'm interested. Here's my setup, wondering if Flirc makes sense here: - General purpose PC with an Nvidia GPU: DVI port connected to a regular PC monitor, and HDMI port connected to a Vizio M series 2014 TV. Windows is running in extended desktop mode. Regular Windows desktop is shown on the DVI monitor, and XBMC is shown on the secondary monitor (TV). - Remote is the remote that came with the TV; has a keyboard on the back I'd like to use with Flirc if possible Here are my questions: I read that Flirc is detected as a keyboard input. Can I set it so input from Flirc goes to XBMC only, rather to where Window's focus is? Here's a use case: I'm watching XBMC on the TV with Flirc. I go to my PC to browse the internet for a bit using M&K that are plugged in. I come back to the TV - I don't want input from Flirc to suddenly go to my browser rather than XBMC. If I now switch the TV from HDMI input (XBMC on the PC) to Netflix running on the TV, is it possible to set it so that Flirc ignores presses on the remote? That is, when switching to the TV's Netflix, I want "right" to affect Netflix on the TV only, not XBMC that's still running on the PC but isn't being displayed anywhere. Can I train Flirc to use the full keyboard on the remote? Thanks for any input.
×
×
  • Create New...