Hi David,

Is it the same issue as this, I wonder??

http://forum.cyberlink.com/forum/posts/list/8183.page

Cheers
Adrian Life is really simple, but we insist on making it complicated. (see below)
Confucius
AMD Phenom IIX6 1055T, win10, 5 internal drives, 7 usb drives, struggling power supply.

Hi Adrian,

Yes, I suspect it's the same issue. It's due to the cameras which use 1080 60i hardware/software path to save 1080 30p footage.

It seems that PowerDirector 8 does not have the capability to deal with such footage in 100% of circumstances. At least in the case of using the "clip speed" function it does not work properly...

-Dave

Is there any tool where you can see that there are actually 2 fields present for a progressive file? In the case you mention, the resolution of each field would be half and the data of one frame would be spread in two fields. Spatially correct, but temporary incorrect. By setting the Main header as 30p they could fool many decoders but not them all because you have to process the two fields anyway (odd first/even first?). If I playback my SX1 FHD originals in MPC-HC by using ATI's hardware decoder or ffmpeg soft one, I get correct statistics of 30fps being played by EVR. If I step frame by frame, I see the image change every step, so I guess that if it is true that they are 30p ala 60i, ffmpeg and ati hardware decoders are smart enough and capable of be instructed to render P content and on the fly reassemble the two fields and render the P frames.

The question is if Cyberlilnk's decoder inside PD8 does the same.

If I render one file only( from my FHD 30p) originals, the result is Ok, but as soon as I make combinations, namely more pieces and multitrims, then the result is still P but with Interlaced artifacts as the pic I posted shows in the thread that is referenced here.

I hope there is someone with enough expertise and the soft tools to point us in the right direction.

If the originals are indeed 30p with two fields (60i) the easy solution would be to get a tool to preprocess the originals in order to merge the two fields in a real Prog frame. That way there is no chance that CL's decoder could make any mistake.

Saludos!!!

My opinion would be: since many cameras now operate this way (and I think Canon is not one of the "small manufacturers"), PD8 should be able to properly interpret this kind of video, natively.

At the very least, the developers should be able to comment on whether this is a known issue... and if/when it may be fixed...

Developers are unlikely to post.

This is a forum for PD users to help each other.

Please read where Adrian has already directed you to.

I have raised the issue with CyberLink.

Dafydd
[Moderator]

Quote: My opinion would be: since many cameras now operate this way (and I think Canon is not one of the "small manufacturers"), PD8 should be able to properly interpret this kind of video, natively.

I would never assume such.

Dafydd Bevan - SoftDeko said:
Developers are unlikely to post.

This is a forum for PD users to help each other.

Please read where Adrian has already directed you to.

I have raised the issue with CyberLink.

Dafydd

Well, I meant that developers provide feedback through you... the forum mod... ; Thanks for raising the issue.

One note, I did try to ask some questions of tech support, but they refer me to pre-sales customer service, who then refers me back to tech support... hence this forum is the only place I find where I can ask "pre-sales" support questions.

I do not *assume* that PD8 can support the new files with PF30 encoded via 60i. (in fact I'm now certain it doesn't support them 100% smoothly). I would only suggest that Cyberlink should want to add such features, to avoid that potential purchasers like myself are not driven away by glitches in commonly used features.

David,

While I do get a small insight into events, I'm not a spokesperson, a PR department would be responsible for that.

I'm not happy with you being given the "run around" by two departments at CyberLink and if you have any reference numbers (I can quote), I will ask Customer Support to track it and contact you with a speedy answer - PM me your email please.

I'd also like a 10 second sample of the new file format, camera details etc. I'll ask CyberLink's R&D team to look the data over and get that format included in PD asap. Let me know if you're willing to provide this info.

I would only suggest that Cyberlink should want to add such features, to avoid that potential purchasers like myself are not driven away by glitches in commonly used features. I agree.

Thanks

Dafydd

I realized that a 10s clip should be doable, many MB but not a problem. How do I attach a large file? Attachment panel has a limit of 100kb/file.

This is a result of PD not allowing you to chose what kind of deinterlacing it does.
It seems to default to "Discard" (that is what VLC calls it anyway)
Your video would look fine if you could pick blend mode, where 60i is played as 30p with both A+B frames blended.

AFAIK there is no way to change the deinterlace mode.

David, just attach the video file here in the forum. It used to 100k but I think it has been changed so people can upload sample videos. My youtube channel====> http://www.youtube.com/user/relate2?feature=mhsn