Vix crashing when viewing 4:2:2 feed over network

[dankargo]

Hi all,

Me and a friend both have an Octagon SF8008 and are running the latest OpenVix image. We have both experienced box crashes throughout the week when viewing a 4:2:2 feed over the network through VLC (via OpenWebif). I initially thought the first crash was due to both viewing the feed over VLC and recording to a HDD at the same time but this has since happened a further three times, when solely viewing the feed over the network using Openwebif.

I have used the box for about 2 weeks and viewing normal broadcast channels is fine, it just doesn't seem to like 4:2:2 feeds. I don't know whether its the feed itself or the fact that I'm viewing it using OpenWebif > VLC, that is causing the box to hang. Me and my friend both get the spinning 'ViX' image in the left hand corner of the screen and the only way to overcome it is by toggling the power by the switch.

The feed is opened with a valid BISS key and at first I suspected the crashes were linked to the softcam being used to read 'constant.cw'. However, the box crashed when I used both Oscam-EMU & NCam to read the constant.cw file. (both not running at the same time)

I've attached my logs and a screenshot showing the plugins I have installed.

Any help would be most appreciated as I've not had this happen on any other receiver/image.

logs.zip
1_0_1_320_3BC4_13E_820000_0_0_0_20190517232502.jpg

[norhap]

try this file. SatConfig.py (unzip)
FTP /usr/lib/enigma2/python/Screens/

restart enigma2...and test you feed 4:2:2

[dankargo]

try this file. SatConfig.py (unzip)
FTP /usr/lib/enigma2/python/Screens/

restart enigma2...and test you feed 4:2:2

Thank you

I have just tried this file but noticed that in that folder, my SatConfig is named '.pyo' and not '.py'. I tried renaming the file you attached to '.pyo' and the box seems to reboot fine, but entering Tuner Config makes it crash. I have attached the crash log.

[twol]

Don't rename it!!!
Copy the .py to the directory and REBOOT... on reboot the .py will automatically be compiled and produce a .pyo that will replace the existing one!!

[dankargo]

Don't rename it!!!
Copy the .py to the directory and REBOOT... on reboot the .py will automatically be compiled and produce a .pyo that will replace the existing one!!

Thank you! I have just done this again, simply using the '.py' file untouched and this has worked.

[abu baniaz]

Please delete the .py file, it hgas created the .pyo file now. We need to update the file, there is a bug affecting tuner setup. If you don't delete it, when you next update, you will be using the same file as you have now.

[dankargo]

Please delete the .py file, it hgas created the .pyo file now. We need to update the file, there is a bug affecting tuner setup. If you don't delete it, when you next update, you will be using the same file as you have now.

Thank you, I have deleted the '.py' file now. Just out of curiosity, is it this bug that was likely the cause of my crashes?