Change Video Usability Information, Without Re-encode

[anana]

Is this possible to change Video Usability Information in x264 mkv file, like : full range, color primaries, transfer characteristics, etc. without re-encode?
please help me...

[Cornucopia]

Reason?

[LigH.de]

AFAIR, h264info may be able to change some details (but I don't know if your interests are covered too). In raw H.264 video streams (not inside MKV containers). Without warranty (means: risk of corruption).

Good luck, Jim.

[poisondeathray]

Try this modified ffmpeg build

http://forum.doom9.org/showthread.php?t=152419

[newpball]

Reason?

Good point, why would anyone what to do that?

[anana]

Reason?

I encode my movie with color primaries & transfer characteristics -> bt709 and I found that some dark area in some scenes isn't good. I decided to change to bt470m or remove the color primaries & transfer characteristics info. So, my mpc can read it as not BT.709 as default.

Bit rate: 4 264 Kbps is quite good for 720p for some movie

here's my encode info:
Writing library : x264 core 146 r2538kMod 121396c
Encoding settings : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=11 / psy=1 / fade_compensate=0.00 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=128 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / fgo=0 / bframes=5 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=24 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=24 / rc=2pass / mbtree=1 / bitrate=4264 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=62500 / vbv_bufsize=78125 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=2:1.00
Language : English
Default : Yes
Forced : No
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Color range : Limited

AFAIR, h264info may be able to change some details (but I don't know if your interests are covered too). In raw H.264 video streams (not inside MKV containers). Without warranty (means: risk of corruption).

Good luck, Jim.

thanks for the info, i'll try it...

Try this modified ffmpeg build

http://forum.doom9.org/showthread.php?t=152419

thanks for the info, but it's quite difficult for me

[newpball]

I encode my movie with color primaries & transfer characteristics -> bt709 and I found that some dark area in some scene isn't good. I decided to change to bt470m or remove the color primaries & transfer characteristics info.

Then fix it at the source instead of hacking flags.

[anana]

I encode my movie with color primaries & transfer characteristics -> bt709 and I found that some dark area in some scenes isn't good. I decided to change to bt470m or remove the color primaries & transfer characteristics info.

Then fix it at the source instead of hacking flags.

I encode it for almost two days...
Now, I'm quite busy to encode it for almost two days again, because of my college's assignment that need more cpu process (i'm on animation major)

[newpball]

I encode my movie with color primaries & transfer characteristics -> bt709 and I found that some dark area in some scenes isn't good. I decided to change to bt470m or remove the color primaries & transfer characteristics info.

Then fix it at the source instead of hacking flags.

I encode it for almost two days...
Now, I'm quite busy to encode it for almost two days again, because of my college's assignment that need more cpu process (i'm on animation major)

Well think of it in a positive way, after this you will probably never make this mistake again!

[anana]

I encode my movie with color primaries & transfer characteristics -> bt709 and I found that some dark area in some scenes isn't good. I decided to change to bt470m or remove the color primaries & transfer characteristics info.

Then fix it at the source instead of hacking flags.

I encode it for almost two days...
Now, I'm quite busy to encode it for almost two days again, because of my college's assignment that need more cpu process (i'm on animation major)

Well think of it in a positive way, after this you will probably never make this mistake again!

Yeah, I'm on it