Open philpax opened 8 months ago
can always make a transcode-interactive.py that does this separately and calls transcode.py with adequate arguments. Alternatively calling it with just an input file puts it in interactive mode, won't be a "breaking change" as no arguments is currently not a use case
Right now, when you run the script, you need to have some idea of what's in the file you're dealing with. You can run the script with
-d
to get more information, but it's a bit slipshod.Instead, what we could do is use
ffprobe
( https://stackoverflow.com/questions/7708373/get-ffmpeg-information-in-friendly-way ) to get information about the streams in the file, and use that to create a wizard for the user to follow. (i.e. "english subtitles, japanese audio, cpu encode")This would also help with #4 as it could be intelligently brought to the user and dealt with.
However, this would break any kind of automated use. I don't think any of us are doing that, and even if we were, you'd still have the same issue about having to intelligently decide which streams to use.