MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD
Couple of build errors:
https://github.com/Huevos/enigma2/co...d6713b9abca281
https://github.com/Huevos/enigma2/co...ac8b465844ecf3
Binary attached.
Output looks like this:
Now we need to try make it configurable from UI.Code:< 13.047> 14:21:06.2154 [fb] double buffering available! < 13.069> 14:21:06.2365 [gFBDC] resolution: 1280x720x32 stride=5120, 17100kB available for acceleration surfaces. < 13.069> 14:21:06.2366 [eInit] + (9) gLCD < 13.069> 14:21:06.2367 [eFbLCD] /dev/fb1: No such file or directory < 13.069> 14:21:06.2368 [eFbLCD] framebuffer /dev/fb1 not available < 13.069> 14:21:06.2369 [eDboxLCD] xres=132, yres=64, bpp=8 lcd_type=2 < 13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6c2aa8 8448 bytes, stride 132 < 13.069> 14:21:06.2369 [eLCD] (132x64x8) buffer 0x6b7198 8448 bytes, stride 132 < 13.069> 14:21:06.2369 [gLCDDC] resolution: 132x64x8 stride=132 < 13.069> 14:21:06.2370 [eInit] + (9) Font Render Class < 13.069> 14:21:06.2370 [Font] Initializing lib...
MIPs one works great. Output with an export ENIGMA_DEBUG_TIME=2 is good:
Code:15:07:31.634 [eInit] - (41) eServiceFactoryDVD 15:07:31.634 [eInit] - (41) eServiceFactoryWebTS 15:07:31.635 [eInit] - (41) eServiceFactoryTS 15:07:31.635 [eInit] - (41) eServiceFactoryHDMI 15:07:31.635 [eInit] - (41) eServiceFactoryM2TS 15:07:31.635 [eInit] - (41) eServiceFactoryMP3 15:07:31.636 [eInit] - (41) eServiceFactoryFS
Huevos (13-04-20)
I am appreciating all the work here everyone. I am really grateful this is going to happen. :-) :-) :-)
This adds configurable option from the user interface...
https://github.com/Huevos/enigma2/co...91e12d7d0c7511
Last edited by Huevos; 12-04-20 at 23:25.
abu baniaz (13-04-20),ccs (12-04-20),Joe_90 (13-04-20)
Would there be negative effects of making default = local time + boot?
Abu, do whatever you think is good. I just set the default to the current format. In the end there is no default anyway because debug log is disabled by default. So this will only apply when enabling debug logs and saving that screen.
Last edited by Huevos; 13-04-20 at 09:48.
Please submit a pull request.
Last edited by Huevos; 27-10-20 at 20:59.
Please explain what help you think it is to debugging having clock output at the start of every line.
I live in "real time", not "number time", so I can see in the logs when something happened without any guesswork.
You're able to see if the log corresponds to what a poster is saying without the need to find time updates. Even then it isn't easy.
If someone says a timer didn't start at 19:00 or a cronjob doesn't work, you can get there straight away.
Same with autotimer, you can see when it ran.
Keypresses can be difficult to pinpoint, but in real time you can tie them in with other activity.
Regular error messages might as well be random error messages without the clock.
I use notepad++ to view logs, I reckon 90% of lines don't need scrolling, and probably 99% of those lines that do only need scrolling if there is something significant to view.
But it sounds like I'm the only one who finds them useful, and 99% of the rest of us probably don't even know you can switch the clock on.
abu baniaz (14-11-20)
I spend a lot of the time debug‘ing especially at the moment and the ability to run without any time stamp is a real positive, means I can run side by side comparisons... so by default my setting is option 0.
Gigablue Quad 4K & UE 4K
.........FBC Tuners:
------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
.......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
Zgemma H9 C/S into Giga4K