Re: [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]

Hello,

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.



Regards,

On 24.4.2017 at 14:12, Cley Faye wrote:

2017-04-24 11:22 GMT+02:00 Georgi D. Sotirov :


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@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Warning "Starting new cluster due to timestamp" on muxing two input streams and resulting movie with muted audio at some locations

[Cley Faye]

2017-04-24 11:22 GMT+02:00 Georgi D. Sotirov :

> 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@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [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]

On 24/04/2017 at 11:39, Cley Faye wrote:

2017-04-24 9:58 GMT+02:00 Georgi D. Sotirov :


Anyone? Meanwhile I've done the muxing with mkvmerge from MKVToolNix <
https://mkvtoolnix.download/> package without any problem and muxed other
movies with FFmpeg successfully.

​Could you give us the full command line and output from ffmpeg?​

Hello,

Sure, the steps to reproduce were the following (i.e. the same that was 
done here ):


1. Download Sintel movie from https://durian.blender.org/download/ :

   ffmpeg -i Sintel.2010.1080p.mkv
   ffmpeg version 3.3 Copyright (c) 2000-2017 the FFmpeg developers
  built with gcc 5.3.0 (GCC)
  configuration: --arch=x86_64 --target-os=linux --prefix=/usr
   --libdir=/usr/lib64 --mandir=/usr/man --docdir=/usr/doc/ffmpeg-3.3
   --enable-gpl --enable-version3 --disable-static --enable-shared
   --enable-runtime-cpudetect --enable-ffmpeg --enable-ffplay
   --enable-ffprobe --enable-ffserver --enable-doc --enable-avdevice
   --enable-avcodec --enable-avformat --enable-swresample
   --enable-swscale --enable-postproc --enable-avfilter
   --enable-avresample --enable-pthreads --enable-bzlib
   --enable-chromaprint --enable-gmp --enable-frei0r --enable-gnutls
   --enable-iconv --enable-ladspa --enable-libass --enable-libbluray
   --enable-libbs2b --enable-libcaca --enable-libcdio
   --enable-libdc1394 --enable-libflite --enable-libfontconfig
   --enable-libfreetype --enable-libfribidi --enable-libgme
   --enable-libgsm --enable-libiec61883 --enable-libilbc
   --enable-libkvazaar --enable-libmodplug --enable-libmp3lame
   --enable-libopencore-amrnb --enable-libopencore-amrwb
   --enable-libopenjpeg --enable-libopenmpt --enable-libopus
   --enable-libpulse --enable-librubberband --enable-librtmp
   --enable-libschroedinger --enable-libsmbclient --enable-libsnappy
   --enable-libsoxr --enable-libspeex --enable-libssh
   --enable-libtesseract --enable-libtheora --enable-libtwolame
   --enable-libv4l2 --enable-libvidstab --enable-libvorbis
   --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265
   --enable-libxcb --enable-libxvid --enable-libzvbi --enable-lzma
   --enable-netcdf --enable-openal --enable-opengl --enable-zlib
   --enable-vaapi --enable-vdpau --enable-videotoolbox --disable-debug
  libavutil  55. 58.100 / 55. 58.100
  libavcodec 57. 89.100 / 57. 89.100
  libavformat57. 71.100 / 57. 71.100
  libavdevice57.  6.100 / 57.  6.100
  libavfilter 6. 82.100 /  6. 82.100
  libavresample   3.  5.  0 /  3.  5.  0
  libswscale  4.  6.100 /  4.  6.100
  libswresample   2.  7.100 /  2.  7.100
  libpostproc54.  5.100 / 54.  5.100
   Input #0, matroska,webm, from 'Sintel.2010.1080p.mkv':
  Metadata:
encoder : libebml v1.0.0 + libmatroska v1.0.0
creation_time   : 2011-04-25T12:57:46.00Z
  Duration: 00:14:48.03, start: 0.00, bitrate: 10562 kb/s
Chapter #0:0: start 0.00, end 103.125000
Metadata:
  title   : Chapter 01
Chapter #0:1: start 103.125000, end 148.667000
Metadata:
  title   : Chapter 02
Chapter #0:2: start 148.667000, end 349.792000
Metadata:
  title   : Chapter 03
Chapter #0:3: start 349.792000, end 437.208000
Metadata:
  title   : Chapter 04
Chapter #0:4: start 437.208000, end 472.075000
Metadata:
  title   : Chapter 05
Chapter #0:5: start 472.075000, end 678.833000
Metadata:
  title   : Chapter 06
Chapter #0:6: start 678.833000, end 744.083000
Metadata:
  title   : Chapter 07
Chapter #0:7: start 744.083000, end 888.032000
Metadata:
  title   : Chapter 08
Stream #0:0(eng): Video: h264 (High), yuv420p(tv,
   bt709/unknown/unknown, progressive), 1920x818, SAR 1:1 DAR 960:409,
   24 fps, 24 tbr, 1k tbn, 48 tbc
Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1(side), fltp, 640 kb/s
Metadata:
  title   : AC3 5.1 @ 640 Kbps
Stream #0:2(ger): Subtitle: subrip
Stream #0:3(eng): Subtitle: subrip
Stream #0:4(spa): Subtitle: subrip
Stream #0:5(fre): Subtitle: subrip
Stream #0:6(ita): Subtitle: subrip
Stream #0:7(dut): Subtitle: subrip
Stream #0:8(pol): Subtitle: subrip
Stream #0:9(por): Subtitle: subrip
Stream #0:10(rus): Subtitle: subrip
Stream #0:11(vie): Subtitle: subrip

2. Extract audio (FFMpeg banner and Input #0 stripped, same as in step 1):

   ffmpeg -i Sintel.2010.1080p.mkv -vn -map 0:1 -map_chapters -1 -c:a
   copy Sintel.2010.1080p.audio.mkv
   ...
   Output #0, matroska, to 'Sintel.2010.1080p.audio.mkv':
  Metadata:
encoder : Lavf57.71.100
Stream #0:0(eng): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz,
   5.1(

Re: [FFmpeg-user] Warning "Starting new cluster due to timestamp" on muxing two input streams and resulting movie with muted audio at some locations

[Cley Faye]

2017-04-24 9:58 GMT+02:00 Georgi D. Sotirov :

> Anyone? Meanwhile I've done the muxing with mkvmerge from MKVToolNix <
> https://mkvtoolnix.download/> package without any problem and muxed other
> movies with FFmpeg successfully.
>

​Could you give us the full command line and output from ffmpeg?​


-- 
Cley Faye
http://cleyfaye.net
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [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]

Anyone? Meanwhile I've done the muxing with mkvmerge from MKVToolNix 
 package without any problem and muxed 
other movies with FFmpeg successfully.



Regards,
--
Georgi D. Sotirov

On 17/04/2017 at 12:23, Georgi D. Sotirov wrote:

Hello,

I'm having the warning "/Starting new cluster due to timestamp/" when 
trying to mux the video and the audio from two (matroska) input 
streams by just copying the video from the first and the audio from 
the second them (i.e. without re-encoding). The resulting movie is 
scrambled - the video is OK, but the audio is inconsistent - it's 
muted in random locations. It's the same problem explained here 
 and I reproduce 
it with Sintel movie  as given 
in the example. The strange is that I've done the same operation many 
times in the past and I'm not sure why I have this warning just now as 
in the source it seem to have been introduced almost 3 years ago (see 
commit 7923aa0fba6b7b55ebbe1af8b7620060f36a1133 
). 
Thus, I normally receive the same warning with newly released FFmpeg 
3.3 as well as with previous 3.2.4 version.


So is there any way to solve this problem, avoid the warning and 
produce movie without muted sound?



Best regards,
--
Georgi D. Sotirov



___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

[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]

Hello,

I'm having the warning "/Starting new cluster due to timestamp/" when 
trying to mux the video and the audio from two (matroska) input streams 
by just copying the video from the first and the audio from the second 
them (i.e. without re-encoding). The resulting movie is scrambled - the 
video is OK, but the audio is inconsistent - it's muted in random 
locations. It's the same problem explained here 
 and I reproduce it 
with Sintel movie  as given in the 
example. The strange is that I've done the same operation many times in 
the past and I'm not sure why I have this warning just now as in the 
source it seem to have been introduced almost 3 years ago (see commit 
7923aa0fba6b7b55ebbe1af8b7620060f36a1133 
). 
Thus, I normally receive the same warning with newly released FFmpeg 3.3 
as well as with previous 3.2.4 version.


So is there any way to solve this problem, avoid the warning and produce 
movie without muted sound?



Best regards,
--
Georgi D. Sotirov
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".