Yet another cant bitstream: added challenge system bluescreens - Printable Version +- Kodi Community Forum (https://forum.kodi.tv) +-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33) +--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111) +---- Forum: Windows (https://forum.kodi.tv/forumdisplay.php?fid=59) +---- Thread: Yet another cant bitstream: added challenge system bluescreens (/showthread.php?tid=197007) |
Yet another cant bitstream: added challenge system bluescreens - mindedc - 2014-06-04 Help please! I'm running gotham on a fresh clean win 7 home premium on an old Core 2 Duo machine with a GT 620 card, 4g ram. I was originally running openelec but could not get bitstreaming working and I'm guessing edid is a player here so I wanted to be able to run moninfo etc.. My receiver is an integra dhc 40.1 which does support DTS-HD MA and TrueHD. I can bitstream just fine with a sony hardware player. Symptom is when I select wssapi audio and enable pass through I get choppy video (basically one frame every 30 secs or so) and no audio. When I look in the xbmc log I get the follwing entries: Code: 00:29:30 T:3448 NOTICE: CAESinkWASAPI::EnumerateDevicesEx: data format "AE_FMT_DTSHD" on device "DHC-40.1-1 (NVIDIA High Definition Audio)" seems to be not supported. When I run moninfo I get the following: Code: CE audio data (formats supported) Which blows me away...looks like moninfo thinks that my reciever supports DTS-HD and 192khz audio and XBMC (or windows?) seems to disagree. Am I correct in my assumption that this is EDID related or is there something else going on here? I can stream plain DTS so I'm confident that is working properly... would really like to get the HD audio formats working... I also get crashes when playing video and changing audio modes... Openelec didn't do that but perhaps thats something that happens with windows when you have your audio screwed up. I stepped back a version from the latest Nvidia drivers and that didn't seem to help the crashing any. Thanks! RE: Yet another cant bitstream: added challenge system bluescreens - jjd-uk - 2014-06-04 Can you post the full log please. RE: Yet another cant bitstream: added challenge system bluescreens - mindedc - 2014-06-05 (2014-06-04, 16:32)jjd-uk Wrote: Can you post the full log please. Certainly: http://xbmclogs.com/show.php?id=217900 This is a different session and it appears to lack some of the errors I was seeing before. The behavior I am seeing now is video plays at a smooth rate (some tearing), but no audio in pass through. If I disable pass through I get multichannel audio. The machine has been in sleep mode all day, no reboots or changes outside xbmc gui since the last snipet of log I posted. Interestingly no crashes. Thanks for the assistance! RE: Yet another cant bitstream: added challenge system bluescreens - mindedc - 2014-06-05 (2014-06-05, 05:05)mindedc Wrote:(2014-06-04, 16:32)jjd-uk Wrote: Can you post the full log please. FYI, I think the major change I did that improved frame rate was alter the render mode under settings > video > acceleration to DXVA-HA instead of just DXVA RE: Yet another cant bitstream: added challenge system bluescreens - mindedc - 2014-06-05 Ok, so I installed 13.1 and then defaulted out the settings under video> acceleration, audio, and video. I then used the recommended settings from the audio quick start guide on the wiki and I'm back to the original conditions, video is a slideshow, no audio to receiver. The receiver is now showing no signal where as before it was not displaying any text. The crashes in xbmc have stopped, however it consistently hangs on exit now. Here is my complete debug log: http://xbmclogs.com/show.php?id=218384 RE: Yet another cant bitstream: added challenge system bluescreens - jjd-uk - 2014-06-06 WASAPI is failing to open for DTS-HD format, Do you have exclusive mode enabled RE: Yet another cant bitstream: added challenge system bluescreens - mindedc - 2014-06-07 This is enabled on my system. My dialog box looks the same except its titled "DHC-40.1-1 Properties", but I reached it by doing properties on the Nvidia interface. |