Best practice for slow motion with clip created out of 360 single photos

Hello,

I'm new to this forum and FCP and I hope someone can help me with my project.

I have 360 single photos of a desk. All photos animated together "moves" the camera around the desk one time and I can seamlessly loop it.

What I want to achieve is to slow down the video to around 10% of the speed so that the desk rotates very slowly and I can show a call-out about a feature. Then I want to go back to normal speed and slow it down on the next feature to show a call-out again.

I hope this is clear and I want to know if this is possible with FCP. Can you please advice me what should I do in FCP? I created different clips out if these 360 photos, for example with 60fps making each photo 2 frames long. This results in an 18-second long clip. I played around with fps in the project settings and also with the individual frames, but I always loose the "fluid animation" of the desk as soon as I slow down the clip too much.

What can I do?
Should I use a plug-in like Twixtor or is it possible to do some tasks to get a clip with 240fps, so that a smooth slo-mo is possible?

Thanks for your help.

Best regards,
Simon

Welcome Simon to fcp.co
The math and concept of slowmo - always big fun

Simon75A wrote:
…
…I created different clips out if these 360 photos, for example with 60fps making each photo 2 frames long. This results in an 18-second long clip. …

No…?

360 x 2 = 720 frames
720 ./. 60fps = 12 secs

fps stands for frames-per-second…

so, when you playback each of your photos in a 30fps project, it takes … 12secs - which is a mildly spoken a very boring Ballhaus-circle, showing just a desk.

when you playback every 4th of your photos in a 30fps project, it takes 360/4=90, 90/30= 3secs

when you double the 'projection time' of each photo, you pic-sequence results in a 30fps project in almost half a minute (24 secs) just showing a desk …

if your project is set to 24fps, the numbers shift… 360 frames = 15secs, 720frames=30secs

…

I think, you see the math principle …
No need for twixtor or FCPX' built-in Opticalflow.-

I think we all dealt with this exact same inquiry sufficiently over on apple's FCPX forum.

bogiesan wrote: I think we all dealt with this exact same inquiry sufficiently over on apple's FCPX forum.

Yes, I think this thread can be closed.