Effect of adding Assume(29.970) for .avs input into CCE

[EuropeanMan]

I'm in the habit of backing up my DVD9s into something which I believe is better than before...by deinterlacing, fixing hues, contrasts, denoising, etc etc...

Let's say I deint to 23.976...As is the norm, I feed my .avs into CCE and after it's done encoding, i use DGPulldown for 23.976--> 29.970.

Is there ANY BENEFIT or HARM if I simply add Assume(29.970) at the end of my script - where it'd require me in DGPulldown to select "no changes"?

{same question goes when I deint to 25fps}

Thanks...

[neuron2]

Is there ANY BENEFIT or HARM if I simply add Assume(29.970) at the end of my script - where it'd require me in DGPulldown to select "no changes"?
You won't get pulldown that way, and you'll mess up the audio sync.

[manono]

Is there ANY BENEFIT or HARM if I simply add Assume(29.970) at the end of my script - where it'd require me in DGPulldown to select "no changes"?
Since you set the encoding framerate in CCE itself and not in your AviSynth script (unlike, say, HCEnc), you're just wasting a line that doesn't have any effect on anything.

I can only wonder why you'd try and set an incorrect framerate in the script, but you can still apply pulldown afterwards with no problem. Also, I'm assuming the "For DVD" box in CCE is unchecked.