Follow:

These tutorials are on Powerdirector 7, principle applies to PD8,9
http://www.youtube.com/watch?v=sY6w3BrPERI

CyberLink PowerDirector 7 - Using Keyframes
http://www.youtube.com/watch?v=K5jd9tCiInI

Good luck! Carl312: Windows 10 64-bit 8 GB RAM,AMD Phenom II X4 965 3.4 GHz,ATI Radeon HD 5770 1GB,240GB SSD,two 1TB HDs.

Hi Barry,

Yeah, I noticed that too. It seems to have started with build 2702 (for me anyway).

Sometimes when going back into PIP Designer, to re-adjust (say a circle following a moving object), or modifying any kind of overlay motion with the Key Frames, it’s like the base video that one is trying to highlight or match, freezes and won’t advance or play. Yet the PIP overlay that one is attempting to apply on top of the base video, does indeed advance properly. This doesn’t happen all the time, but randomly enough to be irritating.

And as you say (or intimated), PIP motion is now basically useless, if you can’t match the PIP motion to he base video’s motion, as the base video now occasionally stays stuck on it’s first frame, even though you are advancing the scrubber manually, or with the advance buttons.

There may be a better workaround yet to be discovered. But I’ve found that simply closing and re-opening PIP designer, sometimes un-sticks the base video display in PIP Designer, but not always. Then I just re-boot my computer, and things get back to normal, and PIP Designer once again continues to work as it is supposed to, and always has. (There was a similar problem in PD7 at one time, if I recall correctly).

Perhaps it’s all somehow related to that unwanted auto disabling of tracks thing that is happening now (as has been mentioned in other threads). Where, instead of fully disabling a track, upon re-entering to modify Key Frame settings and the object’s position in PIP Designer, it somehow just freezes the base video (in lieu of fully disabling it).

Either way, it’s just another one of PD9’s new charming little quirks I guess, that hopefully will be repaired soon.
Perhaps Dafydd will give this anomaly an item number, and forward it to CL?


Click here PDtoots for a collection of PowerDirector Tutorials and Tips

Hi Barry,

This is interesting. Did Cranston restate the problem correctly? His experience certainly states something that should be corrected, but I just wanted to confirm that yours is the same before I start trying to replicate it.

Pax Laptop PC, ASUS
Core i7 Q 720
Win 7, 64-bit
RAM 8GB DDR2
Graphics, NVIDIA GeForce GTS 360M 1GB DDR5

As usual, Kranks is spot on, now if you will excuse me, I must re-enable my tracks, bye. HP Envy Phoenix/4thGen i7-4770(4@3.4GHz~turbo>3.9)
Nvidia GTX 960(4GB)/16GB DDR3/
Canon Vixia HV30/HF-M40/HF-M41/HF-G20/Olympus E-PL5.
Tape capture using 6 VCR, TBC-1000, Elite BVP4+, Sony D8 camcorder with TBC.
https://www.facebook.com/BarryAFTT

As a side note:
This anomaly seems more prevalent (or dependent on), what the base video’s format is.
On my rig, it’s the Avi and Dvix formats that (I think) seem most prone to this PIP Designer base video freeze (or not advancing), when doing motion layering in PD9’s PIP Designer.
But I can’t say this with complete certainty, as I haven’t engaged in any extensive testing to try to methodically zero in on whether or not the anomaly appears to be format dependent or not.


Click here PDtoots for a collection of PowerDirector Tutorials and Tips

Hi guys,

the quirks of PIP Designer in 2702 was one of the reasons I (and at least one other I know of)
had to roll back to 2330. It became too frustrating to go back and forth, close and reopen several
times to see if "this is the moment it'll work". Also, the quirks included; what you thought was finally
a success in PIP- but back in timeline it was something else. Didn't matter if you had a 5sec clip or
15sec clip, graphic or text. (I mostly edit mp4's 1280*720, 30fps. 2702 was not suitable for mts 1920*1080
files at all on my rig, 2330 copes acceptable)

This anomaly might have already been given a report number (?).
Since beta is long gone over, I (and at least one other I know of) just dropped the 2702 all together
and rolled back. Now I can actually get some things done.
You could have speculated; 64bit - thing?
Now we know the quirk excists in 32bit also, at least in 2702.

Chin up Barry! Re-enable!

Nina



Just something.
https://www.petitpoisvideo.com