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 >
Quote PDuser97031B, I maintain what I posted earlier. The behaviour of freeform keyframes in Motion Designer is the same in PDR 17, 16 & 15. Cheers - Tony


I take your word for it. Which makes the subject of this post misleading. Either I went from PD14 to PD17, or I didn't use freeform in PD15. Mea culpa.

In any case, the problem still exists -- in freeform, changing the size of any selection affects the aspect ratio of all the other keyframes. This makes freeform useless. If they don't want to fix the problem, they should just remove the freeform option. But I see how freeform could be useful/desirable.

Later...
Ticket ID: CS002004806
Related Product: PowerDirector
Subject: Magic Motion not working as in PD15 2019/03/28 12:05
I have done steps 1-5 as requested. The problem shown in the video I provided still persists.
Attached are requested documents 1 & 2.
Please please please read the forum thread I previously provided to understand that this issue has been confirmed by at least two Senior Contributors, and fails on multiple machines (the problem is not on my computer). One of the Senior Contributors said that my video does a good job of demonstrating the problem.
I think it's time to raise this ticket to second level support.
Attachments: DxDiag.txt, PD17About.JPG
Subject: Magic Motion not working as in PD15 2019/03/26 16:02
Subject: Magic Motion not working as in PD15 2019/03/24 15:18
I give up. This is why the over dozen trouble tickets I've opened have never come to fruition. Also why the about 2 dozen productivity/user improvements I've suggested over the years have never been implemented. Cyberlink is only interested in selling new product, not supporing their user base.

Ticket ID: CS002004806Related Product: PowerDirectorYou have one reply from the CyberLink Customer Support Team, at 2019/03/27 15:44Subject: Magic Motion not working as in PD152019/03/26 16:02

The video you requested to detail this issue has been posted at...
https://www.dropbox.com/s/xo8hzby5o2v6adm/panzoomtest1_1.mp4?dl=0

Again, the issue is further detailed in this forum thread...
https://forum.cyberlink.com/forum/posts/list/78859.page

Why did you ask me for further information, and then close this ticket as resolved?

=================================================

Customer Support Response2019/03/27 15:44

Dear Roy,
Thank you for your reply.
In reference to your concern, please apply the following steps below and try to play again:
1. Check the minimum system requirements.
Make sure your system meets the minimum requirements for PowerDirector 17. Kindly check the link below:
https://www.cyberlink.com/support/product-faq-content.do?id=23374
2. Ensure your CyberLink PowerDirector 17 is up-to-date.
You can check software updates from here:
https://www.cyberlink.com/support/powerdirector-video-editing-software/patches_en_US.html
3. Update graphic card driver to the latest.
You can download latest driver from AMD / NVIDIA / Intel’s web site. If you have any problem with installing graphics card drivers, please contact your computer manufacturer or the manufacturer of the display and sound cards for latest drivers.
AMD: http://support.amd.com/en-us/download
NVIDIA: http://www.nvidia.com/Download/index.aspx
Intel’s website: https://downloadcenter.intel.com/
4. Check whether the installed drive has enough space on it. This is because large amount of memory space is required for buffering.
5. Run PowerDirector 17 while no other applications are running.
To maximize the available RAM and reduce the chance that another application conflicts with the application, close all open applications (including virus-protection utilities). Then restart your CyberLink program.
If your concerns still persist, kindly provide the following information below for us to analyze and diagnose your concern in a better manner:
1. DxDiag
To create the DxDiag.txt log file please follow the steps below:
1.1.Press the Windows key and type dxdiag in the search box.
1.2.Click on Dxdiag.exe.
1.3.You will see a green progress bar in the bottom-left of the DirectX Diagnostic Tool window while the program is gathering information.
1.4.When the progress bar disappears, it means your report is ready.
1.5.Click Save All Information.
1.6.Save the file to your desktop (make sure it is saving as a text file) and give it a name you will remember.
2. Full screenshot of the Product Version / SR Number
To get the Product version please follow the steps below
2.1. Launch CyberLink PowerDirector 17 software.
2.2. Click Logo of the software or the word of the software to see the Product Version.
Full screenshot
To take a full screenshot:
1. Press PrtScrn on the upper right side of the keyboard when you see the error message
2. Click on Start > Programs > Accessories > Paint or press Windows button, type the word Paint then click on the result to open the program.
3. Paste the screenshot (press Ctrl+V), then save the file in .jpg format.
Please feel free to contact us back for further clarification or assistance related to CyberLink Products. Use the link below to get back to us:
https://membership.cyberlink.com/support/service/technical-support.do
Thanks and Regards,
Julius
CyberLink Technical Support
Ticket ID: CS002004806
Related Product: PowerDirector
Subject: Magic Motion not working as in PD15
2019/03/26 16:02

The video you requested to detail this issue has been posted at...
https://www.dropbox.com/s/xo8hzby5o2v6adm/panzoomtest1_1.mp4?dl=0

Again, the issue is further detailed in this forum thread...
https://forum.cyberlink.com/forum/posts/list/78859.page

Why did you ask me for further information, and then close this ticket as resolved?
I will follow up on this request from support...


Customer Support Response 2019/03/26 11:03
Dear Roy,
Thank you for contacting CyberLink Technical Support.
If we understand you correctly, you have concerns using the freeform with keyframes in Magic Motion.
We may have to get more details so we can identify your concern accurately and assist you further.
Kindly describe your query more clearly. Please list down the steps you did and provide the following:
Video Capture showing the concern:
1. On your PowerDirector, go to the Capture tab.
2. Select Capture from screen (PC with red dot icon).
3. Click Record, then reproduce the concern.
You may upload the video using DropBox or GoogleDrive then provide the shareable link to us.
Please feel free to contact us back for further clarification or assistance related to CyberLink Products. Use the link below to get back to us:
https://membership.cyberlink.com/support/service/technical-support.do
Thanks and Regards,
Julius
CyberLink Technical Support
Thanks for everybody's help in investigating this issue. I guess it turns out I've never used freeform since before PD15 embarassed. That being said, would it be possible for the senior contributors to nudge Cyberlink to get freeform working properly going forward? I can see it being a useful capability. I doubt if the "ticket" I posted above will go anywhere based on my experience submitting previous "tickets". Perhaps the senior contributers could provide support that this needs to be corrected.

Thanks!
I just spent quite a while trying to find a work-around to this problem. Tried shift/ctrl/alt key combinations, changing a keyframe to freeform when other keyframes are locked aspect ratio, presets other than "User Defined", etc., etc. No luck. Changing any freeform keyframe changes all others in proportion. Once it actually worked properly until I added a 3rd keyframe, then fell apart.

I also tried the PIP work-around suggested. I could not find a way to even come close to the things you can do in Magic Motion Pan & Zoom, so that will not work for me.

This is really a mystery. For me it started with PD17, but others say it's always been this way. This has not been my experience. In any case, it's unusable functionality at the present time. I miss it.

P.S. In the Magic Motion Designer if you press the "?" at the top of the dialog and choose "Magic Motion tutorial" you get a video done on PD7, which is completely obsolete from the way this dialog now works.
Quote It does seem that the aspect ratio was maintained as the rabbit is not distorted while panning and zooming.


Yes, once the keyframe selected area is set, it stays that way for that keyframe. If go to another keyframe with different freeform aspect ratio, then PD automatically adjusts between keyframes. Perhaps this wasn't a good example as the keyframes appear to be 4x3 (but actually aren't).
Here's an example of my use of pan/zoom using PD15.
https://youtu.be/_djbPBYzHG0?t=1663
Quote er - re: Magic Motion not working as in PD15 PDR15 does exactly the same thing using freeform in Magic Motion. surprised Keyframes get reset for no obvious reason.


Hmmmm. Something else is going on. I never had that problem on PD15, and did gobs of pan/zooms. I'll find a small clip and upload it as an example.
Ticket ID: CS002004806
Related Product: PowerDirector
Subject: Magic Motion not working as in PD15
2019/03/24 15:18

On PD17-2514.2, when using "freeform" with keyframes in Magic Motion, changes to the size/shape of selection area on any keyframe causes all the other keyframes to change proportionally. This problem is more fully described in this forum posting:
https://forum.cyberlink.com/forum/posts/list/78859.page

Apparently this behavior is also exhibited in PD16. Other users have confirmed this issue on their own systems, and agree that it is not the correct/expected behavior. In fact it makes using "freeform" useless. Freeform is the main reason for even using pan/zoom in Magic Motion.

There is no logical reason for other keyframes to change, and the behavior of keyframe editing needs to be restored back to the way it was prior to PD16.
I'm going to report this as a bug via problem reporting (which rarely has worked in the past and usually results in support wanting me to waste time on trying a bunch of irrelevant things in denial of there being a problem). But it's the best I as a user can do to get the issue rectified (back to the way it worked before).

In the meantime I'll try using the PIP tools work-around, but it sounds more labor intensive with inferior results (e.g. no path smoothing).

Thanks for your replies. At least now I know it's not a user error.

:o)
Quote It hasn't changed from PDR16, as far as I can see. I barely ever use freeform Pan & Zoom/Magic Motion so I've never even noticed that the initial keyframes reset themselves like that. The same thing happens in PDR16 when using freeform.


Hmmm. I went from 15 to 17 so can't confirm this behavior in 16. When I'm doing Pan/Zoom I really don't want a fixed aspect ratio, I'm doing it with freeform to get the best effects (like panning across a portion of an image), or moving in and out on parts of an image (samples provided upon request). Basically I'm turning an image into a video. Being forced to use a fixed aspect ratio would severely limit my purposes for using pan/zoom. Do you really think that the 16/17 behavior is the way it should be for this function? What would be the reasoning behind it?
I have been using PD since about version 7, and have created dozens of videos with magic motion pan and zoom in them. All of sudden since update 17-2514.2 magic motion has changed. Go into Magic Motion on an image -- select User Defined icon. Make sure "freeform" is selected. Create a keyframe about halfway down the clip. Make this keyframe duplicate the first keyframe at the beginning of the image, which is the entire image selected. Then create a keyframe a little farther along. Modify this keyframe to zoom in on the image. Select previous keyframe and bang, both the previous keyframe, and the initial one have changed, but not the same as the last zoomed in keyframe. Fails whether the last keyframe is duplicated or added. In previous versions the previous keyframes were left "as is". Now, a changed to any keyframe results in a proportional change to every other keyframe!

What the?
Often when I upgrade PowerDirector I loose my custom video profiles (and sometimes custom titles, etc). I just upgraded to 17.02514.2 from a previous version of PD17, and my custom video rendering profiles are all gone. Somebody posted here once how I could retrieve them. What was the trick again! Where are the old ones located?

Thanks!
It was an upgrade package and I was given the option to uninstall PD15 or not, with the recommendation to do so. Normally I don't uninstall last version, but it's been a while since upgrading. I didn't know that uninstall last version would not transfer over the user created custom assets to the new version. Yes, you can say it's "pilot error", but why make things difficult for the pilot? Autopilot should work seamlessly for the user. I'm sure this will be my last upgrade of Power Director, so not concerned going forward. Thanks for your thoughts.
Quote The first part of my answer is for restoring all the custom rendering profiles from PD15 to the newly installed PD17. It works if PD15 is still installed so you don’t have to create them again in PD17. The second part of my answer is for those installing a full version of PD17 in which some refers to as an upgrade, but they installed a full version and not an upgrade version. This leaves PD15 intact. PD17 is then able to have all the custom titles, transitions, particles, PiP objects available because it finds them in the PD15 custom folders. It does not create a duplicate of them at all for use in PD17. Those who purchase the Ultimate full versions get to be able to continue using the previous NewBlue premium packs on PD15 itself which can be quite expensive if purchased separately. That is one of the reason for individuals to leave the old versions installed. Buying an upgrade version of PD17 instead of a full version of PD17 say at the end of the year to save $10 is a false economy. You have to do all the custom work again and lose the use of those expensive NewBlue packs. Hope this help someone and clarify whether saving a few dollars now is worth it. P.S. As optodata has indicated those who do backups can restore all those created custom assets from PD15 to the proper PD17 folders upgrade version. All those custom assets will then be available for use in PD17.


What's the logic behind having two different installation methods depending on product purchased? I think most people think an upgrade is an "upgrade" (not replacement). I wish I had know this before installing, as I simply could have said "No" when the install process said -- Please uninstall PD15 -- do you want to do that now? 20-20 hindsight. As previously stated -- be prepared for a love/hate relationship when working with Cyberlink. )o:
Quote I'm sorry your custom content isn't being picked up by PD17. I've never had problems maintaing when updating since PD11 (unless I had to do a full Windows reinstall without a backup), but I know other people have had difficulty. In addition to what tomasc posted, there are other threads dealing with custom content, with this post describing some of the recovery/transfer options, and this one detailing the various folder locations where items are stored.


Thanks for the info!
Quote You have to create the custom profiles in each new version of PD. There is an easy way to do this. If you just installed PD17 then the Profile.ini in PD17 is empty. You can then copy the Profile.ini from the PD15 folder to the PD17 one and overwrite it. You will then have all those custom profiles available from PD15 in PD17. The PD15 Profile,ini is at this location: C:\Users\UserName\AppData\Roaming\CyberLink\PowerDirector\15.0\UserConfigure\Profile.ini . I buy full versions instead of upgrade versions like many others for a reason. I believe all the custom titles and transitions created in PD15 should be in PD17 assuming that you let the PD17 upgrade uninstall the previous version. Mine are all there. If you uninstall PD15 first by yourself then there is no way PD17 can have all the stuff from PD15 transferred over because you already removed it yourself instead of allowing PD17 to do the job correctly.


Thanks for the information. I allowed the upgrade to do what it wanted, which was to uninstall PD15 on-the-fly during the PD17 install. It did not copy/merge any of my previous custom stuff. This has been my experience with every upgrade of PD. Not sure the logic behind this, as all other software does a real upgrade (doesn't loose what you already had) vs a "replace". The latter resulting in the "hacking" of files to get back to where you were. Thanks for reminding me what to do. P.S. The profiles.ini fix doesn't put back the custom texts and other custom components you've made.
This is why we long time users have a love/hate relationhip with PD...

I upgraded from PDF 15 to 17 and lost all my custom rendering profiles, texts, transitions, etc. This is an issue going back to at least PD 7. With every upgrade I have to ask how to get them back again, and then spend time doing it.

So what's the secret this time?
I have a cell phone video of a band playing number. The hand-held camera was moved around a little during the piece. The piano players face is hidden by an object. I want to put a PIP of the piano players face in the video, which is working fine. However as the background moves around a little, the face becomes in the wrong place.

Is there a way to do some kind of motion tracking on a PIP so that I can nudge the face around to keep it at the piano during the 2.5 minute piece. Something like the way Magic Motion works on a still image?

Thanks for whatever you can suggest.
Go to:   
Powered by JForum 2.1.8 © JForum Team