[mythtv-users] 2005 laptop stutters after upgrade from 0.27 to 0.28

[faginbagin]

On 6/6/2017 7:36 PM, Mark Perkins wrote:
> On 07/06/17 08:09, faginbagin wrote:
>> Yep, I've still got a few old laptops that have been working quite
>> well as frontends. But one isn't performing quite as well with mythtv
>> 0.28 and mythbuntu 16.04 as it is with mythtv 0.27 and mythbuntu
>> 12.04. So, I'm trying to understand why, and whether there's anything
>> I can do to get it to perform running 0.28 as well as it does running
>> 0.27. The laptop and the master backend have multiple boot partitions,
>> so that's how I switch back and forth between 0.27 and 0.28
>>
>> ...snip...
>>
>> Has anyone else noticed a degradation in performance on older hardware
>> after upgrading?
>>
>> Any suggestions on how to identify the cause, e.g. OS module, X driver
>> or mythtv?
>>
>> _______________________________________________
>>
> 
> Just brainstorming a bit here:
> - was the 16.04 install a clean install or a dist-upgrade from 12.04?
It was a clean install, although the laptop has been represented in the 
database since 2011, which I think was when my setup was running 0.24.

> If clean install have you checked the judder free and frame display timing
> steps again? https://www.mythtv.org/wiki/User_Manual:JudderFree and
> https://www.mythtv.org/wiki/Frame_display_timing
> - maybe try cutting mythtv out of the equation for a bit. Move a
> recording to local drive and compare playback in VLC using both 12.04
> and 16.04 and look for any differences.
> - maybe try a "complex" transcode on the local test file using ffmpeg on
> both 12.04 and 16.04 to see if that shows a significant difference or
> not (something to make the laptop sweat / work hard so small differences
> might be more readily noticed).

Not sure I understand what you mean by "complex" transcode. Can you 
elaborate?

Many thanks to you and everyone who has replied to this thread. It will 
be a while before I get to follow up on them. I'll report back with my 
findings. I sure hope it's something that can be fixed with the right 
configuration tweak.