Without downloading the files I think both the problems have been noted:

Firstly SVRT does not work if you change the beginning of the clip; this includes transitions.

Secondly when rendering interlaced material , PD9 apparently just line doubles the interlaced field A and hence losing half the information and creating the effect you see.
Panasonic SD9, Panasonic TM700, Panasonic SD600, GoPro HD Hero.

And...don't forget your poor video drivers!!! They are two (2) major releases behind. The new drivers for your card are:

http://www.nvidia.com/object/win7-winvista-64bit-260.99-whql-driver.html

FredB:
thanks for the comment. Just after I posted this, I predicted that response, so I upgraded my video drivers. I'm now using 260.99, and the result is the same.

pjc3:
according to the PD9, SVRT is still enabled after I deleted the one frame, plus I think I saw this same effect when I tried the steps with SVRT disabled the whole time. So I think your second comment is the main reason, if that's true (it's news to me). Is this documented somewhere that I can read more about it?

thanks.

Paul M...yes, I visit here occasionally..if I can "scare" everyone to the new drivers..I thank you.

I believe many of us are struggling to determine the "logic" behind PD9 implementation of SVRT3.

Quote: FredB:
t So I think your second comment is the main reason, if that's true (it's news to me). Is this documented somewhere that I can read more about it?

thanks.

Here is a thread where it is discussed.


http://forum.cyberlink.com/forum/posts/list/14536.page#69574 Panasonic SD9, Panasonic TM700, Panasonic SD600, GoPro HD Hero.

I created a support ticket on this issue. I'm not sure that the problem was comprehended though. I think it's being lost in translation. It looks like they think I'm complaining about a simple reduction in quality due to re-rendering which is normal. I've explained it 3 times with sample files and screen shots.
Fro my research MBAFF is a technique that allows it to encode blocks at a time and determine if it needs to be interlaced or not, per block.
Does anyone know how to "track a bug id" which they provide me below?
Read the response from support:


Dear Eric,

Thank you for writing back.

I understand that you are not getting good quality of video after producing without SVRT feature.

1. The produced file with SVRT scan type is interlace/top field. The produced file without SVRT scan type is MBAFF, also a kind of interlaced coding.

2. If the clip produce without SVRT, it will do transcoding/compress, thus the quality is of course not good as with SVRT or original one.

3. Please try to produce with higher bitrate profile. ( For example, H.264/ AVCHD 1920*1080 (24Mbps) )

Also, I would like to inform you that a Bug has been created for quality issue. You can track it further with the BUG-ID: VDE112504-0016.

I regret for the inconvenience.

Please feel free to contact us back for any further clarification or for any assistance related to CyberLink Products. Use the below mentioned link to get back to us for your further queries:

I don't know if this helps but when I was investigating my own AVCHD problems I found somewhere a note that you should not try to trim AVCHD clips but only ever use the split function.

Unfortunately, despite searching I can no longer find the reference.

Gary.

Just to be clear on the original poster's complaint, I assume he is saying his 60i clip which is 60 interlaced "fields" per second is being converted to 30 unique fields per second.

From my testing, it's still saved at 60i however the A and B frames are duplicates, so it appears like 30P.

The crux of the problem is in order for video to be edited, it must first be deinterlaced. Obviously, you can't apply video effects to a frame that is full of zig-zag lines and expect it to look ok after.

So before the video is processed it must first be "cleaned up" or at least made "normal" video. To do this we decode the video and deinterlace the video. There are several techniques to deinterlace video listed here:


Disabled
(is this what 100fps.com calls "do nothing"?) Other names: "weave" or "no deinterlacing". Should be used for PsF content.

Blend
Each line of the picture is created as the average of a line from the odd and a line from the even half-pictures. This ignores the fact that they are supposed to be displayed at different times.

Bob
Display each half-picture like a full picture, by simply displaying each line twice. Preserves temporal resolution of interlaced video.

Discard
Only display one of the half-pictures, discard the other. Other name: "single field". Both temporal and vertical spatial resolutions are halved. Can be used for slower computers or to give interlaced video movie-like look with characteristic judder.

Linear
Bob with linear interpolation: instead of displaying each line twice, line 2 is created as the average of line 1 and 3, etc.

Mean
Display a half-picture that is created as the average of the two original half-pictures.

X
Generates a full picture taking the odd lines from the odd half-picture, and creating the even lines through a complicated algorithm that uses information from both half-pictures.

This may be similar to what 100fps.com calls Area based?

Yadif
Display a picture as the other deinterlacer like discard and X.

Yadif (2x)
Bob with Yadif 2x interpolation like linear: Instead of 25fps you could try this but it may skip some of the frames when you use this deinterlacer.


It would appear through testing that PD9 is using the fastest method (Discard)

Once the file is saved it is re-interlaced and written at 60i. However you have already discarded half the vertical and temporal resolution, so writing 60 fields per second is just saving a 30P video in a 60i container (duplicate every other field)

The fix would be to allow the user to pick which deinterlace method is used.
The work-around is to use 3rd party software to properly deinterlace 60i and save it as 60p. Then open the 60p file in PD9.

The crux of the problem is in order for video to be edited, it must first be deinterlaced.

Sorry I don't see the logic of that. Interlaced video is edited all the time professionally, with no need to de-interlace first unless you are going to do something that corrupts the interlace, such as running it in slow motion.

Normally the only limitiation is that the field sequence must run continuously across the edit. This is far easier now with digital video than it used to be with analogue NTSC or PAL.

I do however like the idea of uprating 1080i25 to 1080p50 (or 60 if you are in the NTSC region) before editing. Do you know of any software which will do that?

Gary.

The software deinterlaces it behind the scenes so that it can be edited. If you were to blindly edit a frame of interlaced video and played it back on a tv that deinterlaces video automatically, the results would not look very good.

As for up-converting 50i to 50p, this may get you started:
http://www.youtube.com/watch?v=RXByaCFgIHc&feature=channel

Using a high complexity deinterlace algorithm will get you much better quality video than PD9 does with importing 50i, that is for sure.

Also:
http://www.100fps.com/