What Is The Best Codec For 4K Video??

[johns0]

Mpeg1.

4k Mpeg1 video clip:

The video is mpeg2,not mpeg1.

I just demuxed the Scorpion.mpg and ran it through DGindex. It reported the stream was indeed Mpeg-1

Stream Type: Elementary
Profile: [MPEG1]
Frame Size: 3840x2160
Display Size: [not specified]
Aspect Ratio: 1:1
Frame Rate: 24.000000 fps
Video Type: NTSC
Frame Type: Progressive
Coding Type: P
Colorimetry: BT.470-2 B,G*
Frame Structure: Frame
Field Order: Bottom
Coded Number: 174
Playback Number: 174
Frame Repeats: 0
Field Repeats: 0
VOB ID:
Cell ID:
Bitrate: 16.200 Mbps
Bitrate (Avg): 12.458 Mbps
Bitrate (Max): 16.200 Mbps
Timestamp:
Elapsed: 0:00:15
Remain: FINISH
FPS: 10.80
Info:

Try loading the mpeg into tsmuxergui.

[El Heggunte]

It seems ffmpeg muxed the .m1v stream INCORRECTLY, for a change U_U

MediaInfo says Scorpion.mpg contains MPEG-2, BUT after demuxing with TMPGenc,

MediaInfo says Scorpion.m1v is MPEG-1 (doh!)

[racer-x]

Yeah, I only did it as a joke and out of curiously. I was expecting crappy results encoding UHD material with an ancient codec like Mpeg-1, but was surprised by the results I got.

[jagabo]

All MPEG family codecs deliver high quality when given enough bitrate. The issue is how much bitrate each generation (and implementation) needs.

[El Heggunte]

Yeah, I only did it as a joke and out of curiously. I was expecting crappy results encoding UHD material with an ancient codec like Mpeg-1, but was surprised by the results I got.

Well, at least until some years ago, TMPGenc was the only MPEG-1 encoder designed to be good AT ANY resolution (up to 4095x4095). Well, PERHAPS bbmpeg is as good as TMPGenc, however it's incredibly slow (which means, no, I will not test it). ffmpeg's MPEG-1 did suck at anything above 352x288, because its developers were pretty sure that "nobody will ever use MPEG-1 for anything better than VCD"

[El Heggunte]

.........
Besides, VirtualDub cannot open the samples, and says "No video stream!"

Correcting myself again --- the root of all evil is a design flaw in the MPEG-2 input plugin, which applies the limitations of the MPEG-2 specs to MPEG-1 video

The built-in MPEG-1 decoder of VirtualDub does work as it should, OTOH

[El Heggunte]

{
deleted
}

[johns0]

I think the real question to the op has been forgotten,there will be more efficient codecs in the future so it it's either gonna be h264 or h265 for now.

[El Heggunte]

Blame the guy named johns0 , it was he who started the whole MPEG-1 offtopicness

Anyway, thanks to racer-x, we discovered a minor flaw in ffmpeg and a major flaw in the MPEG-2 VirtualDub plugin,
and this is not irrelevant, me thinks.

BTW, sooner or later someone will have to start a brand-new thread for discussing the Ultra-HD "madness" itself ---

4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K, 1M, how far the video and the broadcast "industries" will want to go

: - /

[racer-x]

BTW, sooner or later someone will have to start a brand-new thread for discussing the Ultra-HD "madness" itself ---

4K, 8K, 16K, 32K, 64K, 128K, 256K, 512K, 1M, how far the video and the broadcast "industries" will want to go

: - /

Go ahead and start the thread.

As for the OP, I doubt that he is remotely interested in encoding UHD into any codec. I think he is just trying to decide which container to download. He wants to know which one would provide the best quality available, if there are differences.

That's my assumption anyway.............