|
|
|
Rebooting my computer cleared the problem. Go figure!
|
|
|
Magic Music stopped working when I went to build 3130. Whenever try to use it PD13 hangs (infinite clock) and has to be cancelled. Is there a fix for this?
p.s. Can simulate by just opening PD13 and selecting Magic Music on a new project with no media files or editing.
|
|
|
In Magic Motion Designer...
1. Remember 'snap to' settings.
2. When selecting "User Defined" open clip with entire clip selected.
3. Provide "Select all" control (selected to edges of image).
In Title Designer...
1. In 'Align Objects" provide "Center Both".
(Editorial: Surprising we are at version 13 and still have these basic editing flukes. Almost like the developers don't use their own product.)
|
|
|
SonNic67,
Could you put a posting in the "Cyberlink, listen to this suggestion" pinned thread requesting that PD14 be upgraded to fully exploit DirectX12? What you said here confirms my understanding also. I'm not sure Cyberlink is even paying any attention to this thread, but it's all we users have in the way of requesting product improvements.
Thanks!
|
|
|
I woul like to open PD13 on my second monitor which is larger that the laptop screen. I am able to make other programs open on monitor 2 by going through a process I won't go into here. However, PD13 always opens full screen (no matter how the shortuct is configured). This prevents doing the process which makes it open on monitor 2. I know there are convoluted 3rd party apps to work as a middle man to make this happen, but I don't wish to use them. Is there a way to get PD13 to open "normal" (not full screen? If I can make this happen, and can then get it to open full screen on monitor 2 by going through the simple process that teaches Windows 8.1 where and how the app should open (it requires starting from a "normal" screen).
Thanks!
|
|
|
|
Has anybody tried PD13 on the new Windows 10 that came out yesterday? Are there any noticeable performance improvements that would make one want to upgrade from 8.1 to 10? Directx 12 is supposed to exploit the GPU better, but maybe PD is not coded to support it yet. Just curious.
|
|
|
Productivity Improvement:
Add the ability, with a shortcut key, to add the fade transition to any video cliip or picture or pip by presing the key. Alternately, choose a transition, press a shortcut key, and the transition goes onto the start and end of the selected entity.
|
|
|
|
Add to preferences the ability to specify where the working directories are located. This would include shadow, prefech, caching, thumbnail, save to, locations. This will allow using a solid state hard drive to improve editing and rendering performance. I've tested this and it really makes a difference.
|
|
|
OK, if anybody's interested, here's what I've discovered. First a little background. I'm doing a video biography of a WWII Navy pilot and Lockheed test pilot based on 14 hours of video interviews I've done with him. Naturally I want editing and rendering to go as fast as I can afford! The PC I'm using has the following:
CPU - Intel i7-3630QM. This has turbospeed up to 3.6 ghz
Mem: 8ghz sdram pc3-12800
Video Card: Nvidia GTX 660 with 2048M ram
HD C; 7200 rpm sata3; F: 350G solid state on USB 3.0
The passmark.com Passmark Rating rating of the computer is 2340. CPU Mark is 8457. 2D graphics mark is 650 (what PD mainly uses), memory mark is 2290, disk mark of the SSD drive is 3075!
By doing the following, editing and rendering performance has noticeably improved (subjective guess: 20-30%). I can render 16 minutes of video in 4 minutes. The "pregnant pauses" that existed during editing are mostly gone.
- All project files on SSD (input and output).
- "Video" library on SSD. Do this by right click video library, choose properties, change location to F: This relocates folders ShadowEditFiles and Preview Cache Files to F:
- Searched all PD INI files for drive locations -- none found that are relevant
- Searched windows registry for all PD drive locations -- changed C: to F: on all work areas.
All of my source files are backed up on two other drives. Rendered clips are copied from the F: drive to the C: drive.
|
|
|
I have installed a very fast USB 3.0 external SDD drive. Passmark shows it over 10 times faster than any installed hard drives. Now I want ALL of PowerDirector's disk activities to use the SDD drive, so that my editing and rendering are faster (I want to exploit the SDD drive in PD13). This would include the HD shadow files, and any other "work" spaces PD uses on a hard drive. I understand that the program is installed on my C drive drive, and short of uninstalling and reinstalling there's nothing I can do about that. But how do I get PD to use the SDD drive for shadow files, etc? I have already relocated the "VIDEO" folder to the SDD drive using the Windows relocate library function. Are there INI files I can modify to point PD to the SDD drive?
I'm using Windows 8.1
Thanks!
|
|
|
Integrate audio editing into the main program (improved productivity).
Add an audio edit (effect) to reduce vocal echo. This functionality is available via WaveEditor 2 using VST plug-ins.
Another WE2 VST I use a lot is a compressor/limiter on an audio track. This is different from "normalize", which is to average, not compress and limit.
|
|
|
I have a high powered PC, CPU, HD, and video card. Even so, there is an awful lot of wait time when editing videos. Also goofy idiosyncrhacies like when play a clip the audio goes ahead but the video stop, then finally the audio and video get back in synce. I'm using "normal" preview quality, no other programs running, single track with occasional PIP image, etc. Very simple stuff.
If possible, create a "fast editing" feature that speeds up simple editing by using less CPU and GPU cycles. Perhaps a reduced functionality mode to achieve smoother and more streamlined editing.
Just trying to help make users as happy as possible.
==== FOLLOW UP 7/22 ====
Background on this request...
I have been using PD since version 7. I have been using it on state of the art PC's I build myself, and which have a good "Passmark Rating" (passmark.com). With each of the 7 PD version I have gone thru, the new version requires more horsepower to run than the privious version -- FOR THE SAME SIMPLE EDITING. I use 10 minute or less clips to edit, add a few inline or pip photos, simple non-animated text. For this simple work the productiviy, fluidity, and performance should be the same in 13 as it was in 7. That's not the case. Each PD release increases the hardware requirements by 20-30%. So if you are using the same computer on 13 that you were on 11, you are now in trouble. Your productivity has gone way down. As a software engineer I can tell you this is because the code had been added on to, instead of re-written. This contant adding onto the code creates "bloatware" that runs like a slug, even thought your aren't doing anything different that you were 2 releasses back. You are forced into hardware upgrades just to keep PD running "normal". That's why I'm suggesting an Entry Level verson of PD that does basic editing, with pip tracks and music tracks, but uses only the "core" code from PD13 (the shorter the code path, the fast it runs). I guess I'm suggesting a "Consumer" version of PD, with the option to upgrade to a "Professional" version of PD. THe price-point of PD is not the problem, it's the system requirements.
|
|
|
|
SPELL CHECKER FOR ALL TEXT BLOCKS!
|
|
|
Sorry for my rant. This was a user error. My fault. I didn't choose the correct file type in the little unlabeled drop-down below the file format buttons. 
|
|
|
|
Thanks for the circumvention, but I think you'll have to agree the user should not have to do this. I posted this problem about 3 years ago and it's still not fixed. Oops, my frustration is showing. Thanks again.
|
|
|
|
@#%!$*&^%(*!! It did it again! I just updated from 2604 to 2907, and all my custom rendering profiles are deleted! This has happened 9 out of 10 times whenever I do an update or upgrade since PD 9! The upgrade from 2408 to 2604 didn't do it. And just to make sure, I didn't a clean/fresh install going to PD13 so this wouldn't happen! Our love/hate relationship with PowerDirector continues! )o:
|
|
|
Please update PowerDirector to be compatible with NVIDIA drivers newer than 337.88 (5/26/2014). Those of us with perfectly good CUDA video cards can't update to the latest NVIDIA drivers, because if we do then PowerDirector no longer recognizes and uses hardware acceleration. This is not an NVIDIA problem, it's a CyberLink problem. Software needs to be upgraded to be compatible with newer drivers so the we can exploit the best from both PowerDirector and NVIDIA.
Please don't get into a finger pointing game, just update PowerDirector per the instructions on the web for using CUDA enhanced video cards.
Thanks!
p.s. While some might feel a monochrome all-black user interface is good, I would prefer all-white if you want to go monochrome, or "shades of grey". Creative use of interface colors can actually increase productivity.
|
|
|
Going back to Nvidia driver level 337.88 allowed both PD12 and PD13 to recognize the CUDA hardware acceleration. Thanks the good news, and for which I thank you very much! The bad news is in PD13 the CUDA is only recognized for H.264/AVC, not for H.265/HEVC. Call me a dreamer, but maybe someday CyberLink and Nvidia will get together and allow us to exploit hardware rendoring for all common video formats.
THANKS AGAIN!
|
|
|
Here is the fix I applied before that worked. I just reapplied it and it didn't work this time for either PD12 or PD13.
http://forum.cyberlink.com/forum/posts/list/40521.page
Anybody have any suggestions for getting my CUDA supported Nividia card working again for hardware acceleration (hardware encoding)?
|
|
|
It was a "bootleg" patch somebody came up with -- not a Cyberlink PowerDirector update.
If somebody can tell me how to view all my postings/replies I can probably find it, as I replied that the fix worked. Most forums have a way to view the members postings, but I don't find that here.
|
|
|
I had this problem last year on PD12, somebody here posted a fix/patch. I applied the fix and I was able to check the box for fast video rendering on MP4 files. A few weeks ago I was forced to re-install Windows 7 64. I am now trying to render videos for the first time since. Neither PD12 nor PD13 will let me check the fast rendering box (greyed out) trying to create an MP4 using PS13 AVC or HEVC (called MP4 on PD12). If searched this forum trying to find that fix again, but no luck. I have an Nvidia GTX 560 with the latest driver as of today. PD13 has 2604 update.
Does anyone remember how to acquire the patch that fixed this problem on PD12 last year?
Thanks!
|
