Änderung der Sendefrequenzen bei KabelBW
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 1 line · Hermann Ulrichskötter
Hallo Oliver,
Hi Hermann,
Quoted 11 lines
ich bin am Wochenende bei der TVHeadend-Installation auf meiner Synology über das Problem gestolpert, dass die Kanäle von Kabel-BW nicht mehr gescannt wurden.
Kabel-BW hatte am Donnerstag hier in Freiburg einige Sendefrequenzen geändert, so dass die Datei tvheadend/share/tvheadend/data/dvb-scan/dvb-c/de-Kabel_BW nicht mehr korrekt ist.
Ich habe in der Datei in dieser Datei die einzig relevante Zeile von "C 113000000 6900000 NONE QAM64" auf "C 114000000 6900000 NONE QAM256" korrigieren müssen, so dass der Scan wieder geklappt hat.
It looks like they changed frequencies. Their site confirms that a big changeover happened in June. I have staged this commit and will push it tomorrow unless anybody objects, Dirk, can you confirm/deny this being correct?
I already have it in my private repo [0]
Quoted 8 lines
Vielleicht sollte die Datei in dtv-scan-tables/dvb-c entsprechend angepasst werden?
Die neue Frequenzbelegung findet sich hier:
https://www.kabelbw.de/kabelbw/cms/downloads/kabel-bw-programmuebersicht.pdfSchönen Gruß,
Hermann
Thank you for the information,
A message that is not in the archive (sent off-list or not yet received): [email protected]
Pushed to the dtv-scan-tables tree. A package should be generated thanks to mauro soon, so if packagers download tomorrow, or pull from git now, they have the new version.
Quoted 36 lines · Dirk Ritter
Hello Oliver! :-)
Am Mittwoch, den 03.07.2013, 19:54 +0200 schrieb Oliver Schinagl:
Quoted 4 lines
Quoted 3 lines
Ich habe in der Datei in dieser Datei die einzig relevante Zeile von "C 113000000 6900000 NONE QAM64" auf "C 114000000 6900000 NONE QAM256" korrigieren müssen, so dass der Scan wieder geklappt hat.
It looks like they changed frequencies.
Yes.
Quoted 4 lines
Their site confirms that a big
changeover happened in June. I have staged this commit and will push it tomorrow unless anybody objects, Dirk, can you confirm/deny this being correct?It is correct. I got an e-mail from Martin Klar who lives in a KabelBW area that got the change earlier than mine. I did wait for the change and can positively confirm it. Based on data available (I did try to make sense of his change beforehand) and based on testing done using Kaffeine just after KabelBW changed it in Stuttgart.
Quoted 1 line
I already have it in my private repo [0]
Life took it's toll, so I didn't manage to forward this. Martin already tried without any luck and that's why he contacted me so that I could try. It was a rather difficult story back then I first cooked it up since there was disagreement between documents floating around and actual frequencies used and as a result of further difficulties with different tables for different service levels we concluded it would be best to just have one frequency, especially since that worked across both levels, i.e. for both fully and partly populated network areas within KabelBW.
Quoted 6 lines
I guess Martin would love to see the file changed as he did, see attachment... ;-)
BTW - what about Kaffeeine? How do they handle it? I just changed it locally and it works, but I don't think they did update it either.
They probably maintain their own (bad).
Quoted 6 lines
Hopefully, this will propagate fast...
Cheers!
Dirk
oliver