|
|
Quote
Did I get you right that the new card will give a reduction in render to the one we already have for 20/365?
Yes. Like night and day. That Nvidia nvs 315 requires the old 8 year old fermi drivers and like PD12 to have hardware encoding for avc 1080p.
You can have 8K video encoding with the GTX 1660 Super for an additional $100 if using PD365. The Power Supply in that Dell may need to be replaced anyway to allow the power consumption of any more powerful video cards that you may buy..
|
|
|
The Dell T3600 workstation is 9 years old with that Fermi 2.0 generation card. Many users would stay with the Quadro cards for stability. Interesting that this 19 watt tdp card passmark is higher at 10073 than the 100 watt tdp GTX 1650 Super passmark of 10055. These card pricing of the two is within $20 of each other at launch dates.
The MSI GTX 1650 card requires a 6 pin power connector. See this article on Board Design: https://www.techpowerup.com/gpu-specs/msi-gtx-1650-super-aero-itx.b7443 . Go to the Dell website. You need to check the workstation for the power supply rating and if there is that 6 pin power supply connector available. You need an additional 81 watts to run this card.
You should be able to do nvidia nvenc encoding with the new card in PD20/365. You may expect a 3X to 8X reduction in rendering time depending on resolution and bitrate for avc and hevc.
|
|
|
|
Hold on. Adding the portion of a custom profile from a previous PD version does not disable the custom profiles in PD365. All the custom profiles are working in my PD365. I can write the procedure for you to do it yourself. Just wait. Need some time.
|
|
|
Not that I know of. Once the disk is playing you rely on the Prev and Next button on the remote control on any standalone DVD Player.
DVD software players on the pc can display the controls on the bottom in PowerDVD or in the menu of VLC, etc.
You can upload that menu to the DZ if you are okay with other users here to check out the custom menu you created.
|
|
|
This Hevc 8k custom profile was created back in sept, 2020 in PD17 as a test for the 8k production. It is similar to the one optodata made on Dec 11, 2020 on the other thread. They should work in PD365. My other custom profiles carried over in PD365. This one did not.
My test shows that a 2:25:27 duration video took 2:57 using nvidia encoding and is 365,099 KB. Svrt produced is 97% done in 11 sec. ,99% done in 34 sec. , 100% finished in 1 min. 8 sec. and is 388.016 KB.
Interesting that the produced nvidia encoded 8K video plays smoother with the Movie & TV app. when starts and stops (pauses) are repeatedly used as compared to the svrt produced one..
|
|
|
Please read this sticky: https://forum.cyberlink.com/forum/posts/list/80133.page#post_box_329487 . For further help please attach a screenshot of the pop up box with the version number. Also attach the DxDiag.txt of the pc.
Go to Mediainfo Online: https://mediaarea.net/MediaInfoOnline to see the text of the video file with the error, download the Mediainfo report and attach it too on your next reply.
|
|
|
|
See this tutorial on importing any LUT: https://youtu.be/4mke5VcLvd8 . This should help.
|
|
|
Think that you already answered your own question. If this is a wide scene then crop that singer out using PiP Designer. You may want to be creative and make a tighter crop when the other singer is too close to the middle singer and vice versa using keyframes.
You may want to only blur the unwanted singer and the others using something like the bokeh effect using radial blur. See this demo: https://www.youtube.com/watch?v=oibzeyWXkvc . The mask is part of the same fx.
If the singers move all over in the video then the motion mask in Colordirector may be needed.
|
|
|
|
23.976 as that is the default of the GoPro and the default produce.
|
|
|
|
The LUT apply to all clips is not documented in the F1 key help files of PD365. No such thing in the earlier versions of PD. Good to know that there is this feature now.
|
|
|
|
If the above does not help then contact Cyberlink support.
|
|
|
F1 = Help, F12 = Subtitle Room. While in the Subtitle Room, Click the T to change the font, Style, and Size, etc.
F1 =ヘルプ、F12=字幕ルーム。 サブタイトルルームで、Tをクリックして、フォント、スタイル、サイズなどを変更します。
|
|
|
|
I do get the white i indication that an effect has been applied on my clips on the timeline after adding a LUT in PD365. I can then click the effects button and remove that LUT using the - button.
|
|
|
Thank you for supplying the original clip with the issue.
I have tested the original clip in my system and have no problems in making 5 cuts, rearranging them, playing them, render preview, removing segments, and it still plays properly in PD365. The MediaInfo indicates that the audio is variable bit rate from 96 to 194 kb/s. Variable bit rate in the audio has caused problems in the past especially with the newer versions of PD. I have converted the variable bit rate mp3 in my collections to constant bit rate before using them in PD starting with PD17 through PD365 using Audacity with FFmpeg.
I believe that Warry’s suggestion of converting the original mp4 files with that variable bit audio to a constant bit rate of 96 kbps using HandBrake should fix the issue before you place the original clip on the timeline. This is the easiest and best conversion.
|
|
|
A sample of the original and not the produced clip attached here will be useful for other users to test out on their systems. Use Mediainfo Online on the original clip that will have the problem after producing in PD20 and then download the mediainfo report as text. Attach it to your next reply. Link: https://mediaarea.net/MediaInfoOnline .
It is possible that the original is a recorded gameplay video. If it is then which recorder or capture was used…
|
|
|
Quote
Ok...maybe it was given for free when it came out, or maybe I upgraded, I honestly do not remember. It is installed under my license on my main computer, but I cannot seem to install it on my laptop. Is there anything I can do to resolve this?
Many thanks
Yes. According to this post you have the PD15DS which includes the Screen Recorder: https://forum.cyberlink.com/forum/posts/list/50584.page . Install it instead.
BTW: PD12 is not fully win 10 compatible but PD15 is win 10 compatible and it may have more of the tools and everything that you need.
|
|
|
|
Screen Recorder is NEW in PD14, the first version of PD to have it: See this listing: https://www.cyberlink.com/support/faq-content.do?id=18607 . None in any PD12 here: https://www.cyberlink.com/support/faq-content.do?id=16447 .
|
|
|
You could buy the earlier required version say from Amazon and then apply the upgrade that you bought. It may be better to contact Cyberlink support and tell them you wish to cancel the transaction and buy the full version for a higher price instead.
You have a 30 day money back guarantee only.
|
|
|
|
You need to increase the time duration of the title to slow it down.
|
|
|
See this article. R You Up for It.mp4 was supplied by PD18 and Win 10 at the time: https://www.exefiles.com/en/m4a/r-you-up-for-it-m4a/ . You can download a short .m4a file, rename it and put it in the PD18 Sample Clips folder to fix it. Samples of it I heard on the internet are okay from a Russian pc.
You can also load one of your projects, ignore the error and see if it loads fine. Save the project with a suffix like maybe 1 so you don’t overwrite the original.
|
|
|
I do recall that a well known senior contributor reported the 4 GB capture limit when using PD17 on his pc which would be a NTFS formatted drive. I reported different problems and do not believe all the issues were ever fixed. Support was aware of the issues then. Do not know if they ever fixed the 4 GB capture limit reported to them.
If you can prove that the drive used to record the capture is an internal drive in your pc, then you need to start a support ticket to maybe get it fixed.
I believe that the PD12 supplied with that VC-500 does not have the 4 GB bug but may not support the mp4 capture that you are using.
The copyright protected recording prohibited does not happen if you use the supplied ez grabber software. Your possibilities are endless.
|
