[mythtv] ringbuffer.cpp

[Jean-Yves Avenard]

hi

On 20 February 2014 13:31, Jonas Arndt <jonas.arndt at thearndtfamily.com> wrote:

only what's happening on the backend is of interest here...



> Then on the backend
> Feb 19 17:54:45 howarddvr mythbackend: mythbackend[22423]: I ProcessRequest
> ringbuffer.cpp:1114 (WaitForAvail)
> RingBuf(/data1/Recordings/2655_20140220004933.mpg): Waited 1.0 seconds for
> data #012#011#011#011to become available... 246168 < 360448
> thread:139843287852800
> Feb 19 17:54:46 howarddvr mythbackend: mythbackend[22423]: I ProcessRequest
> ringbuffer.cpp:1114 (WaitForAvail)
> RingBuf(/data1/Recordings/2655_20140220004933.mpg): Waited 2.0 seconds for
> data #012#011#011#011to become available... 246168 < 360448
> thread:139843287852800
> Feb 19 17:57:21 howarddvr mythbackend: mythbackend[22423]: I TVRecEvent
> tv_rec.cpp:1050 (HandleStateChange) TVRec[5]: Changing from WatchingLiveTV
> to None
>

from this I can guarantee you that you're not using the latest patch,
and really you don't have the fix.

Because the text " thread:139843287852800" only existed in my 2nd
attempt at a fix. And isn't in the latest patch


> What's interesting here is that there is nothing really spectacular going on
> on the backend. Just the regular "Waited 2.0 second..." which my front-end
> has no problem surviving.

a 2s wait isn't enough to make the frontend stop playing nor the
backend to drop the connection. it should have been trying up to
16s...

JY