Re: [FFmpeg-user] Transcode from RTMP to RTP iOS

2018-12-13 Thread Utkarsh Agarwal
videotoolbox is paid which i can't use due to budget issues.
Although have posted the same question on the libav-user mailing list.
Lets see if could get a solution.

Thanks for your reply.



[image: Impressico-Business-Solutions-1079759]

A CMMI Level 3

*Impressico Business Solutions Pvt. Ltd.*

B-134, Sector 6, Noida – 201301

Phone - 8860490789
*Email - utkarsh.agar...@impressico.com *


On Fri, Dec 14, 2018 at 7:36 AM Carl Eugen Hoyos  wrote:

> 2018-12-13 12:45 GMT+01:00, Utkarsh Agarwal <
> utkarsh.agar...@impressico.com>:
> > I am working on a screen sharing iOS application . Getting streams from
> > Replay Kit which supports RTMP protocol and sending it to Kurento Media
> > Server which supports RTP.
> >
> > I can do something like below on server side.
> >
> > [Browser] -> WebrtcEndpoint -> [Kurento] -> RtpEndpoint ->
> >
> > [FFmpeg] -> RTMP -> [Node_Media_Server(srs)] -> RTMP -> [Browser]
> >
> >
> > But due to some reasons i have to transcode it in my iOS application .
> >
> > Can i transcode the RTMP stream to RTP before sending it to
> > KurentoMediaServer using FFmpeg on client side i.e iOS platform?
>
> This question seems more appropriate on the libav-user mailing list.
>
> Did you try transcoding with videotoolbox?
>
> Carl Eugen
> ___
> 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] Need assistance finding l transcoding

2018-12-13 Thread Carl Zwanzig


If you haven't already, I'd try pulling the up-to-date source and building 
that. AMD and intel CPUs differ, sometimes in strange ways, and a 
local-built version is often better than any downloaded one.


Also, have you tried capturing the stream directly into a file and using 
that for test? That would remove the UDP receiver from chain and allow some 
more off-line experimentation.


Unfortunately, I don't have anything else to add at the moment (but I'm 
really curious where this goes).


Later,

z!

___
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] Transcode from RTMP to RTP iOS

2018-12-13 Thread Carl Eugen Hoyos
2018-12-13 12:45 GMT+01:00, Utkarsh Agarwal :
> I am working on a screen sharing iOS application . Getting streams from
> Replay Kit which supports RTMP protocol and sending it to Kurento Media
> Server which supports RTP.
>
> I can do something like below on server side.
>
> [Browser] -> WebrtcEndpoint -> [Kurento] -> RtpEndpoint ->
>
> [FFmpeg] -> RTMP -> [Node_Media_Server(srs)] -> RTMP -> [Browser]
>
>
> But due to some reasons i have to transcode it in my iOS application .
>
> Can i transcode the RTMP stream to RTP before sending it to
> KurentoMediaServer using FFmpeg on client side i.e iOS platform?

This question seems more appropriate on the libav-user mailing list.

Did you try transcoding with videotoolbox?

Carl Eugen
___
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] Get exact duration of an mpeg1 file

2018-12-13 Thread Carl Eugen Hoyos
2018-12-13 17:10 GMT+01:00, Robert Krüger :

> is there a way to get the exact duration of a raw mpeg1 file using the
> ffmpeg command line? For testing I created a 30 minute test file using
> ffmpeg (using -c:v mpeg1video -f mpeg1video), then verified the duration
> using VLC and mediainfo and it is indeed exactly 30 minutes long but ffmpeg
> -i shows the file's duration as 00:00:04.98 after displaying this warning:
>
> [mpegvideo @ 0x7fe212806000] Estimating duration from bitrate, this may be
> inaccurate
>
> Are there command line parameters to make it compute the exact size or is
> this a design or implementation limitation?

Just the mpeg specification;-)

$ ffmpeg -i input -c copy -f null -

Carl Eugen
___
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] Need assistance finding l transcoding

2018-12-13 Thread James E. Baird
>It's actually ABR you're creating, if I understand correctly.

Not yet as I am actually outputting 3 multicast streams, each with a set 
bitrate(1500/3500/6000). They will be captured on the other side of the network 
and then muxed together to create the ABR stream (a design that, as of yet, 
cannot be avoided).

>Unfortunately, that preset is a bandwidth hog, and will drop quality 
>significantly. Actually, it also lowers your profile to "Constrained 
>Baseline". :-(

Bandwidth piece wouldn't be as much of a problem since this is layer2 to the 
endpoint that will mux them back together but the quality loss and profile 
change is a problem.
If I go to superfast my speed drops to .914 on average. If I understand 
correctly, this means I am slowing getting farther and farther behind? Will I 
eventually have an overrun in my fifo buffer causing a reset and lost data? 
Just double checking my understanding there.

Thanks so far for the help so far.

Maybe someone else will chime in with the best answer ever!

-Jimbo
CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is confidential 
and may contain information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox.
___
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] Error with mp4 files moov atom (\moov\trak\mdia\minf\stbl\sgpd)

2018-12-13 Thread Karen Norton
On Thu, Dec 13, 2018 at 3:40 PM Moritz Barsnick  wrote:

> Hi Karen,
>
> On Thu, Dec 13, 2018 at 15:04:15 -0500, Karen Norton wrote:
>
> > I only see the error when opening the output files with MP4 Inspector
> > otherwise the files play fine (ex: in VLC) and show no issues in
> > mediainfo.
>
> So basically, it's not an issue at all, *except* for MP4 Inspector?
>
> > I wouldn't have even know this was an issue because everything appears
> fine
> > with V90893. I only discovered this because I just downloaded MP4
> Inspector
> > to try.
>
> See what I mean. ;-)
>
> > The exact error in MP4 Inspector is:
> > Failed on reading box header, parent box path
> > "\moov\trak\mdia\minf\stbl\sgpd", stream position "0x1C7362678B6399",
> > reason "The box size 0 exceeds the remaining file length
> > -8,008,165,506,864,740." (I have attached a screenshot of the error).
>
> I don't want to seem rude - but why would you trust a tool which
> reports negative file sizes?
>
> In other words: Why should MP4 Inspector be more correct than ffmpeg?
> Perhaps they have a bugfix release? ;-)
>
> Now, seriously:
>
> > ffmpeg 90893 (not working in MP4 Inspector):
> > Command: ffmpeg -i inputs01e01.mp4 -metadata media_type="10" -metadata
> > title="Law & Order" -metadata show="Prescription For Death" -metadata
> > season_number="1" -metadata genre="Crime, Drama, Mystery" -metadata
> > episode_id="66209" -metadata episode_sort="1" -metadata:s:a:0
> language=eng
> > -c:v libx264 -vf hflip -c:a copy outputs01e01.mp4
>
> Can you create such files ("broken" for MP4 Inspector) with arbitrary
> input? I.e. with
> $ ffmpeg -f lavfi -i testsrc -t 1 -c:v libx264 output.mp4
>
> Or does it depend on your particular input?
>
> Too bad MP4 Inspector doesn't run under Wine, otherwise I'd try to
> reproduce...
>
> Cheers,
> Moritz


Hey Moritz,

Thanks for the speedy reply. I guess I should have said that this isn't
necessarily an ffmpeg issue it's just that ffmpeg N-85588 seems to fix that
atom (whether it's supposed to or not) but N-90893 doesn't so I'm curious
as to what has changed between the versions in so far as how the moov atom
is handled or is the error not even moov related?

It's hard for me to know exactly what is going on with the broken files
because MP4 Inspector won't even open them. In the few tests I ran with
different files where the input file already has the error I found that all
of them still have the error in the output file using N-90893. If I take
the same input files and run the same command under N-85588 then the moov
atom seems to be fixed and the output files open fine in MP4 Inspector.

I have only recently started going deep into video files to understand how
they are constructed and it was recommended in some posts on other forums
that MP4 Inspector is a good app to see the innards of the files which is
why I started to use it. There was another app that was mentioned in the
forums called atomic parsley. I haven't tried that yet.

You  mentioned whether I can create broken files. I'm assuming I was
supposed to try that command line exactly as you provided? If so the output
file opens fine when created under N-90893.

Cheers.


K
___
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] Need assistance finding l transcoding

2018-12-13 Thread Moritz Barsnick
On Thu, Dec 13, 2018 at 20:49:56 +, James E. Baird wrote:
> It does need to be a CBR. It will be converted to an adaptive stream for a 
> streaming app

It's actually ABR you're creating, if I understand correctly.

> I felt that I should get more horsepower as well and that is the main
> reason I started this thread.

My dual-core Haswell Ultrabook can handle your command line at 1.4x
(using testsrc2 input though, probably easy to encode), at preset
"fast" it drops to 0.7. But that's 2, not 8, cores.

> The biggest performance change I am seeing is changing the preset to
> ultrafast.

Unfortunately, that preset is a bandwidth hog, and will drop quality
significantly. Actually, it also lowers your profile to "Constrained
Baseline". :-(

> The other performance gain comes from combing the 3 output bitrates
> into a single command.

Sure, that's the way to go. (You need to demux and decode only once,
then.)

> Not sure if anyone has further suggestions for this?

I was hoping others had comparable benchmarks.

Moritz
___
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] Need assistance finding l transcoding

2018-12-13 Thread James E. Baird
Moritz,

>Does it need to be fixed bitrate? (Just wondering.)

It does need to be a CBR. It will be converted to an adaptive stream for a 
streaming app

>Is this ultimately the issue? That you can't encode at real time?

These are live streams that need to be forwarded off, packaged in HLS and sent 
to streaming app and accessible within 1 minute from broadcast so that is part 
of it.

>At "constant"/average bitrate (-b:v), you should be able to use libx264's 
>presets to trade off quality for speed. Perhaps you can achieve >1.0x that 
>way. I don't see how you will do three simultaneous encodes though.
>BTW, eight CPUs to encode 1280x720@59.94 in realtime seems sort of heavy. Are 
>these Atom cores or something similarly weak?

I felt that I should get more horsepower as well and that is the main reason I 
started this thread. I have been working with live streams for a few years now 
but surprisingly, this is the first time I have needed to dig into transcoding 
like this so I was hoping there was something glaringly inefficient about how I 
was trying to get to the end result. I see some venders of transcoders using 
CPUs that are not as powerful as this one on their transcoding hardware 
(without GPU or ASIC chips) and I am assuming they are leveraging FFMPEG or 
something similar in the background.

I have edited my command a bit. The biggest performance change I am seeing is 
changing the preset to ultrafast. I am not sure that quality will work yet but 
it gets the utilization down to 350% CPU usage. The other performance gain 
comes from combing the 3 output bitrates into a single command. Not sure if 
anyone has further suggestions for this?

=== New command 
transcoder:~$ ffmpeg -i 
'udp://@239.129.2.110:59110?fifo_size=100_nonfatal=1' \
> -c:v libx264 -x264opts keyint=120:no-scenecut -preset ultrafast -b:v 6000k 
> -minrate 6000k -maxrate 6000k -bufsize 12000k -profile:v high -level 4.0 -c:a 
> aac -f mpegts udp://@239.129.2.240:59240 \
> -c:v libx264 -x264opts keyint=120:no-scenecut -preset ultrafast -b:v 3500k 
> -minrate 3500k -maxrate 3500k -bufsize 9000k -profile:v high -level 4.0 -c:a 
> aac -f mpegts udp://@239.129.2.241:59241 \
> -c:v libx264 -x264opts keyint=120:no-scenecut -preset ultrafast -b:v 1500k 
> -minrate 1500k -maxrate 1500k -bufsize 3000k -profile:v high -level 4.0 -c:a 
> aac -f mpegts udp://@239.129.2.242:59242

===OUTPUT ===
ffmpeg version 3.4.4-0ubuntu0.18.04.1 Copyright (c) 2000-2018 the FFmpeg 
developers
  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu 
--incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping 
--enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa 
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca 
--enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame 
--enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus 
--enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine 
--enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh 
--enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx 
--enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 
--enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal 
--enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm 
--enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv 
--enable-libx264 --enable-shared
  libavutil  55. 78.100 / 55. 78.100
  libavcodec 57.107.100 / 57.107.100
  libavformat57. 83.100 / 57. 83.100
  libavdevice57. 10.100 / 57. 10.100
  libavfilter 6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale  4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc54.  7.100 / 54.  7.100
[mpeg2video @ 0x556b70e9c580] Invalid frame dimensions 0x0.
Last message repeated 7 times
Input #0, mpegts, from 
'udp://@239.129.2.110:59110?fifo_size=100_nonfatal=1':
  Duration: N/A, start: 95234.341144, bitrate: N/A
  Program 3
Stream #0:0[0x31]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), 
yuv420p(tv, bt709, bottom first), 1280x720 [SAR 1:1 DAR 16:9], Closed Captions, 
59.94 fps, 59.94 tbr, 90k tbn, 119.88 tbc
Stream #0:1[0x34](eng): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 
5.1(side), fltp, 384 kb/s
Stream #0:2[0x35](spa): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, 
fltp, 128 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg2video (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))
  Stream #0:0 -> #1:0 (mpeg2video (native) -> h264 (libx264))
  Stream #0:1 -> #1:1 (ac3 (native) -> aac (native))
  Stream #0:0 -> #2:0 (mpeg2video (native) -> h264 (libx264))

Re: [FFmpeg-user] Error with mp4 files moov atom (\moov\trak\mdia\minf\stbl\sgpd)

2018-12-13 Thread Moritz Barsnick
Hi Karen,

On Thu, Dec 13, 2018 at 15:04:15 -0500, Karen Norton wrote:

> I only see the error when opening the output files with MP4 Inspector
> otherwise the files play fine (ex: in VLC) and show no issues in
> mediainfo.

So basically, it's not an issue at all, *except* for MP4 Inspector?

> I wouldn't have even know this was an issue because everything appears fine
> with V90893. I only discovered this because I just downloaded MP4 Inspector
> to try.

See what I mean. ;-)

> The exact error in MP4 Inspector is:
> Failed on reading box header, parent box path
> "\moov\trak\mdia\minf\stbl\sgpd", stream position "0x1C7362678B6399",
> reason "The box size 0 exceeds the remaining file length
> -8,008,165,506,864,740." (I have attached a screenshot of the error).

I don't want to seem rude - but why would you trust a tool which
reports negative file sizes?

In other words: Why should MP4 Inspector be more correct than ffmpeg?
Perhaps they have a bugfix release? ;-)

Now, seriously:

> ffmpeg 90893 (not working in MP4 Inspector):
> Command: ffmpeg -i inputs01e01.mp4 -metadata media_type="10" -metadata
> title="Law & Order" -metadata show="Prescription For Death" -metadata
> season_number="1" -metadata genre="Crime, Drama, Mystery" -metadata
> episode_id="66209" -metadata episode_sort="1" -metadata:s:a:0 language=eng
> -c:v libx264 -vf hflip -c:a copy outputs01e01.mp4

Can you create such files ("broken" for MP4 Inspector) with arbitrary
input? I.e. with
$ ffmpeg -f lavfi -i testsrc -t 1 -c:v libx264 output.mp4

Or does it depend on your particular input?

Too bad MP4 Inspector doesn't run under Wine, otherwise I'd try to
reproduce...

Cheers,
Moritz
___
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] Need assistance finding l transcoding

2018-12-13 Thread Moritz Barsnick
On Thu, Dec 13, 2018 at 18:33:02 +, James E. Baird wrote:
> I spun up a new server running Ubuntu 18.04.1 LTS and installed
> FFMPEG version 7.3.4.4 which is the current supported version for
> Bionic Beaver.

Though I think that't not the issue, you should grab a much newer
version. You can get a pre-built binary here:
https://johnvansickle.com/ffmpeg/
Please use the "git" version from the left hand side.

> Thanks for the suggestions so far. I suspect there is something in
> that command that is causing the high CPU usage. Maybe there is a
> better way to structure the command.

> %CPU 752.2 - %MEM 28.9 - 35:03.24 ffmpeg

Well, at least you seem to be utilizing your 8 CPUs almost as much as
possible, so it doesn't seem to be a threading issue.

> transcoder:~$ ffmpeg -i 
> 'udp://@239.129.2.110:59110?fifo_size=100_nonfatal=1' -c:v 
> libx264 -x264opts keyint=120:no-scenecut -b:v 6000k -profile:v high -c:a aac 
> -f null /dev/null

Does it need to be fixed bitrate? (Just wondering.)

> frame= 2917 fps= 49 q=31.0 size=N/A time=00:00:48.91 bitrate=N/A speed=0.828x

Is this ultimately the issue? That you can't encode at real time?

At "constant"/average bitrate (-b:v), you should be able to use
libx264's presets to trade off quality for speed. Perhaps you can
achieve >1.0x that way. I don't see how you will do three simultaneous
encodes though.

BTW, eight CPUs to encode 1280x720@59.94 in realtime seems sort of
heavy. Are these Atom cores or something similarly weak?

> AMD Opteron(tm) Processor 6282 SE

Oh. Hmm.

> Thoughts?

Not many, sorry.

Moritz
___
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] Need assistance finding l transcoding

2018-12-13 Thread James E. Baird
Carl,

Thanks for the suggestions so far. I suspect there is something in that command 
that is causing the high CPU usage. Maybe there is a better way to structure 
the command. I spun up a new server running Ubuntu 18.04.1 LTS and installed 
FFMPEG version 7.3.4.4 which is the current supported version for Bionic Beaver.

I tried what you said and output to NULL with the same results in regards to 
the CPU usage so I don’t think it’s the re-pack to UDP multicast.

 OUTPUT ==
transcoder:~$ ffmpeg -i 
'udp://@239.129.2.110:59110?fifo_size=100_nonfatal=1' -c:v libx264 
-x264opts keyint=120:no-scenecut -b:v 6000k -profile:v high -c:a aac -f null 
/dev/null
ffmpeg version 3.4.4-0ubuntu0.18.04.1 Copyright (c) 2000-2018 the FFmpeg 
developers
  built with gcc 7 (Ubuntu 7.3.0-16ubuntu3)
  configuration: --prefix=/usr --extra-version=0ubuntu0.18.04.1 
--toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu 
--incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping 
--enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa 
--enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca 
--enable-libcdio --enable-libflite --enable-libfontconfig --enable-libfreetype 
--enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame 
--enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus 
--enable-libpulse --enable-librubberband --enable-librsvg --enable-libshine 
--enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh 
--enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx 
--enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 
--enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal 
--enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm 
--enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv 
--enable-libx264 --enable-shared
  libavutil  55. 78.100 / 55. 78.100
  libavcodec 57.107.100 / 57.107.100
  libavformat57. 83.100 / 57. 83.100
  libavdevice57. 10.100 / 57. 10.100
  libavfilter 6.107.100 /  6.107.100
  libavresample   3.  7.  0 /  3.  7.  0
  libswscale  4.  8.100 /  4.  8.100
  libswresample   2.  9.100 /  2.  9.100
  libpostproc54.  7.100 / 54.  7.100
[mpeg2video @ 0x55d5c951cec0] Invalid frame dimensions 0x0.
Last message repeated 13 times
Input #0, mpegts, from 
'udp://@239.129.2.110:59110?fifo_size=100_nonfatal=1':
  Duration: N/A, start: 89749.701144, bitrate: N/A
  Program 3
Stream #0:0[0x31]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), 
yuv420p(tv, bt709, bottom first), 1280x720 [SAR 1:1 DAR 16:9], Closed Captions, 
59.94 fps, 59.94 tbr, 90k tbn, 119.88 tbc
Stream #0:1[0x34](eng): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, 
5.1(side), fltp, 384 kb/s
Stream #0:2[0x35](spa): Audio: ac3 (AC-3 / 0x332D4341), 48000 Hz, stereo, 
fltp, 128 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (mpeg2video (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))
Press [q] to stop, [?] for help
[libx264 @ 0x55d5c9a46980] using SAR=1/1
[libx264 @ 0x55d5c9a46980] using cpu capabilities: MMX2 SSE2Fast LZCNT SSSE3 
SSE4.2 AVX XOP FMA4
[libx264 @ 0x55d5c9a46980] profile High, level 3.2
Output #0, null, to '/dev/null':
  Metadata:
encoder : Lavf57.83.100
Stream #0:0: Video: h264 (libx264), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], 
q=-1--1, 6000 kb/s, 59.94 fps, 59.94 tbn, 59.94 tbc
Metadata:
  encoder : Lavc57.107.100 libx264
Side data:
  cpb: bitrate max/min/avg: 0/0/600 buffer size: 0 vbv_delay: -1
Stream #0:1(eng): Audio: aac (LC), 48000 Hz, 5.1(side), fltp, 341 kb/s
Metadata:
  encoder : Lavc57.107.100 aac
frame= 2917 fps= 49 q=31.0 size=N/A time=00:00:48.91 bitrate=N/A speed=0.828x


Thoughts?
-Jimbo
CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is confidential 
and may contain information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox.
___
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] Need assistance finding l transcoding

2018-12-13 Thread Carl Zwanzig

On 12/13/2018 9:12 AM, James E. Baird wrote:

ffprobe version git-2017-01-22-f1214ad Copyright (c) 2007-2017 the FFmpeg 
developers


First thing- get a newer version (the latest, if possible) of ffmpeg and see 
how that behaves. Best would to build from the latest source, but at least 
something no more than a couple of months old. The official position of 
developers, and I am not one of them, is that only the latest revision in 
git is "supported" here. Anyway, try a newer version.


You might also try transcoding into a file (or null) and outputing from a 
file to see if one or the other parts is a CPU hog.


z!
___
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] Get exact duration of an mpeg1 file

2018-12-13 Thread Carl Zwanzig

On 12/13/2018 9:07 AM, Robert Krüger wrote:

Sorry, I have to take that back as I used the wrong file and got something
mixed up when looking at it. -probesize doesn't change the behaviour at
all. I set it to a value larger than the file and still got the warning and
the incorrect number. So for mpeg1 this does not seem to work and seems to
be consistent with my last test a long time ago.


Happens :).

You could simply "play" the file into null output and catch the frame count 
at the end ("ffmpeg -i  -f null -"). May have to play with other 
options to get readily-parsible text.


z!
___
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] Get exact duration of an mpeg1 file

2018-12-13 Thread Robert Krüger
Hi again,

On Thu, Dec 13, 2018 at 6:01 PM Robert Krüger 
wrote:

> Hi Carl,
>
> On Thu, Dec 13, 2018 at 5:31 PM Carl Zwanzig  wrote:
>
>> On 12/13/2018 8:10 AM, Robert Krüger wrote:
>> > Are there command line parameters to make it compute the exact size or
>> is
>> > this a design or implementation limitation?
>>
>> IIRC (and I could be wrong), the generic "info" uses metadata whereas
>> mediainfo actually counts frames and applies the frame rate to that.
>> Without
>> a container, there's no appropriate metadata.
>>
>
> yes, absolutely, that's what I assumed, I just didn't know the option to
> force it to do something else.
>
>
>>
>> It's easy enough to tell, if ffmpeg -i returns almost immediately, it's
>> probably not counting frames. You also might get a more accurate answer
>> by
>> using -probesize with a parameter larger than the actual file.
>>
>>
> that did the trick, thanks! There still a minor inaccuracy of a few frames
> but that is probably still https://trac.ffmpeg.org/ticket/3683. My main
> concern was estimating vs. actually parsing.
>
>
>
Sorry, I have to take that back as I used the wrong file and got something
mixed up when looking at it. -probesize doesn't change the behaviour at
all. I set it to a value larger than the file and still got the warning and
the incorrect number. So for mpeg1 this does not seem to work and seems to
be consistent with my last test a long time ago.

Sorry about the confusion.

Robert
___
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] Need assistance finding l transcoding

2018-12-13 Thread Carl Zwanzig

On 12/13/2018 8:51 AM, James E. Baird wrote:

Here is the command I am currently using but the CPU usage seems way to high 
for what I am doing.
AMD Opteron(tm) Processor 6282 SE with 8 cores assigned to VM but all 8 are 
pegged when running this.


Are they all pegged in compute or is there a lot else going on? (and what 
does the VM management system say?)



ffmpeg -i 'udp://@239.129.1.5:59005?fifo_size=100_nonfatal=1' -c:v 
libx264 -x264opts keyint=120:no-scenecut -b:v 6000k -profile:v high -c:a aac -f 
mpegtsudp://@239.129.2.10:50010


It would help to know what version/build and OS you're using and what it's 
doing (please include the full command output, without using --hide-banners).


z!
___
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] Need assistance finding l transcoding

2018-12-13 Thread James E. Baird
Hello,

I am trying to find the most efficient way to take a udp stream (Source OTA) 
and transcode video to h.264, audio to AAC, output as 3 aligned cbr 
(1500/3500/6000k) streams (udp), gop 2 (60 for 30FPS or 120 for 60FPS)

Here is the command I am currently using but the CPU usage seems way to high 
for what I am doing.
AMD Opteron(tm) Processor 6282 SE with 8 cores assigned to VM but all 8 are 
pegged when running this.

ffmpeg -i 'udp://@239.129.1.5:59005?fifo_size=100_nonfatal=1' -c:v 
libx264 -x264opts keyint=120:no-scenecut -b:v 6000k -profile:v high -c:a aac -f 
mpegts udp://@239.129.2.10:50010

-Thanks,
Jimbo





CONFIDENTIALITY NOTICE: This e-mail including attachments is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. §§2510-2521, is confidential 
and may contain information that is privileged, confidential or otherwise 
protected from use and disclosure. If you are not the intended recipient, you 
are hereby notified that any review, disclosure, copying, or dissemination of 
this transmission, or taking of any action in reliance on its contents, or 
other use is strictly prohibited. If you have received this transmission in 
error, please reply to the sender listed above immediately and permanently 
delete this message from your inbox.
___
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] Get exact duration of an mpeg1 file

2018-12-13 Thread Carl Zwanzig

On 12/13/2018 8:10 AM, Robert Krüger wrote:

Are there command line parameters to make it compute the exact size or is
this a design or implementation limitation?


IIRC (and I could be wrong), the generic "info" uses metadata whereas 
mediainfo actually counts frames and applies the frame rate to that. Without 
a container, there's no appropriate metadata.


It's easy enough to tell, if ffmpeg -i returns almost immediately, it's 
probably not counting frames. You also might get a more accurate answer by 
using -probesize with a parameter larger than the actual file.


Later,

z!
who's not at the right system to try this now
___
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] Get exact duration of an mpeg1 file

2018-12-13 Thread Robert Krüger
Hi,

is there a way to get the exact duration of a raw mpeg1 file using the
ffmpeg command line? For testing I created a 30 minute test file using
ffmpeg (using -c:v mpeg1video -f mpeg1video), then verified the duration
using VLC and mediainfo and it is indeed exactly 30 minutes long but ffmpeg
-i shows the file's duration as 00:00:04.98 after displaying this warning:

[mpegvideo @ 0x7fe212806000] Estimating duration from bitrate, this may be
inaccurate

Are there command line parameters to make it compute the exact size or is
this a design or implementation limitation?

Thanks,
Robert
___
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: VBV buffer size not set

2018-12-13 Thread Ulf Zibis
Hi,

Am 12.12.18 um 20:15 schrieb Carl Eugen Hoyos:
> (My answer wasn't wrong but your command line does not make
> much sense.)
>
> If your command succeeds (ie you ignore Hans' warning but still
> get a useful output file) the following will also work and has
> many advantages (apart from not showing a muxer warning):
> cat CYD-001.vob CYD-002.vob ... >CYD_copy.vob

With this I got an unusable result. The file was not playable with
several video players, but the result from

ffmpeg -i "concat:CYD-001.vob|CYD-002.vob|..." -c copy CYD_copy.vob

was.

If you are familiar with German, you can follow the whole case here (the
partial .vob-files had to be created by dvd::rip):
https://forum.ubuntuusers.de/topic/konvertiertes-video-am-ende-ohne-ton-geeignete/
Especially note this post:
https://forum.ubuntuusers.de/post/9029332/

-Ulf


___
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] Transcode from RTMP to RTP iOS

2018-12-13 Thread Utkarsh Agarwal
I am working on a screen sharing iOS application . Getting streams from
Replay Kit which supports RTMP protocol and sending it to Kurento Media
Server which supports RTP.

I can do something like below on server side.

[Browser] -> WebrtcEndpoint -> [Kurento] -> RtpEndpoint ->

[FFmpeg] -> RTMP -> [Node_Media_Server(srs)] -> RTMP -> [Browser]


But due to some reasons i have to transcode it in my iOS application .



Can i transcode the RTMP stream to RTP before sending it to
KurentoMediaServer using FFmpeg on client side i.e iOS platform?
___
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] skipped frames with 18fps DPX - non monotonically increasing dts to muxer

2018-12-13 Thread Paul B Mahol
On 12/13/18, Kieran O'Leary  wrote:
> Hi,
>
> I have encountered some DPX that has an fps of 18. It seems that ffmpeg
> skips every few frames when decoding - at least when I performed a framemd5
> analysis. I noticed that 30522 frames were decoded, 10172 were dropped.
>
> It seems that adding -framerate 18 to as an input option resolves the issue,
> but should ffmpeg not auto-detect the FPS?
>
> I can replicate the issue with just a few frames (I will see if I can share
> the samples) - here's 17 frames decoded with nullm followed by the md5 muxer
> where only 14 frames are processed.:
>
> $ ./ffmpeg -i ffmpeg-1-01_%06d.dpx -f null -
>
> ffmpeg version N-92683-g32601fb821 Copyright (c) 2000-2018 the FFmpeg
> developers
>
>   built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
>
>   configuration:
>
>   libavutil  56. 24.101 / 56. 24.101
>
>   libavcodec 58. 42.100 / 58. 42.100
>
>   libavformat58. 24.100 / 58. 24.100
>
>   libavdevice58.  6.101 / 58.  6.101
>
>   libavfilter 7. 46.101 /  7. 46.101
>
>   libswscale  5.  4.100 /  5.  4.100
>
>   libswresample   3.  4.100 /  3.  4.100
>
> Input #0, image2, from 'ffmpeg-1-01_%06d.dpx':
>
>   Duration: 00:00:00.68, start: 0.00, bitrate: N/A
>
> Stream #0:0: Video: dpx, gbrp10le, 3840x2160, 18 tbr, 25 tbn, 18 tbc
>
> Stream mapping:
>
>   Stream #0:0 -> #0:0 (dpx (native) -> wrapped_avframe (native))
>
> Press [q] to stop, [?] for help
>
> Output #0, null, to 'pipe:':
>
>   Metadata:
>
> encoder : Lavf58.24.100
>
> Stream #0:0: Video: wrapped_avframe, gbrp10le, 3840x2160, q=2-31, 200
> kb/s, 18 fps, 18 tbn, 18 tbc
>
> Metadata:
>
>   encoder : Lavc58.42.100 wrapped_avframe
>
> [null @ 0x7f88d3000600] Application provided invalid, non monotonically
> increasing dts to muxer in stream 0: 1 >= 1
>
> [null @ 0x7f88d3000600] Application provided invalid, non monotonically
> increasing dts to muxer in stream 0: 4 >= 4
>
> [null @ 0x7f88d3000600] Application provided invalid, non monotonically
> increasing dts to muxer in stream 0: 6 >= 6
>
> [null @ 0x7f88d3000600] Application provided invalid, non monotonically
> increasing dts to muxer in stream 0: 9 >= 9
>
> frame=   17 fps=0.0 q=-0.0 Lsize=N/A time=00:00:00.72 bitrate=N/A speed=
> 1.1x
>
> video:9kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing
> overhead: unknown
>
>
> $ ./ffmpeg -i ffmpeg-1-01_%06d.dpx -f md5  -
>
> ffmpeg version N-92683-g32601fb821 Copyright (c) 2000-2018 the FFmpeg
> developers
>
>   built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
>
>   configuration:
>
>   libavutil  56. 24.101 / 56. 24.101
>
>   libavcodec 58. 42.100 / 58. 42.100
>
>   libavformat58. 24.100 / 58. 24.100
>
>   libavdevice58.  6.101 / 58.  6.101
>
>   libavfilter 7. 46.101 /  7. 46.101
>
>   libswscale  5.  4.100 /  5.  4.100
>
>   libswresample   3.  4.100 /  3.  4.100
>
> Input #0, image2, from 'ffmpeg-1-01_%06d.dpx':
>
>   Duration: 00:00:00.68, start: 0.00, bitrate: N/A
>
> Stream #0:0: Video: dpx, gbrp10le, 3840x2160, 18 tbr, 25 tbn, 18 tbc
>
> Stream mapping:
>
>   Stream #0:0 -> #0:0 (dpx (native) -> rawvideo (native))
>
> Press [q] to stop, [?] for help
>
> Output #0, md5, to 'pipe:':
>
>   Metadata:
>
> encoder : Lavf58.24.100
>
> Stream #0:0: Video: rawvideo (G3[0][10] / 0xA003347), gbrp10le,
> 3840x2160, q=2-31, 4478976 kb/s, 18 fps, 18 tbn, 18 tbc
>
> Metadata:
>
>   encoder : Lavc58.42.100 rawvideo
>
> frame=5 fps=0.0 q=-0.0 size=   0kB time=00:00:00.27 bitrate=
> 0.0kbits/frame=9 fps=7.5 q=-0.0 size=   0kB time=00:00:00.50
> bitrate=   0.0kbits/frame=   12 fps=7.0 q=-0.0 size=   0kB
> time=00:00:00.66 bitrate=   0.0kbits/MD5=123fb3ff58ca94c842453b518aeb6a9a
>
> frame=   14 fps=6.6 q=-0.0 Lsize=   0kB time=00:00:00.77 bitrate=
> 0.4kbits/s dup=0 drop=3 speed=0.364x

Here it says it dropped 3 frames.

>
> video:680400kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB
> muxing overhead: unknown

This is because null does not need timestamps so it pass all frames no
matter which timestamps are there, on other hand md5 drops frames with
same timestamps.
___
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] consult volume

2018-12-13 Thread Nicolas George
Moritz Barsnick (2018-12-13):
> On Wed, Dec 12, 2018 at 21:43:02 +0100, Juan carlos Rebate wrote:
> > hello, how can you check the volume number of a file?, to change it
> > useful -filter "volume", but I do not know how to consult the original
> > volume thanks
> The filter "volumedetect" is what you are looking for.

ebur128 might be a better choice.

But Juan Carlos must realize this is not CONSULTING the original volume,
it is measuring it. There is no "original volume value" that the volume
filter adjusts, there is an audio signal that the volume filters
amplifies or reduces.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature
___
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] skipped frames with 18fps DPX - non monotonically increasing dts to muxer

2018-12-13 Thread Kieran O'Leary
Hi,

I have encountered some DPX that has an fps of 18. It seems that ffmpeg skips 
every few frames when decoding - at least when I performed a framemd5 analysis. 
I noticed that 30522 frames were decoded, 10172 were dropped.

It seems that adding -framerate 18 to as an input option resolves the issue, 
but should ffmpeg not auto-detect the FPS?

I can replicate the issue with just a few frames (I will see if I can share the 
samples) - here's 17 frames decoded with nullm followed by the md5 muxer where 
only 14 frames are processed.:

$ ./ffmpeg -i ffmpeg-1-01_%06d.dpx -f null -

ffmpeg version N-92683-g32601fb821 Copyright (c) 2000-2018 the FFmpeg developers

  built with Apple LLVM version 8.0.0 (clang-800.0.42.1)

  configuration:

  libavutil  56. 24.101 / 56. 24.101

  libavcodec 58. 42.100 / 58. 42.100

  libavformat58. 24.100 / 58. 24.100

  libavdevice58.  6.101 / 58.  6.101

  libavfilter 7. 46.101 /  7. 46.101

  libswscale  5.  4.100 /  5.  4.100

  libswresample   3.  4.100 /  3.  4.100

Input #0, image2, from 'ffmpeg-1-01_%06d.dpx':

  Duration: 00:00:00.68, start: 0.00, bitrate: N/A

Stream #0:0: Video: dpx, gbrp10le, 3840x2160, 18 tbr, 25 tbn, 18 tbc

Stream mapping:

  Stream #0:0 -> #0:0 (dpx (native) -> wrapped_avframe (native))

Press [q] to stop, [?] for help

Output #0, null, to 'pipe:':

  Metadata:

encoder : Lavf58.24.100

Stream #0:0: Video: wrapped_avframe, gbrp10le, 3840x2160, q=2-31, 200 kb/s, 
18 fps, 18 tbn, 18 tbc

Metadata:

  encoder : Lavc58.42.100 wrapped_avframe

[null @ 0x7f88d3000600] Application provided invalid, non monotonically 
increasing dts to muxer in stream 0: 1 >= 1

[null @ 0x7f88d3000600] Application provided invalid, non monotonically 
increasing dts to muxer in stream 0: 4 >= 4

[null @ 0x7f88d3000600] Application provided invalid, non monotonically 
increasing dts to muxer in stream 0: 6 >= 6

[null @ 0x7f88d3000600] Application provided invalid, non monotonically 
increasing dts to muxer in stream 0: 9 >= 9

frame=   17 fps=0.0 q=-0.0 Lsize=N/A time=00:00:00.72 bitrate=N/A speed= 1.1x

video:9kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing 
overhead: unknown


$ ./ffmpeg -i ffmpeg-1-01_%06d.dpx -f md5  -

ffmpeg version N-92683-g32601fb821 Copyright (c) 2000-2018 the FFmpeg developers

  built with Apple LLVM version 8.0.0 (clang-800.0.42.1)

  configuration:

  libavutil  56. 24.101 / 56. 24.101

  libavcodec 58. 42.100 / 58. 42.100

  libavformat58. 24.100 / 58. 24.100

  libavdevice58.  6.101 / 58.  6.101

  libavfilter 7. 46.101 /  7. 46.101

  libswscale  5.  4.100 /  5.  4.100

  libswresample   3.  4.100 /  3.  4.100

Input #0, image2, from 'ffmpeg-1-01_%06d.dpx':

  Duration: 00:00:00.68, start: 0.00, bitrate: N/A

Stream #0:0: Video: dpx, gbrp10le, 3840x2160, 18 tbr, 25 tbn, 18 tbc

Stream mapping:

  Stream #0:0 -> #0:0 (dpx (native) -> rawvideo (native))

Press [q] to stop, [?] for help

Output #0, md5, to 'pipe:':

  Metadata:

encoder : Lavf58.24.100

Stream #0:0: Video: rawvideo (G3[0][10] / 0xA003347), gbrp10le, 3840x2160, 
q=2-31, 4478976 kb/s, 18 fps, 18 tbn, 18 tbc

Metadata:

  encoder : Lavc58.42.100 rawvideo

frame=5 fps=0.0 q=-0.0 size=   0kB time=00:00:00.27 bitrate=   
0.0kbits/frame=9 fps=7.5 q=-0.0 size=   0kB time=00:00:00.50 bitrate=   
0.0kbits/frame=   12 fps=7.0 q=-0.0 size=   0kB time=00:00:00.66 bitrate=   
0.0kbits/MD5=123fb3ff58ca94c842453b518aeb6a9a

frame=   14 fps=6.6 q=-0.0 Lsize=   0kB time=00:00:00.77 bitrate=   
0.4kbits/s dup=0 drop=3 speed=0.364x

video:680400kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB 
muxing overhead: unknown



Best,


Kieran O'Leary

Irish Film Institute



--
This email has been scanned for spam and malware by The Email Laundry.


___
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] consult volume

2018-12-13 Thread Moritz Barsnick
On Wed, Dec 12, 2018 at 21:43:02 +0100, Juan carlos Rebate wrote:
> hello, how can you check the volume number of a file?, to change it
> useful -filter "volume", but I do not know how to consult the original
> volume thanks

The filter "volumedetect" is what you are looking for.

Cheers,
Moritz
___
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".