|
|
Hi all, to end these postings I want to tell everyone than even no solutiion was found to my problem and I'm sure it is related to something wrong with the AMD Radeon RX470 as this card becomes the only common factor on all tests, with PD18 working fine when removing such card.
I finally asked for a refund to Cyberlink as PD18 is useless for me at the moment and I´ve got today.
This speaks for a serious company taking care of its customers. I'm very satisfied doing bussines with them.
I hope issues will be fixed in a near future.
Thanks to everyone for their help.
|
|
|
Hi Vezir, I've done all possible checks including updates to graphics card drivers (first step), made sure Windows has no pending updates and so did with Media Player Home Cinema (MPC), Video Lan Player (VLC) and Pot Player (4K player).
Even took the "MP4 rendered" video and played it on my MacBook Air and no image at all in every case.
When rendering output on the plain Intel GPU on the ASUS motherboard all test went fine. Not a sinle problem no matter what kind of setting I used. It's very clear that something is wrong with the AMD Radeon RX470 graphics card.
This morning I installed the free version on a different PC with very limited resources and althoug it took a very long time to create the output using on-board GPU the final video was 100% OK. Same result on both PC running PD16.
Thanks for you suggestion. Greetings
|
|
|
Thanks Tony for your reply.
Thanks for the valuable tutorials you produce. I've watched many of them and learned good tricks and techniques. Please keep on the good work.
Looks like there are things to be done by Cyberlink.
Greetings.
Miguel
|
|
|
After many attempts and all kind of parameter changing I reoved from my PC my AMD Radeon 479 graphics card and test rendering my Hero 6 test video just with the ASUS motherboard's Intel GPU and it renders fine with and without lens correction and hardware decoding/encodeing combination so it seems like PD18 doesnt like Radeon 470 card even PD16 and all other editors make no problem. AMD GPU drivers are up to date as well as Win 10's.
So I'm quitting my attempt to use PD. I'm not going to buy a differten GPU for more money than buying the full license of Davinci Resolve 16 at $299 with iut outstading lens correction (sorry it is not available on the free version) to solve my GoPro clips fisheye. PD16 has served me very well in the past but PD itself is so limited.
Thanks for the help to replying fellows.
|
|
|
Jeff, you are right but it was just my mistake.
I try H265 and captured that screen instead of the right H264, but none of them produces anything on the output.
Video is just black with or without hardware decoding/encoding. Just no combination of parameters produce any output when using Lens Correction. With Gopro normal fisheye lok any combination of settinbgs work OK.
|
|
|
|
Produce tab settings are on attachment
|
|
|
Attachments show PD18 settings.
Video sample is just some seconds filmed on a Hero 6 in 4K 30fps SuperView H264 enconding. Enclosed is MendiaInfor clip info.
PD18 is set for 4K UHD 2840x2160 30fps 73Mbs H264.
With or without Hardware Decoding output is just black video.
With hardware decoding ON the is no preview when applying Len Correction. Without it preiew is fine but no ouput.
Sound track OK.
PC is i7 8700 32Gb RAM 2x1Tb Samsung SSD drive and AMD Radeon 470 graphics card and Windows 10 x64
PD16 does everytinh fine as well as Davince Resolve 16.
|
|
|
I was happy a bit too early. Disabling Hardware decoding solved the image preview being a black window when activating Lens Correction for Gopro video but after rendering the edited video there no image at all. Only when NOT applying Lens Correction PD18 produces an image.
No such problem on PD16 which I will continue enjoying. I regret the upgrade and paying the 365 subscription. This PD18 is crap. Dont upgrade if you use Gopros.
|
|
|
|
Hi Bernd, I had the same problem with GoPro Hero 7 vieos when applying Lens Correction and someone on the forum suggested I disable Hardware Decoding on Preferences. This solved the problem and I can now apply Lens Correction and still have video on preview (not a black screen) but when producing the output video still no image.
|
|
|
WOW !!! Great suggestion Jeff.
Just tried it and it does the magic. WITH Hardware decoding Lens Correction makes video = black screen.
WITHOUT hardware decoding Lens Correction works fine and even a little difference on final appearance using Hero 6 or Hero 7 options.
Thanks for the advice. Problem solved !!!!
|
|
|
May be you can group your dash-cam clips by selecting them all on the timeline and then mouse right-click Group/Ungroup them. This will create one clip which will be easier to manage than separate ones. It may help you with sincronization.
Grouping them would be easier if you place them all on a separate track at first.
|
|
|
Whenever I intend to apply Fix/Enhance + Lens Correction to a GoPro Hero 6/7 video (any resolution FHD/4K) preview window goes black and I get this error on a just installed PD18-365:
Media Source Error Report :
Error type : Video cut
Material type : Video
Error information : Unknown
Material filename : F:\Video_Salida\ShadowEditFiles\GH011918_USH_RestaurantCumbresDelMartial_0.mp4
Detailed information : hr = 0x80040217, at ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:4497
Source filter GUID : E436EBB5-524F-11CE-9F53-0020AF0BA770
Splitter filter GUID : A05CDF6C-287E-47A1-A407-A477A8A5FDCA
Video decoder filter GUID : 8A0836E9-6E48-454D-8F68-507BC13F3D0B
Video hardware decoder filter GUID : 8A0836E9-6E48-454D-8F68-507BC13F3D0B
Sound is fine but no image. Worked (and still does) OK on PD16.
No matter what GoPro model I pickup. Just clicking Lens Correction kills the ideo.
|
