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 >
It is being used for encoding in the "Produce" module, it's just that your CPU is the bottleneck and probably running 100% as the CPU has to do the color retouch and video stabilizer prior to handing to the encoder. This color retouch and video stabilizer are computationally intensive in PD so the GPU is just loafing waiting for the CPU to give it something to encode.
Your requirements say nothing about audio, my example did not use TTS, just AAC 2 channel. You can always select the "+" sign next to profile name and change video and/or audio bitrate to suite your needs. Change 40Mbps video bitrate to 20Mbps if that's what you prefer for smaller file.
The BD spec does not allow AAC5.1 audio, that's why no option in the "Create Disc" module, it's simply not compatible when creating a BD.
If you are talking the "Create Disc" module, correct, as I indicated prior, PD removed Nvidia encoding feature since PD14 in the "Create Disc" module for BD H.264.
I guess as tomasc indicated prior, you have enough info to start experimenting and resolve what works for you and your playback equipment.
Jeff
Jeff and tomasc thank you very much for the reactions.
The Audio must indeed be 5.1
In PD14 it was not necessary to change a profile. Therefor I didn't even knew it was possible!
RTFM So now I will proceed with MP4 1920x1080/28Mbps AAC5.1
GPU is used and the processing speed is good.
Video and sound quality are good and I can play it on my systems.
Again thanks all for helping me out.
This topic is resolved for me.
As mentioned prior, the GPU can encode m2ts 50p H.264 from the "Produce" module, pic attached.
Your RTX3060 will not hardware encode any "i" settings as the hardware does not support that. Buy a different GPU that supports "i" encoding if that was your use case.
Jeff
Thank you for responding. Much appreciated.
The GPU does not always code m2ts.
As a sample file I used 2 clips. In both clips the Retouch functions Video stabilizer and audio noise filter are used.
There is one crossing. (I have a Dutch version so I do not know the exact English words for it)
Total length is 26 seconds.
These are my requirements:
I want 1920*1080 50i or 50p
I don't want TTS for audio because it results in muffled sound. (This is the only selection possibility in your example)
I want to avoid mp4 because I only can select 40 mbps resulting in a huge (1,5x) file
That narrows it down to m2ts or mkv.
MKV I can select H.264 AVC 1920x1080/50p 28 Mbps and choose between AAC 5.1 or DTS 5.1.
Unfortunately MKV gave problems with playing on my media NUC.
So m2ts it should be. But due to the restriction of not using TTS the only way I can produce m2ts with DTS5.1 is using the workaround with BluRay production.
There I can select H.264 with DTS 5.1 (Why not AAC 5.1?)
Then I can choose between 50i with 24Mbps and 50p with 28Mbps.
The GPU will not be used for 50i due to a decision made by NVDIA.
When I produce the H.264 HD1920x1080/50p 28 Mbps the GPU encoder is NOT used. It takes 14 seconds to produce a clip of 26 second.
Then I go to the BluRay folder STREAM and copy the m2ts file.
I anyone has a better suggestion I would be glad to know.
It was unclear to me what you meant by BluRay stream in remarks. It's listed for TT11 with mkv container and H.265 which PD simply cannot do in the "Create Disc" module, only in "Produce"
CL removed Nvidia hardware encoding in the "Create Disc' module for basic H.264 BD disc creation at a PD14 patch because of playback issues for some users and they never put the effort in to resolve, they simply removed it as a option.
Jeff
The BluRay remark was not in the correct line. It should have been for TT8-10.
It was back and forth testing in all the different settings. It was a bit challenging to place the data in the list
I find it still a pity that it is so difficult to preserve the excellent quality of de clips from my Sony Camcorder after video editing.
In PD14 I had good result with m2ts 50i ~16Mbps Dolby Digital 5.1
The closest to that is TT8 where I had to had to use the BluRay workaround. Strange then is that I must play it in VLC because there is no sound in the standard Windows10 app Movie and TV. Where Dollby Digital 5.1 is no problem.
PD14 on my i7 3rd gen PC took a lot of time to produce.
That's why I spent 1800 Euros for a new workstation and PD19. Sofar only the producing speed is far better. Although it would be better if the GPU encoder also could be used for m2ts 50i and 50p instead of only for mp4, mkv or 24p.
The three days I spent sofar in searching for comparable quality didn't give me very much fun neither spectacular result.
I will probably go for (TT10) BluRay m2ts H.264 50p 28mbps DTS5.1 or (TT12) mkv H.264 50p 28y AAC5.1
Anyway thanks all for the help and specially optodata for the hint to the hotfix.
I don't see a lot of non-logical attributes in your table on first scan, just a few but probably more user error.
1) TT5 file size 68MB is odd, however, stated profile of m2ts, H.264 50i 11Mbps is not a default profile so probably some entry error??
2) TT8-10, Don't believe DTS5.1 will be available for the m2ts container, entry error??
3) TT10, HWC should be available, probably a local platform issue
Hardware decoding and encoding are two entirely different feature sets. Many more formats are applicable to decode with a RTX3060 vs encode, that is the hardware side.
Jeff
re the table.
TT5 Typo: 11Mbps should be 21Mbps as reported in the attributes of the file. Setting was 24Mbps.
TT8-10 Were produced as a BluRay disk where I extracted the m2ts Stream. No Hardware Coding selectable. There it is possible to choose DTS5.1. My question is then: WHY NOT in the standard file production? Safes a lot of hassle.
TT10 see 2.
Hardware Coding is not always selectable although and I noticed that the GPU always is activated for Decoding and sometimes for Encoding, I wrote down the max. percentage of the GPU usage if applicable. I can only guess why there is no maximum usage of the GPU.
I only have a passing experience working with anything beyond stereo clips and I hadn't considered how many limitations and interactions there are between the various technologies, Windows versions and PD versions. I clearly must have the inbox codec installed because I can import DD5.1 clips and produce with DD stereo, but it sounds like that's the end of the line.
You are quiet right. The variations and limitations are numerous and IMHO not always logical.
I did some testing (not scientifically) and I would like to share the results as in the attachment. ( i dont know how to put it in this text.
I took a clip with a lot of fast moving action (wakeboarding and surfing). The result was tested on my PC i7 10700 32GB with RTX 3060Ti and Intel NUC i5. I used Windows Films and TV, Windows Mediaplayer and VLC.
QuoteGreat news! the HotFix just posted by PDM lets PDR365 play DD5.1 audio again on my Surface Book 3 even with both problematic KB updates installed
This is indeed great news!! Thank you for sharing this in this topic.
After restoring Win10 with PD19 and installing the Fix it works!!!
Sofar I only focussed on the Editing part.
Now I am a bit puzzled on the producing part.
I can't produce m2ts with DD5.1
I can produce a BlueRay stream with DTS5.1. Sound Quality is nearly the same as DD5.1 but cannot play sound in Windows 10 (need another player)
I can produce MP4 with AAC5.1. Video 50 frame/s. Sound quality is less than DD5.1 or DTS 5.1 and the file size is huge.
You have to click on the selected update. I'd already uninstalled it so I couldn't show that in my screenshot.
Sound is present for me with both KBs uninstalled:
Very frustating to hear the sound in your clip. I also see the waveform in the audio chanel in the track.
Yes, I did click on the selected update. No Update button appeared.
The update was in the list of Microsoft Windows.
In that list none of the updates can be unistalled on my system.
If I select other updates higher in the list than the Uninstall button appears.
I can't show you because now I have a clean install of Win 10 home (restore in a HP Omen system)
I see that you have PD365. Maybe there is a difference between PD365 and PD19?
I went back to a Win10 installation without the KB5001330 plus KB50000842.
I checked that in PowerShell with: DISM /online /get-packages
Sounds like you may not be on the correct Settings page. Go to Start > Settings > Update & Security > Windows Update > View Update History > Uninstall updates. That should bring up this tool view where you should be able to select and uninstall KB5000842:
De
I was on that page but neither as in your example the button Uninstall appears next to Organize.
How did you do it if there's no button?
meanwhile I restored to standard Win10.
I postponed the updates so the fore mentioned updates are not installed.
then I installed PD19 and patch 2808.
Result is very disappointing after all the work: No sound.
I posted a sample file as attachment earlier.
can anyone test this if they can hear sound?
thanks all for your effort.
I contacted the technical Helpdesk. So far the solutions they came up with did not work.
In another thread I read that the licenses of Dolby expired in 2016.
why then was Dolby support removed?
in PD14 it works without a problem.
Most (better) cams from Sony still produce clips with Dolby Digital 5.1
also in Win10 I can play m2ts Dolby 5.1 without a problem.
QuoteI've done some more testing, and on my main desktop system it's clear that KB50000842 (from around Mar 31) is also involved.
As far as I can tell, it's the combination of the latest PD365 build plus KB5001330 plus KB50000842 that caused DD5.1 audio to disappear in PD - so people will either need to use a restore point or (manually created) system image backup to go restore their system to the way it was around Mar 30, or use the DISM command to remove KB5001330 then use the normal uninstaller as described in PDM's notes above to uninstall KB50000842.
Only after I'd removed both of these updates was I able to hear DD 5.1 audio in PD365. I'm using the test clip from the other thread.
Note that you'll also want to pause all Windows updates for at least a couple weeks so there's time for these issues to settle and possibly be patched.
How did you remove KB5000842?
If I select the KB then I have no Uninstall button.
Users are advised to uninstall certain Windows 10 cumulative update: KB5001330 manually by following steps and check if the condition persists:
1. Open Start menu and click on the cog icon to open Settings > Update & security.
2. Click on the View Update History
3. On the Windows Update history page, click on Uninstall updates.
4. On the prompt screen, user will be presented with a list of recent Windows Updates. User can search “KB5001330” through all of the installed/active updates using the search box at the top right.
5. Select the update.
6. Simply click the Uninstall button.
7. Click Yes on the confirmation box to uninstall the update.
8. Reboot user system to finish the process.
9. Open PowerDirector
10. Import the video file and check if the condition persists[/list]
Cheers,
PowerDirector Moderator
Unfortunately, the problem persists after uninstall of KB5001330
Cyberlink.com uses analytical cookies and other tracking technologies to offer you the best possible user experience. By using our website, you acknowledge and agree to our cookie policy. For more information on cookies or changing your cookies settings, read CyberLink’s Cookie Policy.
