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 >
new Bug in PipDesigner in powerDirector 15
BetoValle [Avatar]
Newbie Joined: Nov 15, 2013 11:27 Messages: 35 Offline
[Post New]
As I have not migrated to version 17 yet and won the 30 days of the trial version, it is very likely that the bug will also occur in this version:

intthis link you download the project to evaluate if it is
also occurring in version 17. ( in the PipDesignerjpg file has detail image bug )

The project is very simple and, when creating the zoom "out" effect, the image becomes large, and thereafter memory overflow occurs.

If they confirm the bug I ask the kindness
to report a ticket to support

thanks!
 Filename
BugPowerDirector.zip
[Disk]
 Description
 Filesize
357 Kbytes
 Downloaded:
288 time(s)
optodata
Senior Contributor Location: California, USA Joined: Sep 16, 2011 16:04 Messages: 8630 Offline
[Post New]
Quote in this link you download the project to evaluate if it is also occurring in version 17. ( in the PipDesignerjpg file has detail image bug )

The project is very simple and, when creating the zoom "out" effect, the image becomes large, and thereafter memory overflow occurs.

If they confirm the bug I ask the kindness to report a ticket to support

thanks!

Hi BetoValle. Thank you for sharing the project and the jpeg showing the problem on your machine.

I have opened your project in PD17 and I have no problems. The limits on X and Y in the PiP Designer are -2 and +2, and if I set them to anything outside of that range PD automatically sets them to +/-2. Same with the Scale, the maximum allowed is 6. Here is a video of the tests I made:



I'm not sure why PD15 is using so much memory on your computer. If you want help with that, please look at the Read Me Before Posting thread on the PD17 forum index page and follow the instructions for running the DxDiag test. Also, please tell us the exact version of PD15 you have.

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°
BetoValle [Avatar]
Newbie Joined: Nov 15, 2013 11:27 Messages: 35 Offline
[Post New]
Thanks optodata

The bug is in pd15 with last patch 3929 and by its test in pdr 17 I saw that there was no memory overflow
according to the used memory displayed in your manager task .

No need to report support because the situation has normalized on pdr 17.
Powered by JForum 2.1.8 © JForum Team