[FFmpeg-user] FFmpeg manual - asking for clarification of a definition

ILJA SHEBALIN iljashebalin2 at gmail.com
Tue Oct 24 02:39:43 EEST 2017


Autocorrection option is actiually on hence this gibberish. To reitterate
my question: what bits of the data are actually read when -t is put before
an input file?

On Tue, Oct 24, 2017 at 2:37 AM, ILJA SHEBALIN <iljashebalin2 at gmail.com>
wrote:

> Okm then to simplify the question what what bits of data are actually read
> when -t is before an  input file?
>
> On Tue, Oct 24, 2017 at 2:23 AM, Carl Eugen Hoyos <ceffmpeg at gmail.com>
> wrote:
>
>> 2017-10-23 23:29 GMT+02:00 ILJA SHEBALIN <iljashebalin2 at gmail.com>:
>> > FFmpeg manual - Main options;
>> >
>> > -t duration (*input/output*)
>> >
>> > When used as an input option (before -i), limit the duration of data
>> read
>> > from the input file.
>> >
>> > I have a hard time understanding what the formulation was supposed to
>> > denote. Is the option limiting the data to the *duration *or is the data
>> > that's out of the scope of the *duration *is read?
>>
>> (I don't understand this question, sorry)
>>
>> Normally, -t is used like:
>> $ ffmpeg -i input -t 10 output
>> Only ten seconds are encoded.
>> The following is possible:
>> $ ffmpeg -i input -t 10 output1 output2
>> output2 has the duration of the input file
>> $ ffmpeg -t 10 -i input output1 output2
>> All output files are ten seconds long.
>>
>> The input option may have issues (although I didn't find
>> any on the bug tracker, I mixed it up with the input
>> option -r).
>>
>> Carl Eugen
>> _______________________________________________
>> ffmpeg-user mailing list
>> ffmpeg-user at ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
>
>
>


More information about the ffmpeg-user mailing list