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

[mikkel at broerne.dk]

On 04-07-2017 1:07, John Pilkington wrote:

> On 03/07/17 23:02, mikkel at broerne.dk wrote: On 03-07-2017 22:49, John Pilkington wrote:
> 
> On 03/07/17 22:01, mikkel at broerne.dk <mailto: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> <mailto: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>> <mailto: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 
Ok, sounds right, but then again I am out of my deepth.

Looks like there is a patch? 
I haven't seen one.  I've just been trying to select stuff from google.
But the only reference to get_ue_golomb that I find in the myth code,
outside ffmpeg, is in

libs/libmythtv/mpeg/H264Parser.cpp

And there's external/FFmpeg/libavcodec/tests/golomb.c

which looks as if it might be instructive if I knew how to point it at
something.

Cheers,

John

As far as I can see I have no issues with tunes, recording etc. and I
would therefore suspect it is a bug. 

Do you think I can turn down the level of logging in mythtv - just to
remove the "noise" it makes in my logging? 

cheers 
Mik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170704/8a0ccb9e/attachment-0001.html>