Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
Quote I answered the "best driver" part of your question, but if you're having other problems we'd need to know some specifics about what you're seeing on your end.

For example, you can produce to AVC H.264 or HEVC H.265, but not what you wrote. The more accuate the description you can provide, the quicker we can try to figure things out.




Optodata, my head is still spinning from your fast response, Thanks!

You are correct, I have to render 264 or 265 with the CPU, used to do that with the video board and 10 times+ faster. I guess that a new GTX 1060 driver screwed it up. Now trying to find one that goes back far enough.

Gene
Hello all,
Had some hickups lately trying to render 4K in HEVC 264. Any idea?

Thanks

Eugene
Thanks both for the info.
I will look into it. So PD17 would be a good compromise? All projects and saved data would be transfered I assume. My 265 files are standard gopro 8 stuff.
My main concern is to screw up what is now a well operating PD14 editor. I would of course have HD:C clones and backups to go back to 14.

Thanks again

Gene
Quote

I've not seen anything in registry that controls shadowfile generation performance. However, since PD14, CL has unthrottled the process some so it is faster. Some changes occurred in PD15, a few more in PD17, which is essentially the same as PD18 and PD19. Relative to PD14, shadowfiles generate about 2X faster in 17, 18, and 19.

It is still a CPU only task as in PD14.

Jeff


Thank you Jeff.
I sold my Ax100 last year because of its weight and not too good stabilization and now shoot with a GoPro 8 , linear at 60 fps and 100Mb HEVC 4K and have no more shake problems.

My replays on the PD14 timeline stutter and I now have to wait for the shadow files that are set to full HD quality. I searched the past issues for any info on speeding up Hanamax.exe since it only works at a low 20%?? percentage of CPU availability but found none.

My CPU is a i7 6700. But in the back of my mind I remember a discussion about this subject in the past. I think a registry change is all it takes. Also remember that llater versions of PD offer a option of changing the $ number.

Thanks again
Eugene

I do not want to change from PD 14 bcause I like its Magic Music feature.
Has anybody tried changing the registry to increase the shadowfile generation speed?

Belated Happy Newyear, it MUST be better than the last one

Thanks

Gene
Quote



Yes Jeff, if I have no further problems with WIN10 updates I will stick with what I have.

Eugene






I updated win10 again and PD14 is now working fine. Preventing app drivers from updating kept the old NVidia drivers in place.

Just set "Device Installation Settings" to NO UPDATES

Eugene
Quote

I guess I'm maybe not understanding your question correctly. The screen shot I posted is from within PD18, as far as I have experienced, it works the same as it did in PD14. SmartSound was supported in PD14 (Deluxe, Ultra, Ultimate, Ultimate Suite) so fairly certain PD18 ultra should be the same if you have Smartsound from a previous PD purchase. But correct, my screenshot and experience is only PD18 Ultimate perpetual key.

If PD14 meets your needs, I'm not sure I would update. Nothing better or faster for H.265 producing in PD18 which was your niche need and the life cycle of PD18 is 3/4 over.

Jeff



Yes Jeff, if I have no further problems with WIN10 updates I will stick with what I have.

Eugene
Thank you Jeff

Does this apply to PD18? And does it work from within, as it does with PD14? Not sure if PD18 ultra has any music.

Eugene
As mentionend I did not go beyond PD14 because of the music files and it met my needs.

Can Magic Music be retained if I got a newer, paid up version of PD? Like PD 18?

Thanks

Eugene

BTW I recently got a GOPRO 8 Black and I am amazed at the quality of some shots compared to the FDR AX 100, IF thete is enough light.
Quote



Thanks OPTODATA
I was able to install the old driver after uninstalling 3 MS updates dated 05/30 2ea and one 05/15. Wonder what the next win update will do but now I know what is going on. Since I use plug in drives, it would make sense to have a drive optimized just for editing w/o internet hook up as you pointed out.

I like 14 because of the audio music files and it does all I want to do. Still burn my stuff to UHD.

Thanks to all involved in solving this MS fiasco.

Eugene


win 10 has afeature to disable automatic driver update. I invoked that and hopefully no more surprises

Thanks for all help.

Eugene
Quote Your system images (clones) are the best way to ensure you always have a working copy.

You'll have to completely uninstall the current nVidia driver (using the Windows uninstall app) before you can install the older version. If you aren't prompted to reboot after uninstalling the current nVidia driver, do it anyway and you'll have to make sure Windows doesn't automatically download and install a newer version, so maybe disconnect your internet connection until you get 411.70 installed.

The only way to use new nVidia drivers and hardware is to get a newer copy of PD.



Thanks OPTODATA
I was able to install the old driver after uninstalling 3 MS updates dated 05/30 2ea and one 05/15. Wonder what the next win update will do but now I know what is going on. Since I use plug in drives, it would make sense to have a drive optimized just for editing w/o internet hook up as you pointed out.

I like 14 because of the audio music files and it does all I want to do. Still burn my stuff to UHD.

Thanks to all involved in solving this MS fiasco.

Eugene
Quote




Thanks for your fast reply and I found the problem. Win 10 had a recent update that screwed a lot of users.

I changed the HD to a 10 month old clone and there is no problem. Will now try a 3 mo old clone, that was before the W10 fiasko and also has the old driver.
The driver I installed today is 26.21.14.4614

Lucky I have plug in drives, use old HD to make clones, has saved my hide many times, in addition to backups.

Thanks OPTO



Cannot install the 411.70

not compatible

and how to prevent this from happening again?

Eugene
Quote I'm not sure what happened to cause the change overnight, but you can't run PD versions older than PD16 with new nVidia drivers.

You'll have to uninstall the current driver and go back to 411.70. See this thread for more specifics, and the older driver is here if you
need it.




Thanks for your fast reply and I found the problem. Win 10 had a recent update that screwed a lot of users.

I changed the HD to a 10 month old clone and there is no problem. Will now try a 3 mo old clone, that was before the W10 fiasko and also has the old driver.
The driver I installed today is 26.21.14.4614

Lucky I have plug in drives, use old HD to make clones, has saved my hide many times, in addition to backups.

Thanks OPTO
Hi

Had no problem with PD14 until today when trying to render a 4K video. I canot use HA, rendering only by PCU. Did download and install new drivers for GTX1060, did not help. All PD boxes checked.
Using same video material as before.

Thanks

Eugene
Thanks for the input guys, MUCH APPRECIATED.

It was Handbrake that fixed the problem, did that last night converting a 4K video from variable to fixed 29 fps rate. No more momentary hesitation of the video after using Any Video Converter when having a panning type scene.

My PD 14 did not accept the original variable frame rate video before but does now. Should have mentioned that.

Thanks again

Eugene
Quote Reference Post: https://forum.cyberlink.com/forum/posts/list/79919.page#post_box_328688 .
The Snapshots.zip posted earlier show the PD17 Media Library video snapshot button captures were the poorest when compared to those of PhD10 and VLC. The square pixels appear to be double in size indicating it is 1920 x 1080 scaled up to 3840 x 2160. There is a loss in resolution.

Conducted tests using PowerDirector previous versions 12 and 14, PhotoDirector 10, and VLC. Surprise! PD17 Freeze Frame are indeed full resolution unlike that found in the PD17 Media Library using the snapshot button. See the attached marked up screenshot for the comparison.

The UHD video used in this comparison is “4K Chimei inn (60mbps)” from this website: https://4ksamples.com/4k-chimei-inn-60mbps/ . This is an avc encoded video that works with the earlier versions of PD. Screenshots were taken at 38 sec. !6 frames in the video on each software.
Software----Size--------How Taken
PD12………9.15 MB….….Timeline Snapshot button
PD14………9.15 MB……..Timeline Snapshot button
PD17………9.15 MB……..Timeline Freeze Frame
PD17………3.77 MB………Media Library Snapshot button….(The Worst)
PhD10…….7.35 MB………Snapshot button
VLC…………6.66 MB…..….Snapshot
It is interesting that the PD12, Pd14, and the PD17 Freeze Frame captures are all the same file size of 9.15 MB. The comparison show that a PD17 user does not have to go elsewhere to obtain good 4k snapshots from videos.




. At times I use a second or more still frame and then start motion (4K). Have to use VLC for the still or the difference will show. And my PD14 is not as bad as 17.

Eugene
Is there a good way to convert variable frame rate to fixed?.

Audio not an issue, problem is video stutter.

Gene
Quote

There are two ways I can think of off the top of my head.

The first is to see if the TV has any scaling settings built in that might let you view your SD clip at a 1x scale (no upconversion). That would cause the video to be dsiplayed as tiny window, but it would be at its original quality.

If you want to force the TV to display the clip in ots origina; resolution, scale the clip down in PD using the numbers from this table (again, the clip will show as a tiny rectangle when previewing) and then produce the clip at the TV's full UHD resolution. That way, the frame fills the whole screen and the SD content will display pixel for pixel at its original resolution.

For example, if your TV's resolution is 4096x2160 and your SD clip is 640x480, set the Scale in the PiP Designer to 0.156, which is the ratio of the clip's horizontal resolution divided by the TV's (640 / 4096 = 0.156). You could also try 0.222, which is the ratio of the vertical pixels.

You might even want to play around with slightly bigger numbers to see if you can get the clip a little bigger without losing too much quality.


Well,
I knew the brains on this forum would come up with an answer.

Thanks

Eugene
Hi
we just looked at a 20 year old SD video on a 75" UHD display and it was pretty grim. Is there a simple way for PD14 to scale it so that it will show 7 times smaller or watever the UHD/SD ratio is.

Thanks

Eugene.
Thanks again.

Rather than Google all this, I understand that Display Port carries audio as does HDMI. The use of the splitter was to have the same image on a pc monitor as well as a TV, both via HDMI

Is it possible, on one card, to have two simultaneous outputs HDMI and DP, both with audio?

If a second 1060 is used, or a lesser GPU, can each output a different stream, say one 8 bit and the other 10 bit at the same time, same 4K video?

Or the obvious simple solution, a 10 bit HDR monitor, some now going for less than $500.

regards,

Eugene
Thanks for the reply SoNic67

I got it working after disconnecting the 8bit monitor from the signal splitter so that only the Vizio P TV was connected. In addition the HDR box on the Nvidea display software had to be turned on. After that the downloaded 4K HDRG10 played fine in HDR but only with the VLC video player, may have to update all the other players. The downloaded HDR software was 30Hz, the 4K HDMI stream to the TV was at 30Hz 12 bits. Most likely will be 10 bits at 60Hz. So far that is the only true HDR video that works, all others while claiming to be HDR are not.
Playback is fine as a file as well as from the burned UHD disc.

So far the TV set is indicating HDR even when playing non HDR material,no good. more work

Eugene
Go to:   
Powered by JForum 2.1.8 © JForum Team