276 replies to this topic

[littlesat]

Can you make a screenshot? 

[ims]

 had it on one program today too ( it is event dependently, not channel dependently) on HD ... it seems as x = 1280 only and not 1920

Edited by ims, 12 August 2016 - 14:34.

[Rob van der Does]

On some services this line is always visual, on others sometimes, also on HD, depending on the contents.

[littlesat]

On some services this line is always visual, on others sometimes, also on HD, depending on the contents.

->

I cannot help here... and for "sometimes" when it is on the transmission this feature was not intended for...  Actually it is a work-a-round for incorrect transmitted services... There is no need to show these ugly lines for digital TV... 

[WanWizard]

Can you make a screenshot? 

 

Not at the moment. Movies4men doesn't have the problem now, and the lines on Sony Movies are short enough now to be covered.

[Taapat]

@littlesat or there is any problem to fill a full line?
If you need a screenshot, you can see it in my previous post.
 
And one more question.
Why did you choose to use backgroundColor 0?
Color 0 by default is not defined in enigma and raise skin error:

color '0' must be #aarrggbb or valid named color. Please contact the skin's author!

Maybe it would be better to change it to # 00000000?

[littlesat]

I was trying to let it handle as an integer...

[Taapat]

But what is the benefit to handle as an integer?

 

Maybe I miss something, but looking in parseColor: https://github.com/O...er/skin.py#L218
it seems to me that it will simply raise skin error, and backgroundColor is not used.

 

This is the same as remove backgroundColor attribute from HideVBILine Screen.

[littlesat]

But what is the benefit to handle as an integer?

-> That you only had one zero...  but fully removing it is event better...

 

https://github.com/O...316c6ed4336ce6a

Edited by littlesat, 13 August 2016 - 12:33.

[Taapat]

And why need backgroundColor attribute in HideVBILine Screen if it not used due to wrong color name?

[littlesat]

Sorry I just did edit my previous post...

[Taapat]

Here is another thing.
If I use my skin without the pig, then I'm set in enigma background little transparent.
Of course, in this case also HideVBILine screen is transparent.

 

Perhaps there is chance to set this screen background color not transparent - ignoring the transparent settings in the enigma?

[littlesat]

That will not work... When you set the skin a bit transparant I cannot cover the VBI lines.... Then it is better that the skin itself has transparant backgrounds...

[littlesat]

I'm considering to rename this feature in...

Hide visible VBI lines
Unhide visible VBI lines

I suggest this covers all it does and is less specific than wss...

[Pr2]

Suggestion:

 

In the contextual menu where we can set/unset many features on service (like VBI) there is nowhere an extended help information text (that we have most of the time on other non contextual menu), the help text that appears below the PiG.

 

Can we have also a longer explanation help message on this feature because I am quite sure that 99% of the end-user of OpenPLi won't understand what this function is for.

With a long help text description they can figure out what it is used for without coming and asking on the forum.

 

Pr2

[Rob van der Does]

I'm considering to rename this feature in...

Hide visible VBI lines
Unhide visible VBI lines

I suggest this covers all it does and is less specific than wss...

I wouldn't use the word 'VBI' at all; hardly anybody will understand what it means.

[littlesat]

VBI is in fact what it is...

[ims]

May be - use full naming:

 

Hide vertical blanking interval

Unhide vertical blanking interval

 

or

 

Cover up vertical blanking interval

Not cover up vertical blanking interval

[Erik Slagter]

VBI is in fact what it is...

No it is NOT VBI, that is what I am trying to explain over and over. It is NOT a good description because both users don't understand it and it isn't the correct naming as well. It is also no WSS, so please please don't use that name as well.

 

You need to separate the phenomenon that the user experiences and the actual function.

 

The user experience is a dotted line on the top. Let's just call it that way, it's correct and obvious.

 

The function can be either:

- some VBI lines copied from an analog source (lets not forget that digital video at transmission level does not have a notion of VBI at all!)

- some WSS lines copied from an analog source (same comment, with extra note that WSS is actually VBI data, just like teletext and VPS/PDC)

- time codes inserted by the source (camera, mixing equipment...)

 

Therefore you can't know what part of the line is spanned, as well.

 

In any way, I strongly believe that in-band signalling does not have a place in digital video. I am also convinced that in most cases it does actually serve no purpose and it's only there because nobody notices.

Edited by Erik Slagter, 14 August 2016 - 08:36.

[littlesat]

There is a goal for them... That is wss related in case the channel might also be distributed over an analog (cable) netwerk... In fact these lines are for analog tv still in the vbi area, and they should be invisible due to they are in fact in the overscan, we in fact do not have anymore in the hdtv time frame...

So calling them vbi is fully correct rgards my meaning. Naming them differently will mean long wordings in the config that we also should avoid...