119 FPS > 23 FPS, any way to do this?

[otbwavelength]

I have a ton of Death Note RAWs, and almost all of them are 119 FPS, or somewhere in that range.

Now, i've been using After Effects/Premiere for years now so i'm no noob to either program;

however, this problem has been plaguing me with the Death Note episodes heavily.

Essentially, since the files are 119 FPS, when I drop them in Virtual Dub to rip out small clips for use in my AMV, I have essentially two options;

-Convert at 119 FPS (original FPS of video file)
-Convert at 23.976 FPS (original FPS of what the video file SHOULD be and is theoretically playing at when you watch it)

Problem with both of these is;

Convert at 119 FPS - After Effects will only export out up to 100FPS, meaning that no matter what you do, these clips are getting slowed down. Added into that, the actual visuals of the clip are 23FPS, so there is really no reason to convolute things by editing at 119FPS, and it sucks up memory, bad.

Convert to 23 FPS - This slows down the clip by an insanely high amount of time, obviously, even though it's what you're visually seeing when you watch it on a movie player.

So my question essentially is this;

-Is there a way to convert these 119+ FPS clips down into their TRUE visual FPS, aka 23.976 FPS, for use in Adobe After Effects 7.0 Professional?

And by that I mean, keep it visually as smooth as it was and playing at the same rate, but encoded at 23.976 FPS so that AE doesn't explode trying to scrub through it and because obviously it really is only 23.976 FPS.

If it matters, i'm using VirtualDub 1.6.17, and i've tried exporting it with HuffyUV 1.3, uncompressed, divx, everything in the book.

[Zarxrax]

http://forum.doom9.org/showthread.php?t=82264

avi_tc_package at the bottom of the first post.

[otbwavelength]

thanks bunches for all the extra help on AIM, i researched more of it and managed to get everything resized, formatted, set to correct FPS, and all in a quick and linear format

again, thanks!

[Kero777]

http://forum.doom9.org/showthread.php?t=82264

avi_tc_package at the bottom of the first post.

And here I was thinking I was the only one with that problem! I knew 119fps had to be wrong. I skimmed over that page and I don't understand everything that is there. If I download the avi_tc_package and find a script for Avisynth, I can convert it to it's true visual fps?

[Qyot27]

http://forum.doom9.org/showthread.php?t=82264

avi_tc_package at the bottom of the first post.

And here I was thinking I was the only one with that problem! I knew 119fps had to be wrong. I skimmed over that page and I don't understand everything that is there. If I download the avi_tc_package and find a script for Avisynth, I can convert it to it's true visual fps?

Essentially, avc_tc takes out all the dummy frames that were used to make the file 119fps - you'll have a completely new file (at least that's the way I'd tell it to go about it) at the right framerate, or something like that - it might be 29.97 instead of 23.976, but that can be remedied by AssumeFPS().

[otbwavelength]

http://forum.doom9.org/showthread.php?t=82264

avi_tc_package at the bottom of the first post.

And here I was thinking I was the only one with that problem! I knew 119fps had to be wrong. I skimmed over that page and I don't understand everything that is there. If I download the avi_tc_package and find a script for Avisynth, I can convert it to it's true visual fps?

Essentially, avc_tc takes out all the dummy frames that were used to make the file 119fps - you'll have a completely new file (at least that's the way I'd tell it to go about it) at the right framerate, or something like that - it might be 29.97 instead of 23.976, but that can be remedied by AssumeFPS().

I just used tc, then I used virtualdub to slow it down to 23.976

[Kero777]

http://forum.doom9.org/showthread.php?t=82264

avi_tc_package at the bottom of the first post.

And here I was thinking I was the only one with that problem! I knew 119fps had to be wrong. I skimmed over that page and I don't understand everything that is there. If I download the avi_tc_package and find a script for Avisynth, I can convert it to it's true visual fps?

Essentially, avc_tc takes out all the dummy frames that were used to make the file 119fps - you'll have a completely new file (at least that's the way I'd tell it to go about it) at the right framerate, or something like that - it might be 29.97 instead of 23.976, but that can be remedied by AssumeFPS().

I just used tc, then I used virtualdub to slow it down to 23.976

(Sorry about the very late reply. I've been posting so much I forgot about this one!)

I've done a lot of reading about this on A&E's guide and I still don't understand:

slow it down to 23.976

I now understand that it has to do with removing dummy frames so the footage doesn't slow down when you convert it to 23.976 from 29.97 (or from 119 to 29.97), but I can't really find out how to do that... and when you use AssumeFPS(23.976), that's when the footage really slows down and you aren't removing dummy frames anymore, right? I read about IVTC or Inverse Telecining but it's not really sinking in. Ahhh, oh well, I just need to keep reading on it more I guess.

Thanks for responding!

[Qyot27]

The reason dummy frames are used is because some segments are 29.97, others are 23.976. Instead of using a container like MKV or MP4 that can handle variable framerates, they figured out how to hack it into AVI - but it's such a bad hack that it probably even beats out DivX managing to hack B-frames into the damn things.

Taking the dummy frames out will either leave you with 29.97fps video, where the 29.97 segments are correct and the 23.976 areas still have dummy frames to even them out, or all the dummy frames have been removed and the file set at either 29.97 or 23.976, which means while some of the video will play at the correct speed, the other parts won't. AssumeFPS() just alters the framerate so you don't have to worry about problems which arise when trying to use a framerate like 23.976 in editors like Premiere that have issues with them (in Premiere it's recommended to use 24fps rather than 23.976; 29.97 is handled fine, though). Once the footage is in the editor, you can slow down or speed up the footage as much as you want without fear, so even if it plays back at the wrong speed because of the AssumeFPS line, you can make it play back right during the editing phase.

Inverse telecine or deinterlacing has nothing to do with this at all - these files are already progressive. IVTC or deinterlacing only becomes an issue when dealing with interlaced footage - more often than not ripping DVDs yourself or capturing footage straight from the broadcast signal coming over your cable/satellite/antenna.