Jump to content


Photo

PIP very strange behavior.


  • Please log in to reply
11 replies to this topic

#1 Beeker

  • PLi® Contributor
  • 1,471 posts

+196
Excellent

Posted 24 May 2017 - 07:37

Since commit:

 

https://github.com/O...942108b8b3cf80c

 

-There is no PiP at all
-It appaears very  small and dissapear after zapping.
-Sometimes it's ok.

But not necessary in this partical order.

DM8000, but perhaps more boxes?


DM920, Gigablue UHD TRIO 4K and DM8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.

Re: PIP very strange behavior. #2 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 24 May 2017 - 07:40

But this line I added here was mandatory..... Wierd stuff that PIP.... :( And as we do not have DMM8K (we do not own them anymore) we cannot check this at all...

Does it get small after zapping from the channel selection s.. or does it get small when you zap left/right? When it is from the channel selection screen probably DMM does not see the resize.... (or we have to swap resize and move which I did in the other patch from yesterday).


Edited by littlesat, 24 May 2017 - 07:42.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: PIP very strange behavior. #3 Beeker

  • PLi® Contributor
  • 1,471 posts

+196
Excellent

Posted 24 May 2017 - 07:48

This is with up to date enigma2 this morning.

 

And occurs with normal zapping. zap PiP not tested..but i will do that also.

 

Perhaps this is indeed dm8000 only..


DM920, Gigablue UHD TRIO 4K and DM8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.

Re: PIP very strange behavior. #4 Beeker

  • PLi® Contributor
  • 1,471 posts

+196
Excellent

Posted 24 May 2017 - 07:58

With PiP.. normal zap with left/right doesn't work at all first

 

Only from channelselection. After zapping from channelselection..left/right is working.


DM920, Gigablue UHD TRIO 4K and DM8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.

Re: PIP very strange behavior. #5 ims

  • PLi® Core member
  • 13,608 posts

+211
Excellent

Posted 24 May 2017 - 09:53

On vs1500 is PiP as small black box only ...

Attached Files

  • Attached File  pip.jpg   84.09KB   4 downloads

Kdo nic nedělá, nic nezkazí!

Re: PIP very strange behavior. #6 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 24 May 2017 - 10:09

what is the '*' supposed to do, in ePoint(*(x, y))

(it probably does not do what you intended it to)



Re: PIP very strange behavior. #7 ims

  • PLi® Core member
  • 13,608 posts

+211
Excellent

Posted 24 May 2017 - 10:19

Strange...


Edited by ims, 24 May 2017 - 10:23.

Kdo nic nedělá, nic nezkazí!

Re: PIP very strange behavior. #8 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 24 May 2017 - 10:42


(it probably does not do what you intended it to)

 

 

RFFFFFFFFFFFFFL........ that star should indeed not be there.... ;)

 

Still wierd I did not see those symptoms yesterday evening....

 

'fix' pushed....


Edited by littlesat, 24 May 2017 - 10:49.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: PIP very strange behavior. #9 ims

  • PLi® Core member
  • 13,608 posts

+211
Excellent

Posted 24 May 2017 - 11:02

No, it has no effect ... only rem this line helps ... may be, you something forgot merge ?


Kdo nic nedělá, nic nezkazí!

Re: PIP very strange behavior. #10 littlesat

  • PLi® Core member
  • 56,123 posts

+685
Excellent

Posted 24 May 2017 - 11:18

Then it is getting in a terrible phase..... :(.... all drivers behave different....  

 

With VU ultimo the position of the PIP is never the same is it was before without this line :( :( :(

 

PIP Maddness.... And basically it should just move it...

And all due to we work-a-round on the thing that these boxes do not support hide pip....


Edited by littlesat, 24 May 2017 - 11:19.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: PIP very strange behavior. #11 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 24 May 2017 - 17:42

what is the '*' supposed to do, in ePoint(*(x, y))

(it probably does not do what you intended it to)

Also the compiler probably threw a warning about it as well...


Edited by Erik Slagter, 24 May 2017 - 17:42.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: PIP very strange behavior. #12 Beeker

  • PLi® Contributor
  • 1,471 posts

+196
Excellent

Posted 25 May 2017 - 10:22

PiP ok now, at least for DM8000. Thanks.


DM920, Gigablue UHD TRIO 4K and DM8000. Wavefrontier T55 13.0|19.2|23.5|28.2 + Ziggo.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users