Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Whoops - 60fps, No Varispeed Back to 24fps

Dan Kanes

Well-known member
Joined
Nov 25, 2009
Messages
5,496
Reaction score
12
Points
38
So, a friend of mine is working on some footage shot at 3K,2:1,60FPS (NOT VARISPEED) and wants to conform all of the footage to 24fps for slow motion.

He's working on the Proxy files. I recommended Cinema Tools, but it doesn't look like that works on Red Proxies...?

Any suggestions on conforming the footage that won't take him forever to render and kill him?

Thanks!
 
cinema tools gives an error message when trying to change the frame rate on a proxy.

I suggested conforming clip settings to project settings in final cut, and also maybe try 40% playback speed?
 
Are you talking about someone who shot at a 59.94 timebase at 60fps?

People really need a lesson in film slow motion.

TWIXTOR will do this, but it will never look normal.

david
 
The camera (because of a menu glitch) would not allow 3K, 2:1, 24fps timebase, varispeed @ 60fps.

The operator ran the camera at 3K, 2:1, 60(59.94) fps time base because varispeed would not engage @ 60.

The problem comes with trying to conform a proxy. As of now, the easiest option I see would be to export quicktimes using a redrocket at 59.94, then use cinematools to conform all clips @ 24... tell me if that is stupid?

Are you talking about someone who shot at a 59.94 timebase at 60fps?

People really need a lesson in film slow motion.

TWIXTOR will do this, but it will never look normal.

david
 
The operator ran the camera at 3K, 2:1, 60(59.94) fps time base because varispeed would not engage @ 60.

The problem comes with trying to conform a proxy. As of now, the easiest option I see would be to export quicktimes using a redrocket at 59.94, then use cinematools to conform all clips @ 24... tell me if that is stupid?

No, that's not stupid. It should work. it will also work to "interpret footage" to 24 fps in After Effects (and I think Premiere as well).
 
Can't you use the thingymabob in FCP that uses the Varicam algorithmy whatsit or other some such platform for Varicam footage?

Bit vague but that's how I understood the Varicam to achieve varispeed results.
 
Posted in the other thread (please don't crosspost in future).

Thomas: Varicam style frame flagging is not how the RED ONE achieves slow motion.

Dan: Yes, you will need to convert all your footage to your online format first because TC will not be correct after batch conforming the footage.

General: Yes, it's possible to record real 50P/60P in 3K and below. No, it's almost never a good idea. Not sure what "menu bug" stopped you from varispeeding up to 60fps but I have a suspicion you may have had OPEN GATE turned on?
 
I just thought he could get his result with what he has using said frame flagging.

Cail, do you know what the difference between open gate option and the EVF synced or fixed option is all about?

Thanks
 
Thanks learned something

Thanks learned something

Antony, sure enough, just did it. I learned something, and I shoot at 50FPS constantly. That said, you certainly SHOULDNT! Unless your entire project is being finished at 60, which would be pretty darn odd.
 
I would just render all frames of each of the offending clips out to DPX or TIFF sequence from Redcine-X, then reassemble the frame sequences as new clips at 24fps.

...That is assuming the shutter speed was set to the proper speed/angle to give the desired amount of motion blur at 24fps. May need to add blur (easy) or try to sharpen and remove blur, which is difficult to make it look right. Some of the other tools mentioned like Twixtor, AE, etc.. with their motion interpolation can work too. But if the frames and shutter are right, then image sequences and reassembling to a proper clip is going to give the results you want and will be the easiest if you don't have access to all those other tools.
 
Just checked back in to this discussion. Forgot about it since it wasn't actually my problem - it was a problem for a friend.

In any case- not sure what they did to get it resolved.

Best solution to any menu based camera problem:

go To maintenance under Setup. Reset everything to factory defaults. then do your own preferences for setup. Kind of a waste of time, but the easiest way to assure there aren't any menu glitches.

I think red should offer a command line utility for changing the timebase of an R3D (unless that is impossible because of wavelet compression or something highly technical) as I understand it timebase is mostly a flag that tells the NLE or playback hardware what rate to play back at...

Cinematools doesn't work on R3d's or proxies from what I can tell.
 
Antony, sure enough, just did it. I learned something, and I shoot at 50FPS constantly. That said, you certainly SHOULDNT! Unless your entire project is being finished at 60, which would be pretty darn odd.

Why would that be so odd ? The HD standards are 1080i50/60 and 720p50/60, meaning, for the latter, 50 or 60 full frames per second, and personnally, I prefer that. Like most people who have been shown the same images shot in the two different modes, without knowing which is which, the 720p50/60 was prefered.

Many, well at least some, HD channels are broadcast at 720p50/50 and you can make Bluerays at that format.

Cheers,
Damien
 
it's the p part as I understand, that makes it look better than i, so 1080p should look better than both 1080i and 720p
 
Can't you use the thingymabob in FCP that uses the Varicam algorithmy whatsit or other some such platform for Varicam footage?

Bit vague but that's how I understood the Varicam to achieve varispeed results.

No, that won't work. That only works on DVCPro footage (maybe even only on Varicam footage - I forget).

If your only problem is that you can't re-conform a proxy, the solution is simple: don't use a proxy. Render the shot out, and then re-conform.
 
Back
Top