02.07.2023, 17:53
Sorry it took me so long to reply. Busy, busy weeks in real life.
This is what I tried:
01. Frames > Interlaced encoding + Filtering > (De)Interlace/Telecine > Interlace
FAIL, slow motion video, double duration.
02. Frames > Interlaced encoding + Filtering > (De)Interlace/Telecine > Interlace + Filtering > (De)Interlace/Telecine > Overwrite input scan type to: progressive
FAIL, slow motion video, double duration. Out of my crazy logic, I thought maybe telling the program to overwrite the input scan type, would correct the frame count. It didn't.
03. Frames > Interlaced encoding, Filtering > Avisynth > Progressive to interlace
SUCCESS, Interlaced video, BUT field order is messed up - VERY slow encode, compared to the first two
Regarding the last tryout, I noticed a change in the command line, and I think the problem is there. When I select Frames > Interlace encoding, it adds -tff to the command line, but as soon as I check Filtering > (De)Interlace/Telecine > Interlace or Avisynth > Misc > Progressive to Interlaced, it changes -bff in the command line.
I guess it's because of the interlacing line, AssumeTFF().SeparateFields().SelectEvery(4, 0, 3).Weave(), which outputs TFF video, while the command line sets the encode to -bff.
I tried to attach the debug files here, but one of them exceeds the 200kb limit, so I uploaded the videos and the debug files to my Google Drive.
https://drive.google.com/drive/folders/1...sp=sharing
This is what I tried:
01. Frames > Interlaced encoding + Filtering > (De)Interlace/Telecine > Interlace
FAIL, slow motion video, double duration.
02. Frames > Interlaced encoding + Filtering > (De)Interlace/Telecine > Interlace + Filtering > (De)Interlace/Telecine > Overwrite input scan type to: progressive
FAIL, slow motion video, double duration. Out of my crazy logic, I thought maybe telling the program to overwrite the input scan type, would correct the frame count. It didn't.
03. Frames > Interlaced encoding, Filtering > Avisynth > Progressive to interlace
SUCCESS, Interlaced video, BUT field order is messed up - VERY slow encode, compared to the first two
Regarding the last tryout, I noticed a change in the command line, and I think the problem is there. When I select Frames > Interlace encoding, it adds -tff to the command line, but as soon as I check Filtering > (De)Interlace/Telecine > Interlace or Avisynth > Misc > Progressive to Interlaced, it changes -bff in the command line.
I guess it's because of the interlacing line, AssumeTFF().SeparateFields().SelectEvery(4, 0, 3).Weave(), which outputs TFF video, while the command line sets the encode to -bff.
I tried to attach the debug files here, but one of them exceeds the 200kb limit, so I uploaded the videos and the debug files to my Google Drive.
https://drive.google.com/drive/folders/1...sp=sharing