To.ni

This leads me to the next question: What can I do to record "clean" IR key commands? OK, dark environment, no flickering LED lights or TV screens .... On the other hand, is there a way to use the large database of remote key signals instead of physically recording every key once more? A warning for too much ambient optical noise prior to recording? An editor to review the recorded signals and compare multiple recordings of the same remote key to choose the best? ...

OK just reproduced the issue once more: Gui is running fine on my Win10 machine, connected to the USB Gen2. 1. saved current config to network share instead of default c: drive folder 2. recorded some more remote buttons (not sure whether this step is necessary) 3. disconnected LAN patch cable of my Win10 machine, leads to interruption between PC and NAS 4. removed USB Gen2 to connect it to my Raspi 5. reconnected the USB Gen2 - now the current window is not reacting (regardless whether Flirc GUI or Firefox) My doubt: I recorded some optical disturbance along with the remote key, this disturbance remains and "controls" the active window ... issue seems understood / resolved - sorry!

Hi Team, I'm new at Flirc and still experimenting ... With GUI installed on my Windows machine, I saved the current configuration on a NAS share. After interrupting the connection to my NAS, the GUI hangs if I attempt to change further keys ... Regards, To.ni

Hi, if you run Windows on your NUC, what about recording a macro like <windows><s> - <k> - <o> - <d> - <i> - <enter> to your desired remote button?