Thanks: 0
Ergebnis 1 bis 3 von 3
-
12.07.2020, 13:06 #1
- Registriert seit
- 05.08.2016
- Beiträge
- 5
- Thanks (gegeben)
- 0
- Thanks (bekommen)
- 0
- Total Downloaded
- 40,49 MB
- Total Downloaded
- 40,49 MB
Bouquet Editor Export problem with transponders
Hi,
I have a UE4k in my living room (main receiver) and two Trio 4k receivers elsewhere in the house. To synchronise the services and bouquets between all three, I will sometimes export the bouquets from the UE4k and import to the others via web IF. I've used this approach for years across many dreambox models and other Gigablue models and it worked well as a way to get the same bouquets and services quickly synchronised.
The issue I get with my Trio 4k receivers is that the bouquets_backup.tar exported from the UE4k does not work correctly when imported to the Trio 4k. My setup is irish DTT, sat 28.2E, 19.2E and 13.0E. All DTT, 13.0 and 28.2 services are fine. All 19.2 HD services are also fine. But what seems like all/most of the SD 19.2 services are not working when imported to the Trio 4k. No picture. To correct it, I have to do a blind scan on 19.2 on the Trio 4k and then it will correct the issue. Will also sometimes work with a transponder scan for the given service.
I thought this was a Trio 4k issue but after a lot of checking on files and backups, I think the problem is actually with the UE4K bouquet export. The lamedb and lamedb5 files are not the same if you compare the raw file in /etc/enigma2 with the same file in bouquet_backup.tar.
e.g.
Code:t:00c00000:0453:0001,s:12551000:22000000:0:0:192:1:0 <<<< transponder for Kabel eins Doku (Actual value in /etc/enigma2/lamedb5) t:00c00000:0453:0001,s:12544750:22000000:0:4:192:2:0 <<<< transponder for Kabel eins Doku (same line from lamedb5 in bouquets_backup.tar from the SAME receiver)
Code:s:4465:00c00000:0453:0001:1:0:0,"kabel eins Doku",p:ProSiebenSat.1,c:009ff,c:01a00,c:0229,c:039ff s:4465:00c00000:0453:0001:1:0:0,"kabel eins Doku",p:ProSiebenSat.1,c:009ff,c:01a00,c:0229,c:039ff
This means that to handle new services or re-orgs of services, I just need to make the fixes on one of Trio 4ks, export and then import to the UE4k.
But it seems like there is a bug with bouquet backup exports on the UE4k.
To test this:
* Copy /etc/enigma2/lamedb5 and /etc/enigma2/lamedb from your UE4k
* perform a bouquet backup via web IF
* untar the file
* diff both the lamedb and lamedb5 files between the raw copy and bouquet_backup.tar and you might see that they are different.
Would be interested to know if anyone else sees this same issue.Geändert von dresdner353 (12.07.2020 um 13:09 Uhr)
-
Advertising
-
12.07.2020, 14:20 #2
- Registriert seit
- 20.04.2013
- Beiträge
- 24.824
- Thanks (gegeben)
- 4679
- Thanks (bekommen)
- 9077
- Total Downloaded
- 596,61 MB
- Total Downloaded
- 596,61 MB
Box 1:GB Q4K-SC / UE4K-SC / UE4K-CBox 2:GigaBlue Q-SSC / Q+-SSCBox 3:DM900uhd-SS / Vu+DuoBox 4:ZGemma H7/H9 SF8008Box 5:diverse andere . . .lamedb5 is not yet used in oATV.
Before EXPORT did you check the Button "Aktualisieren" (in german)?Grüßle
Ralf
---------------------------------------------
Gigablue Quad4K-mixed, UE4K, Trio4K, Quad_Plus-SSC, UE_Plus-SC, X2/X3-SC, UltraUE-SC, ...
Astra 19.2E UniCable & KabelBW, oATV/teamBlue
(u.a.: DM900uhd,Vu+Duo,ZGemma H9Twin & H7S), PC-DVB-S/C/T, Xtreamer, BDP5200, Philips 24PFS4022/12, 65OLED855/12,UE32C5700, RPi3+
---- Einen Receiver kann sich jeder kaufen - Eine stabile E²-Box muß man sich verdienen! ----
-
12.07.2020, 18:12 #3
- Registriert seit
- 05.08.2016
- Beiträge
- 5
- Thanks (gegeben)
- 0
- Thanks (bekommen)
- 0
- Total Downloaded
- 40,49 MB
- Total Downloaded
- 40,49 MB
ThemenstarterI have tried reboots etc and this still seems to happen. Just now, I also tried that refresh icon "⟳" and it had no difference. Same different files were exported.
However just to see how an import went, I tried an import in the opposite direction.. Trio 4k -> UE4k and then re-exported from UE4k.. this time the lamedb and lamedb5 files that come down from the UE4k are the same as those in /etc/enigma2. So it seems that whatever was in the files on the UE4k, it caused them to export incorrectly but an import in the opposite direction has now sorted the problem.
I have those lamedb and bouquet files for years from a DM7025 to DM8000 and eventually Gigablue Quad and then from that to a Gigablue UE4K. So despite retunes and channel edits etc, it is possible some bad data has survived causing the issue.
But very happy now it seems to have been solved.
Lesezeichen