Jump to content


Photo

Interlaced parameters issue


  • Please log in to reply
32 replies to this topic

#1 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 11:53

Hi
It seems the PliExtraInfo convert the interlaced format in wrong digit instead of "i50" it gives "i25" most of the times and calculation when using Resolution String is not correct!
Could it be fixed
Thanks

Re: Interlaced parameters issue #2 littlesat

  • PLi® Core member
  • 57,384 posts

+708
Excellent

Posted 14 August 2023 - 12:07

Are you sure it isn't driver related? On which box and which channels do you experience it?


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


Re: Interlaced parameters issue #3 Old Satterhand

  • Senior Member
  • 28 posts

+1
Neutral

Posted 14 August 2023 - 17:35

... instead of "i50" it gives "i25" most of the times and calculation when using Resolution String is not correct!...

 

 

 

i25, a 25 fps interlaced picture, does not and cannot exist.

It is the wrong description for i50, which is de official name for a 50fps interlaced picture.

So you have tot read i50 everytime you see i25.

 

I hope this helps?



Re: Interlaced parameters issue #4 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 17:59

Are you sure it isn't driver related? On which box and which channels do you experience it?


Yes
the box is zero4k
i tested in most of the normal full HD channels and also with SD channels, and compere it simultaneously with another converter at the same time and the result differs from other converter
as I said The only mistake calculation is about "i50" which it shows "i25"

Re: Interlaced parameters issue #5 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 18:05

<widget source="session.CurrentService" render="Label" position="1700,1000" size="200,30" font="Regular;24" halign="right" valign="center" zPosition="1" foregroundColor="grey" backgroundColor="secondBG" transparent="1" >
<convert type="PliExtraInfo">ResolutionString</convert>

You could test it yourself with the other boxes and see the results


Edited by Frenske, 14 August 2023 - 20:10.
I edited your lines and put a part of this between code markers.


Re: Interlaced parameters issue #6 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 18:05

<widget source="session.CurrentService" render="Label" position="1700,1000" size="200,30" font="Regular;24" halign="right" valign="center" zPosition="1" foregroundColor="grey" backgroundColor="secondBG" transparent="1" >
<convert type="PliExtraInfo">ResolutionString</convert>

You could test it yourself with the other boxes and see the results

Attached Files



Re: Interlaced parameters issue #7 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 18:41

For the sample

Attached Files



Re: Interlaced parameters issue #8 mrvica

  • Senior Member
  • 1,270 posts

+87
Good

Posted 14 August 2023 - 19:01

the resolution string is created here

enigma2/lib/python/Components/Converter/PliExtraInfo.py at develop · OpenPLi/enigma2 · GitHub

OpenATV looks very different because of new AVControl -> eAVControl, could you check it on OpenATV

enigma2/lib/python/Components/Converter/PliExtraInfo.py at 7.3 · openatv/enigma2 · GitHub



Re: Interlaced parameters issue #9 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 14 August 2023 - 19:19

There is a lot of confusion about this, even in this thread.

 

Officially, the "i" and "p" should be associated to the resolution, so "1080i" and "1080p", where "1080i25" is a 1080 image with 25fps interleaved, and "1080p50" is an 1080 image with 50 fps non-interleaved. "1080i50" and 1080p25" don't exist (in the wild).

 

In the standard PLi skin is is displayed as "1920x1080i25". which is correct.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Interlaced parameters issue #10 littlesat

  • PLi® Core member
  • 57,384 posts

+708
Excellent

Posted 14 August 2023 - 20:05

I25 is indeed correct… it is i25 or p50..:

Edited by littlesat, 14 August 2023 - 20:05.

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


Re: Interlaced parameters issue #11 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 20:08

There is a lot of confusion about this, even in this thread.
 
Officially, the "i" and "p" should be associated to the resolution, so "1080i" and "1080p", where "1080i25" is a 1080 image with 25fps interleaved, and "1080p50" is an 1080 image with 50 fps non-interleaved. "1080i50" and 1080p25" don't exist (in the wild).
 
In the standard PLi skin is is displayed as "1920x1080i25". which is correct.


Thanks WanWizard
So in this way now I get the point
25i and 50i are the same thing. 25i means "25 frames per second, interlaced". 50i means "50 fields per second", the latter implies interlaced video.

Re: Interlaced parameters issue #12 WanWizard

  • PLi® Core member
  • 70,762 posts

+1,830
Excellent

Posted 14 August 2023 - 20:32

No, they are not the same.

 

25 fps is not the same as 50 fps, the latter has twice the number of frames per second. And 50 fps interlaced does not exist.

 

25i will only become 50 fps after deinterlacing, either by the box, or by the TV. depending on your HDMI settings.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Interlaced parameters issue #13 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 20:49

No, they are not the same.
 
25 fps is not the same as 50 fps, the latter has twice the number of frames per second. And 50 fps interlaced does not exist.
 
25i will only become 50 fps after deinterlacing, either by the box, or by the TV. depending on your HDMI settings.


As I told in previous post
50i means "50 fields per second"
not 50 frames per second

Re: Interlaced parameters issue #14 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 20:59

I meant in this the way too

Re: Interlaced parameters issue #15 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 14 August 2023 - 21:15

Pic

Attached Files



Re: Interlaced parameters issue #16 littlesat

  • PLi® Core member
  • 57,384 posts

+708
Excellent

Posted 14 August 2023 - 21:32

Due to the interlace a frame also has the half of the lines as non interlace…

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


Re: Interlaced parameters issue #17 Trial

  • Senior Member
  • 1,128 posts

+34
Good

Posted 15 August 2023 - 07:46

Hi,

I also had the discussion a few years ago. When you look at the development there is not only one interlaced (1080 but also less) format there are two. First is 50 frames and all from different picutues (50 pictures) and the second with 50 frames but 2 always belong to the same picture (odd/even lines) which means 25 real pictures. This was introduced with DVDs and flags telling the hardware that a frame belongs to the former frame and odd/even frame are combined then. Whereas the first is mainly made to a full picture by line doubling. I think in broadcast systems now the second one is mostly used. You could see the difference if you press stop and you see a good picture or you see a picture which looks like a fence. For the later simple deinterlacing like bob and weave were used.

 

Today we should not care about the name anymore as long as the quality is ok.

 

Ralf



Re: Interlaced parameters issue #18 gh_n

  • Senior Member
  • 39 posts

0
Neutral

Posted 15 August 2023 - 08:24

Thanks all for participating and sharing details about this post

Re: Interlaced parameters issue #19 Old Satterhand

  • Senior Member
  • 28 posts

+1
Neutral

Posted 15 August 2023 - 10:45


I hope this helps?

 

Not a big help I see.
I did not mean to start a discussion.

Being a A/V engineer for half a decade I use i50, like all other professionals.
But using i25 is fine for me, as we mean the same thing.

 

 

Officially, the "i" and "p" should be associated to the resolution, so "1080i" and "1080p", where "1080i25" is a 1080 image with 25fps interleaved, and "1080p50" is an 1080 image with 50 fps non-interleaved. "1080i50" and 1080p25" don't exist (in the wild).

You mean in your world, de Enigma 2 world and probably some other consumer devices.
In my world i50 is used. Check some EBU or ETSI documents and learn.
And I assure you:1080p25 does exist, There is also no interleaved format, i think you mean interlaced.



Re: Interlaced parameters issue #20 mrvica

  • Senior Member
  • 1,270 posts

+87
Good

Posted 15 August 2023 - 13:41

maybe we should use manufacturer driver values (/proc)

ZDF HD Astra 1280x720p50 (shown on the skin)

/proc value different

root@h7:/tmp# cat /proc/stb/video/videomode
1080p50

ServusTV HD Deutschland 1920x1080i25 (shown on the skin)

/proc value different

root@h7:/tmp# cat /proc/stb/video/videomode
1080p50


Edited by mrvica, 15 August 2023 - 13:42.



8 user(s) are reading this topic

0 members, 8 guests, 0 anonymous users