View Full Version : Picture breakup on freeview T2 Belmont transmitter
I've had picture breakup problems for a few months now, all when doing multiple recordings on different mux's ie. multiple tuners.
I'm attaching the transponder file for
https://ukfree.tv/transmitters/tv/Belmont
Abu, can you confirm if anything has changed since you last updated Belmont?
I know BBC 4 HD moved a while ago, but I don't know if that is relevant.
I'm finding it very difficult to establish where the problem lies (ET10k) - tuners, new kernel, new drivers, signal quality.
Currently using 5.1.028
Edit:
Is it possible the power supply is struggling to support more than 1 or 2 tuners, or are they all always "on" anyway?
abu baniaz
11-06-18, 15:50
I'll have a look later. To rule out ABM issue, you can init 4, delete lamedb (leave bouquets), restart. scan your frequencies individually.
I'll have a look later. To rule out ABM issue, you can init 4, delete lamedb (leave bouquets), restart. scan your frequencies individually.Thanks, I'm unable to re-create the problem, but it always seems to happen on a Sunday evening when there are multiple tuners in use.
At the moment, I'm just trying to eliminate the easy bits.
abu baniaz
11-06-18, 18:41
The HD muxes are the same as what were originally added.
Does the breakup occur on all recordings made at the time or only ones on a particular frequency?
The HD muxes are the same as what were originally added.
Thanks, that's one less possibility.
Does the breakup occur on all recordings made at the time or only ones on a particular frequency?
It's SD channels that seem to suffer the most. Not all recordings are affected in any one session.
eg QUEST's (C30- ,545.8MHz) recording of last Sunday's cycle race in Italy was badly affected.
The channels work fine independently, its when more tuners get used.
Worse case senario is when a 2 hour programme is fine for around 60 minutes, say, and then starts to break up.
Corresponds roughly with the start of another recording (on a different mux).
Last night, I'd left BBC4 HD on live tv, when I switched on the tv at around 21:00, BBC4 HD was unwatchable, even though only one recording was active. It was so bad I saw a single frame of the ITV football match for a split second.
I did get it working again without rebooting.
abu baniaz
11-06-18, 19:14
Remind me again, what is the hardware tuner configuration?
Remind me again, what is the hardware tuner configuration?
4 dvb-t2 hybrid tuners, (and one Sundtek usb t2 tuner).
Tuner D is disabled as 4 cannot record together.
The symptom with all 4 hybrids enabled and recording is that a tuner (usually C) stops working with tuner failed, rather than picture breakup.
One other thing I've noticed, when I check which tuners are in use, one channel may say AB and another just B.
Sorry it's so vague, but these inconsistencies are making it even harder for me to work out exactly what's going on.
Just checked last night's cycling on itv4, started at 22:00, unwatchable.
bbc1 hd recording at 21:00-22:00 absolutely fine.
Something went drastically wrong earlier in the evening and didn't recover.
abu baniaz
11-06-18, 20:01
Try a different skin which will show you the tuners.
Remember, the tuner in use will change.
abu baniaz
11-06-18, 20:20
These are your services split by frequency. Recording one and selecting another will force usage of another tuner.
t:eeee0000:104f:233a,t:482000000:0:1:0:2:1:0:0:0:0 :0:0
"BBC FOUR"
"BBC ONE Yk&Li"
"BBC Parliament"
"BBC Red Button"
"BBC TWO"
"CBeebies"
"BBC 6 Music"
"BBC Asian Net."
"BBC Humberside"
"BBC Lincolnshire"
"BBC Norfolk"
"BBC Nottingham"
"BBC R1X"
"BBC R5L"
"BBC R5SX"
"BBC Radio 1"
"BBC Radio 2"
"BBC Radio 3"
"BBC Radio 4 Ex"
"BBC Radio 4"
"BBC Sheffield"
"BBC World Sv."
t:eeee0000:201b:233a,t:506000000:0:1:0:2:1:0:0:0:0 :0:0
"Freeview"
"Channel 4"
"Channel 4+1"
"Channel 5"
"E4"
"Film4"
"ITV +1"
"ITV"
"ITV2"
"ITV3"
"ITV4"
"More 4"
"Sewing Quarter"
t:eeee0000:3006:233a,t:545833000:0:2:0:2:1:0:0:0:0 :0:0
"365 Travel"
"Arise News"
"Asia TV"
"Box Nation"
"CCTV"
"CONNECT 4"
"Juwelo UK"
"Ketchup TV"
"Loveworld"
"Planet Knowledge"
"Racing UK"
"Sonlife"
"Sports Channel Network"
"Television X"
"VisionTV"
"5 USA"
"5SELECT"
"5STAR"
"695"
"696"
"ADULT Party"
"ADULT Section"
"ADULT Studio 66"
"ADULT Xpanded TV"
"Blaze"
"Blaze+1"
"CBS Reality"
"CITV"
"Channel 5+1"
"Drama"
"Hochanda"
"Horror Channel"
"ITV2 +1"
"ITV3"
"ITV3+1"
"ITV4+1"
"ITVBe"
"ITVBe+1"
"QUEST"
"QUEST+1"
"QVC"
"TCC"
"The Store"
"True Entertainment"
"Absolute Radio"
"Capital"
"Heart"
t:eeee0000:4089:233a,t:530000000:0:5:5:0:3:4:4:2:0 :1:0
"530000 SID 0x4cc0"
"Film4+1"
"Film4+1"
"BBC ONE HD",c:0019c9,c:0319c9,c:051,c:1219ca
"BBC TWO HD"
"CBBC HD"
"Channel 4 HD"
"Channel 5 HD"
"ITV HD"
t:eeee0000:5040:233a,t:730000000:0:2:0:2:1:0:0:0:0 :0:0
"Kiss Me TV"
"Proud Dating"
"697"
"ADULT smileTV3"
"Challenge"
"Create & Craft"
"Dave"
"E4+1"
"Food Network"
"Gems TV"
"Pick"
"Quest Red"
"Really"
"Sky News"
"Sony Crime Channel"
"Sony Movie Ch"
"TBN UK"
"TJC"
"YourTV"
"movies4men"
"truTV"
"RNIB Connect"
"talkSPORT"
t:eeee0000:6040:233a,t:785833000:0:2:0:2:1:0:0:0:0 :0:0
"4Music"
"4seven"
"5Spike"
"698"
"ADULT Babestn"
"ADULT Section"
"ADULT smileTV2"
"CBS Action"
"CBS Drama"
"Dave ja vu"
"Home"
"Ideal World"
"Jewellery Maker"
"POP"
"QVC Beauty"
"QVC Style"
"RT"
"Sewing Quarter"
"TalkingPictures TV"
"Travel Channel"
"True Movies"
"Yesterday"
"Classic FM"
"Hits Radio"
"KISS FRESH"
"KISS"
"KISSTORY"
"Kerrang!"
"LBC"
"Magic"
"Premier Radio"
"Smooth Radio"
"heat"
t:eeee0000:8001:233a,t:522000000:0:2:0:0:1:0:0:0:0 :0:0
"ESTUARY"
"POP Max"
"Sony Crime Channel +1"
"Sony Crime Channel"
"Sony Movie Channel+1"
"The Vault"
"Tiny Pop"
"truTV"
t:eeee0000:a000:233a,t:570000000:0:5:5:0:3:4:4:2:0 :1:0
"Bollywood HD"
"5Spike+1"
"5USA+1"
"CBS Reality +1"
"Keep It Country"
"Pick+1"
"Quest Red+1"
"Travelxp"
"Vintage TV"
"CBS Action+1"
"VIVA"
"4seven HD"
"Al Jazeera Eng HD"
"BBC NEWS HD"
"Channel 4+1 HD"
"RT HD"
"Trans World Radio"
t:eeee0000:b000:233a,t:586000000:0:5:5:0:3:4:4:2:0 :1:0
"5STAR+1"
"Forces TV"
"FreeSports"
"More4+1"
"PBS America"
"Rocks & Co 1"
"Together"
"BBC FOUR HD"
"BT Showcase HD"
"CBeebies HD"
"QVC Beauty HD"
"QVC HD"
I'll try a bit harder to reproduce the problem, and I'll try 5.1.021 (older drivers) next Sunday to see how that goes.
abu baniaz
11-06-18, 21:59
You need to establish a reliable method of creating the problem. Otherwise you will be stabbing in the dark.
Have a look at your timers.xml file, it should show the services that were recorded and in the order it did them.
This is the debug log (5.1.026) when the itv4 recording started.
I've highlighted the bit I don't like the look of...
< 30809.068> [RecordTimer] Filename calculated as: '/media/hdd/movie/20180610 2158 - ITV4 - Cycling_ Criterium Du Dauphine___'
< 30809.069> [Navigation] recording service: 1:0:1:208A:201B:233A:EEEE0000:0:0:0:
< 30809.069> [eDVBResourceManager] allocate channel.. 201b:233a
< 30809.069> [eDVBResourceManager] available channel.. 4089:233a
< 30809.069> [eDVBFrontend] opening frontend 1
< 30809.073> [eDVBFrontend] (1)tune
< 30809.073> [eDVBFrontend] tune setting type to 2 from 0
< 30809.073> [eDVBChannel] OURSTATE: tuning
< 30809.073> [eDVBServicePMTHandler] allocate Channel: res 0
< 30809.073> [eDVBCIInterfaces] addPMTHandler 1:0:1:208A:201B:233A:EEEE0000:0:0:0:
< 30809.073> [eDVBChannel] getDemux cap=00
< 30809.073> [eDVBResourceManager] allocate demux cap=00
< 30809.073> [eDVBResourceManager] allocating demux adapter=0, demux=1, source=1 fesource=1
< 30809.073> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.075> [eEPGCache] saveEventToFile epg event id 4b88
< 30809.075> [RecordTimer] prepare ok, waiting for begin
< 30809.076> [Trashcan] Recording(s) in progress: 1
< 30809.079> [eDVBFrontend] startTuneTimeout 5000
< 30809.079> [eDVBFrontend] setVoltage 0
< 30809.079> [eDVBFrontend] setFrontend 1
< 30809.079> [eDVBFrontend] setting frontend 1
< 30809.108> [eDVBFrontend] (1)fe event: status 0, inversion off, m_tuning 1
< 30809.320> [eDVBFrontend] (1)fe event: status 1f, inversion off, m_tuning 2
< 30809.320> [eDVBChannel] OURSTATE: ok
< 30809.320> [eDVBLocalTimerHandler] channel 0x13fca50 running
< 30809.320> [eDVBChannel] getDemux cap=00
< 30809.320> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.321> [eDVBSectionReader] DMX_SET_FILTER pid=20
< 30809.321> [eEPGCache] channel 0x13fca50 running
< 30809.321> [eDVBChannel] getDemux cap=00
< 30809.322> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.322> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.322> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.323> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.324> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.324> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.326> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.326> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.327> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.328> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.328> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.329> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.329> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.330> [eDVBResourceManager] stop release channel timer
< 30809.330> [eEPGCache] next update in 2 sec
< 30809.330> [eDVBChannel] getDemux cap=01
< 30809.330> [eDVBResourceManager] allocate demux cap=01
< 30809.330> [eDVBResourceManager] allocating shared demux adapter=0, demux=1, source=1
< 30809.330> [eDVBServicePMTHandler] ok ... now we start!!
< 30809.330> [eDVBServiceRecord] RECORD service event 5
< 30809.331> [eDVBCAService] new service 1:0:1:208A:201B:233A:EEEE0000:0:0:0:
< 30809.331> [eDVBCAService] add demux 1 to slot 0 service 1:0:1:208A:201B:233A:EEEE0000:0:0:0:
< 30809.331> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.331> [eDVBSectionReader] DMX_SET_FILTER pid=0
< 30809.332> [eDVBServiceRecord] RECORD service event 6
< 30809.332> [eDVBServiceRecord] tuned..
< 30809.332> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.332> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 30809.333> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30809.334> [eDVBSectionReader] DMX_SET_FILTER pid=0
< 30810.064> [eDVBLocalTimerHandler] diff is -4
< 30810.065> [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
< 30810.065> [eDVBLocalTimerHandler] set RTC Time
< 30810.065> [eDVBLocalTimerHandler] update RTC
< 30810.065> [eDVBLocalTimerHandler] time update to 21:57:37
< 30810.065> [eDVBLocalTimerHandler] m_time_difference is -4
< 30810.065> [eDVBLocalTimerHandler] slewing Linux Time by -04 seconds
< 30810.066> [eDVBChannel] getDemux cap=00
< 30811.335> [eEPGCache] start caching events(1528664262)
< 30811.335> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 30811.335> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 30811.336> [eDVBSectionReader] DMX_SET_FILTER pid=18
< 30813.335> [eDVBDemux] open demux /dev/dvb/adapter0/demux1
< 30813.335> [eDVBSectionReader] DMX_SET_FILTER pid=17
< 30815.836> [eDVBScan] the current channel's ID was not corrected - not adding channel.
< 30815.836> [eDVBServicePMTHandler] ignore sdt update data.... incorrect transponder tuned!!!
< 30815.836> [eDVBServicePMTHandler] incorrect namespace. expected: eeee0000 current: ffffffff
< 30815.836> [eDVBServicePMTHandler] incorrect transport_stream_id. expected: 201b current: ffffffff
< 30815.836> [eDVBServicePMTHandler] incorrect namespace. expected: 233a current: ffffffff
< 30821.552> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 1
< 30822.055> [VideoHardware] setting aspect: 16:9
< 30822.056> [VideoHardware] setting wss: auto
< 30822.057> [VideoHardware] setting policy: panscan
< 30822.058> [VideoHardware] setting policy2: letterbox
< 30822.811> [eDVBVideo0] VIDEO_GET_EVENT PROGRESSIVE_CHANGED 0
< 30823.315> [VideoHardware] setting aspect: 16:9
< 30823.316> [VideoHardware] setting wss: auto
< 30823.316> [VideoHardware] setting policy: panscan
< 30823.317> [VideoHardware] setting policy2: letterbox
< 30829.077> [RecordTimer] activating state 2
< 30829.078> [RecordTimer] start recording
< 30829.080> [Notifications] AddPopup, id = None
< 30829.092> [Skin] processing screen MessageBoxSimple:
< 30829.124> [Skin] processing screen MessageBoxSimple_summary:
< 30829.131> [eDVBServiceRecord] Recording to /media/hdd/movie/20180610 2158 - ITV4 - Cycling_ Criterium Du Dauphine___.ts...
< 30829.131> [eDVBServiceRecord] start recording...
< 30829.131> [eDVBServiceRecord] RECORD: have 1 video stream(s) (07d1), and 1 audio stream(s) (07d2), and the pcr pid is 07d1, and the text pid is ffffffff
< 30829.131> [eDVBServiceRecord] ADD PID: 0000
< 30829.131> [eDVBServiceRecord] ADD PID: 07d1
< 30829.131> [eDVBServiceRecord] ADD PID: 07d2
< 30829.133> [setIoPrio] realtime level 7 ok
I'm now able to re-produce the picture breakup, but need to investigate further before giving details.
I need to eliminate one or 2 things.
One thing I have noticed is my SundTek usb dvb-c/t2 tuner no longer works (tune failed) - anyone else having problems before I start another thread?
SundTek tuner ok today, so please ignore my last comment.:)
If I record ITV3 (C30- 545.8MHz, a low-ish powered SD mux @50kW) using tuner B, and record BBC1 SD (C22 482.0Mhz @150kW) on tuner C, there is interference on tuner B.
Tuner B works fine in isolation, and even when tuner C is recording an HD channel.:confused:
Any other combination of tuners seems to work ok.
One thing that caught me out was that different tuners get used when waking up from deep standby if the box doesn't drop back to standby during the recording(s) (as it should).
Just tried again, with Tuner D having its own feed rather than the RF out from Tuner C.
ITV3 now looks ok, however ITV Be, on the same mux, breaks up, but works fine when Tuner C is no longer recording.
I also tried 5.1.021 yesterday, but the problem was still showing.
abu baniaz
22-06-18, 14:33
Is the problem?
the recorded services
viewing live services
both
neither
If recorded services, have you tried a different storage device?
May I also suggests you remove the non-functioning tuner instead of just disabing it.
Both recorded and live services are affected.
Removing tuner D has always been on the list, and replacing C with D if that didn't work.
Odd that it's taken 3 years to show, a faulty tuner which only fails under very specific conditions is a bit hard to understand.
Disabling tuner C and enabling tuner D didn't help.
Removing tuner D didn't help.
Replacing tuner B with tuner D has made a big difference, the mux works fine apart from a couple of minor clitches in a 65 minute recording.
The only fly in the ointment is that the same recording I made on a topfield didn't have the 2 clitches.
Odd that it's taken 3 years to show, a faulty tuner which only fails under very specific conditions is a bit hard to understand.One of the 3 built-in tuners in my et8000 (the B one) started playing up a few months back (A and C were OK). A replacement from Germany worked OK at first (it's a different chipset and seems to prefer a weaker signal...) but then it played up too (possibly signal related). In the end I disabled it, since I have two (different) USB tuners as well and I've never had more than 4 muxes in use at once (in fact I doubt that I've ever had more then 3).
abu baniaz
25-06-18, 03:35
Swapping tuners can possibly cause errors later on. The tuner in use can change depending on timers and mux in use. Might be an idea to test one fitted at a time or two so that the permutations/combinations are reduced. I presume that you have labelled them up.
Thanks for the replies.
I'll just have to keep an eye on it and see how it goes.
Any chance of storing the tuner being used in timers.xml as part of the start recording record?
I've found that working out which tuner has been used for a recording after it has finished is almost impossible.
abu baniaz
25-06-18, 10:59
You can set the preferred tuner for recordings.
Sent from my Moto G (5S) using Forum Fiend v1.3.3.
You can set the preferred tuner for recordings.
I know, but when 3 or 4 recordings are running at the same time, for a variety of reasons, you can't predict which ones will get used.
abu baniaz
25-06-18, 16:22
I don't think that is possible.
Sent from my Moto G (5S) using Forum Fiend v1.3.3.
I don't think that is possible.I'm looking.... Somewhere the code must know which tuner it is using, but it's not at all obvious where that might be.
I'm looking.... Somewhere the code must know which tuner it is using, but it's not at all obvious where that might be.I've found a way to do it - after much searching of the code a look at TimerSanityCheck.py provided a simple method.
Now I just need to get 0, 1, ... mapped to A, B, ... .
This is the required code change (in RecordTimer.py):
@@ -24,6 +24,8 @@
from bisect import insort
from sys import maxint
first
+import string
+
# ok, for descriptions etc we have:
# service reference (to get the service name)
# name (title)
@@ -604,6 +606,21 @@
# retry
self.begin = time() + self.backoff
return False
+# Report the tuner that this recording is using
+ if hasattr(self.record_service, 'frontendInfo'):
+ feinfo = self.record_service.frontendInfo()
+ if feinfo and hasattr(feinfo, 'getFrontendData'):
+ tn = feinfo.getFrontendData().get("tuner_number", -1)
+ if tn < 0 or tn > 25:
+ tuner = "Unknown"
+ else:
+ tuner = string.uppercase[tn]
+ self.log(11, "Recording using tuner %s" % tuner)
+ else:
+ self.log(11, "getFrontendData() failed - tuner unknown")
+ feinfo = None # Free any object...
+ else:
+ self.log(11, "No frontendInfo for recording...")
return True
elif next_state == self.StateEnded or next_state == self.StateFailed:and here's a copy of that file with the change included.
57015
Just drop it into /usr/lib/python/enigma2 (take a backup copy of the existing RecordTimer.pyo first) and restart the GUI.
Any interest in this in general? Should I submit it as a PR for inclusion as standard?
Thanks for your help, I'll set it up later today.
I could have done with it last night - a split second clitch on BBC1 HD turned out to be 30 seconds long when I checked on the toppy.:confused:
Just an optimistic thought - I'm not actually comparing like for like, in this case I was comparing recordings on BBC1 HD and BBC1 SD, so maybe there was a transmission clitch.:)
I've submitted a PR to put this into the standard build. It's slightly different, as it also logs the tuner when recordings stop.
https://github.com/OpenViX/enigma2/pull/272
Just drop it into /usr/lib/python/enigma2 (take a backup copy of the existing RecordTimer.pyo first) and restart the GUI.
Any interest in this in general? Should I submit it as a PR for inclusion as standard?
Looks good, working fine.
Just one minor point, the file is in /usr/lib/enigma2/python and I needed a full reboot. :sofahide:
Just one minor point, the file is in /usr/lib/enigma2/pythonAh, yes. A common mistake of mine...
and I needed a full reboot. :sofahide:In which case there is something seriously strange about your system, as the change is entirely within the enigma2 python code.
In which case there is something seriously strange about your system, as the change is entirely within the enigma2 python code.Well it's bog standard, I did a GUI restart and the .pyo file was not created, so I rebooted and it was.
I checked the folder because after the GUI restart timers.xml didn't show any tuner details for a test recording I'd setup.
Well it's bog standard, I did a GUI restart and the .pyo file was not created, so I rebooted and it was.
I checked the folder because after the GUI restart timers.xml didn't show any tuner details for a test recording I'd setup.
I've just checked the debug logs and the first recording after the GUI restart did show the tuner details (in the log file), but it wasn't in timers/info when I looked, and the .pyo file wasn't showing in FileZilla despite refreshing. Most odd.
GUI restart does (obviously) create the .pyo file, but FileZilla gives a last modified time of 1 hour in the future.
I've upgraded FileZilla today, so what it was showing yesterday is anyone's guess. Everything else eg telnet, gives the correct create time.
GUI restart does (obviously) create the .pyo file, but FileZilla gives a last modified time of 1 hour in the future.Possibly related to Windows inability to understand timezones in its default mode.
You can run Windows with a system clock set to UTC - a simple registry setting does it. (Makes sense for me, as I run dual-boot Linux/Windows systems and it simplifies things.)
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.