Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.


Go Back   Doom9's Forum > Video Encoding > High Efficiency Video Coding (HEVC)

Thread Tools Search this Thread Display Modes
Old 12th October 2017, 19:40   #5641  |  Link
Registered User
Join Date: Jun 2016
Posts: 28
Originally Posted by x265_Project View Post
All dynamic HDR requires external tools to analyze the color volume of the video, frame by frame, saving this metadata to a file. For example, Samsung contributed code to x265 enabling us to parse this metadata and insert it into the HEVC bitstream as SEI messages. We are always working with partners in the video ecosystem to find ways to make these kinds of integrations easier and more reliable for our mutual end-users.
Well that sounds very good. Hopefully you can achieve sth. sooner or later

With mkv not supporting DV you mean Matroska as the stream, right? Cause there are mkv containers with mpeg-ts Dolby Vision streams, that seems to work. But the matroska stream doesnt work?!

For example this one is an mkv: https://drive.google.com/file/d/0Bwx...dZaGtaVm8/view

Last edited by d3rd3vil; 12th October 2017 at 19:42.
d3rd3vil is offline   Reply With Quote
Old 12th October 2017, 21:22   #5642  |  Link
Life looks better in HD
SeeMoreDigital's Avatar
Join Date: Jun 2003
Location: Notts, UK
Posts: 11,189
Oh jeez @d3rd3vil,

That so-called 'sample' is a classic example where some idiot has simply changed the file extension from .ts to .mkv

The sample has not been muxed into the .mkv container!
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
SeeMoreDigital is offline   Reply With Quote
Old 16th October 2017, 12:23   #5643  |  Link
German doom9/Gleitz SuMo
LigH's Avatar
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 4,830
Just in case you do not yet know already: The intel C++ compiler under Linux is not compatible with glibc 2.24-9 and newer, because:

According to x86-64 psABI, xmm0-xmm7 can be used to pass function parameters. But ICC also uses xmm8-xmm15 to pass function parameters which violates x86-64 psABI.

As a workaround, you can set environment variable LD_BIND_NOW=1 by

# export LD_BIND_NOW=1
This seems to be exposed especially on CPU's with AVX support. Of course, x265 will mainly use hand-crafted assembly where possible. But where this is not yet available ... you may have to be aware of possible risks if a recent version of glibc is used (well, I am not sure if x265 uses that, but I believe it is a quite basic library).

There are bug reports from the glibc project and RedHat.

Please don't mind me if this issue is irrelevant for x265. I just assumed that a cross-platform project using AVX instructions may be among the possibly affected.

German doom9 / Gleitz video board
CQME – change the Matrix!
BeSweet 1.5b31 All In One | HeadAC3he 0.24a13

Rémoulade is spoiled
LigH is offline   Reply With Quote

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT +1. The time now is 04:56.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2017, vBulletin Solutions Inc.