Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Chris!

  1. Flirc records key before remote key is pressed


    • When Flirc is being programmed the gui reports the key recorded before ay remote button is pressed


      • Flirc is designed to be sensitive, when programming unusual sources of I/R emissions can affect programming
      • Solution

        Try and eliminate factors that maybe causing interference - once programmed the problem won't be present (as you won't be programming it anymore).

        Unusual sources of interference include Optical mice, MagSafe power adapter (on mac laptops) and certain lights. Changing computers and rooms can also help

        Thanks to forum user meschaefer

  2. You are correct in your logic. (which is why Jason wasn't convinced it it was FLIRC)

    This thread is quite old (relatively) and the user was running an XBMC nightly (i.e. before the betas).

    Don't worry about it if your not having any problems. Are you having problems similar to this?



    (p.s. whilst I'm not Jason I believe I can answer your question, hence why I answered)

  3. hmm. Whilst that is technically true it could cause issues when you program on a mac then plug it in to a non-mac computer.

    Personally, whilst I am a mac user, I find it a bit silly that it is called delete when it functions as backspace.

    Alternatively it could have a symbol instead of saying delete or back space which could be a compromise to this discrepancy between platforms.

    As always it's Jason's choice.



  4. Multi-remote (non-harmony)


    • Only some keys work with FLIRC


      • We're not sure, if you have this issue please let us know what profile your remote is programmed with (when trying to use FLIRC) so Jason can get more remotes support by FLIRC.
      • Solution

        Try and find the manuel for your remote (google-ing it is often the best solution) and try a TV profile to control FLIRC (such as Samsung/Sony/Panasonic etc)

        Thanks to forum user Ridger111

  5. Just to reiterate:

    The XBMC preset in FLIRC GUI should correspond to this list:


    (Some of them appear not to - haven't tested this myself yet)

    and key functions (relatively) fundamental to XBMC that are missing include:

    Home menu = ESC (I think back and previous directory are both mapped to backspace, perhaps merge those two and create a home menu button)

    Context menu = C

    Also I think the "skip track" buttons (second row down at the very right) should be mapped to [ and ] to skip chapters (waiting on results from tis thread though: )

  6. Hi boristheblade,

    Welcome to the forums. I think at the moment the XBMC preset is to get people started as Jason is working hard on features (wake from sleep and other nifty functions) so hasn't made a comprehensive preset for XBMC (yet).

    I've been led to believe that "[" and "]" (i.e. open square bracket and close square bracket), are the shortcut for next and previous chapter (http://forum.xbmc.org/showpost.php?p=905337&postcount=151)

    I think you can just flip to keyboard preset and just program those two keys (without having to re-do the rest).

    Do you mind giving it a quick test and reporting back?

    Also, how are you finding FLIRC in general?



    (p.s. I liked the thread you started about CES on forum.xbmc.org - threw up some interesting stuff.)

  7. Hmm. I remember a similar thread.

    This forum user was having a similar problem and reprogrammed a similar remote to another setting to control flirc.

    I googled your remote control and came up with this PDF guide:


    on page 61 there is some codes for samsung tv's. Perhaps you could give one of those a try to see if it alleviates the issue.



  8. Until then Flirc team, how about a more prominent warning about the type of remotes supported.

    I think this is more than fair enough. Though it is hard to achieve this simply.

    To elaborate on this issue with MCE remotes, it's basically due to non-standard i/r frequencies.

    So a warning would have to be very technical (i.e. frequencies outside of 38kHz may not work as expected) - how would you know that about your remote(?)

    Or name specific remotes (At the moment Microsoft remote - MCE, XBOX remotes) - of which it would be difficult to list all of them.

    I'll leave it it up to Jason (as it's his project), but mjkuwp94 does raise a valid point.

  • Create New...