[mythtv] Problems with the cutlist editor and DVB-T radio recordings

[John Pilkington]

On 15/11/2020 23:15, John Pilkington wrote:
> On 15/11/2020 17:04, Mark Kendall wrote:
>> On Sun, 15 Nov 2020 at 12:32, John Pilkington <johnpilk222 at gmail.com> 
>> wrote:
>>
>>> An update:  I'm still having problems, with the cutlist editor, and not
>>> only with radio recordings.  It's still not clear when a keystroke will
>>> give the unexpected result, but the main problem now is a 20-second
>>> period of unresponsiveness on trying to switch, within the editor, from
>>> play to edit mode.
>>
>> John
>>
>> I've just played a little with latest master and I'm not seeing any
>> obvious problems - though I'm not sure what you mean by 'switch,
>> within the editor, from play to edit mode'. Can you clarify?
>>
>>> On entry to the editor there is a 1-frame flash from cache before
>>> playback starts.  IIRC that's also fairly new.
>>
>> Again, I'm not seeing any problems but I'm also not sure what '1-frame
>> flash from cache' is describing?
>>
>> Regards
>> Mark
> 
> Hi Mark:  I run into the problem quite often when using the editor but 
> it has been hard to reproduce it reliably.  This seems to do it.
> 
> Radio recording with cutpoints esablished near the start and end.
> Start playback, hit > several times and < a few times, then E repeatedly 
> and maybe for slightly longer than would be normal in keyboard 
> operation.  The first E enters the editor and later ones toggle playback.
> 
> By 'flash from  cache' I just meant that playback usually starts with 
> very quick display of some previously displayed frame.  Perhaps it could 
> be from the deinterlacer.  It's no problem but suggests, like the gently 
> pulsating cursor, that something isn't quite right.  This is, of course, 
> all on an old machine without advanced video hardware. I don't use it 
> for 1080 or h264 content.
> 
> Thanks,
> 
> John

After sending that I turned off the monitor.  This morning it was still 
showing the editor screen with the furry AOG display.  On resuming I got 
the logging below.  I believe that I'm now using the standard 
MythCenter-wide theme. Could the 'missing buttonlist state' have 
anything to do with this?

{{{
2020-11-16 08:43:00.292452 I  TV::~TV(): -- lock
2020-11-16 08:43:00.292477 N  Resuming idle timer
2020-11-16 08:43:00.292505 I  Player(0): StopPlaying - begin
2020-11-16 08:43:00.292527 I  Player(0): Exited decoder loop.
2020-11-16 08:43:00.292537 I  Player(0): StopPlaying - end
2020-11-16 08:43:00.301921 I  PlaybackBox: Loading preview 
/mnt/dat1/RSG2/10703_20201115172800.ts.png,
                         msg On Disk
2020-11-16 08:43:00.455271 I  New DB connection, total: 4
2020-11-16 08:43:00.522260 N  'buttontext' (recordings-ui.xml:70): 
height overflow. line height 21 paragraph height 25, area height 21
2020-11-16 08:43:00.522300 N  'buttontext' (recordings-ui.xml:70): 
height overflow. line height 21 paragraph height 25, area height 21
2020-11-16 08:43:00.522775 W  Theme Error: Missing buttonlist state: 
inactive
2020-11-16 08:43:00.522821 W  Theme Error: Missing buttonlist state: 
inactive
2020-11-16 08:43:00.522877 W  Theme Error: Missing buttonlist state: 
inactive
2020-11-16 08:43:00.522927 W  Theme Error: Missing buttonlist state: 
inactive
2020-11-16 08:43:00.522973 W  Theme Error: Missing buttonlist state: 
inactive


}}}