Page 2 of 2

Re: Burn in TimeCode

Posted: Sun Sep 29, 2019 8:50 pm
by admin
Mahmoud Rady, can you please try and set "Force FPS" to 24 and see if that fix your problem?

-steinar

Re: Burn in TimeCode

Posted: Tue Oct 01, 2019 8:04 pm
by Mahmoud Rady
Hi EMcodem, no luck. same output with Avisynth.

Re: Burn in TimeCode

Posted: Tue Oct 01, 2019 8:09 pm
by Mahmoud Rady
admin wrote: Sun Sep 29, 2019 8:50 pm Mahmoud Rady, can you please try and set "Force FPS" to 24 and see if that fix your problem?

-steinar
it works :)

now I'm inserting several frame-rates to this workflow. Forcing to 24FPS will mess the other frame rates... is it fixable?

Re: Burn in TimeCode

Posted: Tue Oct 01, 2019 9:15 pm
by admin
It only makes sense to force 24000/1001 frame rates to 24 when burning timecode. So you should insert a "Conditional" node to test framerate. That way you can route 2400/1001 rates to the forced 24 fps TC-node and the rest to another TC-node that takes what ever frame rate the source have.

-steinar