|
|
Quote
You might try pref > Hardware Acceleration and uncheck the hardware decode option and see if that helps.
Jeff
This worked! But do you have any idea why muting the audio would cause a problem?
|
|
|
Quote
Hi guys, I am used to Final Cut Pro but needed something different so I have been using PD365 for a couple of months now. It is a shame but I think I am just about to stop using it for the second time. The things that really bug me are the lack of keyboard short cuts to move about the timeline and the lack of a centralised 'library'
I had to quickly create an video advert on a tight timescale and dove into it with PD365 but I found that having to use the mouse to grab a pointer to move about from place to place slowed me down considerably. On FCP all you have to do is hit a couple of keys to get around the timeline but the biggest thing I cursed myself for was not being able to centralise the library.
I worked 12 hours straight to get the advert out and had clips, images, sound parts and text everywhere. (Yes, I should have been more methodical... but, the worst is yet to come.
I finished the advert... produced the master and started tidying up my computer and not thinking a deleted files which where in the downloads folder in the documents and in the store....
Then I got a call that the client wanted a tiny change.... so i opened up the project again and many files were missing. That added another couple of hours of editing for me.
Botton line, yes, I should have been more organised but that is not necessary in FCP or iMovie.... all your files are brought into a library.
With these things in mind I will move away from PD365 and hope that someday they will fix the issues and I can come back.
Great shortcut tips video here from Maliek. Well worth the ten minutes ![]()
https://youtu.be/6jU4np5_hBU
|
|
|
Clipping a short video (mp4) from my phone in PD365, produced with the audio muted, and get a black screen. If I unmute the audio it produces fine. I did it three times with the same result.
EDITED: Okay, so if I take the video I produced with audio, and then mute that one, it produces fine. So it must be something with the cell phone video? It's not an issue now since I was able to do it, but I would like to know for future use if anyone has any thoughts.
|
|
|
It's an intermittent problem, but frustrating. Every other day or so, PD won't open, not from the CAM, not from the shortcut, not from going directly to the exe in the program folder. The only thing that works is to reboot my computer (Windows 10 64bit). When this happens, the other Director Suite programs all work (launching from CAM), only PD seems affected. Any thoughts?
I edited the topic but it doesn't seem to have worked - I am using PowerDirector 365 through Director Suite.
EDITED: I should have Googled first. Found a helpful YouTube that directed me to go through Task Manager - even though it wasn't 'open' in the apps list, it was still open in the background processes. Right-clicked, 'end task', and voila - shortcut and CAM work again.
|
|
|
Quote
Contact CL support for resolution. To be honest, your HD4600 is 2013 Quick Sync version 3 encoding technology and really is no huge step forward. Just use CPU encoding.
Jeff
I totally agree about it not being a big difference, it was (and is) more a case of not understanding why it won't work when it should. Here's a new thing: I had been trying all the 'fixes' with the same type of media in my timeline (an mp4), but with new projects every time. On a whim, I decided to try an mkv file and... it worked. I exported a successful mp4 using the Quick Sync. I then imported that video and exported it... again it worked. Chose another mp4 file, no joy. And then an avi file, no joy. Found another mkv and.... it worked.
|
|
|
Well, unfortunately, a clean install of the iGPU drivers didn't help either. I found another threadhere with someone having the same issue a couple years ago. They also talk about the regedit and resetting to '0'.
As many times as I've produced this error in trying to fix it, this registry never changes from all zeros (since the first time I did it back at the start of this thread). At this point I'm ready to quit trying - but it is beyond frustrating.
|
|
|
Correct, Intel Media SDK will not be in Windows add/remove, it comes with its own uninstaller in the installed path. I'm not implying this is the issue, however, I do believe you have something conflicting with the iGPU driver Quick Sync libraries that PD21 uses and this could be one of many potential conflicts.
-- When I didn't see this in Programs or in the Revo Uninstaller, I did some Googling and that is what led me to looking for an uninstaller (which I didn't find). The only place I can find anything to do with "Intel Media SDK" was in the regedit - the screen shots in my last post.
Did the HP iGPU driver installer offer a clean install option? If it does and one clicks the checkbox to execute a clean installation, the install will remove all old drivers and restores Intel settings to the default values. This may help.
-- HP prompted me to download their installer, and I don't recall any options for a clean install. I will try to see if I can roll back and maybe there will be an option.
|
|
|
Quote
I guess I'm at a loss without seeing the entire platform, it appears you have might have a conflict with the iGPU Quick Sync libraries. Have you installed some form of Intel Media SDK? To my knowledge the Intel Media SDK project is no longer active. You've got a series of Quick Sync encoders associated with that package installed that may be causing some issue for PD.
You can always contact CL support.
Jeff
Just because I'm super stubborn, I uninstalled Director Suite completely and reinstalled, no difference. I could not find Intel Media SDK installed on the system (through the Windows add/remove, or REVO uninstaller, which goes deeper). The only thing I could find is in the regedit under Intel there is a Media SDK folder. Images attached. Is this what you were indicating?
|
|
|
Quote
I guess I'm at a loss without seeing the entire platform, it appears you have might have a conflict with the iGPU Quick Sync libraries. Have you installed some form of Intel Media SDK? To my knowledge the Intel Media SDK project is no longer active. You've got a series of Quick Sync encoders associated with that package installed that may be causing some issue for PD.
You can always contact CL support.
Jeff
I'm not even sure what Intel Media SDK is :/. I do appreciate your patience in trying to help me solve this. I will ask my techie friend here at work to check into this. If it ever does get resolved, I'll update. Thanks again!
|
|
|
Quote
You say you tried with encoding option check and unchecked. By saying encoding, that is on the produce page and you get same failed result. If that is true, this would potentially point to the decode setting in pref > Hardware Acceleration being a issue.
Keep in mind, one has 4 permutations of these two settings and different hardware engaged each time for the 4 permutations on checked or unchecked so details and behavior are very relevant for understanding.
The HD4600 only supports MPEG-2 and H.264 Quick Sync encoding and only for certain resolutions.
Jeff
Sorry, just a typo, I tried with the decoding both checked and unchecked.
For encoding I have tried all the options from 640x480/ 24p through 1920x1080/30p
I've also re-checked the regedit after each error message and it remains all zeros.
|
|
|
Quote
The pref > Hardware Accleration > Enable Hardware Decoding is exactly that, use the iGPU for decoding. Based on timeline source content, the iGPU may or may not be able to decode. This setting and decoding is independent of the encoding occurring during produce. If unchecked, CPU will be used for decoding timeline content.
To control encoding, that setting is on the produce page, unfortunately, you only included a small pic of your produce settings so hard to offer advice. It also appears you changed to a 1280x720 profile vs the prior mentioned 1920x1080, although both should support Quick Sync with your HD4600. The "Fast video rendering technology:" area on produce page, the drop down menu should be set to Quick Sync to use the iGPU for encoding. If unchecked, CPU will be used for encoding timeline content.
It's possible that enable hardware decoding is causing the issue too, unselect, and then simply try Quick Sync encoding. Since you had a failure, you may have to verify regedit keys again.
A clean install of PD can fix many of its common issues, usually it has little effect on ability to use hardware encoding, that's typically more a hardware setup issue.
Did you verify your driver version was in fact updated with dxdiag?
Jeff
I tried the encoding option checked and unchecked, same result. The regedit keys are all '0'. Sorry about the change of profile, thought I'd try a smaller one to see if it made any difference (it didn't). I've attached a full screen shot with the 1920x1080 profile, and the error message, and the latest dxdiag after the driver update.
Just FYI, the only other profile that offers the Fast Video Rendering box is 'MPEG-2', and I get the same error with that.
|
|
|
Nevermind this edit... ignore please ![]()
|
|
|
Quote
I'd probably start by at least updating your HD Graphics 4600 iGPU driver to the latest from HP, https://support.hp.com/us-en/drivers/selfservice/hp-prodesk-600-g1-small-form-factor-pc/5387447
Even though you implied your driver is up to date, yours:
Driver Version: 20.19.15.5126
Driver Date/Size: 1/20/2020 8:00:00 PM, 39863784 bytes
HP's latest offer, 20.19.15.5171, Jun 20, 2021, ~1.5yrs newer than your installed version. I'd at least start with what HP has qualified and see if that might resolve the issue.
The regedit non zero entries would only affect that specific defined profile, since the pic now has all zero's, that's at least good but hard to say what produce profiles might have been affected.
Make sure you are using a basic H.264 profile as stated prior, that HD4600 cannot support H.265 encoding and should be trapped by PD making it unavailable.
Jeff
Weird, my device manager said the driver was up to date. I downloaded and installed the update from HP, restarted, Optimized in Preferences - no joy. I do have the Enable Hardware Decoding box checked - that's correct, yes? The error message also mentions making sure Windows Media Player is up to date. My Windows updates are up to date (is there any other way to update WMP?). I do have some optional updates available under "Drivers" (see attached). Would any of these affect things?
I feel like this was working prior to my recent upgrade (from just PDR 365 to Director Suite 365 last weekend (it had me reinstall everything). Is it possible something weird happened? Should I maybe uninstall and try again?
|
|
|
Quote
When unchecked, you are using the CPU to do the timeline encoding. When checked, you are using your iGPU with Intel Quick Sync to do the timeline encoding.
Not knowing the model of CPU/iGPU you have, however, it should be capable of basic H.264 1920x1080/30p 16Mbps profile you are using. You might:
1) Verify you have latest and proper drivers installed for your iGPU from computer vender
2) Since you say all H.264 resolutions affected, not likely but if you are happy with using regedit, verify all keys in Computer\HKEY_CURRENT_USER\SOFTWARE\CyberLink\CES_FunctionLogger\DATA have a value of zero, "0".
3) Supply dxdiag text file (https://forum.cyberlink.com/forum/posts/list/97579.page#post_box_392510) so one can see which CPU/IGPU you have, what drivers you are using, other pertinent computer data.
4) Or, if no desire, leave hardware encoder unchecked and simply use CPU encoding since that's working.
Jeff
Hi Jeff,
I checked the keys as mentioned above. The first three had a value of '1', the fourth had a '2' and the rest were '0'. I reset them all to '0', restarted - no change. All Windows updates are up to date, still getting that same error when I try to use the Intel Quick Sync. I attached the dxdiag file. There is no rush for this - I can still render - I would just like to solve the mystery at this point.
|
|
|
It did indeed. It's a little weird, since you can see by my example in the OP, the letters are individually bordered when spaced out, or when there is a natural space, but where they overlap it must consider it a 'whole title'. Changing that setting immediately gave the desired effect. Thanks!
Edited to add: three days later I have finally received a response from 'support'. They basically said it's a different build, so live with it. Thank goodness for this forum and helpful users, because the 'expert' sure didn't offer any solution.
|
|
|
Quote
Hi,
If you can, it will be simpler, if not just refer to the topic.
The issue seems pretty clear, there is a difference between the previous version and the latest version as regards that title. Whether that is a change in design or a glitch, I have no info. I presume only the development team would have the details.
If you have any feedback from them, it would be good to post it up for others to find.
Cheers
PowerDirector Moderator
I will submit a ticket with this info. Just to add, I have PDR12 on another computer and it does the same as the PDR 365.
|
|
|
Quote
Hi,
Exactly which version of PDR are you using?
On my PDR365 Business 21.1.2401 the title behaves as shown in Maliek's tutorial.
However, on my PDR365 21.4.2812 the title behaves as you have indicated.
No idea what has changed or why, others may confirm your findings and PDR21 users on an older version may perhaps also confirm the original behaviour?
I suggest you raise a support ticket, refer to this topic and see what the official position currently is.
Cheers
PowerDirector Moderator
I'm using PDR365 21.4.2812.0 same as you. Should I include those screen caps in my ticket?
|
|
|
Quote
When unchecked, you are using the CPU to do the timeline encoding. When checked, you are using your iGPU with Intel Quick Sync to do the timeline encoding.
Not knowing the model of CPU/iGPU you have, however, it should be capable of basic H.264 1920x1080/30p 16Mbps profile you are using. You might:
1) Verify you have latest and proper drivers installed for your iGPU from computer vender
2) Since you say all H.264 resolutions affected, not likely but if you are happy with using regedit, verify all keys in Computer\HKEY_CURRENT_USER\SOFTWARE\CyberLink\CES_FunctionLogger\DATA have a value of zero, "0".
3) Supply dxdiag text file (https://forum.cyberlink.com/forum/posts/list/97579.page#post_box_392510) so one can see which CPU/IGPU you have, what drivers you are using, other pertinent computer data.
4) Or, if no desire, leave hardware encoder unchecked and simply use CPU encoding since that's working.
Jeff
Thanks Jeff. This is on my machine at work so I will try those suggestions out on Monday. I know the drivers are up to date. I don't really do anything super complicated (yet!) so the render times are fine, I'm just always curious about these things. I appreciate your input!
|
|
|
|
I am following along with thisPowerDirector University tutorial ( Maliek is awesome) and have a question about a text quirk. I am using the same font and settings that Maliek uses, but I notice that on my work, the text appears a little different. In the screen cap from the tut, you can see that the bordered letters overlap each other, but the border remains intact on the 'top' letter. On my machine, the border disappears where the letters overlap as if it were outlining the word instead. Kerning makes no difference. On the third line of my example, I spaced the letters, so you can see that the letters are indeed outlined individually. Thoughts?
|
|
|
Quote
You can still use your iGPU, Quick Sync encoding option. whether it's beneficial or not relative to CPU encoding depends on which CPU/iGPU you have, which produce formats you are using, timeline content, so usually best to do your own speed trials with it selected and not selected to validate speed and quality for your specific needs.
The error you see when using iGPU may be real, iGPU does not support whatever produce format you are using, or might be aftermath from a crashed encode session using the iGPU. More information would be needed about CPU/iGPU model and produce settings when error occurs to gain some insight into potential issue.
Jeff
Hi Jeff,
I cleared everything and restarted both the PD session and the computer. I've attached a screen shot of the export settings, in short: Exporting to H.264 AVC. In the screen shot, attemption 1920 x 1080/30p, but I tried it at all resolutions. This format and MPEG-2 are the only two where the Fast video rendering tech check box is even an option (greyed out on all others), and if I check it, I get the error message. Unchecked, both formats process fine.
|
|
|
