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 >
PIP Objects Strange things going on
ynotfish
Senior Contributor Location: N.S.W. Australia Joined: May 08, 2009 02:06 Messages: 9977 Offline
[Post New]
Hi Bill -

That's OK. We all do that from time to time, me included.

Anyway - it appears we are looking at two separate issues so it may be best if we open a new topic for this one. Done http://forum.cyberlink.com/forum/posts/list/0/21805.page#116361

Mark's problem (well - it's PD10's problem, really!) is that modifying opacity keyframes in the keyframes settings window causes the motion path to be distorted.



Doing the same thing in PiP Designer causes no change to the shape of the motion path.

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog
PDtoots happily supports fellow PowerDirector users!
wh7262
Member Location: Carrollton, TX Joined: Apr 25, 2011 10:07 Messages: 96 Offline
[Post New]
Sorry Guys,

I had read over or did not catch that word while reading the word "OPACITY". Yes, I did duplicate this in both the NTSC (30 frame) and PAL (25 frame) settings.

When in the Keyframe Setting - Clip Attributes and one changes the OPACITY level at any point other than the starting point of the circular motion path, one will get a really weird motion path. If one even adds a Keyframe, still same results.

Yes, Cyberlink PowerDirector programers really need to fix this issue.

I am off of this topic, now waiting on CLPD for fix and update.

Bill
Thanks,
Bill in Texas

PD-12, PD-14 and PD15 is installed on this iMAC computer under BootCamp, and PD's are running great:
DxDiag Info:
System Information
------------------
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 Language: English (Regional Setting: English)
System Manufacturer: Apple Inc.
System Model: iMac11,2
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 4022MB RAM
Page File: 2031MB used, 6010MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

PD-12 PowerDirector Ultra: 12.0.3403.0

PD-14 PowerDirector Ultra: 14.0.1728.0
SR numbers: VDE14

PD-15 Power Director Ultra
15.0.1725.0
wh7262
Member Location: Carrollton, TX Joined: Apr 25, 2011 10:07 Messages: 96 Offline
[Post New]
Well, I found another with the Keyframes setting under the Clip Attributes in the Rotation entry. Notice in the example below is the 8 frames results of a circular motion created in PIP Designer, no need to use all of the frames to get the point across to CL PD10 designers and us as well.
Here is what I found, the Rotation at the beginning frame has -0.6 Rotation, that is OK, but what is NOT OK, IS IF ONE CHANGES THIS TO ANY DECIMAL NUMBER, LIKE 0.534, IT WILL CHANGE TO 534 NOT .534 .
The Center Position for both X and Y are OK with changing their numbers.

So this leads me to believe that the KEYFRAME issue lies here in PD10 inability to recognize an entry less than whole numbers, like 4, 10, 189 and etc. If one enters 0.870 the results will be 870. This totally screws up the Motion Path. What do you think? Can this some how reach the people that needs this information?

Center Center
Position Position
Frame Rotation X Y

00:00:00;00 -0.6 0.230 0.497
00:00:00;01 0.0 0.231 0.493
00:00:00;02 0.5 0.231 0.489
00:00:00;03 1.0 0.232 0.485
00:00:00;04 1.6 0.232 0.481
00:00:00;05 2.1 0.233 0.477
00:00:00;06 2.6 0.233 0.473
00:00:00;07 3.2 0.234 0.469
00:00:00;08 3.7 0.234 0.465


Bill Thanks,
Bill in Texas

PD-12, PD-14 and PD15 is installed on this iMAC computer under BootCamp, and PD's are running great:
DxDiag Info:
System Information
------------------
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 Language: English (Regional Setting: English)
System Manufacturer: Apple Inc.
System Model: iMac11,2
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 4022MB RAM
Page File: 2031MB used, 6010MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

PD-12 PowerDirector Ultra: 12.0.3403.0

PD-14 PowerDirector Ultra: 14.0.1728.0
SR numbers: VDE14

PD-15 Power Director Ultra
15.0.1725.0
wh7262
Member Location: Carrollton, TX Joined: Apr 25, 2011 10:07 Messages: 96 Offline
[Post New]
The more I dig into PD10 and it's Motion Path w/Keyframes issues, the more I have found the issue to be in the design of the Motion Path itself. If the Motion Path, that was created in the PiP Designer, was either "curved", "waves", or "circular" in their motion path, then problems will occur. When one goes into the Keyframes settings and tries to add, remove a Keyframe, to change the Opacity levels, to change the H scale or the W scales values, then the Motion's path is DEFINIETLY distorted.

If the Motion path, made in PiP designer, were straight, angled, horizontal or vertical, rectangular, square or even partially forms a box then any changes made in the Keyframes setting DOES NOT EFFECT and I repeat DOES NOT EFFECT the Motion Paths does not distort it either.

I tested these theories out today, as I picked nearly everyone of the Motion Paths , in the PiP Designer room, and made those changes to each one. The results are shown here:
http://www.youtube.com/watch?v=LSdYR_tDefI

Be sure to watch these videos at my YT site. Also there are several other videos that I posted as well.

http://www.youtube.com/watch?v=LSdYR_tDefI
http://www.youtube.com/watch?v=2k73E_QmWwg
http://www.youtube.com/watch?v=TbhxexQYIqw

Also thought it was the way I Produced the file as a WMV
http://www.youtube.com/watch?v=Lrt_ZhxQTN8
or the MPEG-2 format

Because when I produced it in Sony Vegas Pro 10 it was OK.
http://www.youtube.com/watch?v=vxUGE5RiZSg
http://www.youtube.com/watch?v=lDjeC3GrPnM
http://www.youtube.com/watch?v=tNGQqrl-jUo
http://www.youtube.com/watch?v=pGRowv0Tl7o
http://www.youtube.com/watch?v=mXKRN0VIw3I
http://www.youtube.com/watch?v=jy3NxJckJEE
http://www.youtube.com/watch?v=TbhxexQYIqw

This all of my videos so far that I have posted to help get this issue resolved. Thanks,
Bill in Texas

PD-12, PD-14 and PD15 is installed on this iMAC computer under BootCamp, and PD's are running great:
DxDiag Info:
System Information
------------------
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 Language: English (Regional Setting: English)
System Manufacturer: Apple Inc.
System Model: iMac11,2
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3 CPU 550 @ 3.20GHz (4 CPUs), ~3.2GHz
Memory: 4096MB RAM
Available OS Memory: 4022MB RAM
Page File: 2031MB used, 6010MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

PD-12 PowerDirector Ultra: 12.0.3403.0

PD-14 PowerDirector Ultra: 14.0.1728.0
SR numbers: VDE14

PD-15 Power Director Ultra
15.0.1725.0
Powered by JForum 2.1.8 © JForum Team