Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Quote

Fellow members (anyone who cares) - could you please download and test this original .mts clip from a Panasonic TZ60, and report your results here?


Cheers - Tony


Hi Tony

on your sample I have same problem like on my, from A6000 - green bar

Irek
Quote
Fellow members (anyone who cares) - could you please download and test this original .mts clip from a Panasonic TZ60, and report your results here?


Cheers - Tony


It's also my link to Dropbox with 38,7mb file, time: 12 sec

https://www.dropbox.com/sh/3ctfjxqnfhd9gip/AAB5EmpEpyB3YFHiA_T7uQ59a?dl=0

let us know how it works on yours computers

Irek
Quote Here is an unlisted screen capture showing the issue Irek has raised.



As stated previously, the same problem does not occur "round-tripping" between PDR15 & CDR6.

Cheers - Tony


I have the same bar as in this yt movie but only after rendering movie.
It not occur if files are from Panasonic A160 or prerendered to MP4 or when I crop a bit original frame from A6000 in EDIT mode.

Irek
post to erase... on original files from Sony A6000 problem still exist.
I work back in PD15, cant wait so long for technical support answer...
temporary solution:

When I crop this fragment(with CD6 correction) in project, green bar disappear after production.

But we lose some pixels from original sources(movie is not real 1920x1080).

Irek
Quote Hi somrozen -

When I pre-produced to a similar profile but used H.264 MP4, there were no issues.

Cheers - Tony


Hello Tony

Its my basic profil, H.264 MP4, on MOV problem also is there.

Irek
Quote In PD16_settings. you also need to uncheck the Enable Hardware decoding in Preference/Hardware acceleration. That should fix it.


I tried it before, no changes...
In my opinion, after many tests, problem is in PD16

PD15+CD6 with graphics acceleration - haven't this green bar

Probably defect is in render engine in PD16

Irek
No change,

I disabled graphic acceleration in PD16 and CD6,

and green belt still here
Quote
Quote when I edit fragment movie in CD6 green bar appear on the edge.


That problem had been resolved in the past. The problem may be that you are using Canon dslr videos which does not have a correct aspect ratio. In ColorDirector go to Preferences/Hardware acceleration/Uncheck Enable hardware acceleration for video decoding. That should fix the problem although your producing time will increase.


I work on Sony A6000 and Panasonic A160AEJ

But will test that configuration

Irek
does not matter, select or not graphic acceleration,

when I edit fragment movie in CD6 green bar appear on the edge.
Hi Maliek

of course, last drivers in Win10Prof updates, not Nvidia drivers standalone.

Preference settings are same in PD15 and PD16, only hardware acceleration enabled.

I will try without that acceleration...but time of production will increase...

we will see

Irek
Hi Paul1945

I'm a wedding filmmaker, and I work only in 1080p,

I use only 1 monitor in single mode,

I never had that problem before in PD15, I just upgraded a few days ago, and that is first project in PD16.

I still have PD15 in my computer next to PD16

It's sad when you have newer version and can't use it



greetings from Poland

irek
Hi

I have a small problem with rendering in project 1080 25p, sources are 1080 50p

In project whole movie looks OK, but after "Produce" these fragments which were edited in ColorDirector6 have small green belt in bottom.

Other fragments without any action in CD6 looks OK...

In old PD15 and CD5 everything was OK

Any suggestions?

Irek
Only driver and PhysX, should I uninstall PhysX?
Thank you so much tomasc, problem solved
Hi, I've upgraded my computer from GTX 560, now I'm with GTX970
from ASUS, but after just one crash in produce mode, my 'Fast video rendering' (both
SVRT and Hardware video encoder) is greyed out for H264 1920x1080
25p profil and after second crash on XAVCS 1920x1080 25p profil disappear too, I can
still produce with hardware video encoding with H265, but I'm afriad so
after one more crash I will lost last profile 25p. Any advice?

Edit: Nvidia released 15 August new drivers for GTX970 - 372.54 WHQL, after instalation all profiles back!...but problem occurred again...first crash, and H264 FHD 25p dissapear. Now I can produce with XAVCS and H265.

When I reinstaled drivers again, nothing change, H264 not return.

My computer: AMD FX 8350, GTX970 4GB STRIX on Nvidia372.54 drivers,

16 GB RAM, 5 x SSD drives from 3xSANDISK, SAMSUNG, ADATA, 256
GB each, Mainboard from ASUS M5A97 EVO R2
Well, BIG THANKS for Dafydd B
Yesterday I reinstalled my computer, now is fresh Windows 10 Prof, and with all sugestion from Dafydd B, especially with ProfileXXX.ini, PD14 working good, I made 3 renders and all are sucsesfull, no crash..now, I going for next weeding, will check it exactly next week.
CU
Irek
P.S. before changing name to ProfileXXX.ini, PD14 crashes as usual, even on fresh Win10
Thank you for contacting CyberLink Technical support.

I understand that your PowerDirector 14 crashes when produced.

In regards to your concern, I would suggest you to try few troubleshooting steps and check if it helps:

1) Ensure your graphics card driver is up-to-date.

Yes, they are

2) Update to the latest version of Windows Media Player or QuickTime software.

all up to date

3) Disable the hardware video encoder when producing, if enabled.

done

4) Try to use another source file format in your project.

what? I have 2 x Panasonic AC160AEJ, with AVCHD record, and 2 x Sony A6000 with XAVCS record, and DJI OSMO

5) Remove all third party codecs if any are installed.

only Klite Codec pack in my computer

6) Try to output the production in a different video file format.

H264, MP4, 1920x1080 25p - I need this one, maybe XAVCS will be better?
Thanks Jeff, I will go that way, contact with support, have no idea whats going on.
Go to:   
Powered by JForum 2.1.8 © JForum Team