|
|
Quote
Hi Jonathan -
Try holding down the Alt or Ctrl key while you use the scoll wheel. Works for me 
Cheers - Tony
Ctrl-scroll, okay sure, but Alt-scroll?
Dude, you have no idea how much this blows my mind... 
Just what I needed, thanks!
|
|
|
I was having a similar problem, too. I did not find a resolution, but I did find a work-around.
In my case, I was taking MOV clips (from my ZOOM Q , editing the sound in Audacity, and then trying to reattach it to the original video. They would be different lengths.
What I discovered is that audio that is "produced" by PD will sync. So pop the raw file in, go to the "Produce" menu, and produce it as a WAV file at the highest possible setting (which will, alas, be lower than your ZOOM H1, despite what the salesman told me...). I can then edit it freely and it will sync just fine.
SOmething like that might work for you too.
=======================
Just in case, though, when you first put your files into PD, are you using the "Sync by Audio" feature? Do that at the start with the audio/video from your camera and the audio from your ZOOM H1.
Then, when you make a cut (ex. by using Ctrl-T), make sure it applies to both the video and audio at the same time (Ctrl-click to highlight both). That way you aren't trying to eyeball it based on the less-than-useful waveform that appears in PD. That's going to mess things up for sure.
|
|
|
|
I've recently reinstalled PD 15, and for some reason whenever it launches, it mutes playback. It's annoying that I have to un-mute it each time, but for me it's a simple click on the preview window, or through the Playback menu.
|
|
|
Have I missed something?
I want to scroll side-to-side on the timeline, but the only option I can find is to manipulate the thin scroll bar at the bottom with my mouse cursor. I can scroll up and down with my mousewheel, but tilting on the mousewheel does nothing (that would be the most obvious solution). There's also no keyboard commands that I can find that do this (PgUp and PgDn, or even the arrow keys would make sense here). Did I miss something, or has this really been overlooked?
|
|
|
|
A non-beta patch would be appreciated... I'm still using 2509 from February, and it is terribly unstable. I've owned PD15 for a mere 11 months. It seems that Cyberlink is more interested in taking money for annual upgrades than producing a stable, working product.
|
|
|
Story time:
After several attempts at reinstalling Windows and PowerDirector, I decided to take a plunge and do a reset on Windows where I deleted all apps and all settings.
It is back to normal again.
One of the first things I reinstalled was PowerDirector. When it first booted up, I noticed something that had not been true for a long time: the default images loaded into the media library.
I had disabled that ages ago.
Previously, when I had reinstalled PowerDirector, however, that setting had remained. Somewhere, my preferences were being retained between installations.
Ergo: I believe my preferences files may have become corrupted somehow. It would have saved me a TON of time, however, if I could have reset THOSE instead of reseting all of Windows and all of my applications. Can anyone tell me how that might have been accomplished? Where are PowerDirector's preferences stored?
|
|
|
Quote
Quote
There's a possibility it could be related to this.
Couldn't say for sure, but it would be my best guess.
Cheers - Tony
It's possible, if it were not for the part where I succumbed and did a complete reinstall of PowerDirector...
But thanks for remembering!
PD 15 is still broke. I have done an in-place reinstallation of Windows 10, and yet another fresh install of PD 15. But the program still seizes up every time I attempt to edit a title. Any other suggestions?
|
|
|
Quote
There's a possibility it could be related to this.
Couldn't say for sure, but it would be my best guess.
Cheers - Tony
It's possible, if it were not for the part where I succumbed and did a complete reinstall of PowerDirector...
But thanks for remembering!
|
|
|
Quote
Why don't you try to restore your system to an earlier date and see what happens?
Because there aren't any restore points between today and yesterday? I closed PD, put the computer to sleep, came back the next day, loaded up my project, and PD has not been working since.
|
|
|
Today, as I went to use PD 15, Title Designer simply decided to start crashing on me. It was working fine yesterday.
I have reinstalled PD. I've used three different versions - 2509, 2820, and 3015 beta. And in every case, PD just hangs as soon as I try to edit a title.
Nothing changed on my system. It is still an ancient i5 2nd gen processor, 32 GB of RAM, and a Radeon RX 550 2GB, which was working just fine yesterday on the 2509 build.
What's going on?
|
|
|
Quote
Hi Jonathan & anyone else interested -
I've been kindly reminded about what prompted me to (incorrectly) state that it was "impossible" to roll back to an earlier build of PDR... Ignoring my exaggeration of the facts, it is possible that rolling back in that way (installing a previous patch without uninstalling first) may cause issues:
- compatibility between DLLs & interdependancies, depending on what was modified between update patches
Essentially, you end up with an "inconsistent set of installs" (to quote my guardian angel friend).
Cheers - Tony
I figured that would be the case. Basically, some of the files from the new version, that are NOT overwrittern by the previous version, would remain.
I recommended it as a stop-gap measure while I wait for a hotfix. It lets me continue working without doing a complete reinstallation. At least, without doing a reinstallation right now - there's probably one in my future. Heck, a whole new computer may be in my future.
Also, I created a tech support ticket for this issue. Still haven't heard back from CyberLink, even after five days. That's typical, though - sometimes it takes them two weeks to respond to those. 
|
|
|
Quote
Quote
These worked in the previous version, and the bug has surfaced since updating to 2820. Can I revert back to the previous build so I can get my work done? Otherwise I need an immediate fix - there's videos that need to be produced and released TODAY.
Since you are in hurry, I suggest you to reinstall the old one to workaround it, old version could open your project correctly.
Even hotfix may need couple days at least.
As mentioned above, I was able to install the previous version on top of the latest version. This seems to be working as well as it had before (with all of its numerous bugs). Doing this, I was able to release the video - at 11:30 p.m. ...
But this bug is a deal-breaker for me to be able to use the current version. I can't upgrade until I know it's been fixed.
Also, I released five videos before I detected this bug. The intros to all of them are all screwed up, but it's too late to fix them now.
|
|
|
Quote
Hi JonathanS -
You are absolutely right! EEK!
Unlisted screen capture
It's impossible to revert to a former version without uninstalling & re-installing  so that might be necessary.
Cheers - Tony
Hey PDToots, thatnks for the reply.
To your last comment, however, I found a way to DOWNgrade: https://www.cyberlink.com/support/powerdirector-ultra/patches_en_US.html
Select the second one down for 2509, run that installer, and PD will be set backward to the previous build. It may not be an offical way to do it, but it seems to be working as it did before, and a new computer is just around the corner, anyway.
|
|
|
Whenever I open a title in Title Designer, the functionality of fade in / fade out breaks for images in the title. Setting these has no meaning. The familiar dark grey bars do not appear on the designer timeline anymore, and the setting simply unticks when I leave the designer.
The only way these work is if I drop a custom title onto the timeline that already uses these features, and then do not open the title in the Title Designer. Obviously, that is not a work-around.
These worked in the previous version, and the bug has surfaced since updating to 2820. Can I revert back to the previous build so I can get my work done? Otherwise I need an immediate fix - there's videos that need to be produced and released TODAY.
|
|
|
Quote
Why wasn't this patch available to me when I used the programs "check for updates" link?
This did not show for me either, but because of the images in the Title Designer issue, I wish I hadn't updated, because my work is now at a halt.
|
|
|
Quote
Hello.
I found new bug after update to 2820 (from 2508 ).
A function Fade (Enable Fade-in / Enable Fade-out) for images in Title designer doesn't works in v15.0.2820.
If I set something of this, it will immediately lose!
When I click to OK (close the Title designer) and open it again track of images are empty (without file name, Fade-in or Fade-out).
I am encountering this bug as well, and need an immediate fix.
|
|
|
Found a work-around ---
Among the options in the "Produce" area is the option to produce a WAV file.
At its maximum setting of 1,536 kbps, the file produced is equivalent in quality to the "extracted" version, also at 1,536 kbps (which is absurdly low, just fyi). However, its duration -- the crux of the discussion here -- comes out exactly the same as the video it comes from. Thus, when played simulatenously as the clip, there are no sync issues, either at the beginning or the ending. I can then edit the audio to my heart's content (in Audacity), re-import it, and not worry that my lips and voice do not line up.
I must say, though, this is a LOUSY workaround, though -- it basically means that from here on out, I have to ignore the "Extract Audio" feature from within PowerDirector, and instead add another time-sucking "Produce" to my routine. If PowerDirector does not even work with the files that it creates, then I'm pretty disappointed with this product.
|
|
|
Continuing to test and get poor results:
The same issue is occuring using H.265 HEVC (which Windows 10 still does not natively support, thus why I use H.264). Extracted audio there, too, is longer than the original. The beginning sounds fine, but the further you get into the clip, the worse the syncronization is, just as with the other "produce" settings.
Whether or not "Hardware decoding" was selected made no difference.
|
|
|
Quote
Hi JonathanS -
I don't think I can shed much light on your observations, except to say that it puzzles me too.
- Just now I took a clip & trimmed it up ready to produce. Duration in timeline 3:23:20
- Produced to H.264 AVC 1920x1080 30fps 15Mbps - duration in timeline 3:23:20
- Extracted audio from produced file - duration in timeline 3:23:19
- MediaInfo read both files (produced video & extracted audio) simply as 3min 23sec (not so useful)
- Moo0 Video Info read the produced video as 3:23.86 & the extracted audio as 3:23.84
(I shouldn't put this here because it only muddies the waters) Each of the files was sent to AudioDirector to check duration:
Original trimmed clip = 3:23.898, Produced video = 3:23.861, Extracted audio = 3:23.840 (consistent with VideoInfo)
On a cheerier note, I couldn't detect any "out-of-syncness" when the files were played back together.
Cheers - Tony
Thanks Tony/PDToots - I remember you confirming another issue I had (have) with Border Blur in titles, too. It eventually came down to Customer Support providing me a custom dll file, that nearly got replaced when an update came out later. The custom file mitigated that issue, but didn't solve it entirely.
I have a feeling this is not a dll issue.
|
|
|
Quote
More than likely your video is of a variable framerate and not really 30fps constant. You can use a utility like MediaInfo to verify file framerate. Variable framerate files do/can/have caused PD issues. Converting the clips to a more compatible format at constant framerate with a utility prior to editing in PD often helps.
As added info, you can move audio at a 1/10 of a frame interval in PD, vs video which is adjusted at a frame interval.
Jeff
The files being produced by PowerDirector are in fact Variable, according to MediaInfo. Do you have a suggestion to stop PD from doing so?
Just for the record, my whole process involves this:
Take multiple MOV (29.97 fps, 1920x1080) files from camera
Use PD to stitch them together
Produce a single MP4 (1920x1080 29.97fps, H.264 AVC)
Start new project
Use PD to extract the audio from the MP4 as WAV
Tweak the WAV in Audacity
Place the MP4 and the WAV on the timeline
Lament that the WAV is longer than the MP4.
For the record, the original MOV files are Constant bit rate...
|
