48fps media conform

Had a kerfuffle. Client shot everything at 48fps to reduce motion blur on freeze frames. Premier sees 48fps, QT sees 48fps, Flame sees 24fps. Moreso first frame of raw media in Premier is 08:16:33:14, Flame is 16:33:08:16

So XMLs from edit were a complete wash and we eye matched everything. I don’t see an obvious fix?

Convert rate from the tools tab then conform based off that maybe?

Or change rate on import

Looking at those tricks now, but as 48fps shows up nowhere in Flame… It’s just the SMPTE established rates it seems. Select Rate on Import at 50fps does get the starting TC much closer.

Can you match by handles instead of source tc? That’s usually my trick for mixed framerate stuff.

id go old school. output an EDL. Then, ask AI to take every shot’s last 2 numbers and divide by 2, rounded to the nearest integer. Conform from that. probably pretty close.

1 Like

AI taking someone’s job!

It makes sense if Flame starts counting TC at 00, it would be at hour 16 when Premier is at hour 8. Double. Anyhow, next round I’ll try some of these tricks. But probably quickest just to eye match on a :30

Flame does not support this frame rate as you have already noticed so you will not be able to import media or sequence formats like EDL, XML or AAF.

1 Like

fwiw they would have fotten the same “less motionblur” shooting 24fps with a faster shutterspeed ….

flame not supporting 48fps is a joke tho.

2 Likes

I did follow up on that: why not just shoot a faster shutter next time? They decided on 48 so “they had more choice which exact frame to freeze.”

2 Likes

#genius

I am sure these will be amazing stills , much better than a dedicated photographer could take 100% lol

3 Likes