Posts: 2,510
Joined: Dec 2012
Reputation:
216
Fwiw, driver 385.69 cannot retain 12bit when using custom modes but 385.28 can. Thus, it remains preferred, at least in my testing.
Yes, MPC can resume as can all other players. I think I already covered this earlier but to save you the hassle, I'll explain again using latest MPC-BE nightly as the example:
Options/Player
Keep history of recently opened files - check
Remember file position - check
Posts: 223
Joined: Jul 2016
Reputation:
2
2018-04-27, 23:02
(This post was last modified: 2018-04-27, 23:28 by Mount81.)
Hello!
I have found some strange states in the latest updated description:
You say KODI doesn't support UHD. -> As far as I know it does.
Quote: The special afedchin build only supports 3D MVC using HDMI 1.3. UHD requires HDMI 2.0 and is not backwards compatible. -> Sure is HDMI 2.0 100% backward compatible with 1.4 and thus also with 3D MVC. Where did you get this information? Or it only applies to the MVC KODI player? As far as I know the problem is the DP->HDMI 2.0a converter chip used on newer Intel platforms, and has basically nothing to do with HDMI 2.0 in general. And thus also won't affect any dedicated video cards with HDMI 2.0 outputs.
You also say that MPCHC-BE/MadVR supports 3D MVC. -> 100% Pure FHD Frame Packed MVC 3D sent right to the TV? No tricking and hicking? Great, at least an alternative to PDVD. I guess it applies both for 3D BD iso and MVC mkvs? What are the experiences, witch has the more reliable, better PQ and smoother 3D playback the MadVR solution or the PDVD? Would be also good to know if it also works fine with AMD cards, like the RX550.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
That's great Windows KODI supports UHD as far as you know. Perhaps you can explain exactly how we can play full UHD HDR.iso rips using the KODI internal videoplayer and harmonize all settings so no manual intervention with anything is needed when playing other formats or other players simultaneously as we are now. This includes specialized hardware, oversaturated video, and the need for Windows HDR setting to be enabled which wipes out the desktop. TIA. We just like to press enter on any and all titles with absolutely no limitations or caveats and have everything automate and work perfectly as intended no matter what it is or what player we'd like to assign as default or manually choose if desired and at the highest quality and versatility as possible.
I think you're misconstruing my words into yours and based on our last bout and I've no desire to resume. "Not backwards compatible" means UHD HDR requires HDMI 2.0a and is not backwards compatible with HDMI 1.4. UHD HDR needs HDMI 2.0a at a minimum. It is not going to render from HDMI 1.4. 3D MVC requires HDMI 1.3 at minimum, however an HDMI 2.0a port will pass 3D MVC from dedicated video cards. Unfortunately, Intel Graphics does not pass 3D MVC and UHD HDR from an HDMI 2.0a port simultaneously afaik.
Yes, MPC players and others with common components (LAV Filters and madVR) 100% support 3D frame packed MVC but main movie only. For complete menus, PowerDVD is required. Each handles any 3D format and iso and mkv as well as other containers. Both are reliable or we wouldn't be using both of them or any of the others. Imo, the madVR solution produces higher quality at the expense of some added CPU usage on top of the GPU usage. Yes, madVR hardware decodes taking most of the load but uses CPU software resources too. This increase in quality is user distinguished.... or not - dependent on hardware, settings, seating distance, etc. Each has enhancement settings, madVR offering much more customization. Each produces smooth playback although NVidia will drop a single frame every few minutes. Each auto switches displays into the appropriate 3D mode. I've no idea how AMD performs let alone how models perform other than what I've read which is good to great.
Posts: 223
Joined: Jul 2016
Reputation:
2
So does Windows KODI support 4K video playback, or not? I still think it does. Your statement was that it doesn't, and that's just false. No mention regarding HDR (as I know well, that the official KODI fork still doesn't support it). There are also many 4K SDR materials available. On the other had: DS Player (based entirely on KODI) with MadVR also supports both 4K AND HDR flawlessly and also almost all possible audio and video formats available at the moment (with the same level PQ as with MPCHC+MadVR). I'm not braking the flag here, or propagate beside KODI at all, I'm just trying to clarify.
Regarding 3D you'r explanation is incoherent and controversial, as first you still state that: HDMI 2.0a and is not backwards compatible with HDMI 1.4. (which is a general delusion), and than entirely controversial you acknowledge that: however an HDMI 2.0a port will pass 3D MVC from dedicated video cards.
I didn't pointed these out to debate or prove you wrong by any means, but your description is either imprecise or just based on false assumptions, therefore is false information and could cause misapprehension and doubtfulness (so did it in me for a moment).
And don't take these as offense or banter, and thanks for the info regarding MadVR MVC Playback!
Posts: 223
Joined: Jul 2016
Reputation:
2
2018-04-29, 06:52
(This post was last modified: 2018-04-29, 07:28 by Mount81.)
I still stand for every word I've wrote as they don't contain any false information. Contrary to your original statements, which still does.
Your post-explanations on the original subjects are over complicated and unnecessarily tangled with many subjective aspects and irrelevant diversion. And they still just over convoluted post-explanations. You seem to fals identify this matter as some kind of personal case with the conceited superior pride of the "unquestionable OP master" (with omnipotent knowledge, of course), which you seem to feel have been invaded here and that must be protected by all cost. And rather than simply acknowledge and step through lightly, you begin to deny and battle and blow up the case making the ant look like an elephant.
On the end I distinctly reject any of your too personal degrading and satirizing predication regarding my self and my intents, based on vicious presumptions and fueled by unnecessary pique. So much the more they have nothing to do with the subject and just seem to fill in the gap in the place of relevant reasoning with cockiness and personal affronting wrapped in something that's intended to be some smarty-like irony.
I won't waste any more word on this case.
Posts: 424
Joined: Sep 2016
Reputation:
25
Are there some news to faulty external player handling in Kodi v18? The latest messages i get are "External Player active" "press ok when playback is finished"!? But the movie never start playing.
HTPC: Windows 10 Pro 22H2, Zalman HD135, Intel i3-7100, GTX 1070, UHD ASUS BW-16D1HT
NAS: Xpenology 7.2 Update 1, Intel i5-6600
Posts: 2,510
Joined: Dec 2012
Reputation:
216
I tried v.18 two days ago but not with the new Windows update. There was no change from the previous months of testing. I doubt the Windows update will change anything. I'll test again in the coming weeks unless someone else reports positive results sooner.
Posts: 2
Joined: Sep 2017
Reputation:
0
Is it possible in MPC-BE (launched from Kodi), if the source file is of Full TAB format, to decode only one image from the two located on the same big image?
This way it could be possible to upscale only that part of the 3D file using madVR's excellent algorithms for my 4K TV as if it was a frame-packed format.
Kodi can play it as 2D now of course, but this way I would miss madVR's capabilities.
Any answer would be appreciated.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
I have no reason to toggle Windows HDR/WCG on/off using W10 nor the need for scripts to accomplish that? Be aware, none of these external players are using Windows HDR. They are using the video card private API's. You will notice it is never engaged during playback. Also, I know of no script or any other method that will automate Windows HDR mode. There are some differences how you are going about your setup. I would help you but the differences might be too far apart as well as unapplicable.
We each use 2160p and W10 v.1803.
I use a GTX 960 4GB and you a 1060 but the driver is shared.
You use DSPlayer. I use the official KODI. I don't think DSPlayer can call more than one external player but I could be wrong. I use 3 external players and the 1 KODI internal VideoPlayer.
I too demand menus for UHD. Our choices are PowerDVD which requires special hardware which I don't have nor you, or DVDFab Player which requires no special hardware. I use DVDFab Player v.3. HDR mode switches on/off automatically 1st time, every time. I have no experience with v.5. Perhaps if you are using the trial version, this auto switch is not performing? I assume since it works perfectly in v.3, it would carry over to v.5? In the event you have the full v.5 and it doesn't auto switch, I would ask them why because it should.
I too demand menus for 3D. To accomplish that, I use PowerDVD v.18 since DVDFab Player v.3 does not support 3D. Now that you have confirmed DVDFab Player v.5 does support 3D, perhaps it could eliminate PowerDVD for me provided the quality is similar and it will auto match refresh rates negating any manual intervention with resolution settings prior, during, after launching or post. I know PowerDVD doesn't.
I have no desire for Netflix and have limited experience. That HDR auto switching I can't comment. I only have the basic version launched from my panels app and I never use it. I also don't use MS Edge which I think is a requirement when launching from Windows.
So, understanding W10 HDR/WCG switch is not part of the equation, a script will not help you. What you need to do is figure out why your HDR mode is not engaged from DVDFab Player v.5:
I am presently using the latest nvidia driver offered. It switches HDR with no problems. Most no switch to HDR with nvidia was limited to early drivers from last year. Late drivers have always worked without fail. So, test and determine if HDR switches proper using Windows Explorer. Bypass your DSPlayer and your scripts to take them out of the equation. Right click your HDR file and select 'open with' and try FAB. FAB needs little to config but there are settings for HDR and 3D you should be familiar with. Make sure its settings are proper. It should open and switch. If not, consult FAB user forum or email support. You can also install v.3 since I can confirm it works just to confirm on your system and rule out FAB as the culprit. Lastly, try MPC-HC/BE with madVR and LAV Filters. This too switches HDR first time, every time but requires more precise settings than FAB. Above all, leave the W10 HDR/WCG switch OFF at all times. Once you can confirm your auto HDR switch working from Explorer, the rest is a process of elimination which will determine compatibility, limitations, bugs, or adjustments, mainly DSPlayer or your scripts. Let us know your results.
Thank you for the DVDFab Player v.5 3D capability report. I'm really hoping an error on your part is preventing it from rendering 3D if the display isn't manually switched to 1080p prior. Are you sure there isn't a 'match refresh rate' setting or something similar? V.3 has a 'always match to original video size' setting which I assume would auto switch resolution to 1080p when starting a 3D title negating manual intervention in the NCP.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
Currently I'm using 397.64. I don't know if settings survive a reboot? I know they didn't as of a couple driver versions ago. It was for retaining the 12bit setting that reverted to 8bit. I'm using 8bit now to avoid banding since nVidia has no 10bit setting and my display, most displays, truly only handle 10bit but our choices are only 8bit or 12bit so, until they give us a 10bit RGB setting, I'll be using 8bit. If your display handles 12bit, by all means use it but you'll need an older driver to retain it. In the mean time, this is why I don't care if 12bit doesn't survive a reboot and defaults to 8bit. I am having an AAC audio problem with this driver and a bunch previous. I had it in the past and by some miracle fixed it. For the life of me, those same fixes won't work again. I will probably end up going back to 385.28. I 'Use nvidia Color Settings' RGB FULL 8bit.