Burn in TimeCode

Questions and answers on how to get the most out of FFAStrans
Post Reply
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Burn in TimeCode

Post by admin »

Mahmoud Rady, can you please try and set "Force FPS" to 24 and see if that fix your problem?

-steinar
Top
Mahmoud Rady
Posts: 29
Joined: Tue Sep 17, 2019 10:49 am

Re: Burn in TimeCode

Post by Mahmoud Rady »

Hi EMcodem, no luck. same output with Avisynth.
Top
Mahmoud Rady
Posts: 29
Joined: Tue Sep 17, 2019 10:49 am

Re: Burn in TimeCode

Post 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?
Top
admin
Site Admin
Posts: 1687
Joined: Sat Feb 08, 2014 10:39 pm

Re: Burn in TimeCode

Post 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
Top
Post Reply

Return to “Usage, tips and tricks”