Ergebnis 161 bis 170 von 205
-
27.07.2020, 12:05 #161
- Registriert seit
- 26.06.2017
- Ort
- Almeria, Spain
- Beiträge
- 14
- Thanks (gegeben)
- 14
- Thanks (bekommen)
- 4
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:GigaBlue UHD Quad 4K
-
Advertising
-
27.07.2020, 12:55 #162
- Registriert seit
- 17.06.2016
- Beiträge
- 362
- Thanks (gegeben)
- 85
- Thanks (bekommen)
- 222
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterThat's very strange, there is nothing in the code that activates the picons only to the second infobar when infobar lite is activated. In fact I have not skinned infobar lite at all (should be the exact same as a normal infobar).
-
05.08.2020, 13:34 #163
- Registriert seit
- 02.11.2014
- Beiträge
- 16
- Thanks (gegeben)
- 3
- Thanks (bekommen)
- 0
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Vu+ Duo4kBox 2:Vu+ DuoHi
Found this nice looking skin.
- First) Where do i get the ATV-pro, ive activarted it but there is nothing to show.
- Second) Did somebody use it on VuDuo4k? It runs so laggy on my side. It took nearly 2 seconds till there is some action. In the settings it runs good, but on live tv it took sooooo long. The same on channel selecting. It took 2 seconds to action the button ive pressed, than it took 2-5 seconds to show a running picture.
Running the latest 6.4 oATV.LG 77C17LB / Denon AVC-X4700H / Vu+ Duo4k / Nvidia Shield TV Pro / PlayStation 5 / Xbox One / Sony BDP-S5500 / Saxx Coolsound CX90 + Saxx Coolsound CX50 + 4x Saxx Coolsound CX30 + XTZ 12.17 Edge / + 4x JBL Control One AW (für 3D Sound) ///
-
05.08.2020, 13:56 #164
- Registriert seit
- 20.04.2013
- Beiträge
- 24.820
- Thanks (gegeben)
- 4679
- Thanks (bekommen)
- 9076
- 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 . . .Activate the Debuglog
https://www.opena.tv/howtos/52-log-f...html#post33949
or
Debug- und Crashlog / ab ATV 6.3
and supply the logs as zipped attachment.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! ----
-
05.08.2020, 14:52 #165
- Registriert seit
- 17.06.2016
- Beiträge
- 362
- Thanks (gegeben)
- 85
- Thanks (bekommen)
- 222
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterThanks for the feedback!
1. ATV-Pro is not yet supported. My skin is full featured, meaning you get everything at once. Perhaps in the future, if time allows it, I will add more screens.
2. Duo4K should have no problems running the skin. There should be absolutely no lag in any receiver with a dual core CPU more than 1000Mhz, which is the minimum requirement. I wouldn't release the skin if it was laggy to begin with.
Perhaps some third party addon slows down the skin.
-
Danke - 1 ThanksPapi2000 bedankten sich
-
05.08.2020, 23:32 #166
- Registriert seit
- 02.11.2014
- Beiträge
- 16
- Thanks (gegeben)
- 3
- Thanks (bekommen)
- 0
- Total Downloaded
- 0
- Total Downloaded
- 0
Box 1:Vu+ Duo4kBox 2:Vu+ DuoHere is a Debuglog. Maybe someone see something.
Enigma2-debug-20200805_23-22-10.zipLG 77C17LB / Denon AVC-X4700H / Vu+ Duo4k / Nvidia Shield TV Pro / PlayStation 5 / Xbox One / Sony BDP-S5500 / Saxx Coolsound CX90 + Saxx Coolsound CX50 + 4x Saxx Coolsound CX30 + XTZ 12.17 Edge / + 4x JBL Control One AW (für 3D Sound) ///
-
06.08.2020, 00:59 #167
- Registriert seit
- 17.06.2016
- Beiträge
- 362
- Thanks (gegeben)
- 85
- Thanks (bekommen)
- 222
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterI don't see any crash error references to my skin at all (the debug is nagging for some missing elements, but that's to be expected, they are not there on purpose and don't hurt).
However, I see lots of other errors completely unrelated to my skin!
Code:23:23:41.3571 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 41ms 23:23:41.4374 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 79ms 23:23:41.5995 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 41ms 23:23:41.6788 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms 23:23:41.6861 [ ] base/console.cpp:111 execute [eConsoleAppContainer] Starting /bin/sh 23:23:41.8475 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:41.9267 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms 23:23:42.0966 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:42.1755 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms 23:23:42.3378 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:42.4176 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 79ms 23:23:42.5215 [ ] service/servicedvb.cpp:1747 timeshift [eDVBServicePlay] timeshift 23:23:42.7680 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 40ms 23:23:42.8480 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 79ms 23:23:43.0173 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 40ms 23:23:43.1803 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:43.2595 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms 23:23:43.4276 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:43.5081 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 79ms 23:23:43.6685 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:43.7507 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 81ms 23:23:43.9096 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:43.9917 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 81ms 23:23:44.2401 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:44.3195 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms 23:23:44.4825 [!W!] dvb/frontend.cpp:1801 readFrontendData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(DTV_STAT_SIGNAL_STRENGTH)', potential driver issue, 39ms 23:23:44.5617 [!W!] dvb/frontend.cpp:1942 getTransponderData [eDVBFrontend] Slow ioctl 'FE_GET_PROPERTY(&cmdseq)', potential driver issue, 78ms
-
07.08.2020, 06:24 #168
- Registriert seit
- 06.04.2013
- Beiträge
- 2.687
- Thanks (gegeben)
- 526
- Thanks (bekommen)
- 463
- Total Downloaded
- 89,58 MB
- Total Downloaded
- 89,58 MB
Box 1:VU+ Ultimo 4kBox 2:Vu+ Uno 4k SEBox 3:Vu+Uno 4kBox 4:Gigablue UE 4kwie und wo kann man die Info die hinter dem sendernamen in der kanalliste erscheint farblich Ändern?
Bleibt bei mir immer weiss
Eurosport1 (umgestellt auf blau) Polenrundfahrt (bleibt weiss)
How can I change the color of the Programm Info Behind Channel Name? All I did it is still whiteGeändert von starkert (07.08.2020 um 06:30 Uhr)
-
08.08.2020, 02:09 #169
- Registriert seit
- 17.06.2016
- Beiträge
- 362
- Thanks (gegeben)
- 85
- Thanks (bekommen)
- 222
- Total Downloaded
- 0
- Total Downloaded
- 0
Themenstarter
On ChannelSelection screen you need to edit this line
Code:<widget name="list" position="785,135" size="1095,850" itemHeight="50" scrollbarMode="showOnDemand" colorServiceDescription="sky" colorServiceDescriptionSelected="lightciel" colorEventProgressbarBorder="white" colorEventProgressbar="sky" colorEventProgressbarBorderSelected="lightciel" colorEventProgressbarSelected="sky" foregroundColorServiceNotAvail="darkgrey" serviceItemHeight="50" serviceNumberFont="Numbers;31" serviceNameFont="RegularB;34" serviceInfoFont="RegularL;31" progressBarWidth="75" progressbarHeight="18" itemsDistances="15" fieldMargins="20" nonplayableMargins="20" transparent="1" selectionPixmap="/usr/share/enigma2/GlamourAuraFHD-ATV/selections/channelselbig.png" alphatest="off" zPosition="3" />
colorServiceDescriptionSelected="lightciel"
has lightciel which is a light ciel color and not white. If you need to change the colour you can add a new one, but this has to be one that is already defined in the colors section of the skin. Otherwise you need to add a hex color with a #.
For instance
colorServiceDescriptionSelected="#c0c0cc"
-
08.08.2020, 02:11 #170
- Registriert seit
- 17.06.2016
- Beiträge
- 362
- Thanks (gegeben)
- 85
- Thanks (bekommen)
- 222
- Total Downloaded
- 0
- Total Downloaded
- 0
ThemenstarterHUGE PROBLEM WITH THE LATEST UPDATE
On Osmio4K after today's update I have this error
Code:Specified related screen 'global.CurrentTime' was not found in screen 'SecondInfoBar'! Please contact the skin's author!!
Notably, HD51 was not affected (yet).
Edit: I see it happens with all skins, so it's a general issue. I'll try to reflash!Geändert von MCelliotG (08.08.2020 um 03:13 Uhr)
Lesezeichen