Quote
IMO, audio bitstream is not rocket science and quite simple and all of processes are about hardware capacity identification and bypass in the entire audio pipeline. Less chance that a player software can go wrong, but not on the hardware or audio pipeline.
"IMO" consider this...Bitstreaming/decode an audio track is more complexing than you might think ... IMO..
Why, only by taking an original → UNTOUCHED media file from an bd or other source and remuxing it into another container... lets say.. mkv 2 *.ts or mkv 2 *.m2ts an more common and bluray compliant container ..
By doing JUST that ↑, can cause all sorts of audio problems... Remember → Untouched A/V that would play (BITSTREAM) flawless in any device or software before remuxing !! Mind u Remuxing... no RECODE of any sort... just merging the tracks !
so, u telling me audio isn't complex...
Come to think of it, the Cinavia protection awhile back still seems to be like rocket science to me , since it still hasn't been cracked/beaten ..
And only can be worked arround / "defeated" by using "non-infected" audio tracks from other sources !!
That or by playback the infected file on an non-cinavia infected hardware player / software to emulate the real deal ..!
Quote
It's great your A/V receiver can play Dolby ATMOS audio, but, at the moment that the audio output mode fall to powerdvd decoding, did Windows still see your HDMI receiver capable of decoding dolby digital audio exactly?
Wy would windows changes its mind mids playback suddenly..!?
After, having my receiver acknowledged as an capable 7.2 DD+ system !?
Has windows become A.I and self aware these days ... LoL!?
Will it zap me if i rollback an update .. LoL !
No, i have double checked that while pdvd runs in the background...
Win still sees my receivers capabilities properly..
Quote
I've seen some cases that the PCM decoded mode occurred because the HDMI audio output device's compatibility work instably on some PCs at the playback moment. Sometimes the audio device works normally to show the hardware has Dolby or DTS decoding capability in Windows, but sometimes not.
Meaning?
Quote
You did find a probable trigger, which is "bitrate" in your case.
But, the moderator mentioned Dolby TrueHD bitstream, its bitrate is usally higher than dolby digital but the bypass workable in powerdvd, too.
Well, bitrate should't be any issue as long you respects the max limits off certain audio formats i.e : ac3 → 640Kb/sec 5.1 channels , EAC3 DD+ 6Mbit/sec / 15.1 Channel etc...
But after torough testing , it seems different bitrates causes the system not to output / bitstream sound !! Even at Lower Bitrates , Even tough the bitrate from that DD+ Audio track is still BD/DVD compliant according to the official pages i have read ..;
Quote
Mystery.
MPC-HC, VLC player or many other open source player software has their own ways to flexibly workaround many compatibility problems as they are not commercial software and not regulated by Dolby or other vendors additionally.
I won't put them on the same basis in the comparison. I'm wondering it won't help your concern in powerdvd.
I get that, you can throw just about anything at mpc and many other players.. it ALL will just play fine, regardless of the BD/DVD strict compliant standards...... .I - M -O
That's why i don't use mpchc to emulate an hardwareplayer to exclude any issues just and because of that strict compliant standards hardware players have ...
Cheeers,
This message was edited 5 times. Last update was at Aug 11. 2023 17:41