Re: [FFmpeg-user] Concat 2 videos, results in wrong length of the result

On Sat, Sep 9, 2017 at 11:01 AM, Nitish Prabhu wrote: > > Won't altering the timebase for "96.out.mp4" make the "96.new.mp4" play > slower than it was recorded at? > When the timescale is changed here, ffmpeg will rescale the timestamps to maintain timing. There's a

Re: [FFmpeg-user] Concat 2 videos, results in wrong length of the result

On Sat, Sep 9, 2017 at 10:24 AM, Gyan wrote: > > Run this on 96.out.mp4 > > ffmpeg -i 96.out.mp4 -c copy -video_track_timescale 12800 96.new.mp4 > > and concat this with the other file. Won't altering the timebase for "96.out.mp4" make the "96.new.mp4" play slower than

Re: [FFmpeg-user] Concat 2 videos, results in wrong length of the result

On Fri, Sep 8, 2017 at 3:38 PM, Marek Sebera wrote: > > Concat of the 2 videos, of lenght (00:00:21.00) and (00:00:28.03) > results in video of lenght (00:01:54.92), which is obviously wrong. > > > ffprobe of 98.out.mp4 > > Stream #0:0(eng): Video: h264

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

On Fri, Sep 8, 2017 at 5:34 PM, Gyan wrote: > Running > > ffmpeg -seek_timestamp 1 -copyts -ss 1 -i src.mp4 > copyts-seekts-ss1.mp4 > > produces a file, reported as, > > Duration: 00:00:01.00, start: 2.00, bitrate: 276 kb/s > > whose video contents correspond to

[FFmpeg-user] Concat 2 videos, results in wrong length of the result

Hi, I'm trying to concat 2 video files, process that worked pretty well for us for the past few months. Using Debian binary distribution ffmpeg (7:3.2.7-1~deb9u1) and libx264 (libx264-148:amd64 2:0.148.2748+git97eaef2-1) Concat 2 files, ffmpeg command, ffprobe of both source files and result

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote: > >> On 9/8/17, Mike Brown wrote: > >> > Are you saying that it takes a version newer

Re: [FFmpeg-user] Concatenate diffetents video size in one output.mp4

On 08/09/17 at 08:49, Paul B Mahol wrote: > On 9/8/17, Marcelo Laia wrote: > > This one should work from quick look. marcelo@marcelo:~/Vídeos/Ceverja$ ffmpeg -i Parte_A1.mp4 -i Parte_B1.mp4 -filter_complex

Re: [FFmpeg-user] Concatenate diffetents video size in one output.mp4

On 9/8/17, Marcelo Laia wrote: > Hi, > > I would like to concatenate two videos files. > > 1. 352 x 640 > 2. 640 x 352 > > All others parameters are the same. > > I doing a lot of search on google and I tried: > > ffmpeg -i VID-20170820-WA0233_edit_A_B.mp4 -i

[FFmpeg-user] Concatenate diffetents video size in one output.mp4

Hi, I would like to concatenate two videos files. 1. 352 x 640 2. 640 x 352 All others parameters are the same. I doing a lot of search on google and I tried: ffmpeg -i VID-20170820-WA0233_edit_A_B.mp4 -i VID-20170820-WA0233_edit_B.mp4 -filter_complex

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 03:55:35PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote: > >> On 9/8/17, Mike Brown wrote: > >> > Are you saying that it takes a version newer

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote: >> On 9/8/17, Mike Brown wrote: >> > Are you saying that it takes a version newer than what I am using in >> > order >> > to decode Dolby-E to ac3? >>

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 03:13:46PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > Are you saying that it takes a version newer than what I am using in order > > to decode Dolby-E to ac3? > > Yes. Well, I have the latest available from the website

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 02:30:08PM +0200, Paul B Mahol wrote: >> On 9/8/17, Mike Brown wrote: >> > On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote: >> >> On 9/8/17, Mike Brown

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 02:30:08PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote: > >> On 9/8/17, Mike Brown wrote: > > > > [trimmed] > > > >> > Why doesn't it matter?

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote: >> On 9/8/17, Mike Brown wrote: > > [trimmed] > >> > Why doesn't it matter? >> > >> > ffmpeg -i input_test.ts -map 0:1 -c:a pcm_s24le output_test.wav

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 01:39:34PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: [trimmed] > > Why doesn't it matter? > > > > ffmpeg -i input_test.ts -map 0:1 -c:a pcm_s24le output_test.wav > > You need -c:a copy here, but you may also need to override

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

On Fri, Sep 8, 2017 at 3:40 PM, Nicolas George wrote: > No, it does not work that way without copyts: without copyts, the > timestamps always start at 0. > There are two issues: a) how to interpret input frame seek point, and b) what happens to timestamps of selected frames.

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 01:15:06PM +0200, Paul B Mahol wrote: >> On 9/8/17, Mike Brown wrote: >> > On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote: >> >> On 9/8/17, Mike Brown

Re: [FFmpeg-user] Dolby E decoder

> > > > >> ffmpeg -i input.wav -c:a copy -f u8 out.u8 > > > > ffmpeg -i - -c:a copy -f u24le - | \ > > > > The Dolby-E is 24bit, not 8. > > > > Doesn't matter, your example will not work, try it. > > Why doesn't it matter? > > ​When you copy a stream as-is, copying each byte individually or

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 01:15:06PM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote: > >> On 9/8/17, Mike Brown wrote: > >> > On Fri, Sep 08, 2017 at 12:54:12AM +0200,

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote: >> On 9/8/17, Mike Brown wrote: >> > On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote: >> >> (Sorry, my knowledge of SMPTE 337M is

Re: [FFmpeg-user] Dolby E decoder

On Fri, Sep 08, 2017 at 09:34:50AM +0200, Paul B Mahol wrote: > On 9/8/17, Mike Brown wrote: > > On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote: > >> (Sorry, my knowledge of SMPTE 337M is limited but I know that so far, > >> this is the only "format"

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

Le duodi 22 fructidor, an CCXXV, Gyan a écrit : > Except with seek_timestamp set to 1, the first packet you 'expect' to get > is pts_time 60. The purpose of my message was to EXPLAIN what happens, not to provide an ad-hoc solution to the showcase. > And it does work that way if copyts is

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

On Fri, Sep 8, 2017 at 2:53 PM, Nicolas George wrote: > After further testing, it seems the -ss option is itself relative to the > file's start time: by setting -ss 60 with a file that starts at 60, you > are asking to seek to timestamp 120. And with -copyts, you get that >

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

Le duodi 22 fructidor, an CCXXV, Nitish Prabhu a écrit : > I am using "-copyts" to maintain the input timestamps at the output > side. Thus, I believed that using "-ss 60 -t 10" with "-copyts" was > supposed to mean "take seconds 60-70 of input_clip_x264_offset as > input and produce 60-70 of the

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

Use ffmpeg -i input_clip_x264_offset.mp4 -copyts -ss 60 -t 10 -filter:v "select=between(t\,60.000\,70.000)" -c:v libx264 offset_extract.mp4 Looks like -seek_timestamp 1 gets inert when used in conjunction with copyts. ___ ffmpeg-user mailing list

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

On Fri, Sep 8, 2017 at 1:20 PM, Nicolas George wrote: >> I tried to seek to a particular time in the generated stream using the >> following: >> $ ffmpeg -ss 60 -t 10 -i input_clip_x264_offset.mp4 -copyts -filter:v > > "take seconds 60-70 of input_clip_x264_offset as input to

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Kieran O Leary wrote: > On 8 Sep 2017 08:35, "Paul B Mahol" wrote: > > On 9/8/17, Mike Brown < > > No, you would need to copy audio to raw container, this raw container would > be > then detected as Dolby-E. > > ffmpeg -i input.wav -c:a copy

Re: [FFmpeg-user] Dolby E decoder

On 8 Sep 2017 08:35, "Paul B Mahol" wrote: On 9/8/17, Mike Brown < No, you would need to copy audio to raw container, this raw container would be then detected as Dolby-E. ffmpeg -i input.wav -c:a copy -f u8 out.u8 This looks like an 8-bit format,is there a reason why 16 or

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

Le duodi 22 fructidor, an CCXXV, Nitish Prabhu a écrit : > I tried to seek to a particular time in the generated stream using the > following: > $ ffmpeg -ss 60 -t 10 -i input_clip_x264_offset.mp4 -copyts -filter:v "take seconds 60-70 of input_clip_x264_offset as input to produce seconds 0-10 of

Re: [FFmpeg-user] Dolby E decoder

On 9/8/17, Mike Brown wrote: > On Fri, Sep 08, 2017 at 12:54:12AM +0200, Carl Eugen Hoyos wrote: >> (Sorry, my knowledge of SMPTE 337M is limited but I know that so far, >> this is the only "format" for which FFmpeg supports Dolby-E, and that >> adding support for other

Re: [FFmpeg-user] Understanding the behavior of "-ss/-t" option

On Fri, Sep 8, 2017 at 11:13 AM, Gyan wrote: > wrote: > You'll want to use the seek_timestamp option. > > As it says in the docs, > > "-seek_timestamp (*input*) > I tried using "-seek_timestamp" prior to posting this, but was not really sure if this works on MP4 files. I