My timers keep crashing when trying the record IPTV. Free to air timers work fine as I watch these though the satellite feed. If I roll back to 5.1.030 all timers work fine. Anyone got any idea as to why it crashes 1463BB6D-A977-4767-ABDE-F5403C7BE6C7.jpg
I'm getting the same issue.
Will be to do with the different streamer type you have chosen for your IPTV maybe?
Sent from my iPhone using Tapatalk
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
You may have downloaded a plugin that changes the default media player or something like that?
Sent from my iPhone using Tapatalk
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
Nothings changed settings or plugin wise from 5.1.030 to 5.1.031. It does exactly the same on my sisters Duo2 and my dads solo2. I’ve re-flashed back to 5.1.030 and timers work fine. Might have to wait for 5.1.032 to be released and see if the issue goes away
Nothing in the changelog to suggest anything has changed, so may likely still happen with 5.1.032.
Only other suggestion is do a clean install without any settings and plugins restore, so basically setting up as new and seeing if this helps.
Sent from my iPhone using Tapatalk
Last edited by Andy_Hazza; 25-07-18 at 13:58. Reason: Typo error
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
If you still have the crash logs, please attach to thread. Default location is /home/root/logs.
Thanks.
The log is empty. Sorry
Enable them and repeat the action and it should create a crash log.
Sent from my iPhone using Tapatalk
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
Just flashed 5.1.032 and it still does it. I've attached the crash log file
Last edited by abu baniaz; 26-07-18 at 01:34. Reason: removed logs
Did you do a fresh install without any restores to test it?Originally Posted by steven1977
Sent from my iPhone using Tapatalk
Vu+ Ultimo 4K with 3TB HDD, Dual FBC (Sat) tuners, 1x Twin Hybrid DVB-C/T/T2 tuner
Vu+ Solo 4K with 1TB HDD, Dual FBC (Sat) tuners, 1x Hybrid DVB-C/T/T2 tuner
Vu+ Solo 2 with 1TB HDD 'White Edition', 2x DVB-S2 tuners
Mut@nt HD2400 with 1TB HDD, 4x DVB-S2 tuners
Fixed 28.2E Technomate 65cm Mesh Satellite Dish with Inverto Unicable II/JESS LNB and Inverto Unicable Splitter
Fixed 28.2E Sky Zone 1 45cm Satellite Dish with Octo LNB
(All receivers installed with the latest Dev build)
Andy looks like a bug .......... will report it.
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
Andy_Hazza (25-07-18),steven1977 (26-07-18)
The bug is in the code which logs the tuner being used.
There isn't a tuner, but for some reason it isn't coming back as None (it did when I tested it on an IP stream).
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
The fix is to change line 440 in RecordTimer.py from:
to:Code:tuner_info = tn is not None and chr(ord('A') + tn) or "?"
I'll submit a PR.Code:tuner_info = type(tn) is int and chr(ord('A') + tn) or "?"
EDIT:Code:https://github.com/OpenViX/enigma2/pull/277
Last edited by birdman; 25-07-18 at 20:59.
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
This is just masking the problem. You really need to be looking at why the underlying code is not returning int or None.
fedata["tuner_number"] should only ever contain an int, or not exist. So what does it contain that it should not? And where/how is that being populated.
Last edited by Huevos; 26-07-18 at 12:20.
Posting Permissions
Reply With Quote