Tere - Have a look at http://forum.cyberlink.com/forum/posts/list/0/40269.page#224654
First Video - PDR13 What's New - There is quite a lot - which is why I upgraded.

I agree with your comments. PDR12 is not an option. What about all the users who bought 13 and don't have 12?? Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer

Flickering still exists to know, with beta Patch 2808, when HW Videodecoding is on. I think this issue wouldn't be fixed anymore in PD13.

Thanks blasiusxx
I have reinstalled PDR12 and will try a comparison to 13. I was afraid to install Beta patches. Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer

Now i tried tu use PD13 with Intel Quick Sync. And now there are no more issues with Hardware Videodecoding and Encoding.

Without Hardware Decoding the speed is very slow, when you works in the timeline. It hangs all the time. Also, i need HW Decoding by creating the movie in the timeline.

There is 100% an incompatibility between geforces maxwell nvenc support and PD13.

The Encoded Videos in AVCHD all flickers.

But There are more issues when you activate Hardware En Coding. The Result is, the Produced BD Movies have issues with chapters and faster/slower forward.

With Intel Quick Sync HW there are no more problems.

Quote: Thanks blasiusxx A
I have reinstalled PDR12 and will try a comparison to 13. I was afraid to install Beta patches.

AlS Don't be afraid of PD's beta patches. If you install one but decide you want to go back to an older version, all you need to do is run the older patch and PD will be "updated" (actually, restored) to that version. No need to uninstall/reinstall the whole program

Quote: ...

There is 100% an incompatibility between geforces maxwell nvenc support and PD13.

blasiusxx - did you see this sticky *post*?

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Yes, i know it. But i have a gtx970. And there are only newer Drivers with ONLY NVENC Support, no more CUDA.

The Hardware Decoding and Encoding in PD13 works, but with many issues by Producing BD Movies or AVCHD H. 264 Streams. I heard, with H. 265 producing there are no issues.

But that is another point. I need HW Decoding without Issues, to work smooth in the timeline.

I understand. This thread is so long I didn't realize you had such a new card!

Have you tried editing the project with your 970, then disabling it when you produce? I know that doesn't really address the issue but it would give you full speed and performance when you're editing and you would then get the flicker-free result when you produce.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Yes, it works. You see only the issues in the Preview Handler. But sometimes i forget to deactivate hw Decoding by Producing.

I think HW Decoding is only used when editing (for playback/preview) and it shouldn't have any effect when Producing.

I think the hard part would be to remember to disable the 970 so only the Intel GPU is active when you produce. Hopefully Cyberlink is aware of the issue now and can come up with a fix...

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I also thought, BUT NO, the Hardware DECODING during editing causes the Flickering, not the Encoding finally when you Burn a BD Disc/Folder. I have tested it many times.

The Encoding causes other issues in the final Video, like problems with fast/forward or play next chapter. The Video hangs in a bootloop and could only play at the beginning with normal speed.

Tested it with PC Playback PowerDVD14, Original BD Disk in the Hardware Player and with my Mede8er from my NAS.


I didn't have much hope, that this bug be fixed in this version PD13. It exists since the Publication of the Maxwell Geforces, and this is more than a half Year ago. I use now Intel Quick Sync.

But it isn't a simple solution, i had to work with two gpu's on one PC and one Display. Once GPU for Video Editing, and once for Gaming. I must always switch the Display to activate the other GPU, because PD13 and many other Software only recognizes activated GPU/Displays.

I had no multi monitoring. My ASUS MX279H has two HDMI.

When i switch to another HDMI/GPU, there are sometimes Display Errors or Audio Issues. But this is another thing.

It does sound complicated. It may help to formally submit this issue to tech support. Providing them with the samples and your DxDiag would be the best hope of getting them to understand and fix the issue.

My apologies if you have already done so!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I had done it months ago. With detailed description. But nothing happens to know.

There's a new beta available now, v2828. It doesn't say that it addresses this issue - but you'll never know unless you try

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I try the Patch since yesterday. Nothing changes.

Thanks for your ideas.

blasiusxx - I'd like to investigate your issue further. Your problem is different enough from the originator of this discussion that I think you should start a new thread. Would you be able to do that, and attach samples of your original media and what happens when you produce with PD13?

I'm afraid it would need to be in this English language forum - mein Deutsch ist nicht sehr gut

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Quote: AlS Don't be afraid of PD's beta patches. If you install one but decide you want to go back to an older version, all you need to do is run the older patch and PD will be "updated" (actually, restored) to that version. No need to uninstall/reinstall the whole program

Wannabe beta testers, I'd be very careful with the statement above. It's not true.

Beta testing and patches are typically not for the light hearted that like to keep a working system. It's great if all the patches are stable, BUT, you cannot go back to a previous version as simply suggested in the above statement.

For example:
After 2725 beta is installed one still has a 4/1/2014 version of MonitorDetect.dll(212,992 bytes) as shown in pic 2725_original
After 2808 beta is installed one now has a 3/31/2015 version of MonitorDetect.dll(217,088 bytes) as shown in pic 2808_original
If one has issues with 2808 beta and decides to simply reinstall 2725 beta release to recover, you maintain the 3/31/2015 version of MonitorDetect.dll(217,088 bytes) as it was not part of the 2725 beta package so it's not updated. this is shown in pic 2725_after_2808_orig

This makes sense, there is no version control in these beta updates. If new dll's are introduced between beta versions that are not common between the two beta versions, you end up with the most recent version of the dll installed when you downgrade to a different beta release. Yes, of course the about box will echo a version of the last patch operations leading you to think you have a given version, there simply is no version control to enforce that. What you end up with is a halfbreed install, a little of 2808 and a little of 2725. Not an ideal situation for many of the computer challenged.

Will it cause issues, depends on the severity of the issues in the beta releases.

Many options to recover, user system images, user backup files, full install again, system restore not one of them though.

Jeff

Jeff, thanks for catching that. I was relying on the version number of the main program (the executable file), and didn't think about DLLs and how they wouldn't necessarily be updated or restored when an earlier patch was run.

You can get everything in sync again if you reinstall the original program (over the current version) and then update with the desired patch, but that's not as simple as what I described.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I never installed beta patches before. But with this issues you give it a try to install any patch, don't you ?!

But this thread is not a question, if i should install Beta Patches.

opdata, thank you very much for your help.

I test today several things with PD13 and AMD/Intel/Nvidia GPU. Then i decide to open a new Thread. But i Think it's pointless.

It is unlikely, because who knows what causes this issues ?! It's the Geforce Driver or the PD13 Software ?!

The Issue exists since publication of the maxwells. Since "NVENC".

PD13 Supports Cuda (to Geforce 340.xx with older Cards) and Nvenc with the newest Cards/Drivers at the same time. I think thats the great problem, and causes incompatibilities like this issues.

Before the GTX970 i had a Notebook with GTX780M. And there were issues, too. Not the same, but others that made me very angry. With Hardware Decoding and Encoding. Something always didn't work with the Nvidias before, in my cases.

With the Intel HD Graphics at the Moment it runs very smoothly. I will test today an AMD Graphic Card, and dedcided then if i renounce of Nvidia Graphics.

If AMD causes more problems, i leave everything at it is.

I tested Nero Recode 15 and have issues, too, with the Geforce Hardware Coding. It supports Intel, too. And runs smooth.

Opdata, here's the Thread i posted this issue 6 Months ago.

http://forum.cyberlink.com/forum/posts/list/41983.page;jsessionid=D24835B0322B5B0DD988C76D8B127FBD#216305

Thank you blasiusxx. Could you attach or post on YouTube what the problem videos looks like? You have already done lots of work to try and fix the issue, and maybe the AMD card will work better for you.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

blasiusxx, I wonder if you could try these 3 steps and see if the problems disappears:

1. Reinstall the latest nVidia driver, but choose Custom and ONLY select the Graphics Driver. Uncheck all other items and check the Perform a clean installation box. Restart the computer when prompted.


2. Right-click on an open area of the desktop, and open NVIDIA Control Panel


3. Click on Manage 3D settings, and change the Power management mode to Prefer maximum performance from the Global Settings tab

Run PD13 again and see if the problem has changed or gone away.

If it has not changed, you can try to disable the CUDA in your GTX970 by going back the NVIDIA Control Panel and unchecking the box for CUDA - GPUs. This should greatly slow down your producing and PD may not even work, but it would be interesting to see what happens.

Please restore the CUDA settings after the test!

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°