[mythtv-users] Help with error: Invalid UE golomb code

[John Pilkington]

On 03/07/17 22:01, mikkel at broerne.dk wrote:
> On 03-07-2017 21:40, John Pilkington wrote:
> 
>> On 03/07/17 21:34, mikkel at broerne.dk <mailto:mikkel at broerne.dk> wrote:
>>> On 03-07-2017 21:20, John Pilkington wrote:
>>>
>>>> On 03/07/17 19:21, mikkel at broerne.dk 
>>>> <mailto:mikkel at broerne.dk> <mailto:mikkel at broerne.dk 
>>>> <mailto:mikkel at broerne.dk>> wrote:
>>>>> //
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> Just updated my installation and now my deamon log is filling up with
>>>>>
>>>>> Jul 3 19:42:41 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:41 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:42 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:42 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:43 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:43 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:43 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:44 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:44 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>> Jul 3 19:42:45 srv2016 mythtv-backend[1620]: Invalid UE golomb code
>>>>>
>>>>> I cannot see any issues with recordings or playback... so what is this?
>>>>>
>>>>> My version is
>>>>> mythtv:
>>>>> Installed: 0.28.1-dmo1~bpo8+2
>>>>> Candidate: 0.28.1-dmo1~bpo8+2
>>>>> Version table:
>>>>> *** 0.28.1-dmo1~bpo8+2 0
>>>>> 500 http://www.deb-multimedia.org/ jessie-backports/main amd64 Packages
>>>>> 100 /var/lib/dpkg/status
>>>>> 0.27.5-dmo2 0
>>>>> 500 http://www.deb-multimedia.org/ jessie/main amd64 Packages
>>>>>
>>>>> debian version
>>>>> 3.2.0-4-amd64
>>>>
>>>> Seems to be deep in the works of ffmpeg
>>>>
>>>> /home/john/rpmbuild/BUILD/mythtv-master/mythtv/external/FFmpeg/libavcodec/golomb.h
>>>>
>>>> and an old reference
>>>>
>>>> http://ffmpeg-devel.ffmpeg.narkive.com/sqJHcK37/patch-golomb-check-log-validity-before-shifting
>>>>
>>>> which originally was
>>>>
>>>>> made ... conditional on a numeric anomaly checker being enabled
>>>>> and applied
>>>>
>>>> but I'm not sure if it still is.   google showed me lots of examples 
>>>> but I didn't see a way of turning it off
>>> thanx for the quick reply
>>> I found the same, but would have expected more users to have the 
>>> issue. As I only updated mythtv, there maybe where some additional 
>>> things to update?
>>>
>>> i.e. libavcodec
>>
>> I get the impression it's a buggy stream;  or perhaps the 'anomaly 
>> checker' has got activated?
> 
> Hmmm... could it be my frontend (kodi)?
> 
> 'anomaly checker' never heard of that?

I thought that might be a compiler option.  Your error is in the backend 
log, so kodi seems an unlikely suspect - but I thought this was a 
decoding issue, which sounds more frontend-ish

It apparently got into myth in one of jya's big ffmpeg commits, 18 
months ago:

https://lists.gt.net/mythtv/firehose/594425

golomb: always check for invalid UE golomb codes in get_ue_golomb