Liste des Groupes | Revenir à co vms |
>
What?s the most complex *nix command you?ve come across? I think it
has to be ffmpeg. This looks broadly like
>
ffmpeg «local-input-options-1» -i «infile-1» \
«local-input-options-2» -i «infile-2» ... \
«local-output-options-1» «outfile-1» \
«local-output-options-2» «outfile-2» ...
>
The convention is that options apply to the immediately following file
specification: this is prefixed with ?-i? for an input file, and is a
plain argument for an output file. Note the lack of ?global? options:
all settings apply to a particular file.
>
But that?s not where it ends. Certain of the options can specify
?filtergraphs?, which are entire chains of effects operations to be
applied to a particular video or audio stream. The man page talks
about ?simple? versus ?complex? filtergraphs, but even the ?simple?
ones can be pretty complex.
>
Filtergraphs can also be used during real-time playback, with the
?ffplay? command. For example:
>
ffplay -autoexit -vf scale=1152:864,setsar=0.9 \
'Sun Is Shining (Official Video).mp4'
>
That ?-vf? option specifies a sequence of video filters, first to
scale up the video to make more use of my screen, and ?setsar? (?Set
Source Aspect Ratio?) to fix distortion in the shape of the image
(everybody looking squashed) from the original digitization of the
video.
>
What would DCL-style syntax for ffmpeg look like? I suppose one
obvious equivalence would be
>
ffmpeg -
«infile-1»/«local-input-options-1»,«infile-2»/«local-input-options-2»,... -
«outfile-1»/«local-output-options-1»,«outfile-2»/«local-output-options-2»,... -
>
(being very careful about where the commas go), but what about the
syntax for filtergraphs? Would it be something like
>
/vf=(«filter-name-1»=«filter-params-1»,«filter-name-2»=«filter-params-2»...)
>
Does DCL have provision for this sort of complexity?
Les messages affichés proviennent d'usenet.