|
|
Quote
OK, so far I haven't been able replicate your issue on PDR365 Business v.2829. Both your sample clips can have 100% fisheye lens correction applied and they can then be successfully produced, either with a default profile or with a custom profile (to mimic the native resolution, bitrate, fps etc. If I use Render Preview that also works as expected.
2 suggestions :
Update PDR to 2829 []https://forum.cyberlink.com/forum/posts/list/96975.page]
If that does not have any effect, unless any other member can replicate your issue, then raise a support ticket with CS and see if they can replicate it or have suggested solutions.
You could just check that you can use a simple PDR sample clip OK and see if it only your GoPro clips that have this issue?
If you get a solution, please report back to help others in the future.
Cheers
PowerDirector Moderator
I did a test with 1080/50p footage from my sony a6600 and no problems with the lens correction so seems it is something to do with gopro footage - which unfortunately is the main footage I want to process with PowerDirector and which most benefits from fisheye correction.
Cheers Andrew
|
|
|
Eureka! Closed the program, cleared out all the cache and shadow files, reopened and immediately produced a 720/30p file - no problems. I then produced an archive file 1080/60p and again no problems.
Thank you very much for the suggestions. Seems possible that the problem arose due to some failures of the render preview process.
Cheers and Thanks Again
Andrew
|
|
|
Thanks for the suggestions, I will try them shortly (some other work to do first).
In suggestion 1 where you say also try and mute the second track - surely that would just give no sound for that segment of the clip.
Also, is the suggestion move both video and audio to a second track or just the audio.
Thanks again, much appreciated.
Cheers Andrew
|
|
|
Deleting the various cache files did not solve the problem.
I have attached a short clip that demonstrates the current version of the problem with the audio towards the end playing two streams on top of each other when there is actually only one.
I can also report that the fault is now manifesting in the preview stage as well.
Andrew
|
|
|
I am having a whack-a-mole experience with audio in a 4 minute clip. The clip is built from many short video clips and in some places the audio and video have been unlinked so that I can use a slightly different segment of audio against the video. There are no problems with the video.
Everything, video and audio, is on a single track, there is nowhere where I have two tracks on audio layered on top of each other.
Usually, but not always, the problem does not show when previewing the clips, only when producing.
The initial problem - which I have experienced before - was right at the end of the 4 minutes, the audio started to play two overlaid segments, one a slight delay from the other.
Since the clip was nearly perfect I decided to solve this by deleting the final part of the clip where the problem occured. This got rid of the overlaid sound but next a horrible loud distortion appeared at the 3m mark for about 10 seconds.
Following suggestions from my earlier post about problens with lens correction I then tried disabling hardware acceleration. I produced a new version. The loud distortion disappeared but now I was getting two streams of audio over a brief section at 2m 4s.
Next I tried updating my version to 2829. The problem continues.
This is extremely frustrating. I am trying a new ploy right now which is to delete all the preview and shadow edit files to see if starting again helps.
I was initially using PD 365, version 20.4.2812.0 which as described I updated to 2829.
I have AMD Ryzen 7 4800HS with Radeon Graphics 2.90 GHz, 16 Gb ram, on Windows 10
Cheers Andrew
|
|
|
Thank you for these suggestions, I will give them a go and report back. Incidentally, I do not have the Director Suite 365 not I believe the business version.
Andrew
|
|
|
Quote
Hello,
Please be advised that PowerDirector 365 20.4.2829 has been released and can be installed by going to CAM. This update includes a hotfix to the crash issue users were experiencing from the last release.
Please let us know if you encounter any issues after installing and using this latest update.
Cheers
PowerDirector Moderator
How can I tell which version the CAM intends to install. It dates it as 4/29/22 but provides no version info that I can see - is that the one you are announcing here which apparently fixes the crashing problems/
Cheers Andrew
|
|
|
Quote
Hi,
Thanks for that.
Can you detail the exact lens correction applied and your produce choices (SVRT?) no need to do all of your tests just the main 264/265 ones for working with.
Cheers
PowerDirector Moderator
The lens correction was fisheye distortion 100% and nothing else.
The produce options varied - where possible I choose the same resolution fps as the source. For example with the 1080 / 60fps I choose the same from the mp4 menu and none of the other produce options were ticked.
I just tried again with on 5% for the correction - no difference.
It always shows the correction visually in the various preview windows and you can see the correction has been applied but if you try to render preview it just stays on 0% forever and if you produce it processes incredibly fast but gives no video content only audio.
If I look at properties for the video produced I see it has all the correct expected properties (resolution and fps) but the actual file size is 552 kb and no sign of video when played in VLC.
I have attached a processed file.
Cheers Andrew
|
|
|
OK, I have run a number of tests and it seems the same happens every time regardless of the properties of the source video.
If I shoot with my GoPro at say 1080 60fps, I can export / produce as long as I do not use the lens correction fisheye option. If I do it exports a clip with sound but black screen video.
However if I take that source clip (no lens correction) and export it either with the same properties, or with different properties (eg 30fps), and the reimport that new Powerdirector created file, then that file can have lens corrections applied and it works fine.
Obviously this not a very desirable workaround both timewise and also for quality.
I have uploaded two different clips both of which behaved as described. I ran this test on 8 different resolution / fps combinations and same every time. You will notice my sample clips - one is H264 and one H265, same both times.
Cheers Andrew
|
|
|
Thanks for the reply and suggestion, will do tomorrow : , have deleted the original files
|
|
|
I am trying to apply lens correction to a 12 sec clip of GoPro 10 2.7K 60 fps H264 video.
When I do this the correction plays in the preview screen while I am in the fix enhance area however it will not render the preview (just stays on 0%) and when I produce the video to 1080 60fps it processes extremely quickly but I get a black screen video with audio playing ok.
As a test I removed the lens correction but did a slight color adjustment and this worked fine.
Cheers from New Zealand, Andrew
Added later:
I am using PD 365, version 20.4.2812.0
I have AMD Ryzen 7 4800HS with Radeon Graphics 2.90 GHz, 16 Gb ram, on Windows 10
|
