Reply to thread

Message: <blockquote data-quote="Scythe42" data-source="post: 1006074" data-attributes="member: 95833">This is a DirectShow issue. HDMI is an external audio renderer. It gets removed when you turn off connected devices. MP does not properly handle this at the moment during playback. What is crashing here is the DirectShow graph and it takes MP down with it as information is still pumped to the not connected audio renderer anymore. You can force this with nearly EVERY player out on the market that uses DirectShow. Only a few actually have some decent DirectShow managemnt. What does not use direct show is not affected. DirectSHow itself is not developed any further by MS, therefore no additional treatment for specific issues that came up with HDMI were introduced, like dynamically sending streams to /dev/null if an audio renderer is gone. Media Foundation is a bit better here, but lacks proper codec support and will so for many years to come. There is an option to "stop playback on loss of audio renderer" that should help some people but not in all scenarios. Some devices (they ones 4+ years old especially) have very often very bad HMDI implementation. With recent devices there should be zero problems on the hardware front as manufacturers have decent code now from their middleware providers / updated SOCs they use in case they do not provide their own software at all. Naturally they do not put out firmwares for older devices as soon as a new model comes out. But we all know that. So the fixes only came in with newer devices over a couple of generations. The device manufacturers are just terrible on the software front. What helps with such hardware are decent HDMI switchboxes. Stuff like a DVDO Edge, Dr. HDMI or what ever. These are just taking over the HDMI handshake part and correct what other devices are doing wrong. Such problem on a firmware level cannot be solved the on Windows side. So often, finding some order how to turn on devices might help. But the root cause is bad implementation of HDMI handshakes in the device itself. The crashing can be prevented on the MP side but firmware issues cannot. There is no way in Windows to hook yourself into the HDMI handshake sequence and correct issues or override it. This could be done by the GPU drivers, but they don't do it. Their standpoint is fully understandable. Sad, but you cannot expect AMD for example to deal with issue of an Onkyo receiver or an LG display or Philips settop box. But this needs to be solved inside the DirectShow code that when an "error" occurs playback is stopped as it cannot continue. If it is resumed later automatically, rebuilding the graph without an audio renderer or whatever is a different thing. But the error handling of the graph needs to be added. PS: LOAD "WINDOWS",8,1 - I love this meme at the moment for obvious reasons.</blockquote>

Verification