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. Jean-Paul

i7-4770K 3.50 GHz, Nvidia GTX 960 2 Go, SSD 500 Go, RAM 32 Go
Win 10 64 bits, DirectorSuite 365

Thanks Jean-Paul

Dafydd

Fixed error particle effect reported in this topic, http://forum.cyberlink.com/forum/posts/list/42011.page AMD-FX 8350 / 8GB DDR3
SSD SUV400S37240G / 2-HD WD 1TB
AMD Radeon R9 270 / AOC M2470SWD
Windows 7-64 / PD16 Ultimate

Right now, I think that PD13 is the only software that does 2K and 4K encoding with hardware acceleration. Of course, only with nvidia "Kepler" or "Maxwell" video cards.


PS: I am still puzzled how it does it on Kepler

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.

From the best Summer with 28 the same ....a big Thanks
NVIDIA " Gigbyte 970"
Pauls PC
X399 AORUS Extreme/AMD Ryzen2970WX/1xQuatro 4000 Driver:Geforce 419.67Skill V DDR4 64GB/3200MHz/Win10 prox64
Intel SSD 750/400 / Intel SSD 750/1.2Tb 1x4TB SSHD /1xSeagate 10TB pro
1xSamsung UA28D590 4k LUMIX GH5 1xLG HDR

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

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. Jean-Paul

i7-4770K 3.50 GHz, Nvidia GTX 960 2 Go, SSD 500 Go, RAM 32 Go
Win 10 64 bits, DirectorSuite 365

Quote: 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.

Thanks for non confirmation, interesting, maybe still something CL should have a look at.

One would only have produced files from steps 1, 3, and 4 for a total of 3, not sure how you got "All the 4 producing worked fine".
I assume you caught the 30p setting change in step 4, that appears to be the trigger for the error, changing from one frame rate to another during the same edit session.

I get the same error message if done in PAL and toggle between 50p and 25p.

Jeff

Mine was doing that error on nVidia even before this update, at 60p encoding.
I just had to create a custom profile with the same settings. That one... worked.

Now I changed the card with an ATI one, so I cannot test it, this one works.

Quote: Right now, I think that PD13 is the only software that does 2K and 4K encoding with hardware acceleration. Of course, only with nvidia "Kepler" or "Maxwell" video cards.


PS: I am still puzzled how it does it on Kepler

Rmember Intel Quick Sync also does 2K/4K encoding Main Machine: Jetway NF9G-QM77, Intel i7-3610QM, Nvidia Geforce GTX 1060 3GB, 128gb SSD, Windows 10 Pro
Secondary Machine: Lenovo Y510p, Intel i7-4700MQ 2.4Ghz, 2x nVidia GT750M, 500GB SSHD, Windows 10 Education
visit http://moisescardona.video

Still no other software that I know uses HA for 4K. Especially not with Kepler class of nVidia.

And, correct, Intel does it too, but only with Haswell CPU's.

That's try. That's why I like PowerDirector. Yet, it would be nice if they somehow figure how to do Hardware HEVC encoding maybe using OpenCL, because HEVC rendering is a lot slower than H264 using CPU only. Main Machine: Jetway NF9G-QM77, Intel i7-3610QM, Nvidia Geforce GTX 1060 3GB, 128gb SSD, Windows 10 Pro
Secondary Machine: Lenovo Y510p, Intel i7-4700MQ 2.4Ghz, 2x nVidia GT750M, 500GB SSHD, Windows 10 Education
visit http://moisescardona.video

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

Interesting, just used PD13 after installing this latest patch and I'm still seeing, or rather NOT seeing buttons!
Ummmm, might be this hurricane force wind that's been blowing for the past week !!!
Cheers all I just want to edit and make pictures, walk my dog and go fishing.

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. Jean-Paul

i7-4770K 3.50 GHz, Nvidia GTX 960 2 Go, SSD 500 Go, RAM 32 Go
Win 10 64 bits, DirectorSuite 365

Quote: Yes, Jeff

For this test, I am using 347.09 nvidia driver.

Thanks for confirmation that you used 347.09 driver and the simple test didn't have the issue.

Quote: Right now, I think that PD13 is the only software that does 2K and 4K encoding with hardware acceleration. Of course, only with nvidia "Kepler" or "Maxwell" video cards.


PS: I am still puzzled how it does it on Kepler

Not sure why the puzzle on Kepler, to my knowledge it has always been supported since initial 2012 release, see attached pic from Nvidia for high level features. It supported 4096x4096 encoding when released, in fact, CL actually had a beta version of MediaEspresso that demonstrated NVENC on Kepler's debut but was never released to the public. To my knowledge these were not released at the time because Nvidia wanted license fees to use NVENC encoder vs CUDA, hence no traction for consumer application. Several revs of SDK later Nvidia dropped that requirement. Currently other COTS products also support encoding and capturing 2k/4k with NVENC.

Quote: That's try. That's why I like PowerDirector. Yet, it would be nice if they somehow figure how to do Hardware HEVC encoding maybe using OpenCL, because HEVC rendering is a lot slower than H264 using CPU only.

The Maxwell 2 generation does support H.265 encoding, just time for CL to support perhaps. Nvidia SDK5 with H.265 encode support was released with 347.09 driver. Personally, I think H.265 real usability for end consumer is maybe at least 1+ years out yet. Lots needs to transpire before being real practical, the compression and decompression algorithms are very processor intensive. Even with this high processor cost, the encode savings really has not lived up to full potential yet, still work to be done but progressing. Low end systems (cell phones,tablets...) won't handle it yet, too big of a processing load. With time maybe, about then a new format will be the talk of the town. Who knows, others are knocking at the door too with Google/Youtube behind VP9 and now VP10 development all with the same H.265 goal of lower bitrate high quality video stream capability.

Jeff

Jeff, thanks for clarifying my confusion. I was typing h264 and thinking about h265... Duh, I was doing h264 even with my Fermi card (CUDA, not NVENC). Getting old I guess.

And you absolutely right about h265 vs VP9 situation - the jury is not out yet

Hi,

I found an issue with the Real-time and Non-Real-Time playback feature. Both options works, but if I close PowerDirector, and then I launch it again, being in non-real-time it behaves like if the Real-Time playback has been switched back and it will start skipping the timeline and moving forward until I switch the real-time setting back to real-time and then switch it back to non-real-time. I have the Live version so I cannot test beta patches, but it would be nice if PowerDirector did release beta patches for the Live version. Main Machine: Jetway NF9G-QM77, Intel i7-3610QM, Nvidia Geforce GTX 1060 3GB, 128gb SSD, Windows 10 Pro
Secondary Machine: Lenovo Y510p, Intel i7-4700MQ 2.4Ghz, 2x nVidia GT750M, 500GB SSHD, Windows 10 Education
visit http://moisescardona.video

Hi Dafydd, another positive outcome of this patch is that it seems to have resolved an issue of slow loading and opening of projects that I was experiencing with 2408. Seeking wisdom - finding fluff - but wise fluff!