Re: Unwanted pause before irw detection

--===============7820497275393129200==
Content-Type: multipart/alternative; boundary="0000000000005fd5f205f09903c0"

--0000000000005fd5f205f09903c0
Content-Type: text/plain; charset="UTF-8"

Thanks for the reply, I appreciate it. I turned on more logging and was
digging into it when I decided to try changing the IR receiver with a
different one. Previous device used the usb_uirt_raw driver and the new one
uses the tira driver. New one works great, no issues at all with delays.

Maybe the old receiver was buggy or something. Thanks again for the help!

On Sat, Dec 24, 2022 at 2:06 PM Bengt Martensson <[email protected]>
wrote:

> On 12/24/22 03:29, Robert Schultz wrote:
> > Sometimes if I briefly press a remote button, irw won't report it for 1
> > to 2 seconds, then it comes through.
> >
> > However if I press any other button after the first one, then both
> > buttons come through right away.
> >
> > Most of the time briefly pressed buttons work ok, but every 10th or 20th
> > button or so has this 'delay/pause'. If I hold down a button for longer
> > than it seems to always come through quickly, but it's more annoying to
> > use this way.
>
> You do not mention the hardware and the driver (plugin) you are using,
> nor operating system and kernel, and it may very depend on the hardware
> or OS. I have three:
>
> 1. Start lircd with a high log-level (second highest I recall I found
> useful) and scrutinize the log.
> 2. Start lircd with --immediate-init; makes initialization take place
> immediately at start. (The standard way is to initialize the hardware
> when the first signal arrives; I wish I knew the rationale for this...).
> May make a difference. (BTW, the option was suggested and implemented by
> myself...)
> 3. If configured both for sending and receiving, turn of the former (at
> least for the test).
>
> Greetz,
>
> Bengt
>
>
>

--0000000000005fd5f205f09903c0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:monospac=
e,monospace">Thanks for the reply, I appreciate it. I turned on more loggin=
g and was digging into it when I decided to try changing the IR receiver wi=
th a different one. Previous device used the usb_uirt_raw driver and the ne=
w one uses the tira driver. New one works great, no issues at all with dela=
ys.<br><br>Maybe the old receiver was buggy or something. Thanks again for =
the help!<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cl=
ass=3D"gmail_attr">On Sat, Dec 24, 2022 at 2:06 PM Bengt Martensson &lt;<a =
href=3D"mailto:[email protected]">[email protected]</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 12/24/2=
2 03:29, Robert Schultz wrote:<br>
&gt; Sometimes if I briefly press a remote button, irw won&#39;t report it =
for 1 <br>
&gt; to 2 seconds, then it comes through.<br>
&gt; <br>
&gt; However if I press any other button after the first one, then both <br=
>
&gt; buttons come through right away.<br>
&gt; <br>
&gt; Most of the time briefly pressed buttons work ok, but every 10th or 20=
th <br>
&gt; button or so has this &#39;delay/pause&#39;. If I hold down a button=
=C2=A0for longer <br>
&gt; than it seems to always come through quickly, but it&#39;s more annoyi=
ng to <br>
&gt; use this way.<br>
<br>
You do not mention the hardware and the driver (plugin) you are using, <br>
nor operating system and kernel, and it may very depend on the hardware <br=
>
or OS. I have three:<br>
<br>
1. Start lircd with a high log-level (second highest I recall I found <br>
useful) and scrutinize the log.<br>
2. Start lircd with --immediate-init; makes initialization take place <br>
immediately at start. (The standard way is to initialize the hardware <br>
when the first signal arrives; I wish I knew the rationale for this...). <b=
r>
May make a difference. (BTW, the option was suggested and implemented by <b=
r>
myself...)<br>
3. If configured both for sending and receiving, turn of the former (at <br=
>
least for the test).<br>
<br>
Greetz,<br>
<br>
Bengt<br>
<br>
<br>
</blockquote></div>

--0000000000005fd5f205f09903c0--


--===============7820497275393129200==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7820497275393129200==--