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 >
Hi, Cazz.... See my picture.....

Under H.264 / AVC you have the choice between M2TS, MP4 and MKV.

You have the same choice under H.265/AVC
Quote:
Quote:
Quote: Hi, thank you, Dafydd,

I installed the 2507 beta patch, and I confirm that there is now no more issue with the producing of 4K resolution with Nvidia GPU hardware encoding enabled.

It's kind of fixed. One still gets the bogus error attached and the error follows my same comments here http://forum.cyberlink.com/forum/posts/list/25/41925.page#217262 in the pdf file about every red line. Since several users have posted similar errors I'm outlining a simple test that maybe CL can replicate as it may offer some resolution to other similar issues as well.

Bhajje, do the following and see if it errors for you for confirmation of the issue.

Another easy test for CL is as follows:
1) put standard Boats.wmv in the timeline and produce to AVC 4K 3840x2160/60p 50Mbps with HA selected with a Nvidia GPU(Kepler/Maxwell) The results of this produced file is desired frame size, 3840x2160
2) remove Boats.wmv from the timeline and drop in produced file from step 1
3) Produce with same settings as step 1, AVC 4K 3840x2160/60p 50Mbps with HA selected with a Nvidia GPU(Kepler/Maxwell)
4) Use the previous button and now select AVC 4K 3840x2160/30p 50Mbps with HA selected with a Nvidia GPU(Kepler/Maxwell)

Step 4 will produce the bogus error upon production and also cause production issues with other profiles. One has to close PD, put the produced file from step 1 or 3 in the timeline, set options as per line 4 and then production is successful.

Jeff


Issue noted above appears to be a feature of PD13 2507 and Nvidia Driver 344.75. The issue is not present with PD13 2507 and Nvidia 347.09 Driver. I was staying away from 347.09 driver with PD as HA has some other significant performance degradation.

Jeff


Yes, Jeff

For this test, I am using 347.09 nvidia driver.
Hi, Jeff,

I followed the 4 steps of this test, and I didn't have the bug you mention.

All the 4 producing worked fine.
Yes.....
Hi, I confim this issue is solved by the last beta patch 2507.
Hi, thank you, Dafydd,

I installed the 2507 beta patch, and I confirm that there is now no more issue with the producing of 4K resolution with Nvidia GPU hardware encoding enabled.
Happy New Year from France.....
Quote: Hi everyone,
The details/report info has been passed onto CyberLink.
Well done
Dafydd


Thank you, Dafydd....
Many thanks, everybody.....

I hope CL will correct that soon. The better would be à good produced clip with HA, and at least to make uncheckable the HA box.

For now, I know that... So, I can produce fine WITHOUT cheking the box....
Sorry, for the translation. My rush is what I take with my camcorder (Sony AX100).

Here a 5 seconds clip.
Yes Jeff, but here, you don't work with a 4K rush.

If I take the boats.wmv exemple of PD13, and produce in 4K with HA, I have the same result that you have.

But it's with a 4K rush, that it doesn't work; and that the produced clip is 1920x1080 with HA.
Quote: Bhajje,

I tried to replicate your issue with PD13 beta 2403 and can not.

XAVC S 3840x2160/25p (60Mbps) France (PAL) setting with HA produced correct file attributes
MPEG-4 4K 3840x2160/25p (50Mbps) France (PAL) setting with HA produced correct file attributes

I tested with a GTX970 (Maxwell) architecture vs your GTX770 (Kepler). I have a GTX650 (Kepler) that I can put in and try. What Nvidia drivers are you using?

Jeff


Jeff, my driver is the last official (344.75).

Thank you, for looking.
Yes, I think so. The error to be corrected in PD13, is to make not checkable Hardware Encoding.

So, it will be clear, and the rvideos produced will be fine;
So. If that's an error in PD13, it should be corrected.

As we see we can check the box, we do that, and the result is false (1920x1080, in place of 3840x2160, as defined in profile used).

Hi, Dafydd.... What do you think about that?
Quote: There is NO hardware acceleration for any 4K profiles, or anything over 1080.
In cannot be, nVidia, Intel or AMD don't support that as of now.


Hi, SoNic67.

perhaps I don't use the proper words 'I am french...). What do you think about the joined picture?

I can check the lower box when choosing 4K profile, H264/MP4 producing. Same with XAVC/MP4 producing. See on the picture the profile and the box checked.

Whith this profile, when the box is cheched, the produced file is 1920x1080. When unchecked, the produced file is 3840x1160.

Why?
Hi Everybody,

Big problem when producing 4K with Hardware acceleration. I choose a default profile 3840x2160, and the result is 1920x1080, when I chek HA. Same thing when I choose a custom profile.

Same profile and HA unchecked produce fine 3840x2160.

So, the problem comes when using HA.

I am using beta build 2403. With buit 2307, same problem.

Pierre,

Dans PD13 en français, cet effet ne s'appelle pas tilt-shift.

Regarde dans la catégorie d'effets "Special', comme l'indique Tony, l'effet "Décentrement".

C'est une traduction littérale....

Note: il s'appelle pareil dans PD12
Hi, Tony,

I confirm this too.... And, as Neil writes, it was not the same in previous versions.

And I agree with you, it should be in the preferencies.
Great, Playsound....

It works fine.

Many thanks....
Hi, No idea?

Nobody can help me?
Go to:   
Powered by JForum 2.1.8 © JForum Team