FFMPEG: "Ability to identify progressive segmented frame material in h.264"

[Stears555]

Hello guys!

http://ffmpeg.org/trac/ffmpeg/ticket/1679
FFMPEG: "Ability to identify progressive segmented frame material in h.264"



What does it mean?

[poisondeathray]

I mentioned this in your other thread, it's already been implemented. Frame rate is read correctly, instead of the field rate

Recent ffmpeg (2013) 25fps

Input #0, mpegts, from 'mozdony.mts':
Duration: 00:00:24.58, start: 0.004033, bitrate: 24881 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 19
20x1080 [SAR 1:1 DAR 16:9], 25 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo,
fltp, 256 kb/s

old ffmpeg 50fps

Input #0, mpegts, from 'mozdony.mts':
Duration: 00:00:24.58, start: 0.004067, bitrate: 24881 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0.0[0x100]: Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9
], 50 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0.1[0x101]: Audio: [129][0][0][0] / 0x0081, 48000 Hz, stereo, 256 kb
/s

[Stears555]

I mentioned this in your other thread, it's already been implemented. Frame rate is read correctly, instead of the field rate

Recent ffmpeg (2013) 25fps

Input #0, mpegts, from 'mozdony.mts':
Duration: 00:00:24.58, start: 0.004033, bitrate: 24881 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p, 19
20x1080 [SAR 1:1 DAR 16:9], 25 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0:1[0x101]: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, stereo,
fltp, 256 kb/s

old ffmpeg 50fps

Input #0, mpegts, from 'mozdony.mts':
Duration: 00:00:24.58, start: 0.004067, bitrate: 24881 kb/s
Program 1
Metadata:
service_name : Service01
service_provider: FFmpeg
Stream #0.0[0x100]: Video: h264 (High), yuv420p, 1920x1080 [PAR 1:1 DAR 16:9
], 50 fps, 50 tbr, 90k tbn, 50 tbc
Stream #0.1[0x101]: Audio: [129][0][0][0] / 0x0081, 48000 Hz, stereo, 256 kb
/s

Are there any FFMPEG codes to achieve that?

Okay, but the Mp4 container problem is still remained in direct-stream-copy mode! The avi container can produce 25fps, but the play-speed of the avi video is half of the normal speed.

OR: could you solve that mp4 and avi problem? Test file: http://dictaphone.atw.hu/mozdony.MTS (Only 67Mbyte)

[poisondeathray]

Okay, but the Mp4 container problem is still remained! The avi container can produce 25fps, but the play-speed of the avi video is half of the normal speed.

"ability to identify" only deals with correctly identifying PsF. There are still other issues with ffmpeg's MP4 muxer (i already mentioned this in your other thread)

Ability to identify correcty is only the 1st step. For example, if youtube eventually merges this and implements it correctly, it should no longer deinterlace your progressive videos

Don't expect everything to be fixed so quickly - these developers are volunteers and work for free... Many things on the "to do" list are higher in priority and still haven't been dealt with for years.

could you solve that mp4 and avi problem?

Re-encoding fixes it because it's no longer encoded interlaced. You're looking for stream copy - that won't fix the stream (because it's copied - so the interlaced flag and encoding are still there - you're not altering the actual video stream) . Before, it would re-encode as 50p, not it's correctly 25p

[Stears555]

Okay, but the Mp4 container problem is still remained! The avi container can produce 25fps, but the play-speed of the avi video is half of the normal speed.

"ability to identify" only deals with correctly identifying PsF. There are still other issues with ffmpeg's MP4 muxer (i already mentioned this in your other thread)

Ability to identify correcty is only the 1st step. For example, if youtube eventually merges this and implements it correctly, it should no longer deinterlace your progressive videos

Don't expect everything to be fixed so quickly - these developers are volunteers and work for free... Many things on the "to do" list are higher in priority and still haven't been dealt with for years.

Okay, but : Has the original camcorder MTS file such an information that the video is a PSF or simple interlaced? How can I achieve that video info in the video file by the usage of FFMPEG after a direct stream copy ?

[poisondeathray]

Okay, but : Has the original camcorder MTS file such an information that the video is a PSF or simple interlaced? How can I achieve that video info in the video file by the usage of FFMPEG after a direct stream copy ?

Do you remember this conversation?
https://forum.videohelp.com/threads/343067-I-want-to-transform-my-PSF-MTS-camcorder-vid...=1#post2137478

Original file just has the field_pic_flag set to 1. This means it's interlaced encoding, not progressive encoding - this is the root of all your problems

Are there any FFMPEG codes to achieve that?

Just to parse use -i input.ext

e.g

ffmpeg -i input.ext

To stream copy use -vcodec copy -acodec copy

Again, it doesn't work for MP4 properly , use something else like MKV

ffmpeg -i input.ext -vcodec copy -acodec copy output.ext

Nothing is changed in the video when you stream copy. It still has interlaced flag so you still get the same types of problems. ie. It's up to the recieving decoder or software. Some players might play it properly , others not

e.g
ffmpeg -i mozdony.mts -vcodec copy -acodec copy output.mkv

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.0
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 2 frames
Format settings, GOP                     : M=3, N=12
Codec ID                                 : V_MPEG4/ISO/AVC
Bit rate mode                            : Variable
Bit rate                                 : 22.3 Mbps
Maximum bit rate                         : 22.7 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Original frame rate                      : 25.000 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Top Field First
Default                                  : Yes
Forced                                   : No

Audio
ID                                       : 2
Format                                   : AC-3
Format/Info                              : Audio Coding 3
Mode extension                           : CM (complete main)
Format settings, Endianness              : Big
Codec ID                                 : A_AC3
Duration                                 : 24s 620ms
Bit rate mode                            : Constant
Bit rate                                 : 256 Kbps
Channel(s)                               : 2 channels
Channel positions                        : Front: L R
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Compression mode                         : Lossy
Delay relative to video                  : 464ms
Stream size                              : 769 KiB (1%)
Default                                  : Yes
Forced                                   : No

But now it's 25p instead of 50p , but notice it's still "interlaced" . ie. Nothing is changed with the field_pic_flag because it's a stream copy

[Stears555]

Okay, but : Has the original camcorder MTS file such an information that the video is a PSF or simple interlaced? How can I achieve that video info in the video file by the usage of FFMPEG after a direct stream copy ?

Do you remember this conversation?
https://forum.videohelp.com/threads/343067-I-want-to-transform-my-PSF-MTS-camcorder-vid...=1#post2137478

Original file just has the field_pic_flag set to 1. This means it's interlaced encoding, not progressive encoding - this is the root of all your problems

Are there any FFMPEG codes to achieve that?

Just to parse use -i input.ext

e.g

ffmpeg -i input.ext

To stream copy use -vcodec copy -acodec copy

Again, it doesn't work for MP4 properly , use something else like MKV

ffmpeg -i input.ext -vcodec copy -acodec copy output.ext

Nothing is changed in the video when you stream copy. It still has interlaced flag so you still get the same types of problems. ie. It's up to the recieving decoder or software. Some players might play it properly , others not

e.g
ffmpeg -i mozdony.mts -vcodec copy -acodec copy output.mkv

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.0
Format settings, CABAC                   : Yes
Format settings, ReFrames                : 2 frames
Format settings, GOP                     : M=3, N=12
Codec ID                                 : V_MPEG4/ISO/AVC
Bit rate mode                            : Variable
Bit rate                                 : 22.3 Mbps
Maximum bit rate                         : 22.7 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Original frame rate                      : 25.000 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Top Field First
Default                                  : Yes
Forced                                   : No

Audio
ID                                       : 2
Format                                   : AC-3
Format/Info                              : Audio Coding 3
Mode extension                           : CM (complete main)
Format settings, Endianness              : Big
Codec ID                                 : A_AC3
Duration                                 : 24s 620ms
Bit rate mode                            : Constant
Bit rate                                 : 256 Kbps
Channel(s)                               : 2 channels
Channel positions                        : Front: L R
Sampling rate                            : 48.0 KHz
Bit depth                                : 16 bits
Compression mode                         : Lossy
Delay relative to video                  : 464ms
Stream size                              : 769 KiB (1%)
Default                                  : Yes
Forced                                   : No

But now it's 25p instead of 50p , but notice it's still "interlaced" . ie. Nothing is changed with the field_pic_flag because it's a stream copy

Many ffmpeg based softwares now can do this. However I need mp4 container for HTML5 video
The problem is the laziness of FFMPEG developer guys. Ok, it is a non-profit project, but it is more than the endurable laziness!

[Selur]

Ok, it is a non-profit project, but it is more than the endurable laziness!

it's probably just a question of priorities, since most people just simple remux with mp4box afterwards small problems with mp4 output are not that important to most folks.

[Stears555]

Ok, it is a non-profit project, but it is more than the endurable laziness!

it's probably just a question of priorities, since most people just simple remux with mp4box afterwards small problems with mp4 output are not that important to most folks.

These are
enormous
problems!!! (for humankind too!!!!)

[Selur]

it takes them normally a while but they fix bugs (last thing I reported directly myself https://ffmpeg.org/trac/ffmpeg/ticket/978 got fixed after half a year , but that's okay, I knew how to workaround the problem and I also knew that not so many people would run into the problem that really bugged me )

[Stears555]

it takes them normally a while but they fix bugs (last thing I reported directly myself https://ffmpeg.org/trac/ffmpeg/ticket/978 got fixed after half a year , but that's okay, I knew how to workaround the problem and I also knew that not so many people would run into the problem that really bugged me )

FFMPEG has frame-rate problem with progressive segmented frame in avi container too...

Can you send a ticket for a Youtube employee too, about the Progressive segmented frame problems?

Further info and sample videos about the youtube problems:

http://productforums.google.com/forum/#!msg/youtube/TCtyuf2PYWk/nvs9Hr2SYcMJ