![]() ![]() In this second case, I suspect metadata set on the swapchain with SetHDRMetaData is not sent to the display itself, but is used by the Windows DWM instead to perform a color space conversion of the video content. ![]() if I keep Windows HDR turned on (as I have disabled the HDR auto-switch in JRVR) and use JRVR instead, then the same HDR10 video has different luminance and saturation than in the madVR case above if I keep Windows HDR turned off, and use madVR to play HDR video with a nVidia graphic card, then madVR uses the NvAPI to switch the display into HDR10 mode, and to pass HDR static metadata to it There's another thing that might warrant some investigation regarding HDR. As a humble suggestion, the HDR info and additional audio info should be accomodated in the current Compression field label itself justthe way like SOT tool does (for example:m2ts video(video: hevc hdr10+, audio:truehd + Dolby Atmos) (2)With more metadata in the library, can we take the indulgence to expect new HDR info field to be displayed in the Standard and Theater View(mentioning Dolby Vision/HDR10+/HDR10 ) just like FPS, Bitrate, Compression etc fields currently? Also, why can't we integrate SOT(Swag of Tools) relevant code/capability using mediainfo to add the Dolby Atmos/DTS-X info in MC itself instead of using the third party tool. (1)Does the Dolby Vision Enhancement Layer support (for UltraHD Blu-ray discs) include support for UHD m2ts rips/remuxes from the UHDs as well(say using DVD-Fab UHD ripper)? I am specifically asking this because earlier there was mention for limited support for mkv rips only for some Dolby Vision capabilities of JRVR although container format should not make any difference. You can check what we achieved in MC29 for JRVR here: Not every enhancement named here will be available right away. These are the planned changes, and will be developed during the lifetime of Media Center 30. HDR -> SDR tonemapping for video conversion and streaming More metadata in the library (HDR info, and more) Cropping information for semi-automated blackbar cropping Video Analysis, similar to the well known Audio Analysis (Maybe) Dolby Vision Enhancement Layer support (for UltraHD Blu-ray discs) (under investigation) Performance Presets for an easier setup Built-in deinterlacing independent of the GPU driver (and on all platforms!) In Media Center 30 there is still more already and more to come! It has matured into a proper high-quality video renderer which "just works". JRVR, or JRiver Video Renderer, was created in MC28 and further developed in MC29. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |