Add Capability to specify FFMPEG Path to Whisperer #2511
+4
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Issue
There are scenarios where specifying a default
ffmpeg
executable path is essential for achieving desired functionality. By default, the program attempts to use the globally availableffmpeg
command, but this approach might not always work.For instance, a common error that users may encounter is:
This error often arises when
ffmpeg
is not properly installed or accessible due to specific system configurations. Even after installingffmpeg
, users might face challenges if their environment is not set up correctly.Proposed Solution
To make configuration more flexible and user-friendly, this update allows users to explicitly specify the path to the
ffmpeg
executable. By setting the path programmatically, users can avoid system-level issues and ensure the correct executable is used.Here’s an example of how this can be configured:
Benefits
ffmpeg
path based on their specific environment, bypassing global configuration issues.ffmpeg
installations.