276 replies to this topic

[littlesat]

In fact just unhide.... Keep it simple...

And just to teach users...

Flickering dashed VBI lines on top of the screen

Edited by littlesat, 18 August 2016 - 08:15.

[Rob van der Does]

In fact just unhide.... Keep it simple...

And you checked an English dictionary that this is an existing word?
No need, I did, it isn't

[littlesat]

"Bullshit..."

 

http://www.thefreedi...nary.com/Unhide

Edited by littlesat, 18 August 2016 - 12:34.

[Rob van der Does]

Excuse me? Please use a proper dictionary.

[Erik Slagter]

it are still VBI lines.... actually Visible VBI lines...

 

And we also do not rename Diseqc to switch that selects low noise band converters...

There is NO SUCH THING as VBI in digital video. It's just as meaningless as talking of PAL or NTSC in the context of digital video. Discussion is futile. The only vertical blanking used in digital video is between the receiver and the screen, using TMDS (DVI/HDMI/DP) where the blanking interval is used for sending audio and metdata. Between provider and receiver, and I say it once again, there is no such thing as vertical blanking interval, there is only relevant pixels in the picture. All metadata is sent out of band.

[littlesat]

There is NO SUCH THING as VBI in digital video. -> 

You're right... but for relay to analogue TV and misconfigurations at the encoder uplink site we're still looking at them...

[Rob van der Does]

I can only refer to my cloud example; use a wording that people understand, not tech-talk.

[littlesat]

Engima2 is full of tech-talk and now we're playing the "holy ghost"....

 

http://www.yourdictionary.com/unhide

 

I still think that cover and uncover might be even better.... as in fact it is covered by a full screen wide wide small in height black box...

Edited by littlesat, 18 August 2016 - 15:32.

[athoik]

Change removeHideVBIFlag to removeCoverVBIFlag in order to be aligned? (s/HideVBI/CoverVBI/)

[littlesat]

It is getting a crazy story... a lot of wording stuff.... what is this feature about ....

[Rob van der Does]

Quite clear actually: this feature is about hiding an ugly line at the top of the TV-screen, that (sometimes) shows on some services.

[WanWizard]

This is exactly the reason why (good) GUI design is so damn difficult, why it is a separate profession, and why developers should be kept far from it.

[littlesat]

And Diseqc is about switching between LNBs... oeps switching between low band converters.... oeps... switching between that electronic thing on your dish where the coax cable is connected via an F plug... Oeps plug you screw directly on your cable...

 

Just to indicate... how far should we go.... ???!?

[Rob van der Does]

That is indeed correct. On the other hand: hobby projects like this can't be run in accordance with full IT-norms (system description, system design, architecture etc).

But the basis is: look at things from the users point of view, not from a professional, technical side.

 

And how far must we go: again look at it from the users viewpoint, what is familiar to 'normal' users. VBI certainly isn't (apart from the discussion if this is VBI or WSS or....).

Edited by Rob van der Does, 18 August 2016 - 17:15.

[littlesat]

From the users point of view there is a lot more than can be adjusted... E2 is in fact a 'hell'... and unless this it is stull user frendly...

[Erik Slagter]

It's not a valid example Littlsat. People that configure DiSEqC devices already bought these devices themselves, so we might expect they should know what it means. In case of VBI, there is a whole generation now that didn't experience analogue television. And for those who did, there is really no reason why one should know what is meant by "VBI".

 

Just call it what it is. It's an ugly noisy line at the top of the picture and it shouldn't be there, so we want to cover it up.

[athoik]

Hi,

On channel E at 3Ε (Digeat Feed) it has 704x576 resolution and hide vbi doesn't work.

On channel ΕΡΤ Word europe 13E it has 720x576 resolution and hide vbi works.

I guess the problem is the 704/360+1 returning 2 instead of 3?

>>> 704/360+1
2
>>> 704./360+1
2.9555555555555557

>>> int(704./360+1.1)
3
>>> int(720./360+1.1)
3
>>> int(math.ceil(704./360+1))
3

Please implement the solution that you consider best...

[littlesat]

The width of the osd is used here.... But it does not care.... Currenly only the height of thr osd is used.....

[athoik]

Why it doesn't work?

I thought that issue was resolution.

A ts recording can help?

class HideVBILine(Screen):
        def __init__(self, session):
                self.skin = """<screen position="0,0" size="%s,%s" flags="wfNoBorder" zPosition="1"/>""" % (getDesktop(0).size().width(), getDesktop(0).size().height() / 360 + 1)
                Screen.__init__(self, session)

Edited by athoik, 9 October 2016 - 20:32.

[littlesat]

Or a screenshot...

It can also be this channel shows more ugly lines instead just a few lines...