Jump to content
Flirc Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


2oh1 last won the day on November 20 2014

2oh1 had the most liked content!

Community Reputation

1 Neutral

About 2oh1

  • Rank
    Junior Flirc-er
  1. I'd love it if the Flirc UI software remembered which controller I used last, or if it would let me choose which controller to see when the app opens. I use Flirc extensively, and I always use the full keyboard controller, so I'd like the Flirc UI app to open with that controller instead of the minimalist one I never use. P.S. I LOVE FLIRC! I've been using the v1 dongle for five years and just bought a v2 in order to upgrade my setup a bit. Flirc is fantastic!
  2. I have a first gen Flirc I've been using for years with a Mac and it's been flawless. I recently switched to using it with a new Raspberry Pi 3 with the commands I'd recorded on my Mac. Single key presses are sending the Pi multiple commands. For example, the Pi sees "Command F1" as three separate commands: # KEY_LEFTMETA # KEY_LEFTMETA+KEY_F1 # KEY_F1 I don't understand why the Pi sees Command F1 as alt (meta), but the real issue for me is that when I press the assigned button on my remote, my Pi is receiving three separate commands. Every time I press the assigned button on my remote, Alt
  3. I use Flirc with a Mac and I love it, except for one thing... if my Mac's monitor is asleep, pressing a button on my remote wakes my monitor instead of executing the assigned hotkey. I'd like to be able to have my monitor stay asleep.
  4. Yeah. The distance those buttons are learned from really makes a remarkable difference. I may experiment with putting Flirc in a drawer when programming it to lessen the signal even more. This is also good news because it means I can move Flirc to a slightly more hidden spot (which I've already tried and it works) for everyday use. I'd been keeping it visible, but now, I have it hidden behind a CD rack and it's working more powerfully than before. I'm going to wipe out Flirc's settings for my universal remote and reprogram it from scratch later. This really is great news!
  5. Whoa. I just ran a quick test, but the difference seems to be night and day. Before, I'd set up Flirc by holding the remote 12 to 18 inches away. This time, following your suggestion, I tried recording the buttons from 18 feet away, without even pointing the remote at Flirc. I just held the remote up and pressed the button. Like I said, I've only done a preliminary quick test, but the difference seems to be huge. Flirc's ability to pick up the signal is greatly increased when the remote is being used from a distance, and there seem to be no ill effects when using the remote while clos
  6. Oh! Yeah, I've tried using a different remote. Of course lights are on, as is the TV. I'm using my Apple remote to control Philips Hue lights, which I've written applescripts to control on my Mac. Thus, the Apple Remote triggers the lights via my Mac's IR receiver. I've had that setup for 18 months and it's been flawless. I bought Flirc because the Apple remote only has a few buttons, and I'd like to do more... but Flirc seems to need to have the remote be pointed directly at it, whereas the Apple Mini's IR receiver just needs the signal line to be clear regardless of whether or not t
  7. I'm not sure I understand what you mean by "remote profile." I launch Flirc. I select Full Keyboard, because I need to teach it keyboard commands such as Command F1 through Command F5 and Option F1 through Option F5, plus Command ESC, and so on. I'm not pairing Flirc with Boxee or Plex. I'm using Flirc to trigger keyboard commands that control various applications. I checked Advanced Settings, and Noise Canceler isn't checked. I'm not suggesting Flirc doesn't work. I'm just finding that it often misses commands if the remote isn't pointed enough in its direction, and I'm surprised
  8. For the sake of clarity, there's a bit more of an issue here than line of sight. I'm running the latest 3.1 firmware. For the sake of comparison, I put Flirc next to the IR receiver on my Mac Mini and I compared the two - mostly because I've been using my universal remote with the Mini for a few years (by teaching the universal remote the Apple remote buttons). So, it's the same universal remote, but some buttons are using Flirc and some are using the Mini's IR receiver. The Flirc misses if the remote is not directly pointed at it, but the Mini's IR receiver almost always works even if the
  9. Keep in mind, my Mac and my stereo are on opposite sides of a room, roughly 15 feet apart. Let's say someone is on the couch. That person always points the remote forward, toward the stereo, rather than reaching up over the back of the couch and aiming it at the Mac (where Flirc is). That's why my Flirc tends to miss remote commands far more often than the TV or any of the equipment in my stereo. That's why I was thinking that if I could somehow move Flirc to where the stereo is, people would naturally point the remote in its direction instead of 180 degrees away from it.
  10. I stream all kinds of stuff from the Mac at my desk to the stereo in front of my couch on the opposite side of the room. I'm using Flirc to control the Mac with a universal remote. It works great except for one problem: people always point the remote at the stereo instead of pointing it back toward the Mac on the other side of the room, which means the commands often fail because the remote isn't pointed at Flirc. My goal is to see if it's possible to move Flirc - to somehow set it by the stereo and connect it wirelessly to my Mac on the other side of the room. My wireless router sit
  • Create New...