More > JRiver Media Center 29 for Windows

NEW: Enhancements in JRVR Video Renderer

(1/5) > >>

Hendrik:
JRVR, or JRiver Video Renderer, is our new in-house cross-platform video renderer, introduced in MC28.

You can find general information about JRVR here on the forums, or on the wiki.

Development continues for MC29, with a lot of improvements already here, and more to come!

Enhancements in MC29

Dolby Vision support
  - Support for Dolby Vision Profile 5 (which would otherwise play in wrong colors)
  - Support for Dolby Vision Metadata in Profile 7 and 8 to enhance the HDR10 image for improved quality
  - No Dolby Vision capable display required, all processing is done in JRVR

Improved HLG HDR support
  - HLG can now be converted to HDR10 for pass-through to the TV

Improved HDR Tonemapping
  - New and re-designed algorithms for a more consistent experience

Shader Caching
  - Significantly reduces startup latency by caching shaders, instead of re-compiling them for every video

Quality, Performance, and compatibility improvements across the board
  - Support for rotated videos (eg. mobile phone recordings taken in portrait)
  - DVD playback now uses hardware deinterlacing
  - Zero-copy hardware decoding for improved performance on integrated graphics (iGPUs)
  - Improved dithering and color handling
  - New performance options for low-end systems

Subtitle Improvements
  - Entirely re-designed subtitle support for playback reliability and performance improvements
    - Subtitles are rendered on a worker thread now and properly pre-rendering several frames in advance
    - Video has priority, and will avoid droping frames due to missing subtitles, worst case subtitles might be missing or delayed
  - Significantly reduced CPU and GPU usage with subtitles by only handling the actual area with subtitles, instead of the full frame
  - Bitmap subtitles (Blu-ray, DVD, TV) are no longer scaled in software, and instead handed to JRVR for final processing
  - HDR menus and subtitles on UHD Blu-rays are now properly color mapped
  - Significant performance improvements for SSA/ASS subtitles, allowing playback of even the most complex subtitle streams

And we're not done. These are only the changes so far in Media Center 29.  More on the way.

Further Reading
Additional information about JRVR in MC29 is available here:
https://yabb.jriver.com/interact/index.php/topic,131974.0.html

Hendrik:
<reserved for future changes>

flac.rules:
This sounds very good, can you give a bit if a rundown on what dolby vision support actually means? The whole thing is a a bit confusing to me, what happens if a movie has dolby vision, I play it on MC, and output it to a display that

A. Supports HDR10 and is 1000 Nits max
B Supports HDR 10 and DV and is 1000 nits max.
C. Is SDR (lets say 200 nits max?)

And how is the 3 different from the same situation on a 1. HTPC with madVR, 2. A UHD-blu-ray player.

Sorry for the newbie questions, but while i think i grasp HDR as a concept reasonably well the technical implementation is not super-clear for me.

Hendrik:
A and B are identical. Dolby Vision support in the TV is not required, and not used. And C is just like any other HDR file, the content is converted to SDR.
madVR would not use Dolby Vision at all, and just give you the HDR10 fallback image (or in case of Profile 5, something unwatcheable). A Blu-ray player would let the TV do the DV processing instead of doing it itself.

JRVR does all Dolby Vision processing itself. The data is used to improve the HDR10 image, and then send it to the TV - as normal HDR10, so no special support in the TV is required (nor used if present).

Not all features of Dolby Vision are used yet, for example the Enhancement Layer (EL) from Blu-ray discs cannot be used yet (only Blu-rays remuxed into MKV are supported, and only partially as well, eg. only metadata, no enhancement layer), and other metadata to aid in the conversion to SDR or a HDR-HDR conversion (to a lower brightness) are not used yet.

flac.rules:

--- Quote from: Hendrik on March 07, 2022, 09:34:42 am ---A and B are identical. Dolby Vision support in the TV is not required, and not used. And C is just like any other HDR file, the content is converted to SDR.
madVR would not use Dolby Vision at all, and just give you the HDR10 fallback image (or in case of Profile 5, something unwatcheable). A Blu-ray player would let the TV do the DV processing instead of doing it itself.

JRVR does all Dolby Vision processing itself. The data is used to improve the HDR10 image, and then send it to the TV - as normal HDR10, so no special support in the TV is required (nor used if present).

Not all features of Dolby Vision are used yet, for example the Enhancement Layer (EL) from Blu-ray discs cannot be used yet (only Blu-rays remuxed into MKV are supported, and only partially as well, eg. only metadata, no enhancement layer), and other metadata to aid in the conversion to SDR or a HDR-HDR conversion (to a lower brightness) are not used yet.

--- End quote ---

Ok, thanks, I think i understand how it works. I am very happy to see all the improvements in JRVR, it certainly seem to be one of the main reasons to upgrade.

Navigation

[0] Message Index

[#] Next page

Go to full version