DGIndex: Field Operation - Ignore Pulldown Flags Speeds Up Video

[Typhoon859]

When I set it to Honor the Pulldown Flags, the video turns interlaced. When I set it to ignore, the video length goes from about 24 minutes to 19. It speeds up. The only way to get the proper speed is by setting the Field Operation to Forced Film. Although that's what I plan to do anyway (get it to 23.976 fps), I don't think getting DGIndex to do it is as good as using FDecimate() in my AVISynth code. What might the problem be? The Ignore Pulldown Field doesn't do this with all the sources...

-In this particular case, the source is from the new Remastered Dragon Ball Z DVDs from FUNimation. The footage was captured originally at 24fps and then converted to NTSC when burned to DVD.

[Guest]

When I set it to Honor the Pulldown Flags, the video turns interlaced. Find out what 3:2 pulldown is. If you set honor pulldown, you are asking for the 3:2 to be present in the served video. Read this thread:

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

When I set it to ignore, the video length goes from about 24 minutes to 19. It speeds up. If you read the users manual you will understand why, and that ignore pulldown is for advanced diagnostic purposes only.

The only way to get the proper speed is by setting the Field Operation to Forced Film. Yes, forced film is the correct mode to use to output the film rate.

I don't think getting DGIndex to do it is as good as using FDecimate() in my AVISynth code. Sounds doubtful, but I'd need a sample to assess that claim.

What might the problem be? I give up. What problem are you experiencing with Force Film mode?

The Ignore Pulldown Field doesn't do this with all the sources... Correct. If there is no pulldown to ignore, then it is a no-op.

Please post a sample of the unprocessed, original source VOB. Use DGsplit to make a sample. Up to 100MBytes is fine, but make it at least 20MBytes in an area of the movie that you find to be problematic. Without a sample, there is no way to help you.

Probably you have blended fields.

[Typhoon859]

Alright, here's a short clip from the original source. If you need a longer clip, tell me and I'll upload a longer one XD

http://mybloop.com/go/sY142e

[Guest]

You didn't answer my question about what problem you are experiencing.

[SeeMoreDigital]

Typhoon859. It seems you have already opened a thread about this subject: -

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

[Guest]

I just tried with your clip with Forced Film mode. I see no problem at all with it.

What are you doing with it that produces ghosting?

Why do you say FDecimate() handles it better?

[Typhoon859]

I just tried with your clip with Forced Film mode. I see no problem at all with it.

What are you doing with it that produces ghosting?

Why do you say FDecimate() handles it better?

Oh, I'm sorry, you misunderstood. There is no problem when I use Forced Film. My question was why the other fields that I set it to caused problems and you explained it. I mostly understood. You answered my question already. I just didn't think that setting it to Forced Film was proper considering the original framerate is 29.97fps. I thought that FDecimate was the proper way to get it done.

[Typhoon859]

Typhoon859. It seems you have already opened a thread about this subject: -

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

Two different problems, two different questions. Just because it's the same clip, doesn't mean it's the same thread..

[Guest]

Oh, I'm sorry, you misunderstood. There is no problem when I use Forced Film. My question was why the other fields that I set it to caused problems and you explained it. No I didn't misunderstand. You said:

"The only way to get the proper speed is by setting the Field Operation to Forced Film. Although that's what I plan to do anyway (get it to 23.976 fps), I don't think getting DGIndex to do it is as good as using FDecimate() in my AVISynth code. What might the problem be?"

Everyone here would read that the way I did. You planned to use Force Film in DGIndex but you think FDecimate() is better.

I thought that FDecimate was the proper way to get it done. I asked you why you thought that and your reply is to simply say again that you thought it. This is getting fun. I'll try again. Maybe we can go in circles a few more times around.

Why did you think doing FDecimate() was better than IVTC for your telecined video?

[Typhoon859]

No I didn't misunderstand. You said:

"The only way to get the proper speed is by setting the Field Operation to Forced Film. Although that's what I plan to do anyway (get it to 23.976 fps), I don't think getting DGIndex to do it is as good as using FDecimate() in my AVISynth code. What might the problem be?"

Everyone here would read that the way I did. You planned to use Force Film in DGIndex but you think FDecimate() is better.

I asked you why you thought that and your reply is to simply say again that you thought it. This is getting fun. I'll try again. Maybe we can go in circles a few more times around.

Why did you think doing FDecimate() was better than IVTC for your telecined video?

Because I was dumb. I read what it does and I thought that it would do a better job than DGIndex "forcing" to film. Does that satisfy you? If you know that it's not true what I said, then no need to doubt yourself. I started doing anything AVISynth related no more than 5 days before my first post here. There's much for me to learn.

-"I thought that FDecimate was the proper way to get it done."

->It isn't necessarily, <explains why>


Don't ask me why, because it's based on the very little knowledge I know of what's going on. If I understood this specifically, I wouldn't have asked about it. Some things I know much about, but many other, even basics, I don't know much about.. As I said earlier, if my lack of knowledge bothers you, no need for you to torture yourself and ever even look at my threads - god forbid reply.

[Inspector.Gadget]

I don't speak for anyone but myself here: The problem with allowing people to post flatly incorrect information on forums and then not correcting it is that it spreads - Doom9 is a well-known, reputable site and thousands of people that aren't members come and read the threads here. Forums are a collaborative tool by their nature and replying to threads to correct mistaken information is something that users - and particularly moderators and software developers - take very seriously. If one person screws up their video encoding, fine - but if they post about it and treat their incorrect procedure as correct, others will rely on it and end up wasting their time and becoming too frustrated to spend time on otherwise worthwhile projects.

[Typhoon859]

I don't speak for anyone but myself here: The problem with allowing people to post flatly incorrect information on forums and then not correcting it is that it spreads - Doom9 is a well-known, reputable site and thousands of people that aren't members come and read the threads here. Forums are a collaborative tool by their nature and replying to threads to correct mistaken information is something that users - and particularly moderators and software developers - take very seriously. If one person screws up their video encoding, fine - but if they post about it and treat their incorrect procedure as correct, others will rely on it and end up wasting their time and becoming too frustrated to spend time on otherwise worthwhile projects.

I agree. But, I didn't make any statements, I only asked questions and asked for my observations to be corrected. I clearly said that I just thought that FDecimate() would do what I wanted to be done more properly. I never mentioned it as a fact.