Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,730
  • Joined

  • Last visited

  • Days Won

    228

Posts posted by jason

  1. In short, I don't have anything or examples that will help get this done for you at the moment.


    Basically, you'll need to write a script that does exactly what you need. Then, you can assign that script to run on keyboard combination. Then, pair that keyboard combination in your harmony to some arbitrary button that's not being used. Then, add that to the power up/down sequence.


    Let me know if that makes sense.


    Very Sincerely,

    Jason

  2. Sorry, I'm traveling, in France right now.

    I would fire up a keyboard with XBMC/OSMC, and figure out which keyboard keys cause the volume to change. Then go to my pairing applicaiton, and record those keys as the volume up/down button on your remote. 

    Does that help? The keys you said that result from the remote presses may very well be because your keyboard is mapped to a different language and as such, is not sending the keys we expect. So you might have to translate your current keyboard to an english keyboard.

  3. Considering I work at NVIDIA full time, you'd think I would already have this done. I work on the Tesla line though, and it's been a really rough project schedule.

    I have been asking my friends on Tegra for a unit so I can get this done, it's been slow going, but I'll get it done soon.

    It's just a matter of mapping the keys. I tell you what, if you plug in a keyboard, and report back to me all the missing key buttons that show up on their basic remote, I'll credit back to you your order.

    Let me know how that sounds Sage, I'll put together the GUI update to take care of that for you.

     

    • Like 2
  4. If you are able to record buttons as the volume up/down key, on the remote, then everything is working. Now it's a matter of figuring out what keyboard keys control the volume in Kodi/OSMC. 


    Try the keys listed here: http://kodi.wiki/view/Keyboard_controls

    That's what should be in my GUI, but you never know, they update the shortcuts periodically.

    Looks like the + and - keys.

    Fire up a text editor, press those keys on the remote, and see if you see a + or - key in the text editor. That way you know the remote is working, the pairing worked, and then let's just figure out why the app isn't working.

     

     

  5. Just a heads up, the jumpers that come with the streacom, you can remove the motherboard side with a tweezers. Take a look at it, there is exposed metal in the plastic. Pushit it in and the connector should come out, so you don't need to build a cable or cut it.

    Good question regarding the sata, I'm not sure. Let me try and figure it out.

     

  6. check out the attached. Basically, take the cable included, remove the 5V one and don't have it go to the jumper on the motherboard (that has the USB and supply), and bring the 5V supply from somewhere else in the system. (make sure it's from the motherboard).

    Does that make a bit of sense?

    Screen Shot 2015-09-18 at 4.10.32 PM.png

  7. This doesn't sound right at all. Did you return the device already? I have a great relationship with harmony and it should work without a hitch. What device on your harmony are you using to control your flirc?

  8.  

    Thank you. I believe I understand those points now. However, almost every one of those unsupported buttons does have a keyboard equivalent, so Flirc could support those buttons in the WMC configuration if it wanted to.

     

    http://windows.microsoft.com/en-us/windows/media-center-keyboard-shortcuts#1TC=windows-7

     

    Record a TV show = Ctrl+R

    Open Media Center or return to the Media Center start screenWindows logo key 0d8a4985-b5e2-41a6-a1b6-e4bafb517937_92.+Alt+Enter

    Go to Recorded TV = Ctrl+O
    Go to the Guide = Ctrl+G
    Go to live TV = Ctrl+T
    Go to the DVD menu = Ctrl+Shift+M
     
    The only one that doesn't have an explicit shortcut is Standby, and that can be simulated with a series of keystrokes (WIN, right-arrow, S -- or something like that).
     
    What it can't do is wake the HTPC from sleep, which is unfortunate, but survivable.  :)

     

     

    Noted those keys, I'll get them in the GUI. 

     

    You can wake the machine from sleep. In the controllers->media keys, record the suspend key. It both wakes and suspends the machine.

  9. First of all, I blame myself for not researching this receiver more. I bought another receiver a while back and it "just worked" with my WMC remotes, so I expected Flirc would, too. I didn't realize that it merely mapped IR signals to keystrokes.

     

    I have a WMC remote that, I think, came with one of my Hauppauge tuners. (It's been years.) The keys are the same as the Rosewill RHRC-11002, but its shape is more like the Adesso ARC-100 remote (but it's black).

     

    Keys

    http://amazon.com/gp/product/B005ZAK50K

     

    Shape

    http://www.amazon.com/Adesso-Media-Center-remote-control/dp/B000XVNJRM

     

    It was nice to get an e-mail about the product before I had even received it. It gave me the feeling that Flirc was truly interested in providing a good customer experience.

     

    I like the simple setup and driver installation that automatically updates the firmware (if necessary). The key-mapping portion is very easy to use as well. I suggest improving the method of selecting the configuration though because it's not obvious at startup that the user should do that first. Maybe a panel could be added on the side that lists the available configurations and highlights the selected one.

     

    Unfortunately, after installing and configuring my Flirc, there are a few problems with the way I want to use it.

     

    1. Using the WMC configuration, there are a number of missing (and important) buttons:

    • Windows button ("The Green Button")
    • Record
    • Standby
    • Go to TV recordings
    • Go to Guide
    • Go to Live TV
    • Go to DVD Player

    I don't know if there are equivalent keystrokes, so I'm not sure if it's possible to map these, but it'd sure be nice.

     

    The Green Button is weird, because it seems to work sometimes. That might be related to point #2 below, but I haven't had a lot of time to experiment yet. I'll update this post with more info if I have any.

     

    2. I must press a button on my remote twice in order for WMC to respond.

     

    This is , pretty obviously, a deal-breaker, and I think, regardless of its support for WMC remotes, this is something Flirc needs to fix (or tell me what I'm doing wrong, which is certainly probable). :-)

    I'm constantly improving my software, and I have an unreleased version that fixes windows media center issues. You can grab it here: 

     

    It has a new windows media center controller. Also, the controller is just a bunch of keyboard shortcuts, so if I'm missing a shortcut, just find it here; http://windows.microsoft.com/en-us/windows/media-center-keyboard-shortcuts#1TC=windows-7

     

    Then use  the keyboard controller to manually record those keys.

    You have a remote that uses a funky protocol, the solution is pretty easy, record each button twice. 

    Thanks for the feedback, I really do appreciate it.

×
×
  • Create New...