mirror/ffmprovisr
1
0
Fork 0
mirror of https://github.com/amiaopensource/ffmprovisr.git synced 2025-07-15 13:33:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

added additional text to troubleshooting section

Browse Source
This commit is contained in:
aln363
2023-12-18 16:45:17 -05:00
committed by GitHub
parent ddb89301bf
commit eaef67b683
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
index.html
View File

@ -111,10 +111,13 @@
<input type="checkbox" id="troubleshooting">
<div class="hiding">
<h5>Troubleshooting Common Issues</h5>
<p>There are many common issues you may encounter when using FFmpeg. This section is here to provide some possible explanations and solutions.</p>
<p>There are many common issues you may encounter when using FFmpeg. This section is here to provide some possible explanations and solutions.For more general solutions to issues regarding download, installation, and other possible questions or issues, please refer to the <a href="https://ffmpeg.org/faq.html">FFmpeg FAQ.</p>
<p>Before delving into some specific error messages and what may cause them, there are a few general tips you can follow to help make sure your files are doing what you want them to.
First, always check that the output file actually opens, plays, looks, and/or sounds the way you intended it to. It is possible that FFmpeg will create an output file that, on the surface, looks correct, but upon further inspection, there may be inconsistencies with the codec, extension, or other file information, depending on what you intended to do with the file.
Second, always be certain that the file extension you are using for your output files is the intended extension. Within FFmpeg, certain extensions default to certain codecs, such as <code>.mp4</code> encoding to H.264. You always want to make sure that your extension coincides with your intended codec. A list of extensions and codec defaults can be found <a href="https://amiaopensource.github.io/ffmprovisr/#codec-defaults">here.</a>p>
<h5>General Error Messages</h5>
<p><b>Error: No such file or directory:</b> <img src="img/directory_error_example.png" alt="no such file or directory error message"img></p>
<p>There are a few reasons why this error may be appearing. First, check to make sure that you are in the correct directory. It can be easy to lose track of where your files are actually stored, especially on a personal computer.
If you are working on a personal computer, the easiest way to do this is to check where your files are. When working with MacOS, for example, files are often stored in the downloads or documents folders. To change your directory from home to this specific directory, use the command <code>cd</code> followed by your desired folder. For downloads, it would look like this: <code>cd downloads</code></p>
<p>There are a few reasons why this error may be appearing. First, check to make sure that you are in the correct directory. It can be easy to lose track of where your files are actually stored, especially on a personal computer. If you are working on a personal computer, the easiest way to do this is to check where your files are. When working with MacOS, for example, files are often stored in the downloads or documents folders. To change your directory from home to this specific directory, use the command <code>cd</code> followed by your desired folder. For downloads, it would look like this: <code>cd downloads</code></p>
<p>After you have ensured that you are in the correct directory, and the error is still occurring, check that your argument is formatted correctly. If you are copying and pasting from a separate document or ffmprovisr directly, there may be typos or missing spaces.
If the error message includes other parts of the command, such as a flag, that indicates where your typo or missing space may be, as in this example, where the <code>-c</code> flag has not been separated from the file name:</p>
<p><img src="img/typo_space_error.png" alt="missing space typo error message"img></p>
@ -122,8 +125,8 @@ If the error message includes other parts of the command, such as a flag, that i
<p><b>Killed:</b></p>
<p>"killed" does not appear as a normal error message, but will show up at the end of the progress of the command, and the point at which it appears can vary. Sometimes, after you run a command it will be "killed" immediately, only making it through one frame before terminating, as in this example:</p>
<p><img src="img/first_frame_killed.png" alt="command killed at first frame example" img></p>
<p><b>Could not find tag for codec:</b></p>
<p><b>Error splitting argument list: option not found:</b></p>
<p><b>Could not find tag for codec:</b></p>
<!-- End Troubleshooting Common Issues -->
</div>
<div class="well">