How PsF video from the V1 is different than "p" or "F" video

[Timo Mukari]

Originally Posted by Piotr Wozniacki

However, before I make my final decision, a quick but important question to any PAL version users out there: with the recommended by Sony sharpness at 3, is your component/HDMI output on a full HD display completely twitter free?

I would say mine is completely "twitter" free at 3, and usable at least to 5-7.
Btw. I also managed to get my clips burnt on an HD-DVD (using stnd DVD, see the other thread). Pls. tell us which cam did you ended up choosing ?

[Piotr Wozniacki]

Originally Posted by Timo Mukari

I would say mine is completely "twitter" free at 3, and usable at least to 5-7.
Btw. I also managed to get my clips burnt on an HD-DVD (using stnd DVD, see the other thread). Pls. tell us which cam did you ended up choosing ?

I'll soon be changing my signature - then you will know:)

In the meantime I can tell you that (at least in my unit) there is still some twitter even with sharpness at zero. Also, I learned from Manfrotto that the MN523Pro lanc controller that used to work just fine with the original V1E (i.e. before the fix) doesn't wotk with the "fixed" V1E's (it switches the camera off after several seconds). So, yet another problem to solve...

[Timo Mukari]

Originally Posted by Piotr Wozniacki

I'll soon be changing my signature - then you will know:)

In the meantime I can tell you that (at least in my unit) there is still some twitter even with sharpness at zero. Also, I learned from Manfrotto that the MN523Pro lanc controller that used to work just fine with the original V1E (i.e. before the fix) doesn't wotk with the "fixed" V1E's (it switches the camera off after several seconds). So, yet another problem to solve...

Too bad. Luckily I don't have any lanc controller, just the normal plain tripod.
But this means Sony have really changed somethig in the SW since you did not have this problem before, i.e. they did not only change some filter settings as speculated here somewhere?

[Steve Mullen]

Originally Posted by Bob Grant

Last night I watched a video game on the PS3 hooked up to the latest Sony Full HD TV of monsterous proportions. The fine detail in the game had line twitter.

Bob's comment suggests the answer to your question "with the recommended by Sony sharpness at 3, is your component/HDMI output on a full HD display completely twitter free? Because mine is not; even with sharpness at zero!"

Twitter has a way of showing-up when ever the source has very high V rez plus very thin lines. The solution is to pre-filter before recording or in post. Sony's not filtering -- which perhaps it should on the V1E. Perhaps an optical anti-aliasing filter could be added.

PIOTR -- you might want to go to dvfilm.com and download DVfilm Maker. Not only does it deinterlace and optionally add grain -- it has a twitter filter!

BOB -- did you ever actually record 24 with 2-3 pulldown added back to the camcorder?

PIOTR -- did you ever actually record 1080i50 from a 25p Timeline back to the V1E?

[Piotr Wozniacki]

Steve

Yes I PTT'ed a 25p timeline as 1080i, but did watch it through component/HDMI yet. Did you read Timo's comment about the Toshiba HDTV not showing any line twitter in his V1E's 25PsF?

[Bob Grant]

Originally Posted by Steve Mullen

BOB -- did you ever actually record 24 with 2-3 pulldown added back to the camcorder?

PIOTR -- did you ever actually record 1080i50 from a 25p Timeline back to the V1E?

Just recorded 24p back to a M15U deck, no problems. Captured it back with Pulldown Removal Enabled and got back 23.976. Note that I had to start from a HDV 23.976 project and PTT from that T/L, for some reason the VCR did not like the 60i clip I posted previously. Still no harm done, as it can be done.

[Douglas Spotted Eagle]

To my knowledge Sony haven't changed anything in the LANC. I use LANC daily, and while I don't have a Manfrotto, I've had the V1 on several 3rd party LANCs and no change/differences of any kind. Just used the newer Canon LANC yesterday, and all features worked as expected.
LANC is a protocol, it's not something they're going to be messing with.

[Michael Phillips]

[QUOTE=Piotr Wozniacki;627765]That's what I've always done. I only meant that while it's easy with Premiere, my Vegas 7.0d cannot export a 1080/25p MPEG-2 by just changing the frame rate in the 1080/24p "Blue Print" template; I'll try to go through advanced video settings in order to make it work as soon as I have captured 25p material from the "fixed" V1E that I've just got an hour ago.

I just use the 1080/50i set to progressive and it produces a playable M2t that is progressive. I play it in VLC as progressive with no problems. I did one test with median filter in Vegas just to tidy up some anti-aliasing, did a good job but took a long time to render.I don't have any software to make a HD-DVD, but I would say there should not be a problem playing in a full progressive setup as the M2t appears compatible.

[Steve Mullen]

Originally Posted by Michael Phillips

[I just use the 1080/50i set to progressive and it produces a playable M2t that is progressive. I play it in VLC as progressive with no problems. I don't have any software to make a HD-DVD, but I would say there should not be a problem playing in a full progressive setup as the M2t appears compatible.

Since you can't record 25p to your V1E, since BD doesn't support 25p, and the Toshiba HD DVD player doesn't yet support 25p playback -- there's not a big need to export 25p. (Unless you are going to film.)

Likewise for a 24p timeline. You can't record 24p to your V1E, the low-cost BD creation software may not yet support 24p; and the HD DVD creation may not yet support 24p -- there's not a big need to export 24p. (Unless you are going to film.)

Did you find difference between setting the output file to Progressive or Upper Field interlace?

[Michael Phillips]

Originally Posted by Steve Mullen

Since you can't record 25p to your V1E, since BD doesn't support 25p, and the Toshiba HD DVD player doesn't yet support 25p playback -- there's not a big need to export 25p. (Unless you are going to film.)

Likewise for a 24p timeline. You can't record 24p to your V1E, the low-cost BD creation software may not yet support 24p; and the HD DVD creation may not yet support 24p -- there's not a big need to export 24p. (Unless you are going to film.)

Did you find difference between setting the output file to Progressive or Upper Field interlace?

If you mean was there any other differences than just setting progressive, no. But I did notice in the advanced settings that some of the Pal settings did not automatically display and you had to set them manually, and trying to tweak the advanced settings to achieve "better" results was a waste of time.
The interesting fact I really wanted to know was just putting M2t files on DVD and playing them via PlayStation 3 and what quality was achieved through a progressive TV or even as interlaced.

[Piotr Wozniacki]

Originally Posted by Douglas Spotted Eagle

To my knowledge Sony haven't changed anything in the LANC. I use LANC daily, and while I don't have a Manfrotto, I've had the V1 on several 3rd party LANCs and no change/differences of any kind. Just used the newer Canon LANC yesterday, and all features worked as expected.
LANC is a protocol, it's not something they're going to be messing with.

Spot, LANC is a protocol, but we all know it has some flavours; eg. the Canon's implementation varies from Sony's in certain aspects. For this reason, many controllers' PAF button works with some cameras but doesn't work with others. With the V1E, all MN523Pro's buttons function as intented, but only for several seconds - than the camera is simply switched off. My dealer informed me that the first V1E units he had before the 25p fix worked flawlessly (just like all the FX7s). So, go figure!

The Manfrotto's lanc controllers are being developed in Poland, and I will probably become their Beta-tester for the fixed MN523Pro.

[Steve Mullen]

Bob -- thank you. Previously, you mentioned that the P-flag was not being set in your exports.

Then I read this from from Michael -- "I just use the 1080/50i set to progressive and it produces a playable M2t that is progressive. I play it in VLC as progressive with no problems."

What were you trying trying to export?

How did you do this?

How did you find the P-flag wasn't being set?

Michael -- I'm confused by "1080/50i set to progressive." Do you mean you CHANGED the Field seting for a 1080/50i preset to NONE?

[Steve Mullen]

I'm now not using: 1080/24PsF 1080/25PsF 1080/30PsF

I find it far more clear to use:

1080i60 -- the way my magazine writes 1080/60i

1080i60/24p -- V1U (2-3 pulldown used)

1080i60/30p -- V1U

1080p60 -- coming someday


1080i50 -- the way my magazine writes 1080/50i

1080i50/25p -- V1E

1080p25 -- coming for HD DVD players via firmware

1080p50 -- coming someday


1080p24 -- pure 24p (BD and HD DVD)

1080p24F -- Canon's true 1080p24 but not with 24p images


720p25

720p30 -- likely to go away

720p50

720p60

720p60/24p -- 2-3 pulldown used

One can instantly see the nature of the video format by the first "i" or "p" and it reminds one they are working with interlace video even though Sony calls it 24p, 25p, and 30p.

The second number -- if there is one -- tells you the frame rate. The "p" tells you the carried images are really progressive.

The ratio between the two numbers, if not "2" -- tells you 2-3 pulldown is being used. For example, you can instantly see that to have a 1080p24 timeline, the 2-3 pulldown must be removed from 1080i60/24p. However, you also instantly see that you can edit in a 60i timeline because of the "1080i60" designation. Then when one wants to go to film, which is 1080p24 -- one instantly sees by the ratio between "60" and "24" that the 2-3 pulldown must now be removed.

For example, if one is editing 1080i50/25p, when one wants to go to film they DEINTERLACE which removes the "i" and replaces it by a "p" yielding 1080p25.

Or, if one has a 1080p25 timeline and wants to PTT to their V1E they must "convert" to 1080i50/25p. They know the Sony camcorder can only record 1080i50.

[Michael Phillips]

Originally Posted by Steve Mullen

Bob -- thank you. Previously, you mentioned that the P-flag was not being set in your exports.

Then I read this from from Michael -- "I just use the 1080/50i set to progressive and it produces a playable M2t that is progressive. I play it in VLC as progressive with no problems."

What were you trying trying to export?

How did you do this?

How did you find the P-flag wasn't being set?

Michael -- I'm confused by "1080/50i set to progressive." Do you mean you CHANGED the Field seting for a 1080/50i preset to NONE?

Yes, Steve, changed to none. I was just using the template in Vegas for 1080/50i and changing it to progressive with 25P captured from from the V1P. Reimported the rendered clip into Vegas and it showed as progressive.

[Piotr Wozniacki]

Steve, Bob, Michael at al,

My impression is that we have started repeating what has already been said on the main subject. I realize I have my own, private agenda (of choosing the best cam for myself), please accept my apologies for that. I'd like to re-ask the question: whatever you call it Steve (1080/25PsF or 1080i50/25p), don't you agree that the V1E progressive material isn't "flawed" per se, but simply is not being correctly displayed? What we have is each of 25 frames per second written as two fields (or segments), taken in the same moment of time, one containing the odd lines and the other - the even ones. Now, to get back a full 1080 lines frame, both segments should not be "deinterlaced" (this process always assumes some method of approaching the temporal difference between fields), but displayed at the same time (weaved). This is evidently not the case, when the V1E is connected through HDMI or component to a progressive display. The fields are bobbed, which pronounces the aliasing effects present in the material.

The experiment with the 1080-line chart from Bob confirmed that it can be displayed correctly, without aliasing, as long as no deinterlacing is engaged. Bobbing it leads to horrible flicker (even worse than with the 25p material from the V1E, as we have fields of 1080 not just 540 lines being bobbed).

All the above is my understanding of the problem. If I'm missing something, please correct me.