problem with framerates - can't join assumed 23.976

[nanga parbat]

hello,

i once made a small intro with a friend of mine which i now and then like to put at the start of my ripped movies. (now, please don't get me wrong, it's just for me! )
i have it here in 25 fps huffyuv because usually my movies are PAL, but right now i have a NTSC one which was IVTC'ed.
the movie is already encoded. so naturally i load the small clip via avs and do assumefps(23.976) (the sound isn't that problem, i later edit it manually) - however when i try to join this encoded snipped with the movie in vdubmod, it will tell me that the framerates won't match (23.976 vs. 23.976).
well that tells me that 23.976 for an ivtc'ed ntsc movie is not the true framerate and i do assumefps(framerate(clip1)) where clip1 would be the encoded movie. however that results in the same error while later trying to join the two streams.

so i'm kinda lost here. i know i can just do sth. like assumefps(23.976) on the clip and join both in avisynth with unalignedsplice. it would take the first framerate which is the assumed one. but i kinda don't want the movie to turn out not in synch with the audio - which might just be marginal and unnoticeable.
so, anyone got a thought what i could do to get the movie framerate into my clip? do i have to work with real fractions (sth. like 239760/10000) or can i just splice them together without fear of losing synch later.

suggestions welcome, nanga

[stickboy]

i do assumefps(framerate(clip1)) where clip1 would be the encoded movie.That may not work due to floating-point rounding error from the rational number -> floating-point value -> rational number conversions.

You either need to use IanB's FrameRateNumerator/FrameRateDenominator (http://forum.doom9.org/showthread.php?s=&threadid=78727) functions--but they're not available in any released builds yet--or to call AssumeFPS(23.976) on both segments.

I think the AssumeFPS(23.976) route should be fine; since both segments are approximately 23.976 fps, the difference should be negligible.

[nanga parbat]

I think the AssumeFPS(23.976) route should be fine; since both segments are approximately 23.976 fps, the difference should be negligible.

well, i thought as much. still, that means i'll have to encode the movie again :/. i guess there's no way around that... off we go.

thanks anyway!

nanga