Converting to 60p in the browser

Hi Guys,

I shot a video over the weekend using a load of frame rates. My intention is to slow it all down into a 24p timeline.

I shot some at 240FPS on a Sony FS5 and other stuff at 60FPS on an iPhone. The Sony gives you the 240p footage in slow motion in the browser. The iPhone and other cameras put the 60p footage at normal speed. To slow it down, you have to put it in Timeline and retime it.

I like to use favourites and keywords from the browser before I start to assemble my timeline. The issue I have is that I can see the 240p footage in the browser, but I can't see what the 60p footage looks like. I have to drag it all into the Timeline to retime. Then I can't use favourites and keywords on it.

So... is there a way of slowing down all the footage in the browser? So all the 60p turns into silky slow mo... I can then work my way through it?

Thanks in advance !!!

Phil x

phil@circuitfactory.ae wrote: I like to use favourites and keywords from the browser before I start to assemble my timeline. The issue I have is that I can see the 240p footage in the browser, but I can't see what the 60p footage looks like. I have to drag it all into the Timeline to retime. Then I can't use favourites and keywords on it.

Afaik (please correct me) there is no interpret footage option in the Browser like in Premiere. You could filter all 60p clips in the browser, select them and copy them to a preview timeline set to 24p and retimed with automatic speed, then jump back and forth between timeline and browser to tag, favor and reject them.

Perhaps there was no need to tag the 60ps anymore but just copy the good parts from the preview timeline into your actual project (retiming preserved then). Sure, this doesn't look like FCP X at all, it more resembles the Premiere pancake editing, but it actually is less complicated as it sounds. Depending on how many 60p clips you have, it could even be faster. The wiser head steals practical solutions wherever he finds them )

EDIT : There are external frame rate changers (that's the Google term) that work similar to the rate conform tool in FCS's old Cinema Tools. But I have no personal experience, and I doubt that they will facilitate your work at the end of he day.

Thanks Axel... This would seem like a really obvious feature for FCPX... Given that you can only really F and Keyword clips at real time speed.

Phil

phil@circuitfactory.ae wrote: ... is there a way of slowing down all the footage in the browser? …

Just as a reminder:
there are TWO sorts of slow-mo recording.

as an example on my consumer [strike]toy[/strike] cam Lumix FZ1000
50fps shutter are recorded with 50fps => playback in browser: 1sec=1sec
100fps shutter is recorded with 25fps (or whatever I've set) => playback in browser 1sec=4secs

Sooo, a browser should, imho, playback 1 sec as 1 sec… 
If the camera 'conforms ' on recording, it isn't FCPX fault… 

phil@circuitfactory.ae wrote: Thanks Axel... This would seem like a really obvious feature for FCPX... Given that you can only really F and Keyword clips at real time speed.

Phil

I disagree with your request. You put the cart before the donkey. With very few exceptions - i.e. 10 x slomo of 240p - time manipulations are a common way of accentuating something in the timeline, relative to realtime. As an editor, you see the realtime appearance first and after that decide to change it. And for mixed frame rates and easy and intuitive time remapping without worries about track conflicts right to the change, FCP X is really good.

EDIT : What is more, FCP X is really good at preserving the original frame rate (it's motion phases) even without using automatic speed. As Premiere is. How do I know? I've been reading on the new PP CC feature to edit with proxies. People complained it were useless if you had to interpret footage (for the same purpose you ask for), because proxies can't be interpreted. Until someone found out that the results of a speed change in the timeline (which is a better and more intuitive approach anyway) - i.e. playing back 60p @40% speed - gave the same results as interpreting the footage in the browser.