<p>FFMPEG is probably a better tool for the job, if you are prepared to deal with the command line. Install ffmpeg from the packages found <a href="https://ffmpeg.org/download.html" rel="nofollow">here</a>. These are all ready-built and should have all the included libraries you need.</p>

<p>Once you've installed ffmpeg you will need to run it from the command line. Since there's different ways of doing that depending on your platform, the one safe bet is that if you drag the ffmpeg icon into the command line window you should get the path to the ffmpeg executable auto-filled for you. Next you type out a command like this:</p>

<pre><code>&lt;ffmpeg executable path&gt; -r 60 -i &lt;input path&gt; -preset ultrafast -crf 0 -r 30 -c:a copy &lt;output path.mp4&gt;
</code></pre>

<p>for a lossless mp4 file or</p>

<pre><code>&lt;ffmpeg executable path&gt; -r 60 -i &lt;input path&gt; c:v prores -profile:v 3 -r 30 -c:a copy &lt;output path.mov&gt;
</code></pre>

<p>for a prores encoded quicktime file (ffmpeg <em>will</em> encode prores on Windows and Linux, but whether ProRes is readable depends on what software you're editing on. Alternatives are DNxHD/DNxHR and Cineform, but that's beyond the scope of this answer).</p>

<p>In both instances the <code>&lt;ffmpeg executable path&gt;</code>, <code>&lt;input path&gt;</code> and <code>&lt;output path.mp4&gt;</code> means the path to the respective files, i.e. what you get when you drag them into the terminal. So to fill out the path to the input file, just drag it into the terminal. Since the output file doesn't exist, copy the input file and change the name and extension to whatever you want. On Windows it will be something like <code>"c:\users\stib\folder\another folder\movie1.mp4"</code> on a mac it will be <code>/Users/stib/folder/another\ folder/movie1.mp4</code> Linux will be similar to mac (though the home folder will vary depending on your distro. But anyway…).</p>

<p>The first example use h.264 compression with the Constant Rate Factor <code>-crf</code> (inverse of quality) set to <code>0</code> or lossless. Since you're not looking for small file sizes the preset is set to ultrafast and the audio codec <code>-c:a</code> is set to copy (this is assuming you're using an mp4 as input) so that the audio will not be re-encoded.</p>

<p>The second uses prores compression with the <code>-profile:v 3</code> setting it to ProRes HQ, a very solid codec for editing work on Macs or Windows machines using Adobe Premiere. You could change this to Avid DNxHD or other codecs of your choice, with ffmpeg there are literally <a href="https://ffmpeg.org/ffmpeg-codecs.html" rel="nofollow">hundreds to choose from</a>.</p>

<p>In both examples I changed the video frame rate using <code>-r 30</code>, this will drop input frames to output a constant 30fps. Since your input is 59.94fps.</p>

<p>I also used <code>-r 60</code> before the <code>-i</code> input flag to force ffmpeg to treat the input file as 60fps (although it doesn't add or remove frames, just changes the way they are interpreted). You could instead change your output to 29.97 fps by using <code>-r 30000/1001</code> instead of <code>-r 30</code> for the output, and not bother putting a <code>-r</code> rate flag before the input.</p>

<p>Applying this to a whole folder of files involves using the shell. How you do that depends on your OS.</p>

<p>on a Mac or Linux machine, here's one way </p>

<pre><code>cd "/path/to/my folder of media/"
mkdir "30FPS_converted"
for i in *.mov; do
ffmpeg -i $i &lt;ffmpeg options here&gt; "./30FPS_converted/${i/mov/mp4};"
done
</code></pre>

<ol>
<li>change directory to the folder using the <code>cd</code> command, e.g. <code>cd "/Users/stib/my media/folder1"</code> once again, you can drag the folder onto the terminal window.</li>
<li>Create a new directory for your output files with the <code>mkdir</code> command (or do it in finder / file browser of your choice.</li>
<li>create a loop with the contents of the folder using the <code>for</code> command, and use that to provide the input for the ffmpeg command. The command above creates a list of all the files with the suffix ".mov", creates a variable <code>$i</code> and every time the loop goes round it changes the value of <code>$i</code> to the next file in the list. The <code>${i/mov/mp4}</code> is called brace substitution. It substitutes the letters "mov" in the value of $i with the letters "mp4"</li>
</ol>

<p>On Windows here's how you'd do it with Powershell (you could do it it with batch scripting, but I refuse to learn batch scripting):</p>

<pre><code>set-location "c:\Users\me\my media files\"
new-item "30FPS_converted" -type directory
get-childItem*.mov | foreach {
ffmpeg -i $_ &lt;ffmpeg options here&gt; (".\30FPS_converted" + $_.name.replace("mov", "mp4))}
</code></pre>

<ol>
<li>change directory to the folder using the <code>Set-Location</code> command (though usually <code>cd</code> works too), e.g. <code>Set-Location "C:\Users\stib\my media\folder1"</code> once again, you can drag the folder onto the terminal window.</li>
<li>make a new directory using the new-item command (mkdir usually works too). In the example above the path for the output folder is <code>.</code> (a full stop), this means "the current directory"</li>
<li>list the files in the folder (<code>get-childItem</code>, though usually <code>ls</code> works too) that end with the suffix you're after, and pipe <code>|</code> the output to a <code>foreach</code> loop. Inside that loop the variable <code>$_</code> takes on the value of the file objects in the list one by one. Then use the <code>name.replace()</code> function to create the appropriate output name, and append that to the directory name.</li>
</ol>

<p>Obviously if your source files aren't .movs you change the .mov bits in the command to whatever you've got, and the same for the output file extension.</p>

CC BY-SA 3.0
2016-07-09T17:09:42.717Z
Awesome! Can this take a whole folder of video as input?
Anson Savage
CC BY-SA 3.0
2016-07-09T17:10:40.557Z
For 29.97, it's better to represent r as `30000/1001`.
Gyan
CC BY-SA 3.0
2016-07-09T17:16:39.133Z
Oh, and you can skip the `:v` after `-r`. Unlike, `-b` , `-r` is taken to refer to video.
Gyan
CC BY-SA 3.0
2016-07-09T16:51:27.660Z
2016-07-11T08:03:18.947Z
2016-07-11T08:03:18.947Z
stib
<p>I'm making the 3rd instalment of my Sand Wars series (<a href="https://www.youtube.com/watch?v=dpENrCozv34" rel="nofollow noreferrer">Sand Wars II</a>) and I shot the majority of my footage at 60p (which I think means 60fps and progressive rather than interlaced).  I do <em>not</em> want to rotoscope lightsabers 60 frames per second and would much rather do 30. The footage is currently at 59.94, which I think is close enough to 60. I know I can lower the frame rate using HandBrake, but I don't want to have to lose more quality than I already will, as each clip is probably going to be run through Blender a few times.  What settings can I enable on HandBrake to take an entire folder of my footage (I don't want to have to do this hundreds of times for each video file) and output it into another folder with each video having a frame rate of 30 fps (or 29.97) with as <em>little quality loss as possible</em>?</p>
<p>Thanks,
Anson</p>

CC BY-SA 3.0
2016-07-09T14:27:55.837Z
I think you're probably pushing Handbrake further than it was designed to go. I'd suggest using ffmpeg - it's the right tool for the job. `ffmpeg -i input.mp4 -preset ultrafast -crf 0 -r:v 30 -c:a copy output.mp4` will do a lossless h.264 encode of your footage at 25fps. You could also use another codec, h.264 can be dodgy for editing. For example prores: `ffmpeg -i input.mp4 -c:v prores -profile:v 3 -c:a pcm_s16le -r:v 30 output.mov`.
stib
CC BY-SA 3.0
2016-07-09T15:21:13.280Z
@stib Sounds cool! I am not sure how to do anything like that (I probably sounded like I know more than I do). If you could put some instructions in an answer, that would be great!
Anson Savage
<video-quality><framerate><blender><handbrake>
How to change framerate with HandBrake without side effects
Anson Savage
# How to change framerate with HandBrake without side effects

(Asked by: username_0 on 2016-07-08)

I'm making the 3rd instalment of my Sand Wars series ([Sand Wars II](https://www.youtube.com/watch?v=dpENrCozv34)) and I shot the majority of my footage at 60p (which I think means 60fps and progressive rather than interlaced). I do *not* want to rotoscope lightsabers 60 frames per second and would much rather do 30. The footage is currently at 59.94, which I think is close enough to 60. I know I can lower the frame rate using HandBrake, but I don't want to have to lose more quality than I already will, as each clip is probably going to be run through Blender a few times. What settings can I enable on HandBrake to take an entire folder of my footage (I don't want to have to do this hundreds of times for each video file) and output it into another folder with each video having a frame rate of 30 fps (or 29.97) with as *little quality loss as possible*?

Thanks,
Anson

**Tags:** video-quality, framerate, blender, handbrake

> **Comments:**
> **username_1**: I think you're probably pushing Handbrake further than it was designed to go. I'd suggest using ffmpeg - it's the right tool for the job. `ffmpeg -i input.mp4 -preset ultrafast -crf 0 -r:v 30 -c:a copy output.mp4` will do a lossless h.264 encode of your footage at 25fps. You could also use another codec, h.264 can be dodgy for editing. For example prores: `ffmpeg -i input.mp4 -c:v prores -profile:v 3 -c:a pcm_s16le -r:v 30 output.mov`.  
> **username_0**: @username_1 Sounds cool! I am not sure how to do anything like that (I probably sounded like I know more than I do). If you could put some instructions in an answer, that would be great!  

---

## 1 answers

### Answer by username_1 on 2016-07-09. Score: 4

FFMPEG is probably a better tool for the job, if you are prepared to deal with the command line. Install ffmpeg from the packages found here. These are all ready-built and should have all the included libraries you need.
Once you've installed ffmpeg you will need to run it from the command line. Since there's different ways of doing that depending on your platform, the one safe bet is that if you drag the ffmpeg icon into the command line window you should get the path to the ffmpeg executable auto-filled for you. Next you type out a command like this:
 -r 60 -i  -preset ultrafast -crf 0 -r 30 -c:a copy 

for a lossless mp4 file or
 -r 60 -i  c:v prores -profile:v 3 -r 30 -c:a copy 

for a prores encoded quicktime file (ffmpeg will encode prores on Windows and Linux, but whether ProRes is readable depends on what software you're editing on. Alternatives are DNxHD/DNxHR and Cineform, but that's beyond the scope of this answer).
In both instances the ,  and  means the path to the respective files, i.e. what you get when you drag them into the terminal. So to fill out the path to the input file, just drag it into the terminal. Since the output file doesn't exist, copy the input file and change the name and extension to whatever you want. On Windows it will be something like "c:\users\username_1\folder\another folder\movie1.mp4" on a mac it will be /Users/username_1/folder/another\ folder/movie1.mp4 Linux will be similar to mac (though the home folder will vary depending on your distro. But anyway…).
The first example use h.264 compression with the Constant Rate Factor -crf (inverse of quality) set to 0 or lossless. Since you're not looking for small file sizes the preset is set to ultrafast and the audio codec -c:a is set to copy (this is assuming you're using an mp4 as input) so that the audio will not be re-encoded.
The second uses prores compression with the -profile:v 3 setting it to ProRes HQ, a very solid codec for editing work on Macs or Windows machines using Adobe Premiere. You could change this to Avid DNxHD or other codecs of your choice, with ffmpeg there are literally hundreds to choose from.
In both examples I changed the video frame rate using -r 30, this will drop input frames to output a constant 30fps. Since your input is 59.94fps.
I also used -r 60 before the -i input flag to force ffmpeg to treat the input file as 60fps (although it doesn't add or remove frames, just changes the way they are interpreted). You could instead change your output to 29.97 fps by using -r 30000/1001 instead of -r 30 for the output, and not bother putting a -r rate flag before the input.
Applying this to a whole folder of files involves using the shell. How you do that depends on your OS.
on a Mac or Linux machine, here's one way 
cd "/path/to/my folder of media/"
mkdir "30FPS_converted"
for i in *.mov; do
ffmpeg -i $i  "./30FPS_converted/${i/mov/mp4};"
done


change directory to the folder using the cd command, e.g. cd "/Users/username_1/my media/folder1" once again, you can drag the folder onto the terminal window.
Create a new directory for your output files with the mkdir command (or do it in finder / file browser of your choice.
create a loop with the contents of the folder using the for command, and use that to provide the input for the ffmpeg command. The command above creates a list of all the files with the suffix ".mov", creates a variable $i and every time the loop goes round it changes the value of $i to the next file in the list. The ${i/mov/mp4} is called brace substitution. It substitutes the letters "mov" in the value of $i with the letters "mp4"

On Windows here's how you'd do it with Powershell (you could do it it with batch scripting, but I refuse to learn batch scripting):
set-location "c:\Users\me\my media files\"
new-item "30FPS_converted" -type directory
get-childItem*.mov | foreach {
ffmpeg -i $_  (".\30FPS_converted" + $_.name.replace("mov", "mp4))}


change directory to the folder using the Set-Location command (though usually cd works too), e.g. Set-Location "C:\Users\username_1\my media\folder1" once again, you can drag the folder onto the terminal window.
make a new directory using the new-item command (mkdir usually works too). In the example above the path for the output folder is . (a full stop), this means "the current directory"
list the files in the folder (get-childItem, though usually ls works too) that end with the suffix you're after, and pipe | the output to a foreach loop. Inside that loop the variable $_ takes on the value of the file objects in the list one by one. Then use the name.replace() function to create the appropriate output name, and append that to the directory name.

Obviously if your source files aren't .movs you change the .mov bits in the command to whatever you've got, and the same for the output file extension.

> **Comments:**
> **username_0**: Awesome! Can this take a whole folder of video as input?  
> **username_2**: For 29.97, it's better to represent r as `30000/1001`.  
> **username_2**: Oh, and you can skip the `:v` after `-r`. Unlike, `-b` , `-r` is taken to refer to video.  

---

