profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/quietvoid/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

quietvoid/hdr10plus_parser 67

CLI tool to read HEVC files and parse dynamic metadata.

quietvoid/dovi_tool 59

Stuff about Dolby Vision

quietvoid/subtitle_tonemap 9

Tonemaps subtitles to lower brightness

quietvoid/vspreview-rs 6

minimal VapourSynth script previewer

quietvoid/BitrateViewer 4

Bitrate/time graph

quietvoid/hevc_parser 4

HEVC format parser

quietvoid/bitvec_helpers 2

BitVec based bitstream reader and writer

quietvoid/vs-placebo 2

libplacebo-based debanding, scaling and color mapping plugin for VapourSynth

quietvoid/av1parser 0

AV1 video codec bitstream parser (not decoder!)

quietvoid/dlb_mp4base 0

The Dolby MP4 streaming muxer (dlb_mp4base) is a software implementation of a muxer of fragmented or unfragmented ISO base media file format (mp4). It supports muxing of Dolby Digital (AC-3), Dolby Digital Plus (E-AC-3), and Dolby AC-4 audio formats as well as Dolby Vision.

issue closedquietvoid/hdr10plus_parser

Compute metadata scene related information

Samsung's HDR10+ tools expect scene information to be present for a valid JSON file.

Should be present for every metadata frame in SceneInfo:

SceneFrameIndex: Index of the frame relative to the current scene (starting from metadata change) SceneId: Incremented scene index (Id) when metadata changes SequenceFrameIndex: Metadata frame index (total length should be number of frames)

Should be present at the JSON root:

"SceneInfoSummary": {
    "SceneFirstFrameIndex": Array of `SequenceFrameIndex` where a metadata's `SceneFrameIndex` is 0
    "SceneFrameNumbers": Array of the number of frames (length) of every scene
}

closed time in 2 hours

quietvoid

push eventquietvoid/hdr10plus_parser

quietvoid

commit sha 468cac224571b6bfcfba4abd3c66f83ce9085cde

Add JSON scene information (#33) Implements #32

view details

push time in 3 hours

PR merged quietvoid/hdr10plus_parser

Add JSON scene information

Implements #32

+1413 -643

0 comment

18 changed files

quietvoid

pr closed time in 3 hours

push eventquietvoid/hdr10plus_parser

quietvoid

commit sha b38b3569df8f71a58280009a501fcf719098089e

Add JSON scene information Implements #32

view details

push time in 3 hours

PR opened quietvoid/hdr10plus_parser

Add JSON scene information

Implements #32

+1412 -640

0 comment

18 changed files

pr created time in a day

create barnchquietvoid/hdr10plus_parser

branch : scene_info

created branch time in 2 days

created tagquietvoid/dovi_tool

tag0.3.5

Stuff about Dolby Vision

created time in 4 days

release quietvoid/dovi_tool

0.3.5

released time in 4 days

push eventquietvoid/dovi_tool

quietvoid

commit sha 7d7c176302c53329b648a729911a928f8a828758

Couple fixes, RPU parsing inconsistencies Add progress bar for frame indices computation in `inject-rpu` (closes #27) Fix `inject-rpu` `rpu-in` argument to match documentation (closes #28)

view details

push time in 4 days

issue closedquietvoid/dovi_tool

Argument '--rpu-in' instead of '--rpu_in'

In the inject-rpu documentation, the example has --rpu-in argument, but it doesn't work and you need to use --rpu_in.

I think the ideal would be to change the argument to --rpu-in, instead of updating the documentation with --rpu_in, since all other arguments are also - and not _ (--rpu-out, extract-rpu).

Thanks and regards!

closed time in 4 days

manuelrn

issue closedquietvoid/dovi_tool

Add progress bar for "Computing frame indices"

The process is pretty slow and there's no feedback. Noticeable with full length videos (150k frames and more).

closed time in 4 days

quietvoid

push eventquietvoid/hevc_parser

quietvoid

commit sha db0fae6936b74044485c3eff1d9bc34f6d0764e0

Allow parsing different start code lengths

view details

push time in 4 days

issue openedquietvoid/dovi_tool

Allow generating custom RPUs

For example, it could be useful to create generic metadata (for example ST2086, level 6 metadata). Perhaps min/max/avg PQ values as well..

created time in 5 days

issue commentquietvoid/dovi_tool

Argument '--rpu-in' instead of '--rpu_in'

Indeed, that was pointed to me. I'll fix it.

manuelrn

comment created time in 5 days

issue openedquietvoid/dovi_tool

Add progress bar for "Computing frame indices"

The process is pretty slow and there's no feedback. Noticeable with full length videos (150k frames and more).

created time in 5 days

issue openedquietvoid/hdr10plus_parser

Compute metadata scene related information

Samsung's HDR10+ tools expect scene information to be present for a valid JSON file.

Should be present for every metadata frame in SceneInfo:

SceneFrameIndex: Index of the frame relative to the current scene (starting from metadata change) SceneId: Incremented scene index (Id) when metadata changes SequenceFrameIndex: Metadata frame index (total length should be number of frames)

Should be present at the JSON root:

"SceneInfoSummary": {
    "SceneFirstFrameIndex": Array of `SequenceFrameIndex` where a metadata's `SceneFrameIndex` is 0
    "SceneFrameNumbers": Array of the number of frames (length) of every scene
}

created time in 5 days

push eventquietvoid/dovi_tool

quietvoid

commit sha 3f2f8c1858ba21981c4223244853e0a4a1f51855

Update readme

view details

push time in 9 days

created tagquietvoid/dovi_tool

tag0.3.4

Stuff about Dolby Vision

created time in 10 days

push eventquietvoid/dovi_tool

quietvoid

commit sha 1caf8c0aa22ac8908e07a95d6b51431f708dbcf4

Bump version

view details

push time in 10 days

delete branch quietvoid/dovi_tool

delete branch : editor_features

delete time in 10 days

push eventquietvoid/dovi_tool

quietvoid

commit sha 28919d00ff48cc55dfcd4145c34f33db83e4c64a

Remove & duplicate metadata in editor (#26)

view details

push time in 10 days

PR opened quietvoid/dovi_tool

Remove & duplicate metadata in editor
+140 -45

0 comment

9 changed files

pr created time in 10 days

push eventquietvoid/dovi_tool

quietvoid

commit sha c0d0dc17851dabcb1f164c755832a32aeababa79

Add duplicate option

view details

push time in 10 days

delete branch quietvoid/dovi_tool

delete branch : nalu_start_len

delete time in 12 days

pull request commentxbmc/xbmc

[Android] Improve Dolby Vision compatibility and hinting

One difference with this PR is that it doesn't include the changes for files containing both HDR10+ and Dolby Vision metadata. Though as far as I know that fix is specific to the FireTV Stick 4K.

quietvoid

comment created time in 14 days

create barnchquietvoid/dovi_tool

branch : editor_features

created branch time in 20 days

issue commentquietvoid/dovi_tool

Inject DV into existing hdr10 file?

Injecting cannot be used with piping, because it relies on the whole decoded order for interleaving metadata.

You can just use ffmpeg to demux, like this: ffmpeg -i file.mkv -c:v copy video.hevc And then use dovi_tool using the HEVC bitstream.

After injecting, you can mux the final file to MKV using MKVToolNix v58. There's no need for MakeMKV.

koolkunz

comment created time in 20 days

push eventquietvoid/vs-placebo

Lypheo

commit sha 0c990138fef1cd7c508aa73cf7229921487f8899

Merge pull request #9 from quietvoid/master Remove haasnsoft

view details

akarin

commit sha 834dc300bbe2b3e5d8adf89a78264fbd1f33b8bb

meson.build: use pkg-config to find libplacebo Signed-off-by: akarin <i@akarin.info>

view details

Lypheo

commit sha cf02e29e542c1c2fc3cf9434f5ba521e6421551d

Merge pull request #10 from AkarinVS/patch/meson-dependency meson.build: use pkg-config to find libplacebo

view details

quietvoid

commit sha 22d56b09fec9bb10ac236920c679683e086a377e

Move delinearize to use pl_color_space

view details

push time in 22 days