Seite 17 von 20 ErsteErste ... 71516171819 ... LetzteLetzte
Ergebnis 161 bis 170 von 194
  1. #161
    Anfänger
    Registriert seit
    26.06.2017
    Ort
    Almeria, Spain
    Beiträge
    14
    Thanks (gegeben)
    14
    Thanks (bekommen)
    4
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    GigaBlue UHD Quad 4K
     
     
    @MCelliotG
    If picons works, to be visible in the second infobar activate in:
    Setup/ Usage&Interface/Settings

    GLAMOUR AURA FHD SKIN vB.5 for OpenATV images FIRST PUBLIC VERSION-osd-settings_b.jpg

    GLAMOUR AURA FHD SKIN vB.5 for OpenATV images FIRST PUBLIC VERSION-dobleinfobar_b.jpg

    Thank you
    Miniaturansichten angehängter Grafiken Miniaturansichten angehängter Grafiken GLAMOUR AURA FHD SKIN vB.5 for OpenATV images FIRST PUBLIC VERSION-osd-settings.jpg   GLAMOUR AURA FHD SKIN vB.5 for OpenATV images FIRST PUBLIC VERSION-dobleinfobar_x.jpg  

    Geändert von Next13 (27.07.2020 um 11:13 Uhr)

    •   Alt Advertising

       

  2. #162

    Registriert seit
    17.06.2016
    Beiträge
    343
    Thanks (gegeben)
    82
    Thanks (bekommen)
    213
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    That'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).

  3. #163
    Anfänger Avatar von hanspampel
    Registriert seit
    02.11.2014
    Beiträge
    11
    Thanks (gegeben)
    2
    Thanks (bekommen)
    0
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    Vu+ Duo4k
     
     
    Box 2:
    Vu+ Duo
     
     
    Hi

    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 65B7D / Yamaha RX-A3050(Titan) / Vu+ Duo4k / Sony BDP-S5500 / PlayStation 4 Pro / Xbox One / T+A Pulsar S350 + Nubert NuBox CS330 + NuBox 380 + NuBox 310 + Nubert AW880 / + 4 JBL Control One AW (für Dolby Atmos) / powered by Scaler iScan Duo ///

  4. #164
    Avatar von Papi2000
    Registriert seit
    20.04.2013
    Beiträge
    18.336
    Thanks (gegeben)
    3180
    Thanks (bekommen)
    5778
    Total Downloaded
    595,11 MB
    Total Downloaded
    595,11 MB
    ReceiverDankeAktivitäten
    Box 1:
    GB Q4K-SC / UE4K-SC / UE4K-C
     
     
    Box 2:
    GigaBlue Q-SSC / Q+-SSC
     
     
    Box 3:
    DM900uhd-SS / Vu+Duo
     
     
    Box 4:
    E4HD ZGemma H7/H9 SF8008
     
     
    Box 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 Quad 4K-multi,Quad+-SSC,Quad-SSC, andere Gigas, Astra 19.2E, UniCable & KabelBW, oATV/ teamBlue
    (weitere: DM900uhd,Vu+Duo,Technisat,Edision),PC-DVB-S/C/T,PCH-A110,Xtreamer,BDP5200
    UE32C5700,Philips65OLED865,Tosh40xyz
    ---- Einen Receiver kann sich jeder kaufen - Eine stabile E²-Box muß man sich verdienen! ----



  5. #165

    Registriert seit
    17.06.2016
    Beiträge
    343
    Thanks (gegeben)
    82
    Thanks (bekommen)
    213
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von hanspampel Beitrag anzeigen
    Hi

    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.
    Thanks 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.

  6. Thanks Papi2000 bedankten sich
  7. #166
    Anfänger Avatar von hanspampel
    Registriert seit
    02.11.2014
    Beiträge
    11
    Thanks (gegeben)
    2
    Thanks (bekommen)
    0
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Box 1:
    Vu+ Duo4k
     
     
    Box 2:
    Vu+ Duo
     
     
    Here is a Debuglog. Maybe someone see something.
    Enigma2-debug-20200805_23-22-10.zip
    LG 65B7D / Yamaha RX-A3050(Titan) / Vu+ Duo4k / Sony BDP-S5500 / PlayStation 4 Pro / Xbox One / T+A Pulsar S350 + Nubert NuBox CS330 + NuBox 380 + NuBox 310 + Nubert AW880 / + 4 JBL Control One AW (für Dolby Atmos) / powered by Scaler iScan Duo ///

  8. #167

    Registriert seit
    17.06.2016
    Beiträge
    343
    Thanks (gegeben)
    82
    Thanks (bekommen)
    213
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    I 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

  9. #168
    Senior Mitglied Avatar von starkert
    Registriert seit
    06.04.2013
    Beiträge
    2.695
    Thanks (gegeben)
    525
    Thanks (bekommen)
    457
    Total Downloaded
    89,58 MB
    Total Downloaded
    89,58 MB
    ReceiverDankeAktivitäten
    Box 1:
    VU+ Ultimo 4k
     
     
    Box 2:
    Vu+ Uno 4k SE
     
     
    Box 3:
    Vu+Uno 4k
     
     
    Box 4:
    Gigablue UE 4k
     
     
    wie 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 white
    Geändert von starkert (07.08.2020 um 05:30 Uhr)

  10. #169

    Registriert seit
    17.06.2016
    Beiträge
    343
    Thanks (gegeben)
    82
    Thanks (bekommen)
    213
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    Zitat Zitat von starkert Beitrag anzeigen
    wie 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 white

    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" />
    This part:
    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"

  11. #170

    Registriert seit
    17.06.2016
    Beiträge
    343
    Thanks (gegeben)
    82
    Thanks (bekommen)
    213
    Themenstarter
    Total Downloaded
    0
    Total Downloaded
    0
    ReceiverDankeAktivitäten
    HUGE 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!!
    What has happened to global.CurrentTime? It affects a whole lot of screens and now clock is not showing!

    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 02:13 Uhr)


Seite 17 von 20 ErsteErste ... 71516171819 ... LetzteLetzte

Stichworte

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •  
Alle Zeitangaben in WEZ +1. Es ist jetzt 20:32 Uhr.
Powered by vBulletin® Version 4.2.5 (Deutsch)
Copyright ©2021 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.
Resources saved on this page: MySQL 5,56%
Parts of this site powered by vBulletin Mods & Addons from DragonByte Technologies Ltd. (Details)
vBulletin Skin By: PurevB.com