|
|
Quote
Has anyone noticed a serious bug in PD16?
There is something wrong when you create a BD disc, conforming (BDMV, 1080 60i). In all other Power Director versions, such as PD15, it is that a created BD disc in 1080 60i (interlaced), the result looks absolutely great. The playback on both the PC and all media players and Blu Ray players is wonderful and soft.
In contrast, the PD16-created BD movies in 1080 60i no longer look smooth. It looks as if every 3 picture is missing, or something similar. The playback is restless and the picture flickers.
I compared that, and for me it definitely looks like a bug in PD16.
You can take any x-arbitrary source material, eg AVCHD H.264 video clips in 60p, which were taken with Panasonic or Sony camcorders.
Likewise smartphone clips in 1080 60p.
Unfortunately, the result in PD16 always looks miserable, and is not acceptable, to say the least.
Just try it, and create a BD disc in PD15 and PD16 in 1080 60i and compare the Result.
The media info file does not really help here. There is definitely something wrong in PD16, because the MP4 or MKV production in 1080 60i Interlaced delivers the same result. But not in PD15, there's all good.
As long as progressive is being produced, as is BD disc creation, everything looks good in PD16.
But not in interlaced. But then you are not standard in the BD disc creation, in Progressiv. I have already written to the support, but so far received no answer. Wanted to ask if you have similar experiences here. Neither the operating system nor the PC hardware plays a role, because I tested it on 2 different systems (Windows 7, Windows 10, different Hardware).
The settings in PD16 can not be, these are exactly the same as in PD15. Also disabling and enabling any GPU support does not change the problem.
Ihave the same problem. NOW I know that All files product in 60i or 30fps are not good ( every file,DVD OR Bluray) This is One big mistake of PD16
|
|
|
Quote
I recently upgraded to PD 16. While working with 60 fps (GoPro 3+ black) and 30 fps (Cycliq Fly 6) clips for a video I ran into the problem that the preview would intermittently but frequently black out. The picture came back when jumping a bit around in the video, so initially I did not think of this as a hug issue.
However, after hours of editing, when finally producing the video I ran into the same issue - portions of the video were simply black! That was independent of the format I produced the video in.
I opened support case CS001830088 to which I even uploaded a demo of the issue. The ticket was still unresolved after 30 days into my ownership of the product, so I asked for a refund, which was processed. Shortly thereafter I received an email from 'Donna' at Cyberlink stating now that my refund was processed they no longer see a need to fix the issue.
Shortly after getting the refund I upgraded my PC which happens to have PD 14 pre-installed. I tried with that right away and the issue was not seen. So this is clearly a regression bug in PD 16. Too bad to learn that the issue is apparently considered fix because I decided not to risk my investment by waiting for a fix to become available seeing there was no urgency behind it in the first place. Sad, Cyberlink!
-Matthias
I can say that all video produced in 60i or 30fps are no good (files and DVD ARE THE SAME) I wait one update long time but nothing.
|
|
|
Quote
Quote
...
1. On my system (a 16 Gig Surface Book 4) ...
this means nothing to us. please attach your dxdiag.txt of your baby.
reason it's jerky is because the frame rate is an odd ball at 21 fps! also the resolution is 1620x1080; moreover, panned the camcorder too quick.it takes me about 2minutes or longer for 180 degree pan.
one must slow down a lot especially if you're using so called film looksy at 24 fps. less jerky rendered at 30(29.9997) fps...
oh, happy happy joy joy
PepsiMan
'garbage in garbage out'
I produced all videos with 30fps and DVD 720X480 (60i),all of them were jerky.When I changed to 60fps,they were better.I could'n
use PD 16,uninstall it and re-install PD15.I'M waiting a update to fix it.
|
|
|
