[mythtv-users] mythcommflag failure on mythtv-light system
jfabernathy at gmail.com
Sun Aug 18 14:10:28 UTC 2019
> On Aug 18, 2019, at 9:53 AM, Mike Bibbings <mike.bibbings at gmail.com> wrote:
> On 17/08/2019 16:42, James Abernathy wrote:
>> On 8/16/19 5:48 PM, Klaas de Waal wrote:
>>> On Fri, 16 Aug 2019 at 23:39, Klaas de Waal <klaas.de.waal at gmail.com> <mailto:klaas.de.waal at gmail.com> wrote:
>>>> About this bug:
>>>>> QObject::connect: No such slot ClassicCommDetector::m_sceneChangeDetectorHasNewInformation(unsigned int,bool,float) in ClassicCommDetector.cpp:262
>>>> I can confirm this is a bug and will fix this asap.
>>> Done; error message is gone.
>> So this was a PI only issue not x86 related, right? mythcommflag works fine on my PC based mythtv backend.
>> So your fixes will have to be rolled out where apt update will see them by the maintainer of:
>> deb http://dl.bintray.com/bennettpeter/deb/ <http://dl.bintray.com/bennettpeter/deb/> buster myth30
>> is that right?? I'm not building from source using git.
>> Jim A
> That fix is only for mythtv master branch and does not affect your mythtv-light 30 Buster version, which does not need the fix.
> I have raised a trac ticket on the failure against mythtv master branch fon Raspbian Buster, but the same problem is present on your mythtv-light 30 Buster version, and on mythtv-light 30 Stretch.
> see https://code.mythtv.org/trac/ticket/13476 <https://code.mythtv.org/trac/ticket/13476>
Thanks, for the explanation. It’s really not an issue for my as my usual recordings don’t respond well the mythcommflag. So I don’t run it by default and just use the 1 minute skip on the remote to get pass the commercials.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users