"Add ReadInternalMode to RingBuffer class" commit breaks editing

[gnassas@…]

I recently updated from late March master to recent (April 26) and editing stopped working for me.

The symptom is the frame display no longer updates when you move around the recording. The frame and position numbers change but the frame stays the same. When you exit the edit you get the end of recording "keep/delete" dialog as if you were at the end of the recording even if you aren't.

A bisect pointed the finger at the recent RingBuffer? changes. The bisect output was:

c519bba367320a3773c093c30d05e1330534589c is the first bad commit
commit c519bba367320a3773c093c30d05e1330534589c
Author: Jean-Yves Avenard <jyavenard@mythtv.org>
Date:   Sat Apr 26 17:31:36 2014 +1000

    Add ReadInternalMode to RingBuffer class
    
    This mode allows to limit the content of the ringbuffer to the content already loaded. Seeking, reading and other operations will not be destructive.
    This allows for almost instantaneous streams and bitrate detection.
    
    Duration calculated will obviously be wrong, but as the duration is stored in the DB we’ll use that duration instead anyway, meaning we only have to worry about streams detection itself.
    
    This greatly speed up liveTV transition change and playback startup

:040000 040000 f7bc65ad6761416b61127aa9e987058f0e8463c3 2cbb58487e13b39b373b08b006762ad33930e206 M	mythtv

[JYA]

can't reproduce it here...

As mentioned earlier it is *impossible* for this change to have an effect for video editing, as the code is only active during live TV , right at the start of live TV (when the stream is opened)

[JYA]

actually, was using the devel/027candidates branch which has all my last changes to the ringbuffer..

I can reproduce it in master, even going back to end of february....

tracking...

I wonder if this issue is similar to the one causing an old frame to appear from time to time when we switch channel

[JYA]

very weird...

Running a master frontend against a 0.27 backend/0.27 database issue can't be reproduced

0.27 frontend -> 0.27 backend : ok

0.27 fronted -> 0.27 backend with master database: no okay

[JYA]

If you revert e46904385382ca90f71ae472e88bd3dcd6cf1d7f and c519bba367320a3773c093c30d05e1330534589c (in that order) you're saying you don't have the problem?

[JYA]

I reverted to an older database backup from a few days ago, and again I can't reproduce the issue despite trying for the past 3 hours.

Closing this bug as it's obviously related to something that was done in the database but can't figured what

[JYA]

it does introduce a regression...

apologies

[Jean-Yves Avenard <jyavenard@…>]

In 013ac54e19ac200173986d819d2c0abb91dfb07d/mythtv:

Fixes #12128

[Jean-Yves Avenard <jyavenard@…>]

In bcd3aa822dfe3224a4f6c1f7a55cacf321a7bfdc/mythtv:

Fixes #12128
(cherry picked from commit 013ac54e19ac200173986d819d2c0abb91dfb07d)