[FFmpeg-user] Warning "Starting new cluster due to timestamp" on muxing two input streams and resulting movie with muted audio at some locations
Georgi D. Sotirov
gdsotirov at dir.bg
Sat Apr 29 12:50:42 EEST 2017
Yes, it should be something like this, but I'm not able to reproduce the
warning anymore, so I won't dig further unless it appears again.
On 24.4.2017 at 14:12, Cley Faye wrote:
> 2017-04-24 11:22 GMT+02:00 Georgi D. Sotirov <gdsotirov at dir.bg>:
>> What is the general reason for warning "Starting new cluster due to
>> timestamp" to appear anyway?
> I'm not sure of the exact cause of this warning by ffmpeg, but if the
> actual message is to be trusted (usually it is), it could be an
> inconsistency in timestamps. Clusters are kind of an MKV "unit" that
> contain the actual audio/video data (the frames). If there is a hole in the
> timestamps, or if they are out of order, the muxer might create a new
> cluster to accomodate this.
> Since it only happen on the audio, you might want to check that the audio
> stream itself is well formed, and also check the output file with some
> other player (try ffplay)
> . Other than that, a greater ffmpeg "guru" will have to step in ;)
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user