Answers.Body: <p>Place those options <strong>before</strong> <code>-i "1"</code></p>
  
  <p>In ffmpeg, parameters and flags apply to the next input/output entry.</p>
  
  <p>So,</p>
  
  <pre><code>ffmpeg {-flags for input1} -i input1 {-flags for input2} -i input2 {-flags for output1} output1 {-flags for output2} output2
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-18T12:33:07.737Z
Answers.LastActivityDate: 2015-12-18T12:33:07.737Z
Answers.UserDisplayName: Gyan
Body: <p>Situation: cash-strapped ivory tower visionary and ffmpeg newbie manacled to a 2nd hand 2010 Macbook Pro concealing a 'Black Screen of Death' NVIDIA GeForce GT 330M graphics chip.</p>
  
  <p>With the help of the gfxCardStatus app (option 'Integrated Only' selected), I overcame this particular Apple quality control failure to record fullscreen video and at full resolution, using the following command:</p>
  
  <pre><code>ffmpeg -video_size 1680x1050 -framerate 30 -f avfoundation -i "1" -c:v libx264 -qp 0 -preset ultrafast -capture_cursor 1 -capture_mouse_clicks 1 capture.mkv
  </code></pre>
  
  <p><strong>The capture_cursor and capture_mouse_clicks options, however, are steadfastly ignored.</strong></p>
  
  <p>Aside from these omissions, ffmpeg is recording at a quality and smoothness better than any of the screencapture/screencast apps I've tried, so for once I'm pretty sure this has nothing to do with the crap hardware, but rather with my use of ffmpeg.</p>
  
  <p>There is nothing to suggest the installation/compilation process went wrong, for which I used:</p>
  
  <pre><code>$ brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-frei0r --with-libass --with-libvo-aacenc --with-libvorbis --with-libvpx --with-opencore-amr --with-openjpeg --with-opus --with-rtmpdump --with-schroedinger --with-speex --with-theora --with-tools --with-libavformat --with-OpenCV --with-libx264
  </code></pre>
  
  <p><strong>Is there something I'm overlooking, but which is needed for capture_cursor and capture_mouse_clicks to work? Compilation parameter? ffmpeg option order? Some OS flag setting?</strong></p>
  
  <p><strong>Operating System</strong>
   - OS X Yosemite
   - Version 10.10.5 (14F1021)</p>
  
  <p><strong>Hardware:</strong></p>
  
  <ul>
  <li>MacBook Pro (15-inch, Mid 2010)</li>
  <li>Processor 2.8 GHz Intel Core i7</li>
  <li>Memory 8 GB 1067 MHz DDR</li>
  <li>Graphics Intel HD Graphics 288 MB</li>
  <li>NVIDIA GeForce GT 330M</li>
  </ul>
  
  <hr>
  
  <p><strong>Addendum</strong></p>
  
  <p>Here the ffmpeg video capture command usage, following the guidelines provided by @Mulvya:</p>
  
  <pre><code>$ ffmpeg -video_size 1680x1050 -framerate 30 -f avfoundation -capture_cursor 1 -capture_mouse_clicks 1 -i "1" -c:v libx264 -qp 0 -preset ultrafast capture.mkv
  </code></pre>
  
Tags: <ffmpeg><video-capture>
Title: Using ffmpeg with avfoundation, capture_cursor and capture_mouse_clicks options are ignored
UserDisplayName: user1019696
ThreadText: # Using ffmpeg with avfoundation, capture_cursor and capture_mouse_clicks options are ignored
  
  (Asked by: username_0 on 2015-12-18)
  
  Situation: cash-strapped ivory tower visionary and ffmpeg newbie manacled to a 2nd hand 2010 Macbook Pro concealing a 'Black Screen of Death' NVIDIA GeForce GT 330M graphics chip.
  
  With the help of the gfxCardStatus app (option 'Integrated Only' selected), I overcame this particular Apple quality control failure to record fullscreen video and at full resolution, using the following command:
  
  ```
  ffmpeg -video_size 1680x1050 -framerate 30 -f avfoundation -i "1" -c:v libx264 -qp 0 -preset ultrafast -capture_cursor 1 -capture_mouse_clicks 1 capture.mkv
  
  ```
  
  **The capture\_cursor and capture\_mouse\_clicks options, however, are steadfastly ignored.**
  
  Aside from these omissions, ffmpeg is recording at a quality and smoothness better than any of the screencapture/screencast apps I've tried, so for once I'm pretty sure this has nothing to do with the crap hardware, but rather with my use of ffmpeg.
  
  There is nothing to suggest the installation/compilation process went wrong, for which I used:
  
  ```
  $ brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-frei0r --with-libass --with-libvo-aacenc --with-libvorbis --with-libvpx --with-opencore-amr --with-openjpeg --with-opus --with-rtmpdump --with-schroedinger --with-speex --with-theora --with-tools --with-libavformat --with-OpenCV --with-libx264
  
  ```
  
  **Is there something I'm overlooking, but which is needed for capture\_cursor and capture\_mouse\_clicks to work? Compilation parameter? ffmpeg option order? Some OS flag setting?**
  
  **Operating System**
  - OS X Yosemite
  - Version 10.10.5 (14F1021)
  
  **Hardware:**
  
  * MacBook Pro (15-inch, Mid 2010)
  * Processor 2.8 GHz Intel Core i7
  * Memory 8 GB 1067 MHz DDR
  * Graphics Intel HD Graphics 288 MB
  * NVIDIA GeForce GT 330M
  
  ---
  
  **Addendum**
  
  Here the ffmpeg video capture command usage, following the guidelines provided by @Mulvya:
  
  ```
  $ ffmpeg -video_size 1680x1050 -framerate 30 -f avfoundation -capture_cursor 1 -capture_mouse_clicks 1 -i "1" -c:v libx264 -qp 0 -preset ultrafast capture.mkv
  
  ```
  
  **Tags:** ffmpeg, video-capture
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-12-18. Score: 7 | Accepted answer
  
  Place those options **before** `-i "1"`
  
  In ffmpeg, parameters and flags apply to the next input/output entry.
  
  So,
  
  ```
  ffmpeg {-flags for input1} -i input1 {-flags for input2} -i input2 {-flags for output1} output1 {-flags for output2} output2
  
  ```
  
  
  ---
  
  