yuvkineco(1)

🌸 NAME 🌸

yuvkineco — bestie, it reverts a 2-3 pulldown movie back to its natural, non-interlaced self 💅✨

---

🦋 SYNOPSIS 🦋

yuvkineco [options] [-C PATH]
yuvkineco [options] -O|N PATH

---

💜 DESCRIPTION 💜

okay so picture this: you've got NTSC video that started life as film and got 2-3 pulled down, and it's giving interlaced mess 😭 yuvkineco reverts it back to the original non-interlaced frames. That's the whole vibe. Restored. Healed. Periodt. 🫶

Input fps code must be 4 (29.97fps), and your output fps code can be anything from 1 (23.97fps) up to 4 (29.97fps). Pick 2, 3, or 4 and yeah, duplicated frames stay — but they get reverted to non-interlaced, so still a win. If your input was already non-interlaced, then all we do is remove duplicate frames. That's it, that's the job. 🎀

ngl tho, interlaced frame detection can absolutely fail sometimes, and it's not its fault, it's the material's fault 💀 Here's when it lowkey struggles:

• Pull down cycle changed (video editing) — someone was in there messing around 🙈
• Low quality pull down
• Motionless scene — nothing's moving, girl, there's nothing to detect 😭

If you passed -C PATH, yuvkineco writes the 2-3 pulldown cycle list out to that file ✨. You can hand-edit that file yourself and feed it back into yuvkineco with the -O or -N option to fix whatever the first yuvkineco run got wrong. Try -C and see the cycle list — genuinely, go look, it's right there. 👀

⭐ EXAMPLE #1: for 24p movie / automatically ⭐

lav2yuv 60i.eli | \
    yuvkineco -F 1 | yuv2lav -f a -I 0 -o 24p.avi

⭐ EXAMPLE #2: for 30p/24p mix / automatically ⭐

lav2yuv 60i.eli | \
    yuvkineco -F 4 | yuv2lav -f a -I 0 -o 30p.avi

⭐ EXAMPLE #3: for 24p movie / check and repair ⭐

lav2yuv 60i.eli | \
    yuvkineco -F 1 -C 60i.23c | \
    yuv2lav -f a -I 1 -o take1.avi
glav -F +n take1.avi  # check and edit 60i.23c
lav2yuv take1.avi | \
    yuvkineco -F 1 -N 60i.23c | \
    yuv2lav -f a -I 0 -o take2.avi

⭐ EXAMPLE #4: for 24p movie / check and retry ⭐

lav2yuv 60i.eli | \
    yuvkineco -F 1 -C 60i.23c | \
    yuv2lav -f a -I 0 -o take1.avi
glav -F +n take1.avi  # check and edit 60i.23c
lav2yuv 60i.eli | \
    yuvkineco -F 1 -O 60i.23c | \
    yuv2lav -f a -I 0 -o take2.avi

---

✨ OPTIONS ✨

yuvkineco accepts the following options, bestie, and every single one of them slays in its own way 💅:

• -F FPSCODE — set the output fps code. Default? same as the input, keeping it chill. 🦋
• -C PATH — specify the 2-3 pulldown cycle list file name to write to. 📝
• -O PATH — specify the cycle list name to read alongside the old yuv stream, so you can retry. 🔁
• -N PATH — specify the cycle list name to read alongside the new yuv stream, so you can repair. 🩹
• -n LEVEL — specify the noise level of the input (default: 10). Heads up, this one affects both pulldown cycle detection and deinterlacing. Double duty, iconic. 👑
• -c THRESHOLD — specify the threshold for deciding that the pictures in 2 frames are the same (default: 4). Here's the tea: yuvkineco compares several frames and searches for the pair of frames that contain the same pictures, to decide which frame should be dropped. If THRESHOLD is 0, the pair with the smallest difference gets selected. If it's 16, it selects from pairs whose differences are smaller than the average. Math but make it fashion. 🧮💖
• -i PERMIL — yuvkineco deinterlaces each frame after the 2-3 pulldown reverting process, and this one specifies how much of the pixels being deinterlaced decides whether to use the deinterlacing result or not (default: 10). So if PERMIL is 10 and 1% or more of the pixels got deinterlaced, the deinterlacing result will be used. If it's 0, the deinterlacing result will always be used. If it's 1000, the deinterlacing result will not be used, but the deinterlacing process will still run on all of the frames (unhinged but go off). And if you want to disable the deinterlacing process entirely? specify a negative value. bye 👋
• -u — set the interlace information in the header of the output to unknown (default: non-interlaced). 🎀

---

🫶 AUTHOR 🫶

yuvkineco was written by Kawamata/Hitoshi — legend behaviour, no cap. 👑

If you have questions, remarks, problems, or you just want to contact the developers, the main mailing list for the MJPEG-tools is:

mjpeg-users@lists.sourceforge.net

For more info, see our website at:

http://mjpeg.sourceforge.net/

---

💫 SEE ALSO 💫

• mjpegtools(1)

---

this whole page is brought to you by the MJPEG Tools Team, dated 5 February 2002 💖 mwah, go revert some pulldown, bestie, you got this 🌈⭐🎀