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 >
CyberLink PowerDVD 19 Audio Output?
Djhulp [Avatar]
Newbie Joined: Apr 22, 2019 23:50 Messages: 5 Offline
[Post New]
Explaining:
When I play a Blu-Ray with PowerDVD.
And go to Settings --> Video, Audio, Subtitles.
And Click on More Audio Settings.
I got different settings with CyberLink PowerDVD 19, what I used to have before.

When I use CyberLink PowerDVD 18, I have these settings.
Speaker environment: Use HDMI.
Output Mode: PCM decoded by PowerDVD & Non-decoded Dolby Digital/DTS audio to external Device.
I always use: PCM decoded by PowerDVD.

When I use CyberLink PowerDVD 19, I have these settings.
Speaker environment: Use HDMI.
Output Mode: Stereo.

Question:
So I was wondering is the Audio not worst by CyberLink PowerDVD 19?
Can you fix this into the next update, so I can use the correct Audio.
Jets2011
Senior Contributor Location: Canada Joined: Sep 29, 2006 05:26 Messages: 760 Offline
[Post New]
I don't have the same problems with PowerDVD 19. My HDMI audio output settings are normal. So there must be an issue with your audio card or PC. Especially when "Stereo" is not a possible output selection for HDMI according to the help:

https://help.cyberlink.com/stat/help/powerdvd/19/pc-mode/enu/11_02_02_more_audio_settings.htm

So I suggest updating your HDMI audio drivers or contact CS support.

Dave
Djhulp [Avatar]
Newbie Joined: Apr 22, 2019 23:50 Messages: 5 Offline
[Post New]
CyberLink PowerDVD 18:

CyberLink PowerDVD 19:
Only PowerDVD 19 gives this Error, never happend before not in PowerDVD 16,17,18.
Updating Drivers didn't help either, when PowerDVD 18 Plays Blu-Ray Audio is Correct.
I Have sended a Support Ticket, and just sended this url, so hopefully it will soon be fixed.

This message was edited 4 times. Last update was at Apr 23. 2019 10:35

Powered by JForum 2.1.8 © JForum Team