<p>You should be safe setting playback rate at 0.400. 59.94 is actually 60/1.001 and 23.976 is actually 24/1.001, so the 0.4 multiplier is technically exact. Switch off resample to be sure. Of course, how Vegas actually handles this internally is anybody's guess.</p>

<p>One way to test this would be to generate a frame sequence just containing an incremental numeral display (1,2,3...) in AE or similar, then render that as a 59.94p video. Import in vegas with playback 0.4 and resample off and then cycle through the frames to see if there are any duplicates or missing.</p>

CC BY-SA 3.0
2012-02-18T18:23:57.680Z
Your experiment solves the problem as exactly as possible. Wonder why I didn' think about that before. Thanks!
Frantisek
CC BY-SA 3.0
2012-02-18T17:45:29.320Z
2012-02-18T17:45:29.320Z
Gyan
<p>Let me start at the very beginning:</p>

<p>My project frame rate is 23.976 fps (standard film). When I create such a project in Adobe Premiere and then want to add a clip to the timeline, I can set the frame rate of the clip manually. Therefore, when my clip is 60 fps shot with a Canon DSLr (actually I believe and hope it's 59.94 fps), I can override its fps to 23.976 and then drop it to the timeline, thus getting the perfect slow-motion = as slow as possible without any frames missing in-between.</p>

<p>Now, I don't know how do I do this in Vegas Pro 11. All I can do is drop the clip to the time-line and then set its playback rate to 0.4x original speed (59.94 * 0.4 = 23.976). However, I don't know how safe this is. Is it safe to assume that the playback speed of the clip will be EXACTLY 23.976 fps and there won't be any frames missing in-between, thus creating the perfect slow-motion?</p>

CC BY-SA 3.0
2012-02-16T19:59:31.663Z
Well, if it looks good, then no one can blame you. (Just advertising for Adobe After Effects here.. ^^ )
Friend of Kim
CC BY-SA 3.0
2012-02-21T22:32:26.457Z
I am very sorry I did not understand your question correctly, I have since deleted my answer.
filzilla
<premiere><slowmotion><vegas-pro>
How do I PROPERLY slow down a 60 fps clip in Vegas Pro 11?
Frantisek
# How do I PROPERLY slow down a 60 fps clip in Vegas Pro 11?

(Asked by: username_0 on 2012-02-16)

Let me start at the very beginning:

My project frame rate is 23.976 fps (standard film). When I create such a project in Adobe Premiere and then want to add a clip to the timeline, I can set the frame rate of the clip manually. Therefore, when my clip is 60 fps shot with a Canon DSLr (actually I believe and hope it's 59.94 fps), I can override its fps to 23.976 and then drop it to the timeline, thus getting the perfect slow-motion = as slow as possible without any frames missing in-between.

Now, I don't know how do I do this in Vegas Pro 11. All I can do is drop the clip to the time-line and then set its playback rate to 0.4x original speed (59.94 \* 0.4 = 23.976). However, I don't know how safe this is. Is it safe to assume that the playback speed of the clip will be EXACTLY 23.976 fps and there won't be any frames missing in-between, thus creating the perfect slow-motion?

**Tags:** premiere, slowmotion, vegas-pro

> **Comments:**
> **username_1**: Well, if it looks good, then no one can blame you. (Just advertising for Adobe After Effects here.. ^^ )  
> **username_2**: I am very sorry I did not understand your question correctly, I have since deleted my answer.  

---

## 1 answers

### Answer by username_3 on 2012-02-18. Score: 2 | Accepted answer

You should be safe setting playback rate at 0.400. 59.94 is actually 60/1.001 and 23.976 is actually 24/1.001, so the 0.4 multiplier is technically exact. Switch off resample to be sure. Of course, how Vegas actually handles this internally is anybody's guess.

One way to test this would be to generate a frame sequence just containing an incremental numeral display (1,2,3...) in AE or similar, then render that as a 59.94p video. Import in vegas with playback 0.4 and resample off and then cycle through the frames to see if there are any duplicates or missing.

> **Comments:**
> **username_0**: Your experiment solves the problem as exactly as possible. Wonder why I didn' think about that before. Thanks!  

---

