30 replies to this topic

[doglover]

I have a TV (kitchen) were I cannot fix the overscan, so I need the overscan settings in the image.

The overscan wizzard works and the GUI is displayed properly.  However the picture is not.

 

Second problem. 

When I restart the receiver, the overscan settings are not applied.  Tjhe GUi is again displayed oversized

The picture also.

 

When you run the overscan wizzard, the settings I made before are still there, but I have to confirm these settings.  The gui is then again properly sized.

The picture is still oversized.

 

I tested these with 2 skins:

Pli-HD2

PLi-FullNigthHD

Same result.

 

My receiver:

 

Merk & model:  MaXitec MultiboxSE
Chipset:  hi3798mv200
Totaal geheugen:  528844 kB vrij / 873200 kB totaal
Box Uptime:  0:15
Software
Systeem OE:  PLi-OE
Firmware versie:  OpenPLi develop (2021-05-27-develop)
Kernel versie / stuurprogramma datum:  4.4.35 / 20201204
 

 

 

 

[Dimitrij]

Maybe...

https://github.com/O...nwizard.py#L194

				else:
					config.plugins.OSDPositionSetup.dst_left.value = 0
					config.plugins.OSDPositionSetup.dst_width.value = 720
					config.plugins.OSDPositionSetup.dst_top.value = 0
					config.plugins.OSDPositionSetup.dst_height.value = 576
				config.misc.do_overscanwizard.value = False
-			        config.save()
+                               config.plugins.OSDPositionSetup.dst_left.save()
+                               config.plugins.OSDPositionSetup.dst_width.save()
+                               config.plugins.OSDPositionSetup.dst_top.save()
+                               config.plugins.OSDPositionSetup.dst_height.save()
+                               config.misc.do_overscanwizard.save()
				setConfiguredPosition()

 

           

[WanWizard]

Why doesn't config.save() cover that?

 

I'd rather see a bug fixed than worked around...

[doglover]

Downloaded the .py file.

Applied the changes.  Cpthe fie t the rcver.

Disabled the pyo file.

Restarted the receiver and got a crash when trying to access the overscan wizzard.

OpenPLi Enigma2 crash log
crashdate=za jun 19 13:33:33 2021
compiledate=May 28 2021
skin=PLi-HD2/skin.xml
sourcedate=2021-05-27
branch=develop
rev=a84bd16
component=Enigma2
stbmodel=multiboxse
stbmodel=multiboxse
kernelcmdline=root=/dev/mmcblk0p23 rootsubdir=linuxrootfs3 rootfstype=ext4 kernel=/dev/mmcblk0p21 console=ttyAMA0,115200 blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13 mem=937M mmz=ddr,0,0,60M vmalloc=500M
nimsockets=NIM Socket 0:
imageissue=openpli develop %h
REMOVE Peer multiboxse
REMOVE Peer multiboxse
ADD Peer hd2400=hd2400.local:8001
ADD Peer hd2400=hd2400.local:8001
Traceback (most recent call last):
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 77, in action
  File "/usr/lib/enigma2/python/Components/ActionMap.py", line 57, in action
  File "/usr/lib/enigma2/python/Screens/Menu.py", line 62, in okbuttonClick
  File "/usr/lib/enigma2/python/Tools/BoundFunction.py", line 10, in __call__
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/OSDPositionSetup/plugin.py", line 30, in main
  File "/usr/lib/enigma2/python/Plugins/SystemPlugins/OSDPositionSetup/overscanwizard.py", line 199
    setConfiguredPosition()
    ^
IndentationError: unexpected indent
[ePyObject] (CallObject(<bound method NumberActionMap.action of <Components.ActionMap.NumberActionMap instance at 0xb1b73ee0>>,('OkCancelActions', 'ok')) failed)

dmesg<4>FAT-fs (mmcblk0p4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Edited by doglover, 19 June 2021 - 12:41.

[WanWizard]

IndentationError: unexpected indent

Make sure the indentiation of the code is correct, and you don't mix tabs and spaces. Python requires correct indentation due to the absence of "end" statements.

[doglover]

Sorry.  Tried tabs and spaces.

Same result.

I have said several time before that the logic behind python escapes me.  I missing some basics which cannot get from on-line information.

[mrvica]

The picture is still oversized.

 

the OSD (skin, GUI) is the frame buffer, the picture (video buffer) is anoher /proc

you may try manually (could be done as well with plugin)

#!/bin/sh

# /usr/script/Picture_reduce.sh
echo 229 > /proc/stb/vmpeg/0/dst_height
echo d > /proc/stb/vmpeg/0/dst_left
echo c > /proc/stb/vmpeg/0/dst_top
echo 2b7 > /proc/stb/vmpeg/0/dst_width
echo 0 > /proc/stb/vmpeg/0/dst_apply

and picture full again

#!/bin/sh

# /usr/script/Picture_full.sh
echo 240 > /proc/stb/vmpeg/0/dst_height
echo 0 > /proc/stb/vmpeg/0/dst_left
echo 0 > /proc/stb/vmpeg/0/dst_top
echo 2d0 > /proc/stb/vmpeg/0/dst_width
echo 0 > /proc/stb/vmpeg/0/dst_apply

[doglover]

you may try manually (could be done as well with plugin)

#!/bin/sh

# /usr/script/Picture_reduce.sh
echo 229 > /proc/stb/vmpeg/0/dst_height
echo d > /proc/stb/vmpeg/0/dst_left
echo c > /proc/stb/vmpeg/0/dst_top
echo 2b7 > /proc/stb/vmpeg/0/dst_width
echo 0 > /proc/stb/vmpeg/0/dst_apply

 

This script works, in the sense it reduces the picture on the screen.

However the reduction is too much.  Picture has black borders around it.

So the value have to be changed.  And I do not have any idea how and how much.

 

PS: this TV in question is still a HD ready one.  (1280x720).

It is a 22 inch screen in my kitchen.  And is good enough for this purpose.

[Dimitrij]

Sorry.  Tried tabs and spaces.

Same result.

I have said several time before that the logic behind python escapes me.  I missing some basics which cannot get from on-line information.

 

[doglover]

Tried this.

Does not help.  Picture still oversized.

GUI is OK.

[WanWizard]

Afaik this has nothing to do with the picture, only with your remark that the overscan GUI settings were not saved.

 

Is this issue addressed with Dimitrij's patch? If so, @Dimitrij, why does the original save() call not save these values? This suggests a bug in save(), possibly with recursive items?.

 

OpenPLi doesn't have any option in the GUI to adjust the picture size, and not sure every box can do that either.

[Dimitrij]

 

Is this issue addressed with Dimitrij's patch? If so, @Dimitrij, why does the original save() call not save these values? This suggests a bug in save(), possibly with recursive items?.

This was just my guess.

But that's not it.

The problem is different.

[WanWizard]

I read two different problems:

1. after a reboot, the overscan values are reset so the GUI position is wrong again
2. there is no option to resize the video, the same way you can resize the GUI

@Doglover, is that correct?

[doglover]

ad 1:

After a reboot the GUI position is wrong again.

Although when I run the overscan wizard.  Confirm I do not see the arrows.

Then in the screen you can set the offsets to see the arrows,  There are some values present.

And they are correct.

So I confirm I can close the overscan wizard.  The GUI is now correct.

But after a reboot I could do the whole thing over.

But with the Dimitrij mod the problem seems solved.  (I restarted 3 times and the GUI remained OK - we will see further tomorrow morning)

 

In the setting file I find now:

config.plugins.OSDPositionSetup.dst_height=543
config.plugins.OSDPositionSetup.dst_left=54
config.plugins.OSDPositionSetup.dst_top=18
config.plugins.OSDPositionSetup.dst_width=630

BTW:  this problem is critical, missing part the GUI is a problem (I am bit overstating)

 

ad2.

Correct.  And this is not changed.

Although I was under the impression that before on the Zgemma and the same screen, the video was resized too.

But I start to doubt this now.  (I remember watching Eurosport some time ago with half the logo off screen)

And if this the case, it is not the end of the world.

Most channels still cater for overscan on TV's.

And this TV has never been able to disable overscan on a permanent base when it was used for watching analog TV.  (You could change it each time - but after doing that 3 times, you never bother again)

It is only now, that I started to wonder about this.  And under the impression that I saw this being done, I wondered why it did not work now.

But as I said, I am probably mistaken.

Edited by doglover, 19 June 2021 - 19:43.

[WanWizard]

ad 1:

But with the Dimitrij mod the problem seems solved.  (I restarted 3 times and the GUI remained OK - we will see further tomorrow morning)

 

Ok. So that means there is a bug in config.save(), because it should save all config changes, no matter how deep in the hierarchy the data has changed.

[Dimitrij]

[OSDPositionSetup] use standard save instead config.save()

[WanWizard]

That doesn't fix the problem in config.save(), but works around it, so I don't think this should be merged.

 

If config.save() doesn't save all changes in the config, chances are rather big this same problem happens elsewhere. So the root cause needs to be found, and fixed.

[Dimitrij]

And who said that config.save() should save all the settings?

[WanWizard]

Doesn't sound very logical if it didn't. Then again, there's a lot in Enigma that isn't logical...

 

I also think the original author of that code ( @littlesat? ) assumed that it would.

[Dimitrij]

 

«Entia non sunt multiplicanda praeter necessitatem»