forget what people have told you, we need to get you smooth first, you can experiment later with other settings. Set your desktop to 4:2:0 YCBR 10 bit, this should eliminate any bandwidth issues, you wont notice any difference in quality anyway.
The reason you have high rendering is likely MADVR settings and refresh rate, wipe you MADVR settings and start again. Leave everything at default and go back to COPYBACK decoding.
make sure you've turned off MADVR refresh rate switching and turn it on in KODI DS. If you have the KODI GUI set to 2160p it will upscale everything to that resolution so there is nothing more to set.
Dont forget windowed mode in KODI DS.
Start with unchecking enable automatic fullscreen exclusive mode in general settings. madshi recommends windowed mode in Windows 10 because Windows is moving away from supporting exclusive mode. It should still work but can fail with some GPUs. It’s failed for me on the wrong driver. It probably won’t fix the problem, but it’s easy to try it.
And there are now four users I know who’ve had issues with the new D3D11 decoder. Does DXVA2 copy-back work for you? Again, I don’t think this will fix it, but those are the only settings in the media player I can think of.
mclingo’s suggestion to use a batch file to wake the computer might be the best option.
(2018-04-03, 19:54)Bibio Wrote: [ -> ]mkohman, is HDR engaging (a small box on screen usually flicks up for a second or two saying HDR) on your JVC when you play an HDR 4k UHD movie and have madvr HDR set to auto?
My HDR is set to Pass through with metadata checked .. I will post a full screen shot of all my settings tomorrow when I get a chance make thing easier
(2018-04-02, 15:48)Bibio Wrote: [ -> ]Fourth: Kodi -> settings -> system -> audioMy applied settings.
Interaction of sound devices between LAVaudio/DSPlayer and Kodi.Modern GPU’s have built in codecs which can act like sound devices via HDMI so can be confused with motherboard sound devices or add-on sound cards. GPU codecs are reported to windows as a sound device and as such will be in your windows sound device list.Having different sound devices can cause confusion as to which one to use. If you are using the onboard motherboard sound device or a high quality add-on sound card to gain higher quality audio for use with such things as headphones then things can get a bit more complicated. I’m not going to cover this in this mini guide.Kodi -> settings-> system -> DSPlayer -> Audio Renderer (see screen capture in part Three), set this to the ‘sound device’ you want DSPlayer to use with LAVaudio. Mine is set to ‘default’ as this is the default sound device in windows. Due to turning off my motherboard onboard sound device in the BIOS I only have one sound device which is the GPU and as such is the default sound device in windows. Look at your windows sound device list and work out which one is the GPU and set DSPlayer to use that to send HD audio via HDMI to your AVR. Your AVR should now auto switch codecs. If not then you need to set your AVR properly.The problem, Kodi does not know if LAVaudio is being used in DSPlayer as Kodi does not know about LAVfilters. So you have to tell Kodi not to use HD audio codecs on the HDMI sound device. This is especially true if using WASPI. So we need to turn off WASPI and all HD audio codecs in Kodi then use LAVaudio filter to turn on bitstreaming for the HD audio codec’s for DSPlayer. This will affect the use of videoplayer but lets face it we are not using Kodi-DSPlayer to use videoplayer.If you don’t turn off HD audio and WASPI in Kodi then things can get rather confusing regarding audio switching and can ‘lock’ audio output as LAVaudio and Kodi have a handshaking battle when you exit DSPlayer after watching a movie.When the above is set properly you should get no ‘locking’ of HD audio exiting playback from DSPlayer back to the Kodi interface.Depending on how you have set Kodi -> settings -> system -> audio -> number of channels will default Kodi interface to use them, it matters not how many. I use 2 so not to have sound out all my speakers while browsing Kodi interface. I also used ‘fixed’ for output configuration as it automatically disables WASPI and HD codec’s. This seems to make switching that little bit faster/stable.
Thanks for this.. this section is a little confusing .. I always have Wasapi:default selected on mine.. Is this incorrect? What shall I have it on? I do bitstreaming to my anthem.. thanks.
i know that you only use your HTPC for watching movies so my best suggestion would be to turn off the onboard sound device in your BIOS.
or right click the speaker icon on your taskbar and then choose playback devices from the list.
in the list you will find a device called "AMD High Definition Audio Device" (it may be called something else) with a icon of a monitor or box to represent your AVR this is usually your GPU.
you need to set your GPU as your "default device" sound device.
now start kodi and go to settings -> system -> audio and copy over the settings in the first screen capture above.
now go to settings -> system -> dsplayer -> filters "-audio decoder" and copy the settings in the second screen capture above. this is your LAV audio.
restart kodi and play a movie. on exit of playback you will find that it helps switching of audio on your AVR.
explanation:
you dont need HD audio while browsing the Kodi interface (GUI). if you set WASPI and HD audio then Kodi might 'lock' the HD audio on dsplayer exit.
this results in HD audio codecs still being displayed on your AVR display, sometimes it "unlocks" when you start to brows kodi again or after a small period of time has elapsed.
you are basically telling kodi to drop audio to stereo while browsing kodi. but when playing a movie the LAV audio takes over until exit of playback at which point kodi takes over again.
Thanks.. I believe mine has always been like that.. My main device in Sounds is shown as the AMD but under the name of the Anthem AVM60 which is set as my default. In kodi in settings for Audio mine is set to wasapi default.. There is wasapi (amd avm 60), wasapi default, direct Sound default and Direct Sound (avm 60 amd).... Which one are you suggesting to choose? Thanks
"directsound default" if your GPU is set to the default sound device in windows. direct sound (avm 60 amd) is the GPU sound device. give both a try. the correct one will be when you hear sound (clicks and feedback sounds) while browsing kodi.
if "directsound default" works then keep it as that.
do not use wasapi.
(2018-04-04, 05:33)Bibio Wrote: [ -> ]"directsound default" if your GPU is set to the default sound device in windows. direct sound (avm 60 amd) is the GPU sound device. give both a try. the correct one will be when you hear sound (clicks and feedback sounds) while browsing kodi.
if "directsound default" works then keep it as that.
do not use wasapi.
I hear the click sound etc in kodi with wasapi. I have always used Wasapi, for some reason I thought WASAPI was far superior. Why are you saying do not use WASAPI what is the logical explanation for this please? Also whats the difference between Direct Sound and WASAPI? Thanks.
Isn't WASAPI exclusive as in there is no interference with other sounds from Windows.. I have ready that WASAPI is superior and should be used but I may be wrong...
wasapi is prefered to be used over direct sound, as it bypasses windows audio mixer giving a purer sound.
As far as sometimes kodi not releasing the audio device after a video, that may be the "keep alive" setting in kodi and not anything lav audio codecs or dsplayer is doing.
Hey Guys... GREAT NEWS
... I hope that I do not jinx myself in saying this but I think my problems have gone away thanks to all your help
.. So basically the first thing I did was as @Warner360 suggested.. I turned off Fullscreen Exclusive mode and it has not given me any black screen at all .. I have played around for approx 1 hr in and out of multiple 1080p then 4K then back to 1080p movies.. upscaling is working fine and no black screens or system hang.. Obviously time will show but it has never been as stable as now with the new settings etc and 4K etc.. so all good
I also enabled force fullscreen exit on end on playback stop (I can't remember exactly what this option is called) but I enable that too.
By the way DXVA copyback doesn't seem to be working for me anymore.. its rendering times are around 60-100 so it's all choppy.. I think this is because my desktop is run at 4K resolution thats probably why.. so I just use D3D11 Automatic (Native) which works a treat..
All I need to know for sure now is whats the best option to leave the Desktop in ?
1 - RGB FULL 4:4:4 which only allows me 8 bit as desktop but when playing movies it says 12bit in the JVC info menu,
2 - YcBcR 4:2:2 or 4:2:0 which both allow me 8, 10 and 12 bit and in the JVC info they display only as YUV
there is also other options like RGB Limited and YcBcR 4:4:4
Too many options to choose from.. Just want to know the purest one and the one with the least conversion ... Thanks and would appreciate if you could help.. Thank you.
I have no issues with FSE with my system, I need it for 3D, surprised this fixed the black screens, are you sure it did, did you also enable windowed mode and change refresh rate switching to KODI DS or have you not done that yet?
i'm currently using 4:4:4 Full RGB 8 bit but this is only because I know my system is stable and is switching correctly between 8bit 1080p stuff and 10 bit HDR stuff, when I'm having issues or i'm trying new settings I tend to I put it back to 4:2:0 10 bit, I genuinely see no picture quality difference at all on a 65 inch OLED from 8 ft away.
I was getting HDMI dropouts with 4:2:2 10 bit so I scrapped that, something in my chain struggles with the extra bandwidth.
keep audio device alive and send low signal noise is to keep subwoofers that have auto standby "alive".
why do you need to use HQ audio while browsing kodi?
if you are using bitstreaming via LAV audio and you exit playback in dsplayer then kodi can still hold onto HD audio if you use wasapi.
the lower part of of the audio section when wasapi is set, is for use with videoplayer and not dsplayer.
the problem is kodi can get confused...
there is a lot of confusion regarding some of the settings inside kodi as they are used for videoplayer only and not dsplayer.
same goes for some of the settings in dsplayer when using madvr.
you dont have to use madvr with dsplayer. its just that if you do you get much better PQ if madvr is set up properly.
same goes for LAV filters you dont need to use them you can use something else.
think of dsplayer as an external player like for instance mpc-hc except that you can configure some of the settings within the kodi interface (GUI) for dsplayer.
With that option Kodi sends a low level single to keep those sound devices alive.
Regardless of a video playing or not.
I always use wasapi, but I also always turn off kodi system sounds, because I find them annoying. So that's maybe why i don't have any issues.
I prefer wasapi. In general, it is perfectly fine to use. But also may be the case where I have the kodi sounds off.
I also prefer to manually select the sound device instead of system default. As a lot of times with a driver update the system default sound gets put onto another device, and I end up with no sound when I start a video. Which you can imagine would be rather annoying.
"Windows Audio Session API (WASAPI) exclusive mode output support, allowing bit-exact output and muting all other sounds. Windows Vista SP1 or newer required."
"WASAPI provides exclusive access to the audio devices, bypassing the system mixer, default settings, and any effects provided by the audio driver. Unless your audio interface has an ASIO driver, WASAPI is the recommended Audio Output Mode for Windows. WASAPI replaces all Microsoft Windows legacy output modes including Kernel Streaming and Direct Sound."
The bit-exact output and muting all other sounds is why wasapi is preferred over direct sound. Direct sound can manipulate your sound, and can also over ride any sound being sent.