Answers.Body: <p>With ffprobe 5.1 or later, you can add <code>-o OUTFILE</code> to store probe data in a file.</p>
  <p>If using redirection with earlier versions, redirect stderr as well.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-03T00:52:34.920Z
Answers.Text: I have tried this, but I believe this is part of ffmpeg and not ffprobe. It works in ffmpeg when converting or remuxing, but I am unable to get output saved to a file with the same flag.
Answers.UserDisplayName: Mr. Mendelli
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-04-03T03:57:21.557Z
Answers.Text: ffmpeg has no `-o` option.
Answers.UserDisplayName: Gyan
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-03-25T04:31:38.860Z
Answers.LastActivityDate: 2024-03-25T04:31:38.860Z
Answers.UserDisplayName: Gyan
Body: <p>I made a script for ffprobe I can use to view information of my media more easily.  An additional feature I want is to breakout the output information to a log file.</p>
  <p>Implementation 1:</p>
  <pre><code>@echo off
  
  for %%f in (%*) do (ffprobe -hide_banner -i %%f&gt;&quot;%~dp1ffprobe.log)
  </code></pre>
  <p>Implementation 2:</p>
  <pre><code>@echo off
  
  (
  for %%f in (%*) do (ffprobe -hide_banner -i %%f)
  )&gt;&quot;%~dp1ffprobe.log&quot;
  </code></pre>
  <p>The issue I am having is that the log is being created in the expected location but it it always empty with either of these implementations. Usually either of these methods for breaking into a file have worked for me. Is there a native or alternative way of accomplishing this?</p>
  
Tags: <ffmpeg><windows><ffprobe>
Title: Save ffprobe Output to Log File?
UserDisplayName: Mr. Mendelli
ThreadText: # Save ffprobe Output to Log File?
  
  (Asked by: username_0 on 2024-03-24)
  
  I made a script for ffprobe I can use to view information of my media more easily. An additional feature I want is to breakout the output information to a log file.
  
  Implementation 1:
  
  ```
  @echo off
  
  for %%f in (%*) do (ffprobe -hide_banner -i %%f>"%~dp1ffprobe.log)
  
  ```
  
  Implementation 2:
  
  ```
  @echo off
  
  (
  for %%f in (%*) do (ffprobe -hide_banner -i %%f)
  )>"%~dp1ffprobe.log"
  
  ```
  
  The issue I am having is that the log is being created in the expected location but it it always empty with either of these implementations. Usually either of these methods for breaking into a file have worked for me. Is there a native or alternative way of accomplishing this?
  
  **Tags:** ffmpeg, windows, ffprobe
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-03-25. Score: 1
  
  With ffprobe 5.1 or later, you can add `-o OUTFILE` to store probe data in a file.
  
  If using redirection with earlier versions, redirect stderr as well.
  
  > **Comments:**
  > **username_0**: I have tried this, but I believe this is part of ffmpeg and not ffprobe. It works in ffmpeg when converting or remuxing, but I am unable to get output saved to a file with the same flag.  
  > **username_1**: ffmpeg has no `-o` option.  
  
  ---
  
  