Jump to content
Flirc Forums

ankurgupta1

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ankurgupta1

  • Rank
    Curious Flirc-er

Recent Profile Visitors

1,655 profile views
  • j

  1. I think it's a larger problem, as I am using Windows 7 and still can't get it to work.
  2. You "can" or "can't" seem to load one now?
  3. I think I might be having a similar issue to yours and I was wondering if you were able to get flirc to recognize volume up, volume down, and mute as different button presses. I tried what you suggested on my RC64 (similar to RC65), but flirc still sees the button presses as the same.
  4. Well the way my set up is the TV (pc monitor) volume isn't being used. The audio is outputted to my desktop speakers. Eventually, I want to try and get it to work with the media keys built into Windows, but first I need to get flirc to see that each button press is different. I did some more research and it seems to be an issue with all DirecTV remotes in the way they handle volume controls. I'm trying to see if there's a way I can get the remote to send a different signal for volume up, volume down, and mute.
  5. I just tried it out. Mapped my keys while in v1, then upgraded to the media keys beta and tested out the buttons in the Utilities program and none of the buttons worked which means I lost the configuration. I tried loading the configuration and it still didn't recognize any of the button presses. So yes, it is losing whatever configuration is on it when I upgrade, and then I can't restore the configuration after the upgrade (upgrade/downgrade...basically whenever I flash the firmware).
  6. So I tried uploading the media keys beta firmware via the GUI after saving my configuration. Once the firmware was uploaded, I loaded my configuration and it said "File Restored", but then none of the buttons did anything. I tried remapping a button that I knew was already configured and it said "Recorded Successfully", which means nothing was mapped there before. It should have complained that it already existed. I thought this may have been an issue with the beta firmware so I downgraded back to the stable 1.0 firmware and tried loading it again and the same issue occurred. I even used the Flirc Utilities software to see what commands it was seeing when I pushed a button and it saw nothing. So basically I can't restore my original configuration, which means I need to remap all the buttons again. Any idea why this may be happening?
  7. I just received my flirc today and I am truly impressed! This little bugger does almost exactly what I wanted it to do (I explain the almost below). Congratulations on such an amazing product, Jason. Definitely money well spent. So my setup is that I am using the SlingPlayer desktop application and wanted to pair an old DirecTV remote (RC64) with it so I don't have to be at my computer to control it. I got all the buttons mapped to SlingPlayer keyboard shortcuts via the flirc GUI except for the Volume Up/Down, Mute, and TV Input (I was using this button to control a different part of the application) buttons. I ran the Flirc Utilities application to see what was happening when I pressed those buttons and I noticed that those 4 buttons all were doing the same thing. Whatever I mapped to one of those, the other 3 would end up doing the same thing. I thought maybe the remote was bad so I tried my current DirecTV remote (RC65R), which has the same layout, but the same issue occurred. I'm not sure why this is happening, but my guess is that flirc can't seem to decipher between the IR signals of those 4 buttons for some reason. Jason, do you think this may be the issue or have any suggestions or what else could be the issue? In the meantime, I mapped those commands to the red, green, yellow, and blue buttons since SlingPlayer can't use those buttons properly anyway, but this isn't a very convenient workaround as I have to remember that blue = volume up and yellow = volume down :P
×
×
  • Create New...