[mythtv-users] Remote Mythfrontend Problem
Steve Milner
mythtv at stephen-milner.me.uk
Fri Jul 17 19:47:56 UTC 2009
Right I have done some further tests.
With both the backend machine running a frontend and remote frontend
tuned to the same channel I could not see or hear any problems on the
backend machine
I let both the frontend and backend machines log the frontend output for
a couple of hours and then compared the logs.
An initial examination of the frontend logs revealed:
Log on the backend: 184 Lines
Log on the remote frontend: 4444 Lines
Typical sample from the frontend log on the backend machine:
2009-07-17 19:00:29.202 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:00:29.203 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:01:17.852 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:01:17.852 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:03:37.002 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:03:37.003 [dvbsub @ 0x605f180]Invalid y position!
2009-07-17 19:03:37.003 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:04:59.899 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:04:59.899 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:06:23.199 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:06:23.200 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:12:42.143 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:12:42.143 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:19:10.808 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:19:10.809 [dvbsub @ 0x605f180]Invalid object location!
2009-07-17 19:21:56.853 [dvbsub @ 0x605f180]Junk in packet
2009-07-17 19:21:56.890 [dvbsub @ 0x605f180]Invalid object location!
Typical sample from the remote frontend log:
2009-07-17 19:02:09.255 [mpeg2video @ 0x3b9533f620]invalid cbp at 36 1
2009-07-17 19:02:13.685 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 8
2009-07-17 19:02:13.685 [mpeg2video @ 0x3b9533f620]skipped MB in I frame
at 1 9
2009-07-17 19:02:13.685 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 10
2009-07-17 19:02:13.686 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 11
2009-07-17 19:02:13.686 [mpeg2video @ 0x3b9533f620]skipped MB in I frame
at 1 12
2009-07-17 19:02:13.686 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 13
2009-07-17 19:02:13.686 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 14
2009-07-17 19:02:13.686 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 15
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 16
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 17
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 18
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 19
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 20
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 21
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 22
2009-07-17 19:02:13.687 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 23
2009-07-17 19:02:13.688 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 24
2009-07-17 19:02:13.688 [mpeg2video @ 0x3b9533f620]ac-tex damaged at 0 25
I am afraid my knowledge of what these errors mean is lacking, but
superficially it seems like running the frontend on the same machine as
the backend is working within (at least my own) acceptable limits and
the remote frontend is having significant problems.
I would guess the problem is related to networking, but I have to be
honest that is only a guess.
Any advice that can be given would be of benefit, especially someone
with better knowledge who could interpret the meaning in the logs to
point me in the correct direction as to where my problem could be.
BTW the attenuator I experimented with seems to have had little effect,
but was still in line when running the above tests.
Regards,
Steve
More information about the mythtv-users
mailing list