I Found The Answer by MYSELF to my 47.972 FPS Dilema!

[Krelmaneck]

I am so happy to share this information with you people. Remember how I posted earlier about getting this junky 47.972fps to a native NTSC rate..well, I DID IT, FINALLY.

At first, the moderate of this board suggested I decimate by 2 and add 2:3 pulldown...I did that.........it was still jerky on the tv.

MY SOLUTION:Use FDecimate with MultiDecimate. I read about Fdecimate and I researched it a bit,and ended up with a 25FPS--there is no pattern repeat in frames in my video. And then I used Multidecimate by using the "cycle based protect static scenes" opition setting that to CYCLE=9--removing every 9th frame because Fdecimate left it behined causing it to be 25 FPS,setting the threshold to 1 and thus end up with a NATIVE 23.976 video FILM rate. Just using the regular decimate(cycle=2 didn't help).

Thus my script that made EVERYTHING work BEAUTIFULLY for this horrid 47.972 goes as follows:

LoadPlugin("C:/fdecimate.dll")
LoadPlugin("C:/MultiDecimate.dll")
AVISource("G:/517 - Polly in the middle.avi")
ConvertToYUY2()
Fdecimate(rate=26.973, threshold=2.75) #results in 25 FPS
MultiDecimate(pass=2) #results in 23.976 FPS
BilinearResize(480,480,0.0,0.5)
ConvertToYV12()

So that was the script that made everything work BEAUTIFULLY, the way it should be. So once it was a native 23.976 FPS, I added 2:3 pulldown and did all the usual steps of SVCD, and it came out perfectly.


Everyone will have different Fdecimate and Multidecimate results since fdecimate tries to take out the repeated frames. Sometimes I had 3 repeated frames--no joke. It will be different for you.

Thanks to for the person suggested the doom9 forum
Thanks to Moderate for his first idea of using decimate.
Thanks to myself for figureing this out.

Feel free to share this knowledge.

[underwurlde]

Request this info gets added to guides?

[BJ_M]

how often does someone have a 47.972fps totally screwed up film ?

[Krelmaneck]

Well, not a guide at all...just somethings i have done to accomplish something. If you want to learn more about Fdecimate, do as earch for it on the doom9 forum. Also Fdecimate comes with good documentation'

BUT IF YOU DON'T WANT TO DO THE SEARCH, READ THIS:

It tells you to make a ratio of repeated frames to unique frames(new) within a 10 second period--I did 5 seconds--too much work, and then multiply the ratio by your source's frame rate. This equals your what it should be rate. In my case my rate was 26.973 and my source(file) was 47.972. Thus fdecimate(rate=26.973).


How did I get the metric? well, I didn't, really...but to do that just write "fedcimate(metrics=true)' and open in virtualdub and it will tell you the metric for each frame...pick one so that they don't repeat...I couldn't, but I found one where it only repears 9 time and wrote that as the metric--2.75, thus fdecimate(rate=26.975, metric=2.75).....



But I still have every 9th frame repeated and it's 25 FPS which is okay,COINCIDENATLLY for pal, but not ntsc. To get rid of the every 9th frame, use MULTIDECIMATE.

Please note MultiDecimate only works with YuY2 color space. That's why I put ConvertToYUY2() in my script. But to make it natural, I put converttoYuY2 before fdedcimate.


On to Multidecimate:

Answer: I put Mulitdecimate(pass=1) in my script andplayed the whole video in virtualdub and then quit it......this created a thing called "mfile." I I loaded the GUI and selected to save static frames(last option on the pulldown menu),and set randomly(no thinking to threshold=1, and my cycle=9(getting rid of every 9th frame. I hit the button create, and this made a text file called "dfile." I then went back to my avs script and erased multidecimate(pass=1),and wrote multidecimate(pass=2).

Now at the end of the script, convertback to YV12, or if you wish RGB, if you use TMPGenc. i used QuEnc 0.59 Beta 2.


After I did this, there were no repeated frames and I got a 23.976 Film rate,and then added pulldown to make it play naturrally for NTSC. in the GUI for Pulldown, DO NOT SET FRAMERATE AND DO NOT SET TYPE OF FRAME--LEAVE ALL SELECTIONS AS NONE. Setting a framerate just messes up your video even more. If you just select none for everything, pulldown will still be applied, once you hit GO!

Well, I hope that's more readable.

Now the trick is to see if I can do 10 FPS to NTSC. Well, haven't found one yet; therefore, I don't have to think about it.

[Krelmaneck]

how often does someone have a 47.972fps totally screwed up film ?

when soneone uses the DGBob filter it can add so many frames to something. The reason why it does this is so itcan go from an interlaced source to progrssive. I think someone DGBob'd my source.

[sacajaweeda]

If you want to learn more about Fdecimate, do asearch for it on the doom9 forum.

The reason I referred you there to the doom9 forum is that I felt it was a more appropriate place for the type of discussion you're looking for. Here on this site - this board in particular - you are posting in a newbie forum. A lot of the people reading in this forum don't even know what avisynth scripting is, much less care about it. Mostly it's just what the name implies....noobs. The doom9 forum - unlike this one - has a board exclusively for avisynth scripting and it is regularly frequented with several of it's developers. Those people will gladly engage you in theoretcal discussions for weeks on end about the most trivial effects of an advanced scripting technique or application of a filter.

Not flaming, just pointing out that your intended target audience is not residing in this forum. Most people reading here are either looking for basics or looking to help someone struggling with the basics.

Your particular problem is a relatively obscure one and discussion of it doesn't really fit here. I don't really see the need for a guide about it either.

My $.02

[Krelmaneck]

No, actually, this not a problem anymore............I posted here to tell you how I have resolved the 49.972 dilemna. And didn't you see my acknowledgment to you at the end of the 1st post on this subject. I repeat this is no longer a problem. I'm just shareing good newshow I resolved my issue.[/quote]

[BJ_M]

glad it worked out --- good solution

[Krelmaneck]

No, actually, this not a problem anymore............I posted here to tell you how I have resolved the 49.972 dilemna. And didn't you see my acknowledgment to you at the end of the 1st post on this subject. I repeat this is no longer a problem. I'm just shareing good newshow I resolved my issue.

[/quote]


I'm here to have fun and share common interests? isn't that right? I quote myself to prove this theory.

[sacajaweeda]

I'm just shareing good newshow I resolved my issue.

Good deal. More people should do that, rather than leaving a thread open without a solution, as you have done here in your original thread. You would have been better serving this community by simply amending the original with the solution instead of starting a new thread like this one here.

My $.02