Re: [FFmpeg-user] Differences in output between FFmpeg versions

2019-10-15 Thread Carl Eugen Hoyos
Am Mi., 16. Okt. 2019 um 00:25 Uhr schrieb Ethan Coeytaux
:

> Thank you for the response.  It's not 100% clear to me what the differences
> are since it's decoded output, but when converting the same exact MP3 file
> with different FFmpeg versions the decoded output files are different in
> size and don't fully match up throughout the file.  For example on a test
> MP3 file the decoded output using v2.2.1 had far more leading 0s than the
> output from the v4.1.1 version.

Note that v4.1.1 is old and unsupported.

The leading zeros sound like a bug fix.

Please find out what top-posting means and avoid it here.

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Differences in output between FFmpeg versions

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 23:44 Uhr schrieb Moritz Barsnick :

> I believe decoding of MP3 and AAC should be pretty precise.

I believe that both mp3 and aac are not supposed to decode to
one "correct" output, both know many correct outputs.
So the fact that the outputs are different is not a sufficient
indication for a bug.

But as always: Command line and complete, uncut console
output missing, I suspect it will provide part of the answer.

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] problem ffmpeg with cuda and scale

2019-10-15 Thread Dennis Mungai
On Wed, 16 Oct 2019 at 01:14, Michele Salerno  wrote:
>
> Il giorno mar 15 ott 2019 alle ore 23:33 Dennis Mungai
>  ha scritto:
> >
> > On Tue, 15 Oct 2019 at 23:47, Carl Eugen Hoyos  wrote:
> > >
> > > Am Di., 15. Okt. 2019 um 22:25 Uhr schrieb Michele Salerno
> > > :
> > >
> > > > ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
> > >
> > > This looks old.
> > >
> > > Carl Eugen
> >
> > And secondly, if you want the scale_npp filter, you must compile
> > FFmpeg from source with --enable-cuda-nvcc option passed to the
> > ./configure script. Note that the CUDA SDK must be installed on the
> > system you're building and running FFmpeg on.
> >
> > Since you have nvenc present and enabled, you should be able to use
> > the scale_cuda filter, yadif_cuda, thumbnail_cuda and hwupload_cuda
> > filters respectively as they're dependent on the ffnvcodec headers
> > package needed to enable the NVENC feature set.
> >
> > For usage, see:
> >
> > ffmpeg -h filter=scale_cuda
> >
> Unknown filter 'scale_cuda'.
>
> > So with your command, substitute scale_npp with scale_cuda as shown:
> >
> > #!/bin/bash
> > for i in *.mp4; do
> > ffmpeg -threads 8 -hwaccel nvdec -i "$i" -vf scale_cuda=720:-1
> > -c:v h264_nvenc -preset slow "convert/$i";
> > done
> >
> > NVDEC should be available on your platform as ffmpeg was configured
> > with the aforementioned ffnvcodec header package.
> > Note the thread count limit I've added to the command above, as nvdec
> > will warn you on high thread counts exceeding ~16.
> >
> thanks.

Build the latest ffmpeg git tip and retest.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Differences in output between FFmpeg versions

2019-10-15 Thread Ethan Coeytaux
Hi Moritz,

Thank you for the response.  It's not 100% clear to me what the differences
are since it's decoded output, but when converting the same exact MP3 file
with different FFmpeg versions the decoded output files are different in
size and don't fully match up throughout the file.  For example on a test
MP3 file the decoded output using v2.2.1 had far more leading 0s than the
output from the v4.1.1 version.  Past that it mostly comes down to numerous
flipped bits throughout the files.  I'm not sure what "more correctly" is
in this context, and if one is more correct I would assume the latest
version is the most correct, but the outputs are undeniably different.

As for the consequences, I can't go into too much detail unfortunately, but
because we are trying to match songs and the first step is to decode the
audio it becomes far more difficult when the same exact song has different
decoded output depending on when it was decoded.

Would it be helpful if I posted the outputs of a decoded MP3 file?

-Ethan

On Tue, Oct 15, 2019 at 3:44 PM Moritz Barsnick  wrote:

> On Tue, Oct 15, 2019 at 15:08:56 -0600, Ethan Coeytaux wrote:
>
> > When upgrading however we noticed there are substantial differences
> > in the output of FFmpeg when using a newer version (either 2.6.8,
> > 3.3.4, or 4.1.1) compared to the older version, which has notable
> > consequences on our analysis of the audio. However, the output from
> > 2.6.8, 3.3.4, and 4.1.1, while still different, are much more similar
> > than the output from 2.2.1.
> [...]
> > Any tips or advice would be much appreciated, thank you!
>
> You forgot to tell us what those differences in the output are. What
> are the "consequences on our analysis of the audio"?
>
> Are you saying audio was decoded (to raw) more correctly previously
> than it is now?
>
> I believe decoding of MP3 and AAC should be pretty precise. You can try
> alternative decoders (such as libfdk_aac) for comparison, but I'm
> riddled what you mean.
>
> Moritz
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> https://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
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] problem ffmpeg with cuda and scale

2019-10-15 Thread Michele Salerno
Il giorno mar 15 ott 2019 alle ore 23:33 Dennis Mungai
 ha scritto:
>
> On Tue, 15 Oct 2019 at 23:47, Carl Eugen Hoyos  wrote:
> >
> > Am Di., 15. Okt. 2019 um 22:25 Uhr schrieb Michele Salerno
> > :
> >
> > > ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
> >
> > This looks old.
> >
> > Carl Eugen
>
> And secondly, if you want the scale_npp filter, you must compile
> FFmpeg from source with --enable-cuda-nvcc option passed to the
> ./configure script. Note that the CUDA SDK must be installed on the
> system you're building and running FFmpeg on.
>
> Since you have nvenc present and enabled, you should be able to use
> the scale_cuda filter, yadif_cuda, thumbnail_cuda and hwupload_cuda
> filters respectively as they're dependent on the ffnvcodec headers
> package needed to enable the NVENC feature set.
>
> For usage, see:
>
> ffmpeg -h filter=scale_cuda
>
Unknown filter 'scale_cuda'.

> So with your command, substitute scale_npp with scale_cuda as shown:
>
> #!/bin/bash
> for i in *.mp4; do
> ffmpeg -threads 8 -hwaccel nvdec -i "$i" -vf scale_cuda=720:-1
> -c:v h264_nvenc -preset slow "convert/$i";
> done
>
> NVDEC should be available on your platform as ffmpeg was configured
> with the aforementioned ffnvcodec header package.
> Note the thread count limit I've added to the command above, as nvdec
> will warn you on high thread counts exceeding ~16.
>
thanks.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to rename libx264 shared library(libx264.so.152) in FFmpeg

2019-10-15 Thread Moritz Barsnick
On Tue, Oct 15, 2019 at 10:48:06 +0530, Anand Veerappan wrote:
> Step 1: As mentioned in your email we remanded the libx264-mv.so.152 file.

You obviously went for the less hacky, but more correct way.

> Step 3: While executing FFmpeg binary it requires original libx264.so.152
> instead of modified libx264-mv.so.152.

This means that, when ffmpeg was linked, it found a libx264.so with an
SONAME of libx264.so.152. So perhaps the libx264.so symlink was
pointing at a different libx264.so.XXX (i.e. the original one).

- Where is your libx264.so located?
  Please show the output of
  ls -l /usr/lib/libx264.so
  (or to whatever its path is - replace /usr/lib with the actual path
  please).
- Please show us the output of
  objdump -p /usr/lib/libx264.so.152 | grep SONAME
- Please show us the output of
  objdump -p /usr/lib/libx264-mv.so.152 | grep SONAME

> Regards
> Anand V

BTW, I'm subscribed to the list, that's how I saw your original
question. You don't need to Cc: me on your emails.

Furthermore, instead of using screenshots of text, just copy and paste
text into your email. It's much more efficient and easier to read.

Thanks,
Moritz
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Differences in output between FFmpeg versions

2019-10-15 Thread Moritz Barsnick
On Tue, Oct 15, 2019 at 15:08:56 -0600, Ethan Coeytaux wrote:

> When upgrading however we noticed there are substantial differences
> in the output of FFmpeg when using a newer version (either 2.6.8,
> 3.3.4, or 4.1.1) compared to the older version, which has notable
> consequences on our analysis of the audio. However, the output from
> 2.6.8, 3.3.4, and 4.1.1, while still different, are much more similar
> than the output from 2.2.1.
[...]
> Any tips or advice would be much appreciated, thank you!

You forgot to tell us what those differences in the output are. What
are the "consequences on our analysis of the audio"?

Are you saying audio was decoded (to raw) more correctly previously
than it is now?

I believe decoding of MP3 and AAC should be pretty precise. You can try
alternative decoders (such as libfdk_aac) for comparison, but I'm
riddled what you mean.

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

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

Re: [FFmpeg-user] problem ffmpeg with cuda and scale

2019-10-15 Thread Dennis Mungai
On Tue, 15 Oct 2019 at 23:47, Carl Eugen Hoyos  wrote:
>
> Am Di., 15. Okt. 2019 um 22:25 Uhr schrieb Michele Salerno
> :
>
> > ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
>
> This looks old.
>
> Carl Eugen

And secondly, if you want the scale_npp filter, you must compile
FFmpeg from source with --enable-cuda-nvcc option passed to the
./configure script. Note that the CUDA SDK must be installed on the
system you're building and running FFmpeg on.

Since you have nvenc present and enabled, you should be able to use
the scale_cuda filter, yadif_cuda, thumbnail_cuda and hwupload_cuda
filters respectively as they're dependent on the ffnvcodec headers
package needed to enable the NVENC feature set.

For usage, see:

ffmpeg -h filter=scale_cuda

On my build, I see:

Filter scale_cuda
  GPU accelerated video resizer
Inputs:
   #0: default (video)
Outputs:
   #0: default (video)
cudascale AVOptions:
  w  ..FV.. Output video width (default "iw")
  h  ..FV.. Output video height (default "ih")



So with your command, substitute scale_npp with scale_cuda as shown:

#!/bin/bash
for i in *.mp4; do
ffmpeg -threads 8 -hwaccel nvdec -i "$i" -vf scale_cuda=720:-1
-c:v h264_nvenc -preset slow "convert/$i";
done

NVDEC should be available on your platform as ffmpeg was configured
with the aforementioned ffnvcodec header package.
Note the thread count limit I've added to the command above, as nvdec
will warn you on high thread counts exceeding ~16.

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

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

[FFmpeg-user] Differences in output between FFmpeg versions

2019-10-15 Thread Ethan Coeytaux
Hello all,


My work involves analyzing large quantities of songs and determining
"matches" and for some time we've been using FFmpeg to convert MP3s and
AACs from numerous sources to raw data to then analyze.  However this
system was put into place several years ago and we're still using a very
old version of FFmpeg (v2.2.1).  When upgrading however we noticed there
are substantial differences in the output of FFmpeg when using a newer
version (either 2.6.8, 3.3.4, or 4.1.1) compared to the older version,
which has notable consequences on our analysis of the audio.  However, the
output from 2.6.8, 3.3.4, and 4.1.1, while still different, are much more
similar than the output from 2.2.1.


My question is: are there any ways to eliminate or minimize these changes
in the output?  The command we're running is "ffmpeg -loglevel warning -i
$AUDIODIR/$filename -ar 8000 -ac 1 -f s16le -acodec pcm_s16le
$RAMDIR/RAW/$rawFilename".


The config for our v2.2.1 version is:


ffmpeg version 2.2.1

built on Dec 11 2015 16:14:14 with gcc 4.4.7 (GCC) 20120313 (Red Hat
4.4.7-16)

--prefix=/usr

--bindir=/usr/bin

--datadir=/usr/share/ffmpeg

--incdir=/usr/include/ffmpeg

--libdir=/usr/lib64

--mandir=/usr/share/man

--arch=x86_64

--optflags='-O2

-g

-pipe

-Wall

-Wp,-D_FORTIFY_SOURCE=2

-fexceptions

-fstack-protector

--param=ssp-buffer-size=4

-m64

-mtune=generic'

--enable-bzlib

--disable-crystalhd

--enable-gnutls

--enable-libass

--enable-libdc1394

--disable-indev=jack

--enable-libfreetype

--enable-libgsm

--enable-libmp3lame

--enable-openal

--enable-libopenjpeg

--enable-libopus

--enable-libpulse

--enable-libschroedinger

--enable-libspeex

--enable-libtheora

--enable-libvorbis

--enable-libv4l2

--enable-libxvid

--enable-x11grab

--enable-avfilter

--enable-avresample

--enable-postproc

--enable-pthreads

--disable-static

--enable-shared

--enable-gpl

--disable-debug

--disable-stripping

--shlibdir=/usr/lib64

--enable-runtime-cpudetect

libavutil  52. 66.100 / 52. 66.100

libavcodec 55. 52.102 / 55. 52.102

libavformat55. 33.100 / 55. 33.100

libavdevice55. 10.100 / 55. 10.100

libavfilter 4.  2.100 /  4.  2.100

libavresample   1.  2.  0 /  1.  2.  0

libswscale  2.  5.102 /  2.  5.102

libswresample   0. 18.100 /  0. 18.100

libpostproc52.  3.100 / 52.  3.100


and the config for v4.1.1 is:


ffmpeg version 4.1.1-static https://johnvansickle.com/ffmpeg/  Copyright
(c) 2000-2019 the FFmpeg developers

built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516

--enable-gpl

--enable-version3

--enable-static

--disable-debug

--disable-ffplay

--disable-indev=sndio

--disable-outdev=sndio

--cc=gcc-6

--enable-fontconfig

--enable-frei0r

--enable-gnutls

--enable-gmp

--enable-gray

--enable-libaom

--enable-libfribidi

--enable-libass

--enable-libvmaf

--enable-libfreetype

--enable-libmp3lame

--enable-libopencore-amrnb

--enable-libopencore-amrwb

--enable-libopenjpeg

--enable-librubberband

--enable-libsoxr

--enable-libspeex

--enable-libvorbis

--enable-libopus

--enable-libtheora

--enable-libvidstab

--enable-libvo-amrwbenc

--enable-libvpx

--enable-libwebp

--enable-libx264

--enable-libx265

--enable-libxml2

--enable-libxvid

--enable-libzvbi

--enable-libzimg

libavutil  56. 22.100 / 56. 22.100

libavcodec 58. 35.100 / 58. 35.100

libavformat58. 20.100 / 58. 20.100

libavdevice58.  5.100 / 58.  5.100

libavfilter 7. 40.101 /  7. 40.101

libswscale  5.  3.100 /  5.  3.100

libswresample   3.  3.100 /  3.  3.100

libpostproc55.  3.100 / 55.  3.100


Any tips or advice would be much appreciated, thank you!


- Ethan Coeytaux
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Multiple Glob Inputs

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 20:19 Uhr schrieb James Tan :
>
> >
> > A concat filter exists, but I suspect the concat demuxer (that works
> > differently and does not use glob) is what you need.
> > https://ffmpeg.org/ffmpeg-filters.html#concat
> > https://ffmpeg.org/ffmpeg-formats.html#concat-1
>
>
> Ah so basically you're saying you don't think there is a way to
> concatenate with glob

No, I would expect the concat filter to work fine but I believe
all other options are simpler in your case.
(concat demuxer or reordering with symlinks for the image2 demuxer)

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] problem ffmpeg with cuda and scale

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 22:25 Uhr schrieb Michele Salerno
:

> ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers

This looks old.

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

[FFmpeg-user] problem ffmpeg with cuda and scale

2019-10-15 Thread Michele Salerno
I don't speak English well I hope to be understood.
Hi to all users. :)

My hw is:
- CPU Core i7
- GPU Nvidia GTX 660 Ti
- RAM 32GB
My sw is:
- Debian Buster 64bit
- Driver nvidia packager manger and cuda toolkit

My /etc/modprobe.d/blacklist.conf
blacklist nouveau
blacklist nvidia-drm
options nouveau modeset-0

My script is:
#!/bin/bash
for i in *.mp4; do
ffmpeg -hwaccel cuvid -c:v h264_cuvid -i "$i" -vf scale_npp=720:-1
-c:v h264_nvenc -preset slow "convert/$i";
done

i have this error:
AVFilterGraph @ 0x560380a8d6c0] No such filter: 'scale_npp'
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Conversion failed!

if remove "-vf scale_npp=720:-1" it's ok.

I want the files in 720p, how can I do?

Thanks.

Michele

root@tux:~ # ffmpeg -h filter=scale_npp
ffmpeg version 4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --disable-decoder=amrnb --disable-decoder=libopenjpeg
--disable-libopencv --disable-outdev=sdl2 --disable-podpages
--disable-sndio --disable-stripping --enable-libaom --enable-avfilter
--enable-avresample --enable-gcrypt --disable-gnutls --enable-openssl
--enable-gpl --enable-libass --enable-libbluray --enable-libbs2b
--enable-libcaca --enable-libcdio --enable-libcodec2
--enable-libfdk-aac --enable-libfontconfig --enable-libfreetype
--enable-libfribidi --enable-libgme --enable-libgsm --enable-libilbc
--enable-libkvazaar --enable-libmp3lame --enable-libopencore-amrnb
--enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg
--enable-libopenmpt --enable-libopus --enable-libpulse
--enable-librubberband --enable-libshine --enable-libsnappy
--enable-libsoxr --enable-libspeex --enable-libtesseract
--enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc
--enable-libvorbis --enable-libvpx --enable-libx265 --enable-libzimg
--enable-libxvid --enable-libzvbi --enable-nonfree --enable-opencl
--enable-opengl --enable-postproc --enable-pthreads --enable-shared
--enable-version3 --enable-libwebp
--incdir=/usr/include/x86_64-linux-gnu
--libdir=/usr/lib/x86_64-linux-gnu --prefix=/usr --toolchain=hardened
--enable-frei0r --enable-chromaprint --enable-libx264
--enable-libiec61883 --enable-libdc1394 --enable-vaapi --enable-libmfx
--enable-libvmaf --disable-altivec
--shlibdir=/usr/lib/x86_64-linux-gnu
  libavutil  56. 22.100 / 56. 22.100
  libavcodec 58. 35.100 / 58. 35.100
  libavformat58. 20.100 / 58. 20.100
  libavdevice58.  5.100 / 58.  5.100
  libavfilter 7. 40.101 /  7. 40.101
  libavresample   4.  0.  0 /  4.  0.  0
  libswscale  5.  3.100 /  5.  3.100
  libswresample   3.  3.100 /  3.  3.100
  libpostproc55.  3.100 / 55.  3.100
Unknown filter 'scale_npp'.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Multiple Glob Inputs

2019-10-15 Thread Nicolas George
James Tan (12019-10-15):
> But I was wondering if there was also a way to add start number to a file
> list. I was hoping something like this might be possible?

No, options to individual files are not supported. A patch to support
that would be appreciated, though, if it does it cleanly.

Regards,

-- 
  Nicolas George


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

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

Re: [FFmpeg-user] Multiple Glob Inputs

2019-10-15 Thread James Tan
>
> A concat filter exists, but I suspect the concat demuxer (that works
> differently and does not use glob) is what you need.
> https://ffmpeg.org/ffmpeg-filters.html#concat
> https://ffmpeg.org/ffmpeg-formats.html#concat-1


Ah so basically you're saying you don't think there is a way to concatenate
with glob, and I should just do it with numbering? I was able to run a
shell script to make a list of all images used, something like this.

#! /bin/bash

# with a bash for loop
for f in ./Time\ Lapse\ 11/*.JPG; do echo "file '$f'" >> mylist.txt; done
for f in ./Burst\ Sequence\ 5/*.JPG; do echo "file '$f'" >> mylist.txt; done
for f in ./Burst\ Sequence\ 6/*.JPG; do echo "file '$f'" >> mylist.txt; done

But I was wondering if there was also a way to add start number to a file
list. I was hoping something like this might be possible?

ffmpeg -f concat -safe 0 -i mylist.txt \
-c:v libx264  -pix_fmt yuv420p -r 24 -crf 23 -preset fast -y output.mp4

where mylist.txt looks like

-start_number 0152396 file './Time Lapse 11/G%07d.JPG'
-start_number 0162603 file './Burst Sequence 5/G%07d.JPG'
-start_number 0172625 file './Burst Sequence 6/G%07d.JPG'

This obviously hasn't worked yet, and just writing all the filenames to
mylist.txt does work, but I was just wondering for curiosity's sake. Thank
you!
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread Ted Park
>> I have read the source code of mpegts demuxer/muxer in ffmpeg, which doesn't 
>> support
>> decoding/encoding self-defined metadata.
> 
> If you already know the answer for a question we cannot understand (see 
> above),
> why are you asking?

Maybe he found the answer while reading the source after the fact. On the other 
hand, I think this may be related to the strange issue of the mpegts decoder 
complaining of invalid timestamps on a reference (albeit obsolete) HLS stream 
that was brought up a while ago. 
 

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

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 18:18 Uhr schrieb qw :

> >> How to send some metadata in mpeg2 ts periodically at some fixed interval 
> >> via ffmpeg?
> >
> > I believe this is (always) done automatically. Since you did not provide 
> > the command line
> > you tested together with the complete, uncut console output I cannot guess 
> > why it does
> > not work for you.
> >
> > Or are you searching for the option pat_period?
>
> I have read the source code of mpegts demuxer/muxer in ffmpeg, which doesn't 
> support
> decoding/encoding self-defined metadata.

If you already know the answer for a question we cannot understand (see above),
why are you asking?

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread qw


>> mpeg2 ts supports metadata and private data. How to send some metadata in 
>> mpeg2 ts periodically at some fixed interval via ffmpeg?
>
>Are you talking about timed id3 metadata?

In ISO/IEC 13818-1, 2.12 carriage of metadata gives several options for 
transport of metadata. I don't know timed id3 metadata.


Andrew

At 2019-10-15 23:55:49, "Ted Park"  wrote:
>> mpeg2 ts supports metadata and private data. How to send some metadata in 
>> mpeg2 ts periodically at some fixed interval via ffmpeg?
>
>Are you talking about timed id3 metadata?
>___
>ffmpeg-user mailing list
>ffmpeg-user@ffmpeg.org
>https://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
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread qw


>> mpeg2 ts supports metadata and private data.
>
>Please provide a sample containing the metadata you need.

flv demuxer/muxer can decode/encode metadata in data stream. Does mpegts 
demuxer/muxer have the same function?
Mpeg2 ts standard provides several methods to transport metadata. Is there some 
apporpriate way to transport some metadata at some fixed interval?





>> How to send some metadata in mpeg2 ts periodically at some fixed interval 
>> via ffmpeg?
>
>I believe this is (always) done automatically. Since you did not provide the 
>command line you tested together with the complete, uncut console output I 
>cannot guess why it does not work for you.
>
>Or are you searching for the option pat_period?

I have read the source code of mpegts demuxer/muxer in ffmpeg, which doesn't 
support decoding/encoding self-defined metadata.







At 2019-10-15 18:00:38, "Carl Eugen Hoyos"  wrote:
>
>
>> Am 15.10.2019 um 11:14 schrieb qw :
>
>> mpeg2 ts supports metadata and private data.
>
>Please provide a sample containing the metadata you need.
>
>> How to send some metadata in mpeg2 ts periodically at some fixed interval 
>> via ffmpeg?
>
>I believe this is (always) done automatically. Since you did not provide the 
>command line you tested together with the complete, uncut console output I 
>cannot guess why it does not work for you.
>
>Or are you searching for the option pat_period?
>
>Carl Eugen
>___
>ffmpeg-user mailing list
>ffmpeg-user@ffmpeg.org
>https://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
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Multiple Glob Inputs

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 01:20 Uhr schrieb James Tan :
>
> The inputs are all images which have the same resolution, are taken from
> the same GoPro, etc. If I manually move all the images to one folder, it
> easily concatenates them all and does what I want. I can also do
>
> ffmpeg -pattern_type glob -i '*/*.JPG' \
> -r 24 -c:v libx264 -crf 23 -preset fast -pix_fmt yuv420p tl11_fast.mp4

This command uses one input (one "-i" option) that does not need
concatenation...

> which does concatenate them all, but this actually puts Burst Sequence 5
> and 6 before Time Lapse 11 because of alphabetical order I assume.

... but as you found out glob has its disadvantages, use numbering instead.

Please do not top-post here, Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] Multiple Glob Inputs

2019-10-15 Thread Carl Eugen Hoyos
Am Di., 15. Okt. 2019 um 01:27 Uhr schrieb James Tan :
>
> Sorry here's the console output. So you can see the three threads with
> durations of 8.28s, .88s, and .68s, but the final result is only 8.33s. In
> addition, the video where I just put all the images in the same folder has
> duration 9.92s.
>
> ffmpeg -pattern_type glob -i 'Time Lapse 11/*.JPG' \
> > -pattern_type glob -i 'Burst Sequence 5/*.JPG' \
> > -pattern_type glob -i 'Burst Sequence 6/*.JPG' \
> > -r 24 -c:v libx264 -crf 23 -preset fast -pix_fmt yuv420p tl11_fast.mp4

(The output option "-r" is not what you want, use the input option
"-framerate" instead.)

This command has three inputs (three times "-i"), ffmpeg does not
concatenate the three inputs.

> ffmpeg version 4.1.3 Copyright (c) 2000-2019 the FFmpeg developers

Please remember that only current FFmpeg git head is supported on
this mailing list (but the behaviour should be identical for all versions
of FFmpeg, past and future).

A concat filter exists, but I suspect the concat demuxer (that works
differently and does not use glob) is what you need.
https://ffmpeg.org/ffmpeg-filters.html#concat
https://ffmpeg.org/ffmpeg-formats.html#concat-1

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread Ted Park
> mpeg2 ts supports metadata and private data. How to send some metadata in 
> mpeg2 ts periodically at some fixed interval via ffmpeg?

Are you talking about timed id3 metadata?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

Re: [FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread Carl Eugen Hoyos


> Am 15.10.2019 um 11:14 schrieb qw :

> mpeg2 ts supports metadata and private data.

Please provide a sample containing the metadata you need.

> How to send some metadata in mpeg2 ts periodically at some fixed interval via 
> ffmpeg?

I believe this is (always) done automatically. Since you did not provide the 
command line you tested together with the complete, uncut console output I 
cannot guess why it does not work for you.

Or are you searching for the option pat_period?

Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

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

[FFmpeg-user] how to send metadata in mpegts via ffmpeg

2019-10-15 Thread qw
Hi,


mpeg2 ts supports metadata and private data. How to send some metadata in mpeg2 
ts periodically at some fixed interval via ffmpeg?


Thanks!


Regards


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

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