Jump to content
Flirc Forums

Xyzzy

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Posts posted by Xyzzy

  2. Programming is recorded, but not remembered correctly

    in GUI Bugs

    Posted · Edited by Xyzzy

    3 hours ago, jason said:

    When you are recording, hold your button down on the remote for a 3 seconds. If you press and lift up your finger, you only capture one of the packets of the remote ,and it has to guess the time between packets.

    The "Key has been recorded" (or something similar) appears always after well below 1 second. Should I just keep the remote key pressed? Why the message then?

    3 hours ago, jason said:

    In your config you sent me, there were two buttons called play/pause. I'm not sure if you actually had two buttons for the same function.  Or if when you hit record, one of the recordings actually caught noise, which would now play back a spurious play/pause if it see's that 'noise' again.

    May it be a bug in GUI? I tried to use original Sony MC RC6 remote with separate play/pause keys - and they were recorded both as Play keys. Whatever remote config I try, it always records play and pause as play key. Also when irtools listen shows different outputs for them.

    Also, after the latest upgrade flirc stops reacting to keys (listen shows input, but later both GUI and flirc_util record just wait for keypress detecting nothing.) Reflashing firmware unstucks flirc.

  3. Programming is recorded, but not remembered correctly

    in GUI Bugs

    Posted · Edited by Xyzzy

    @jason

    Hello,

    Thanks for the answer. It raises as many questions as gives answers, and unfortunately the attached config is useless, as I've already reconfigured the remote to work as another device trying to make it useful (and there's been so many of them that I don't remember which was the one I was using when posting).

    1. If the interkey delay is wrong, how do I manually fix it (and forget the reason, I don't care at this point). Hex editing the config file is OK for me. Whatever I try, it's in 100-110 ms range.

    2. What does it mean "the buttons were not being held down while you are recording"? I clicked a key in Flirc GUI, then I did not press anything on the remote but instead some noise was recorded by Flirc as the pressed key? Or should I first press key on the remote, and while it is pressed click a key in Flirc GUI to learn it (it seems to do not work at all - the GUI seems frozen).

    3. " any button matched in the table will wake up the device" - what's "the table"? How do I look it up?

    4. "Remember to do something about the play/pause duplication." - like what? Record the Play key again? So then I am going to get again a wrong code with 100ms+ delay, right?

  5. Programming is recorded, but not remembered correctly

    in GUI Bugs

    Posted · Edited by Xyzzy

    Some additional information: by reconfiguring my remote for different strange devices (so that it does not interfere with my other devices) and Flirc for them, I achieved the state, that keypresses are mostly recognized, but double-presses happen now very often (and the option to affect double keypresses interval detection seemingly has been removed). Additionally, something around the Flirc acts as a power button signal, waking computer from sleep in random moments (as powercfg /lastwake shows - the source of wake event being sleep button). AND ability to disable wake is disabled in the Flirc app...

     

     

  6. Programming is recorded, but not remembered correctly

    in GUI Bugs

    Posted · Edited by Xyzzy

    USB Flirc V2, OneForAll URC-7960 remote set up for Media Center configuration

    In GUI I modify configuration for Kodi. Arrow keys and digits work out of the box. I program all the remaining keys I need (back, info, menu, epg and media control keys) without any issues.

    Problem:

    The programmed keys work very erratically:

    In the GUI, Play and Stop are never detected as pressed; Pause, Rew, FF, Previous, Next like on 1 in 5 attempts, the others are detected like on 3 in 4 attempts.

    In Kodi, all the keys seem to work the same - about 1 in 2 attempts is not detected; of the detected ones, 1 in 3 results in multiple keypresses.

    I attach saved config and log from pressing all the Media Control keys - in the log there seem to be no problems - either with lack of detection or duplicating keypresses (the latter seem to happen sometimes, but less often than in the GUI/Kodi).

    Please advise what can be the problem.

    One remark - the remote worked without any issues with an Intel NUC computer with build-in IR receiver.

    my_flirc_log.txt my_flirc_config.fcfg

×
×
  • Create New...