Re: [FFmpeg-user] ffmpeg convert to wrong duration using dvd2concat

[Nicolas George]

Le primidi 1er pluviôse, an CCXXIV, Etienne Desautels a écrit :
> I'm analyzing/converting video from DVD .iso and I use dvd2concat for
> this. For at least 2 DVD, when using dvd2concat, ffmpeg return a video
> that is 1.5 x longer then the original. ffmpeg report the good duration in
> the stream info at the start, but the wrong duration at the end of the
> process. The problem is not present if I don't use dvd2concat (by
> specifying .iso directly as the input or by specifying .VOB of the mounted
> .iso). Also, video converted with the concat file will have the same frame
> repeated for the extra duration (almost 5 min. in the case below).

There is so much in the VOB files of a DVD image that anything can go wrong,
especially with so-called anti-piracy measures. Full-fledged players have
counter-measures, but not simple tools.

> file 
> 'subfile,,start,0,end,312870912,,:/home/mmac/iso/mountpoint/VIDEO_TS/VTS_01_1.VOB'
> duration 00:04:57.734
> 
> file 
> 'subfile,,start,312870912,end,625534976,,:/home/mmac/iso/mountpoint/VIDEO_TS/VTS_01_1.VOB'
> duration 00:04:57.433

I suggest you extract the given segments of this file into temp files and
try to decode them to see if they match the declared duration.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] [FFmpeg-devel] How to build for static ffmpeg executable

[Tobias Rapp]

On 21.01.2016 00:57, John Pompeii wrote:

But for convenience, you have to make sure the external libraries
are built as static libraries with DLLs disabled, or the compiler
will link to them by default.

Im not building things like the compilers and runtime libs, they just
come with the platform.


Tim was referring to the libraries you have listed in your previous post 
like fontconfig, freetype, glib-2.0, etc. You should make sure they have 
been compiled with "--enable-static --disable-shared" or some similar 
configure option (depending on the libraries build system).


The following script contains information on the static build options 
for a list of libraries, helpful even when you do not cross-compile:

https://github.com/rdp/ffmpeg-windows-build-helpers

> Since the project distributes versions of

ffmpeg builds as static exe's, I would assume there is a build
process for it?  (without having a specially created environment or
hacking the configure file...) --john


The FFmpeg project does not directly provide binary builds. I guess you 
refer to the Zeranoe download page which has a link on 
ffmpeg.org/download.html?


BTW: I'm building my ffmpeg win32/win64 executables on a GNU/Linux 
virtual machine using the mingw64 cross-compiler. This way the 
environment tools like shell, make, yasm, etc. are installed a lot easier.


Regards,
Tobias

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

Re: [FFmpeg-user] Why is it possible to set a timecode with 24:00:00:00 and beyond?

[Christoph Gerstbauer]

Am 13.01.2016 um 22:30 schrieb Dave Rice:

On Jan 13, 2016, at 9:25 AM, Bouke / VideoToolShed  
wrote:

On Jan 13, 2016, at 14:17, Robert Krüger  wrote:

On Wed, Jan 13, 2016 at 12:53 PM, Christoph Gerstbauer <
christophgerstba...@gmail.com> wrote:


FFmpeg allows me to set a timecode of 24:00:00:00 and beyond.

e.g "-timecode 24:00:00:00"

When I make an MXF D10 for example, the value of 24:00:00:00 is still in
the file.
Most but not all programs ignore this and display 00:00:00:00 correctly.

Here are some sample extractions of the timecode offset value in different
mxf d10 files generated by ffmpeg:

PAL 25fps:

-timecode 12:34:56:11  -> in file: 11477b hex -> 1132411 dec

-timecode 10:00:00:00 -> in file: 0dbba0 hex -> 90 dec

-timecode 20:00:00:00 -> in file: 1b7740 hex -> 180 dec

-timecode 23:59:59:24 -> in file: 20f57f hex -> 215 dec

-timecode 24:00:00:00 -> in file: 20f580 hex -> 216 dec -> 24h

-timecode 24:00:00:01 -> in file: 20f581 hex -> 2160001 dec

-timecode 25:00:00:00 -> in file: 225510 hex -> 225 dec -> 25h


NTSC 30fps

-timecode 23:59:59;29 -> in file: 2782df hex -> 2589407 dec

-timecode 24:00:00;00 -> in file: 2782e0 hex -> 2589408 dec


Why is this possible to set a timecode after 23:59:59:XX?
Is there a usecase?


I wasn't able to find any official spec that says what the limit for the
hour part is but since it in the general case does not define a time of day
but an offset, why limit it to 25 hours and not use the full 100? On a
side-note, I have not come across a real-world use case for a timecode of
that magnitude either.


Some forms of TC just lack the space to store higher numbers IIRC (LTC / VITC, 
perhaps also in MpegII frame headers)
But there is logic in not going higher, as it is ‘time’.
For a real world use case, in the old days of tape, a reelname most of the time 
corresponded with the hour.
So a production with more than 24 tapes needed better administration in reel 
names that had to be written on the tape and box.

FWIW QuickTime timecode flags includes a "24 hour max" flag to clarify when it is and is 
not enabled in a timecode track, but >24 hour values are certainly allowed in the QuickTime 
spec. https://developer.apple.com/library/mac/documentation/QuickTime/QTFF/QTFFChap3/qtff3.html 

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


Hello Dave,

as seen in SMPTE S012M Time and Control Code from 1999:

Page 2 of 21 pages:

"4.2 Time address of a frame
Each frame shall be identified by a unique and complete
address consisting of an hour, minute, second,
and frame number. Refer to ANSI/SMPTE 258M for
standard formats used to display frame-based time.
The hours, minutes, and seconds follow the ascending
progression of a 24-hour clock beginning with 0
hours, 0 minutes, and 0 seconds to 23 hours, 59
minutes, and 59 seconds. "

It would be interesting what would be mentioned in the newest SMPTE 
version about timecode.

Does anyone have this standard paper? (Year 2014)

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Moritz Barsnick]

On Thu, Jan 21, 2016 at 15:54:08 +, John Pompeii wrote:
> Maybe another way to ask this question is: How do I replicate the
> static ffmpeg build for windows? 

http://ffmpeg.zeranoe.com/faq/
https://ffmpeg.zeranoe.com/blog/?p=414#more-414
  "Some key features of this script are:
   [...]
   * Allow for a fully static build.
   [...]

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

[FFmpeg-user] How to build for static ffmpeg executable

[John Pompeii]

Hi,
I am building ffmpeg.exe and ffprobe.exe on 64 bit windows (7) using 
MSYS2/MINGW64.  I've resolved all the dependent libraries and got a build and 
it does appear to run just fine as a 64 windows app.  This issue that I have is 
that its linking the external libraries as dlls instead of static libs.  I 
build the ffmpeg libs as static and assumed that the build would statically 
link all libraries, but not so. 

Can someone let me know how to build version of ffmpeg.exe that doesn't require 
dlls for the dependent libraries (including the compiler and gnu runtimes) for 
windows?  In the binary packages distributed by ffmpeg, these dependent dlls 
are not there for the windows versions, regardless of a static or shared lib 
build, so I'm missing something in the way I'm configuring the build.

thanks,--john

The configure command line I'm using is:./configure 
--prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver 
--disable-doc --enable-gpl --enable-version3 --disable-w32threads 
--enable-avisynth --enable-bzlib --enable-fontconfig --enable-iconv 
--enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus 
--enable-libtheora  --enable-libvo-aacenc --enable-libvorbis --enable-libvpx 
--enable-libwavpack --enable-libx264 --enable-libx265 --enable-libzimg 
--enable-lzma --enable-zlib

The DLL's required to load and run ffmpeg.exe are:libbz2-1.dll
libfontconfig-1.dll
libfreetype-6.dll
libgcc_s_seh-1.dll
libglib-2.0-0.dll
libharfbuzz-0.dll
libiconv-2.dll
libintl-8.dll
liblzma-5.dll
libopenjpeg-5.dll
libstdc++-6.dll
libtheoradec-1.dll
libtheoraenc-1.dll
libwavpack-1.dll
libwinpthread-1.dll
libx265.dll
libzimg-2.dll
SDL.dll

It would seem that some libs (such as x264) are linking statically



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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[John Pompeii]

Thanks for the reply James,
1) I have static libs for all of the media libraries, however the build is not 
using them.  If I simply remove the *.dll.a libs from the /lib directory as 
suggested in the reply you are referring to (so that only the static libs are 
available), I get about 10K unresolved symbol errors from the linker2) 
libgcc_s_seh, libglib, libstd++, libharfbuzz, etc are not external libraries 
that I can build, they are part of the environment.  From what I can tell, the 
linker is instructed to link to shared libraries, and I cant see anything in 
the configure script that modifies those options.  As I pointed out, the 
windows binaries that are provided on the ffmpeg site don't contain gcc/gnu 
dlls and I would assume there is a build configuration that enables that.  Or 
not?
Maybe another way to ask this question is: How do I replicate the static ffmpeg 
build for windows? 
 --john

  From: James Darnley 
 To: FFmpeg user questions  
 Sent: Thursday, January 21, 2016 10:13 AM
 Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable
   
On 2016-01-21 15:52, John Pompeii wrote:
> libbz2-1.dll
> libfontconfig-1.dll
> libfreetype-6.dll
> libgcc_s_seh-1.dll
> libglib-2.0-0.dll
> libharfbuzz-0.dll
> libiconv-2.dll
> libintl-8.dll
> liblzma-5.dll
> libopenjpeg-5.dll
> libstdc++-6.dll
> libtheoradec-1.dll
> libtheoraenc-1.dll
> libwavpack-1.dll
> libwinpthread-1.dll
> libx265.dll
> libzimg-2.dll
> SDL.dll

As you were told on ffmpeg-devel: build these *external* libraries as
static libraries.

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


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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[James Darnley]

On 2016-01-21 15:52, John Pompeii wrote:
> libbz2-1.dll
> libfontconfig-1.dll
> libfreetype-6.dll
> libgcc_s_seh-1.dll
> libglib-2.0-0.dll
> libharfbuzz-0.dll
> libiconv-2.dll
> libintl-8.dll
> liblzma-5.dll
> libopenjpeg-5.dll
> libstdc++-6.dll
> libtheoradec-1.dll
> libtheoraenc-1.dll
> libwavpack-1.dll
> libwinpthread-1.dll
> libx265.dll
> libzimg-2.dll
> SDL.dll

As you were told on ffmpeg-devel: build these *external* libraries as
static libraries.



signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

[FFmpeg-user] Dolby-E Codec

[Christoph Gerstbauer]

Hi,

Is it possible to decode or encode Dolby-E with ffmpeg?

I just find decoder encoder information about:
ac3 -> dolby digital
eac3 -> Dolby digital plus

but no dolby E

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

[FFmpeg-user] Concat introduce artifact between streams

[Moro Alexandre]

Hello,

 

I concat media files using -f concat command but there are always problem
during the switch between stream 1 and 2.

There are artifact, it is very strange, if some part do not move in the new
video it keep the old last image and blend it with the new one.

 

The command i use :

ffmpeg.exe -f concat -i clips.list -codec:v copy -acodec none -movflags
faststart -y out.mp4

 

I use 2.8.2, but i try with different version down to 2.5.2 and artifact are
still here.

 

-  Every media are from the same codec h264.

-  Stream are short, between 10 and 30 seconds.

 

Thanks.

 

Alexandre.

 

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

Re: [FFmpeg-user] Concat introduce artifact between streams

[Moritz Barsnick]

On Thu, Jan 21, 2016 at 17:29:10 +0100, Moro Alexandre wrote:
> ffmpeg.exe -f concat -i clips.list -codec:v copy -acodec none -movflags
> faststart -y out.mp4

Please show us the complete, uncut console output.

> I use 2.8.2, but i try with different version down to 2.5.2 and
> artifact are still here.

How about a newer version instead of an older one (though I acknowledge
that you could find a regression by going backwards)? git master HEAD
is recommended on this list.

> -  Every media are from the same codec h264.

That does not suffice. From the docs:
https://www.ffmpeg.org/ffmpeg-formats.html#concat-1

  All files must have the same streams (same codecs, same time base,
  etc.).

  The duration of each file is used to adjust the timestamps of the
  next file: if the duration is incorrect (because it was computed
  using the bit-rate or because the file is truncated, for example), it
  can cause artifacts. The duration directive can be used to override
  the duration stored in each file.

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 21.01.2016 um 20:12 schrieb G A:

specify -—disable-shared —enable-static


that's not enough if your shared libraries are just dll/so files
they *all* need to be built static



signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 21.01.2016 um 20:27 schrieb G A:

of course it is enough.  it works on unix/osx, i build ffmpeg with 40 plugins 
from the repo every few days and these flags work.


pure nonsense, you need .a files and not .so for static linking

[root@buildserver:~]$ rpm -q --filesbypkg x264-latest
x264-latest   /usr/local/x264/libx264.a
x264-latest   /usr/local/x264/x264.h
x264-latest   /usr/local/x264/x264_config.h

guess what - libx264 is static linked

--extra-ldflags="-I%{_prefix}/local/x264 -L%{_prefix}/local/x264 -ldl'
--enable-static
--disable-shared

the others are *not* - ask "ldd" if you don't believe it

[root@buildserver:~]$ ldd /usr/local/bin/ffmpeg
linux-vdso.so.1 (0x7ffd5c4f9000)
libdl.so.2 => /lib64/libdl.so.2 (0x7f2b15dee000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7f2b15bd2000)
libssl.so.10 => /lib64/libssl.so.10 (0x7f2b1596)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x7f2b15568000)
libvpx.so.1 => /lib64/libvpx.so.1 (0x7f2b151e1000)
libm.so.6 => /lib64/libm.so.6 (0x7f2b14ed8000)
libtheoraenc.so.1 => /lib64/libtheoraenc.so.1 (0x7f2b14c98000)
libtheoradec.so.1 => /lib64/libtheoradec.so.1 (0x7f2b14a7f000)
libmp3lame.so.0 => /lib64/libmp3lame.so.0 (0x7f2b147c6000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x7f2b1459d000)
libbz2.so.1 => /lib64/libbz2.so.1 (0x7f2b1438d000)
libz.so.1 => /lib64/libz.so.1 (0x7f2b14175000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f2b13f5e000)
libc.so.6 => /lib64/libc.so.6 (0x7f2b13b9e000)
/lib64/ld-linux-x86-64.so.2 (0x55f75aec)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 
(0x7f2b1394f000)

libkrb5.so.3 => /lib64/libkrb5.so.3 (0x7f2b1366a000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x7f2b13466000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x7f2b13232000)
libgomp.so.1 => /lib64/libgomp.so.1 (0x7f2b1301)
libogg.so.0 => /lib64/libogg.so.0 (0x7f2b12e09000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 
(0x7f2b12bf9000)

libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x7f2b129f5000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x7f2b127d9000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x7f2b125b5000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x7f2b12344000)


On Jan 21, 2016, at 11:22, Reindl Harald  wrote:



Am 21.01.2016 um 20:12 schrieb G A:

specify -—disable-shared —enable-static


that's not enough if your shared libraries are just dll/so files
they *all* need to be built static




signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] Dolby-E Codec

[Moritz Barsnick]

On Thu, Jan 21, 2016 at 11:11:04 -0800, G A wrote:
> decadec lib might do it.

No. dcadec handles DTS, which is not Dolby.

If you Google a bit, you will see that there were both requests and
attempts to at least decode Dolby E, but it doesn't seem current ffmpeg
has any support at all yet.

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos:

John Pompeii  ffmpeg.org> writes:


--enable-bzlib
--enable-iconv
--enable-lzma
--enable-zlib


These options have no effect, they do not do
what you seem to believe they do. I suggest
you remove them


since you always suggest to remove them *why* do the exist at all in 
./configure --help and not only their counterpart --disable-xx?


i suggest *you* remove them or stop tell users remove them when there is 
no harm




signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Carl Eugen Hoyos]

Reindl Harald  thelounge.net> writes:

> Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos:
> > John Pompeii  ffmpeg.org> writes:
> >
> >> --enable-bzlib
> >> --enable-iconv
> >> --enable-lzma
> >> --enable-zlib
> >
> > These options have no effect, they do not do
> > what you seem to believe they do. I suggest
> > you remove them
> 
> since you always suggest to remove them *why* do 
> the exist at all in ./configure --help and not 
> only their counterpart --disable-xx?

[quote]
  --disable-bzlib  disable bzlib [autodetect]
  --disable-zlib   disable zlib [autodetect]
  --disable-iconv  disable iconv [autodetect]
  --disable-lzma   disable lzma [autodetect]
[/quote]

???

Carl Eugen

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 22.01.2016 um 01:07 schrieb Carl Eugen Hoyos:

Reindl Harald  thelounge.net> writes:


i suggest *you* remove them


See http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=0f05b72f
=-)


* removed 2013
* most configure scripts are way older
* no warnings
* just mailing-list complaints




signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos:

Reindl Harald  thelounge.net> writes:


Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos:

John Pompeii  ffmpeg.org> writes:


--enable-bzlib
--enable-iconv
--enable-lzma
--enable-zlib


These options have no effect, they do not do
what you seem to believe they do. I suggest
you remove them


since you always suggest to remove them *why* do
the exist at all in ./configure --help and not
only their counterpart --disable-xx?


[quote]
   --disable-bzlib  disable bzlib [autodetect]
   --disable-zlib   disable zlib [autodetect]
   --disable-iconv  disable iconv [autodetect]
   --disable-lzma   disable lzma [autodetect]
[/quote]

???


typically configure scripts warn about unkonwn params
ffmpeg don't


~/rpmbuild/BUILD/ffmpeg-20160117/generic ~/rpmbuild/BUILD/ffmpeg-20160117
+ ../configure --prefix=/usr/local --bindir=/usr/local/bin 
--mandir=/usr/local/man '--extra-cflags=-I/usr/local/x264 -m64 -O2 -g0 
-march=sandybridge -mtune=sandybridge -fopenmp -mfpmath=sse -pipe 
-fno-strict-aliasing -fomit-frame-pointer -finline-functions 
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=6 
-D_FORTIFY_SOURCE=2 -Wstack-protector -Wformat -Werror=format-security 
-Ofast -ffast-math -funsafe-math-optimizations -funroll-loops 
-funswitch-loops -Wno-pointer-sign -minline-all-stringops -flto 
-fuse-ld=gold -fuse-linker-plugin' '--extra-ldflags=-I/usr/local/x264 
-L/usr/local/x264 -ldl -Wl,-z,now 
-Wl,-z,relro,-z,noexecstack,-fuse-ld=gold -m64 -O2 -g0 
-march=sandybridge -mtune=sandybridge -fopenmp -mfpmath=sse -pipe 
-fno-strict-aliasing -fomit-frame-pointer -finline-functions 
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=6 
-D_FORTIFY_SOURCE=2 -Wstack-protector -Wformat -Werror=format-security 
-Ofast -ffast-math -funsafe-math-optimizations -funroll-loops 
-funswitch-loops -Wno-pointer-sign -minline-all-stringops -flto 
-fuse-ld=gold -fuse-linker-plugin' --enable-pic --enable-lto --ar=gcc-ar 
--ranlib=true --enable-nonfree --enable-gpl --enable-version3 
--enable-libmp3lame --enable-libtheora --enable-libx264 --enable-libvpx 
--enable-openssl --enable-static --enable-runtime-cpudetect 
--enable-bzlib --enable-zlib --disable-amd3dnow --disable-amd3dnowext 
--disable-avdevice --disable-debug --disable-devices --disable-ffplay 
--disable-ffprobe --disable-ffserver --disable-htmlpages 
--disable-hwaccels --disable-iconv --disable-libdc1394 --disable-libfaac 
--disable-libfreetype --disable-libgsm --disable-libopencore-amrnb 
--disable-libopencore-amrwb --disable-libopencv --disable-libopenjpeg 
--disable-libopus --disable-librtmp --disable-libschroedinger 
--disable-libspeex --disable-libvorbis --disable-libxvid 
--disable-podpages --disable-postproc --disable-protocol=gopher 
--disable-shared --disable-txtpages

nm: /tmp/ffconf.WVafcwrW.o: plugin needed to handle lto object
install prefix/usr/local
source path   /home/builduser/rpmbuild/BUILD/ffmpeg-20160117



signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Carl Eugen Hoyos]

John Pompeii  ffmpeg.org> writes:

> --enable-bzlib
> --enable-iconv
> --enable-lzma
> --enable-zlib

These options have no effect, they do not do 
what you seem to believe they do. I suggest 
you remove them.

Carl Eugen

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Carl Eugen Hoyos]

Reindl Harald  thelounge.net> writes:

> Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos:
> > Reindl Harald  thelounge.net> writes:
> >
> >> Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos:
> >>> John Pompeii  ffmpeg.org> writes:
> >>>
>  --enable-bzlib
>  --enable-iconv
>  --enable-lzma
>  --enable-zlib
> >>>
> >>> These options have no effect, they do not do
> >>> what you seem to believe they do. I suggest
> >>> you remove them
> >>
> >> since you always suggest to remove them *why* do
> >> the exist at all in ./configure --help and not
> >> only their counterpart --disable-xx?
> >
> > [quote]
> >--disable-bzlib  disable bzlib [autodetect]
> >--disable-zlib   disable zlib [autodetect]
> >--disable-iconv  disable iconv [autodetect]
> >--disable-lzma   disable lzma [autodetect]
> > [/quote]
> >
> > ???
> 
> typically configure scripts warn about unkonwn params
> ffmpeg don't

FFmpeg configure does not warn about unknown parameters, 
it errors out, just try "./configure --enable-foo".

The parameters above are not unknown, they are useful 
for debugging but not for users, this is why they 
are not listed in configure --help (that was what 
you both denied and requested, no?).

The options you use in your configure line are to 
some degree useless, to some degree they hurt 
performance for no gain and some (as --enable-zlib) 
do not work the way you (apparently) think they work: 
They simply have no effect.
Since the configure line is often needed to 
debug issues it is very useful to remove all 
unneeded options, especially those that may produce 
issues in the future because they never had the 
meaning you think they have.

Carl Eugen

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Reindl Harald]

Am 22.01.2016 um 01:16 schrieb Carl Eugen Hoyos:

Reindl Harald  thelounge.net> writes:


Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos:

Reindl Harald  thelounge.net> writes:


Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos:

John Pompeii  ffmpeg.org> writes:


--enable-bzlib
--enable-iconv
--enable-lzma
--enable-zlib


These options have no effect, they do not do
what you seem to believe they do. I suggest
you remove them


since you always suggest to remove them *why* do
the exist at all in ./configure --help and not
only their counterpart --disable-xx?


[quote]
--disable-bzlib  disable bzlib [autodetect]
--disable-zlib   disable zlib [autodetect]
--disable-iconv  disable iconv [autodetect]
--disable-lzma   disable lzma [autodetect]
[/quote]

???


typically configure scripts warn about unkonwn params
ffmpeg don't


FFmpeg configure does not warn about unknown parameters,
it errors out, just try "./configure --enable-foo".

The parameters above are not unknown, they are useful
for debugging but not for users, this is why they
are not listed in configure --help (that was what
you both denied and requested, no?).

The options you use in your configure line are to
some degree useless, to some degree they hurt
performance for no gain and some (as --enable-zlib)
do not work the way you (apparently) think they work:
They simply have no effect.
Since the configure line is often needed to
debug issues it is very useful to remove all
unneeded options, especially those that may produce
issues in the future because they never had the
meaning you think they have


when "they simple have no effect" how can they "be useful" for debugging?

which ones hurt performance for no gain?





signature.asc
Description: OpenPGP digital signature
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Carl Eugen Hoyos]

Reindl Harald  thelounge.net> writes:

> when "they simple have no effect" how can they 
> "be useful" for debugging?

They have no effect in your configure line and they 
have no effect in the configure line that was posted 
in this thread.
There are configure lines (that are hardly useful 
for users but can be very useful when debugging as 
a developer) in which they have an effect.

Carl Eugen

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[John Pompeii]

Thanks Carl for the heads up.  I am fairly new to ffmpeg in general and have a 
need to 
add a new protocol that supports reading video files that our application 
encrypts usinga aes-ctr algorythm.  So not knowing any better, I grabbed the 
build flags that are 
displayed when running the latest ffmpeg from the binary distribution.  I have 
eliminated 
about half of those already but I wasn't sure about these.  I didn't add them 
becauseI thought I needed them, I was just trying to replicate the distribution 
version.
thanks,--john
  

  From: Carl Eugen Hoyos 
 To: ffmpeg-user@ffmpeg.org 
 Sent: Thursday, January 21, 2016 6:41 PM
 Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable
   
John Pompeii  ffmpeg.org> writes:

> --enable-bzlib
> --enable-iconv
> --enable-lzma
> --enable-zlib

These options have no effect, they do not do 
what you seem to believe they do. I suggest 
you remove them.

Carl Eugen

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


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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[John Pompeii]

Thanks Glen,These flags are the default.  I build with them anyway and got the 
same result.  the ff* libs are build as static libs but the ffmpeg excutable is 
linked w/the shared libs for the external libs and runtimes.
here's my cmd line for configure:
./configure --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay 
--disable-ffserver --disable-doc --enable-gpl --enable-version3 
--disable-w32threads --enable-static --disable-shared --enable-avisynth 
--enable-fontconfig --enable-libfreetype --enable-libmp3lame 
--enable-libopenjpeg --enable-libopus --enable-libtheora  --enable-libvo-aacenc 
--enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 
--enable-libx265 --enable-libxvid --enable-libzimg



  From: G A 
 To: FFmpeg user questions  
 Sent: Thursday, January 21, 2016 2:12 PM
 Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable
   
specify -—disable-shared —enable-static

Sent from somewhere in … The Twilight Zone

> On Jan 21, 2016, at 06:52, John Pompeii  wrote:
> 
> 
> 
> 
> Hi,
> I am building ffmpeg.exe and ffprobe.exe on 64 bit windows (7) using 
> MSYS2/MINGW64.  I've resolved all the dependent libraries and got a build and 
> it does appear to run just fine as a 64 windows app.  This issue that I have 
> is that its linking the external libraries as dlls instead of static libs.  I 
> build the ffmpeg libs as static and assumed that the build would statically 
> link all libraries, but not so. 
> 
> Can someone let me know how to build version of ffmpeg.exe that doesn't 
> require dlls for the dependent libraries (including the compiler and gnu 
> runtimes) for windows?  In the binary packages distributed by ffmpeg, these 
> dependent dlls are not there for the windows versions, regardless of a static 
> or shared lib build, so I'm missing something in the way I'm configuring the 
> build.
> 
> thanks,--john
> 
> The configure command line I'm using is:./configure 
> --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver 
> --disable-doc --enable-gpl --enable-version3 --disable-w32threads 
> --enable-avisynth --enable-bzlib --enable-fontconfig --enable-iconv 
> --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg 
> --enable-libopus --enable-libtheora  --enable-libvo-aacenc --enable-libvorbis 
> --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 
> --enable-libzimg --enable-lzma --enable-zlib
> 
> The DLL's required to load and run ffmpeg.exe are:libbz2-1.dll
> libfontconfig-1.dll
> libfreetype-6.dll
> libgcc_s_seh-1.dll
> libglib-2.0-0.dll
> libharfbuzz-0.dll
> libiconv-2.dll
> libintl-8.dll
> liblzma-5.dll
> libopenjpeg-5.dll
> libstdc++-6.dll
> libtheoradec-1.dll
> libtheoraenc-1.dll
> libwavpack-1.dll
> libwinpthread-1.dll
> libx265.dll
> libzimg-2.dll
> SDL.dll
> 
> It would seem that some libs (such as x264) are linking statically
> 
> 
> 
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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


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

Re: [FFmpeg-user] Concat introduce artifact between streams

[Moro Alexandre]

Thanks for your fast response.

I will try with with the git master next week,

I'm pretty new to FFmpeg but i developped an application which create theses 
video stream from images.

Every video are created with ffmpeg within a custom application, so they all 
have the same parameters,
They play very well in VLC.


Meanwhile, please find below the complete console output.

ffmpeg -concat -i video_bribes.list -c:v copy -acodec none -movflags faststart 
-y v_5.mp4
ffmpeg version N-76776-g3c110b0 Copyright (c) 2000-2015 the FFmpeg developers
  built with gcc 5.2.0 (GCC)
  configuration: --disable-static --enable-shared --enable-gpl --enable-version3
 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --ena
ble-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --e
nable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-
libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame
--enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --ena
ble-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-
libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-lib
vo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-li
bwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --e
nable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
  libavutil  55.  8.100 / 55.  8.100
  libavcodec 57. 15.100 / 57. 15.100
  libavformat57. 18.100 / 57. 18.100
  libavdevice57.  0.100 / 57.  0.100
  libavfilter 6. 15.100 /  6. 15.100
  libswscale  4.  0.100 /  4.  0.100
  libswresample   2.  0.101 /  2.  0.101
  libpostproc54.  0.100 / 54.  0.100
[mov,mp4,m4a,3gp,3g2,mj2 @ 00c56ca0] Auto-inserting h264_mp4toannexb bitstream f
ilter
Input #0, concat, from 'video_bribes.list':
  Duration: N/A, start: 0.00, bitrate: 898 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1280x720,
 898 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc
Metadata:
  handler_name: VideoHandler
[mp4 @ 02d607e0] Codec for stream 0 does not use global headers but container fo
rmat requires global headers
Output #0, mp4, to 'v_5.mp4':
  Metadata:
encoder : Lavf57.18.100
Stream #0:0(und): Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q
=2-31, 898 kb/s, 30 fps, 30 tbr, 15360 tbn, 15360 tbc
Metadata:
  handler_name: VideoHandler
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
Press [q] to stop, [?] for help
[mov,mp4,m4a,3gp,3g2,mj2 @ 00c56ca0] Auto-inserting h264_mp4toannexb bitstream f
ilter
[mov,mp4,m4a,3gp,3g2,mj2 @ 0299a0a0] Auto-inserting h264_mp4toannexb bitstream f
ilter
[mp4 @ 02d607e0] Starting second pass: moving the moov atom to the beginning of
the file
frame= 1062 fps=0.0 q=-1.0 Lsize=3905kB time=00:00:35.36 bitrate= 904.6kbits
/s
video:3897kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing
overhead: 0.207633%


Thanks for your help.

-Message d'origine-
De : ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] De la part de Moritz 
Barsnick
Envoyé : jeudi 21 janvier 2016 17:37
À : FFmpeg user discussions
Objet : Re: [FFmpeg-user] Concat introduce artifact between streams

On Thu, Jan 21, 2016 at 17:29:10 +0100, Moro Alexandre wrote:
> ffmpeg.exe -f concat -i clips.list -codec:v copy -acodec none 
> -movflags faststart -y out.mp4

Please show us the complete, uncut console output.

> I use 2.8.2, but i try with different version down to 2.5.2 and 
> artifact are still here.

How about a newer version instead of an older one (though I acknowledge that 
you could find a regression by going backwards)? git master HEAD is recommended 
on this list.

> -  Every media are from the same codec h264.

That does not suffice. From the docs:
https://www.ffmpeg.org/ffmpeg-formats.html#concat-1

  All files must have the same streams (same codecs, same time base,
  etc.).

  The duration of each file is used to adjust the timestamps of the
  next file: if the duration is incorrect (because it was computed
  using the bit-rate or because the file is truncated, for example), it
  can cause artifacts. The duration directive can be used to override
  the duration stored in each file.

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


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

Re: [FFmpeg-user] Dolby-E Codec

[G A]

decadec lib might do it.

Sent from somewhere in … The Twilight Zone

> On Jan 21, 2016, at 07:12, Christoph Gerstbauer 
>  wrote:
> 
> Hi,
> 
> Is it possible to decode or encode Dolby-E with ffmpeg?
> 
> I just find decoder encoder information about:
> ac3 -> dolby digital
> eac3 -> Dolby digital plus
> 
> but no dolby E
> 
> Best Regards
> Christoph
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[G A]

specify -—disable-shared —enable-static

Sent from somewhere in … The Twilight Zone

> On Jan 21, 2016, at 06:52, John Pompeii  wrote:
> 
> 
> 
> 
> Hi,
> I am building ffmpeg.exe and ffprobe.exe on 64 bit windows (7) using 
> MSYS2/MINGW64.  I've resolved all the dependent libraries and got a build and 
> it does appear to run just fine as a 64 windows app.  This issue that I have 
> is that its linking the external libraries as dlls instead of static libs.  I 
> build the ffmpeg libs as static and assumed that the build would statically 
> link all libraries, but not so. 
> 
> Can someone let me know how to build version of ffmpeg.exe that doesn't 
> require dlls for the dependent libraries (including the compiler and gnu 
> runtimes) for windows?  In the binary packages distributed by ffmpeg, these 
> dependent dlls are not there for the windows versions, regardless of a static 
> or shared lib build, so I'm missing something in the way I'm configuring the 
> build.
> 
> thanks,--john
> 
> The configure command line I'm using is:./configure 
> --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver 
> --disable-doc --enable-gpl --enable-version3 --disable-w32threads 
> --enable-avisynth --enable-bzlib --enable-fontconfig --enable-iconv 
> --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg 
> --enable-libopus --enable-libtheora  --enable-libvo-aacenc --enable-libvorbis 
> --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 
> --enable-libzimg --enable-lzma --enable-zlib
> 
> The DLL's required to load and run ffmpeg.exe are:libbz2-1.dll
> libfontconfig-1.dll
> libfreetype-6.dll
> libgcc_s_seh-1.dll
> libglib-2.0-0.dll
> libharfbuzz-0.dll
> libiconv-2.dll
> libintl-8.dll
> liblzma-5.dll
> libopenjpeg-5.dll
> libstdc++-6.dll
> libtheoradec-1.dll
> libtheoraenc-1.dll
> libwavpack-1.dll
> libwinpthread-1.dll
> libx265.dll
> libzimg-2.dll
> SDL.dll
> 
> It would seem that some libs (such as x264) are linking statically
> 
> 
> 
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[G A]

of course it is enough.  it works on unix/osx, i build ffmpeg with 40 plugins 
from the repo every few days and these flags work.  

Sent from somewhere in … The Twilight Zone

> On Jan 21, 2016, at 11:22, Reindl Harald  wrote:
> 
> 
> 
> Am 21.01.2016 um 20:12 schrieb G A:
>> specify -—disable-shared —enable-static
> 
> that's not enough if your shared libraries are just dll/so files
> they *all* need to be built static
> 
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] How to build for static ffmpeg executable

[Moritz Barsnick]

On Thu, Jan 21, 2016 at 11:27:54 -0800, G A wrote:
> of course it is enough.  it works on unix/osx, i build ffmpeg with 40
> plugins from the repo every few days and these flags work.

That's nonsense. Even though we're talking Windows here (for the
original poster at least), that's not valid on the named platforms.

And BTW ffmpeg doesn't support anything which resembles plugins.

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