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. |
21st March 2019, 06:01 | #1 | Link | |
Registered User
Join Date: May 2014
Posts: 51
|
How to encode 1080i source with x265 interlaced?
Source clip, a segment of a BD M2TS:
Code:
Bit depth : 8 bits Scan type : Interlaced Scan type, store method : Separated fields Scan order : Top Field First Bits/(Pixel*Frame) : 0.317 Code:
LoadPlugin("LSMASHSource.dll") LWLibavVideoSource("some.m2ts") AssumeTFF() SeparateFields() #actually the encoded .265 has the same md5 even if this line is removed Code:
avs2yuv -raw %1.avs -o - | x265_SSSE3_32 --input-res 1920x1080 --fps 30000/1001 --interlace tff --preset medium --output %1.265 -- - Quote:
If the "field order" is set to TFF instead of AUTO, the playback is somehow at 60fps. However from the screen capture, it looks like it is force-deinterlacing a bad-deinterlaced progressive clip. Are there any tools to check if the encoded clip is a properly interlaced one? With mediainfo, it shows the "Scan type" of mpeg4 1080i as "MBAFF". But for hevc 1080i clips, it shows nothing about the scan type. Thank you very much! (Yes interlaced mode is deprecated in x265. This is just a test. ) |
|
21st March 2019, 07:48 | #2 | Link | |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,277
|
iirc.:
Quote:
Personally I would look at the frames to decide whether the content is interlaced or not and then decide what I deemed best for my usage goal. Cu Selur |
|
21st March 2019, 08:22 | #3 | Link | ||
Registered User
Join Date: May 2014
Posts: 51
|
Quote:
For h264 clips... if the "scan type" flag in mediainfo is MBAFF, and when checking the screen capture, there are combed edges for moving objects, it should be a proper one. if the "scan type" flag in mediainfo is Progressive, but there are still combed edges, then it should be a bad-interlaced (or bad-deinterlaced) clip. It happens when an interlaced source is fed to the x264 encoder without the --tff switch. Quote:
Last edited by cagali; 21st March 2019 at 13:31. |
||
21st March 2019, 08:58 | #5 | Link | |
Registered User
Join Date: May 2014
Posts: 51
|
Quote:
Anyway it is just a side question. The main one is "How to encode 1080i source with x265 interlaced (using avisynth)?" |
|
21st March 2019, 09:28 | #6 | Link | |
Registered User
Join Date: May 2006
Posts: 3,997
|
Quote:
Code:
AssumeTFF() separatefields() From the doc: https://x265.readthedocs.io/en/defau...utable-options HEVC encodes interlaced content as fields. Fields must be provided to the encoder in the correct temporal order. The source dimensions must be field dimensions and the FPS must be in units of fields per second. The decoder must re-combine the fields in their correct orientation for display. Last edited by Sharc; 21st March 2019 at 09:43. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|