Re: [FFmpeg-user] Encoding Warnings

2020-06-30 Thread Jim


On 06/29/20 11:18, Moritz Barsnick wrote:

On Mon, Jun 29, 2020 at 10:44:04 -0400, Jim wrote:

AFAIK, ffmpeg does not have the ability to analyze the volume of every
sample throughout an audio file, find the greatest amplitude, calculate
the adjustment needed to make the loudest part of the file the maximum,

It does.


and then apply that scaled volume adjustment to the entire file.

This makes this a two-pass operation, which your external tool probably
also does. ffmpeg can analyze first:

$ ffmpeg -i INPUT -map 0:a -af volumedetect -f null -

and will find the absolute maximum of the first audio channel. Take the
max value from the log (something like "max_volume: -18.1 dB"[*]), and
use that value for an additionally inserted "volume" audio filter in
your conversion.

$ ffmpeg -i INPUT [...] -af volume="18.1 dB",otherfilters OUTPUT

You thus only have an additional input analysis step.

[*] Documentation says this will not cause any clipping, though I don't
know what the behaviour is, if the volume is massively different across
channels. I *believe* the maximum is safe to use (while the average is
also an average across channels, by some kind of mixdown).


same question in my searching for a solution to this same message - this
is the first time I've read this.

(I personally find this confusing as well.)


(Assuming I don't run into anything weird when processing different
video formats in the future of course. ;) )  I'm happy, happy, happy
about that! :) :) :)

We like happy people. :-)

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



On 29 Jun 2020, at 15:44, Jim  wrote:

  (While this doesn't equalize the volume or eliminate all volume-related 
inconsistencies, it does make the loudest part of each video the same and is 
the best solution I've found;


I think you would like the loudnorm filter that incorporates ebur-128 
adjustments.
It can run as two pass or one pass (useful for live streaming) and adjusts the 
audio levels to maintain the specified levels.
An example would be -af loudnorm=I=-23:TP=-1.0:LRA=11
This sets the average loudness at -23LUFS (this is pretty standard for UK TV) 
the True Peak value as -1.0dBfs and the loudness range shows the distribution 
of loudness throughout the programme.

LUFS is great because it is based on perceptual loudness and not just sample 
values.

Have fun
Adam



I would like to say that the progress this project has made since I 
initially wrote this script is absolutely amazing!  When I first wrote 
my processing script, I wanted to simply down-sample the audio from n 
channels to stereo and transcode to MP3 - no volume manipulation at 
all.  (The DVR I had at the time would totally freak if I threw audio at 
it with more than 2 channels.)  There were many people complaining about 
it at the time, but no real solutions.  I had to use a 2-step process - 
dump to stereo wave and then encode to MP3 - because ffmpeg refused to 
reduce the number of channels in an audio stream.  (Having to do this 
2-step process combined with my continual frustration with the volume of 
various files is what led me to work out the maximization of the volume 
throughout each file.)  Now, ffmpeg has the ability to do everything 
itself!  I know it's been several years, but still... excellent work 
guys - very impressive. :)


Jim

___
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] Encoding Warnings

2020-06-30 Thread Jim


On 06/29/20 17:39, Carl Eugen Hoyos wrote:

Interesting that this warning is not present in the windows version of
ffmpeg yet is on Linux.  Any idea why that would be?  Even more
You do realize that FFmpeg offers neither a "windows version" nor
a "Linux" version but only source code?

I absolutely do understand that Carl.  I am sorry - should have phrased 
it differently.  'Windows version' = the older version that I had 
running on the computer that recently died which ran the windows xp 
professional operating system, the full version of which was reported in 
my original post:


ffmpeg version N-78758-g5156578 Copyright (c) 2000-2016 the FFmpeg developers
built with gcc 5.3.0 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads
--enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r
--enable-gnutls --enable-iconv --enable-libass --enable-libbluray
--enable-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
--enable-libopus
--enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex
--enable-libtheora --enable-libtwolame --enable-libvidstab
--enable-libvo-amrwbenc
--enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp
--enable-libx264
--enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg
--enable-lzma
--enable-decklink --enable-zlib
libavutil 55. 19.100 / 55. 19.100
libavcodec 57. 27.100 / 57. 27.100
libavformat 57. 26.100 / 57. 26.100
libavdevice 57. 0.101 / 57. 0.101
libavfilter 6. 37.100 / 6. 37.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
libpostproc 54. 0.100 / 54. 0.100



When I said 'Linux version', I was referring to the newer version I am 
running on the Linux machine:


ffmpeg version 4.3-statichttps://johnvansickle.com/ffmpeg/   Copyright (c)
2000-2020 the FFmpeg developers
  built with gcc 8 (Debian 8.3.0-6)
  configuration: --enable-gpl --enable-version3 --enable-static
--disable-debug --disable-ffplay --disable-indev=sndio
--disable-outdev=sndio --cc=gcc --enable-fontconfig --enable-frei0r
--enable-gnutls --enable-gmp --enable-libgme --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-libsrt --enable-libvorbis
--enable-libopus --enable-libtheora --enable-libvidstab
--enable-libvo-amrwbenc --enable-libvpx --enable-libwebp
--enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d
--enable-libxvid --enable-libzvbi --enable-libzimg
  libavutil  56. 51.100 / 56. 51.100
  libavcodec 58. 91.100 / 58. 91.100
  libavformat58. 45.100 / 58. 45.100
  libavdevice58. 10.100 / 58. 10.100
  libavfilter 7. 85.100 /  7. 85.100
  libswscale  5.  7.100 /  5.  7.100
  libswresample   3.  7.100 /  3.  7.100
  libpostproc55.  7.100 / 55.  7.100



What I should have said was: "Interesting that this warning is not 
present in ffmpeg version N-78758-g5156578 running on a windows xp 
operating system yet is on ffmpeg version 4.3-static running on Ubuntu 
Linux 20.04, each with the above reported compilation options & versions 
of the related libraries, when operating on identical files."  I 
apologize - did not realize that using shorthand as I did would cause 
confusion.


I've no idea how N-78758-g5156578 compares with 4.3-static as far as age 
goes, other than it's older because I've been running it for years.  
(And this is assuming it's not something to do with the underlying 
operating system and not ffmpeg itself.)  I am curious as to why the 
older version doesn't issue a warning that the newer version does, but 
it's not important either.


Jim
___
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] Encoding Warnings

2020-06-29 Thread adam smith via ffmpeg-user


> On 29 Jun 2020, at 15:44, Jim  wrote:
> 
>  (While this doesn't equalize the volume or eliminate all volume-related 
> inconsistencies, it does make the loudest part of each video the same and is 
> the best solution I've found; 

I think you would like the loudnorm filter that incorporates ebur-128 
adjustments.
It can run as two pass or one pass (useful for live streaming) and adjusts the 
audio levels to maintain the specified levels.
An example would be -af loudnorm=I=-23:TP=-1.0:LRA=11
This sets the average loudness at -23LUFS (this is pretty standard for UK TV) 
the True Peak value as -1.0dBfs and the loudness range shows the distribution 
of loudness throughout the programme.

LUFS is great because it is based on perceptual loudness and not just sample 
values.

Have fun
Adam
___
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] Encoding Warnings

2020-06-29 Thread Carl Eugen Hoyos
Am Mo., 29. Juni 2020 um 16:44 Uhr schrieb Jim :

> >> The two lines that are concerning to me are:
> >>
> >>   'Guessed Channel Layout for Input Stream #1.0 : stereo'
> >>
> >> Of course it's stereo - I jump dumped it to a 2-channel wave in the step 2!
> >> :)
> >>   I'm guessing that I can safely ignore this one
> >
> > Obviously.
> > (The wav standard does not require writing the channel layout for some
> > mono and stereo files and we don't do it to maintain compatibility with
> > ancient software that fails if the information is present.)
>
> Interesting that this warning is not present in the windows version of
> ffmpeg yet is on Linux.  Any idea why that would be?  Even more

You do realize that FFmpeg offers neither a "windows version" nor
a "Linux" version but only source code?

> interesting is your explanation... out of curiosity, what ancient
> software are you referring to?  (Not really important - just curious.)

I wanted to answer "I don't remember" but I just realized that the
Home Theatre System "Sony DAV-DZ340K" is probably among
them.

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] Encoding Warnings

2020-06-29 Thread Moritz Barsnick
On Mon, Jun 29, 2020 at 17:18:51 +0200, Moritz Barsnick wrote:
> $ ffmpeg -i INPUT -map 0:a -af volumedetect -f null -
>
> and will find the absolute maximum of the first audio channel.

I meant: of the first audio *stream*. Sorry.

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] Encoding Warnings

2020-06-29 Thread Moritz Barsnick
On Mon, Jun 29, 2020 at 10:44:04 -0400, Jim wrote:
> AFAIK, ffmpeg does not have the ability to analyze the volume of every
> sample throughout an audio file, find the greatest amplitude, calculate
> the adjustment needed to make the loudest part of the file the maximum,

It does.

> and then apply that scaled volume adjustment to the entire file.

This makes this a two-pass operation, which your external tool probably
also does. ffmpeg can analyze first:

$ ffmpeg -i INPUT -map 0:a -af volumedetect -f null -

and will find the absolute maximum of the first audio channel. Take the
max value from the log (something like "max_volume: -18.1 dB"[*]), and
use that value for an additionally inserted "volume" audio filter in
your conversion.

$ ffmpeg -i INPUT [...] -af volume="18.1 dB",otherfilters OUTPUT

You thus only have an additional input analysis step.

[*] Documentation says this will not cause any clipping, though I don't
know what the behaviour is, if the volume is massively different across
channels. I *believe* the maximum is safe to use (while the average is
also an average across channels, by some kind of mixdown).

> same question in my searching for a solution to this same message - this
> is the first time I've read this.

(I personally find this confusing as well.)

> (Assuming I don't run into anything weird when processing different
> video formats in the future of course. ;) )  I'm happy, happy, happy
> about that! :) :) :)

We like happy people. :-)

Cheers,
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] Encoding Warnings

2020-06-29 Thread Jim

Hi Carl

On 06/27/20 06:11, Carl Eugen Hoyos wrote:

Am Fr., 26. Juni 2020 um 21:56 Uhr schrieb Ruler2112 :


Step 3: Standardize Volume
Not performed by ffmpeg

I am curious: Why?

[...]


AFAIK, ffmpeg does not have the ability to analyze the volume of every 
sample throughout an audio file, find the greatest amplitude, calculate 
the adjustment needed to make the loudest part of the file the maximum, 
and then apply that scaled volume adjustment to the entire file.  (While 
this doesn't equalize the volume or eliminate all volume-related 
inconsistencies, it does make the loudest part of each video the same 
and is the best solution I've found; I don't have to re-adjust my volume 
when playing ~95% of the files run through this script.)  I've never 
seen anything about this in the documentation & frankly, it seems like 
it's something esoteric enough to be out of scope for the project.  Am I 
wrong in this regard?




The two lines that are concerning to me are:

  'Guessed Channel Layout for Input Stream #1.0 : stereo'

Of course it's stereo - I jump dumped it to a 2-channel wave in the step 2!
:)
  I'm guessing that I can safely ignore this one

Obviously.
(The wav standard does not require writing the channel layout for some
mono and stereo files and we don't do it to maintain compatibility with
ancient software that fails if the information is present.)


Interesting that this warning is not present in the windows version of 
ffmpeg yet is on Linux.  Any idea why that would be?  Even more 
interesting is your explanation... out of curiosity, what ancient 
software are you referring to?  (Not really important - just curious.)




'Timestamps are unset in a packet for stream 0. This is deprecated and
will stop working in the future. Fix your code to set the timestamps
properly'

This warning is not meant for you and you cannot fix it.


Huh???  If it's not intended for the user and there's no way for the 
user to fix it, I assume it must be a warning specifically for 
developers.  As such, why would it be printed without having some flag 
turned on to print debug warnings???  Never saw it when using the older 
windows version I was running and have found a LOT of people with the 
same question in my searching for a solution to this same message - this 
is the first time I've read this.


An idea just popped into my head... if someone involved with organizing 
the ffmpeg project reads this, you might want to start an 'error code' 
database where people could copy/paste the error they received and it 
would provide them information like this.  It would certainly lighten 
the volume of repeated questions/problems to the mailing list and other 
forums.  I pride myself on finding & fixing problems myself and only ask 
for help when I see no other choice; I'm glad I gave up on this when I 
did!  A search of the mailing list archives for "timestamps are unset in 
a packet" came back with over 70 hits, and that doesn't include hits 
from all the other different forums I found.  (Hopefully, each of those 
people didn't waste as much time as I did chasing a problem they had no 
hope of fixing.)  I'm sure other errors are even more commonly repeated; 
a database of error messages could help reduce such repetition.  Just an 
idea.




For future questions: Please understand that posting excerpts of the
console output is not acceptable, always post the command line(s)
together with the complete, uncut console output.


The output of the commands was complete except for version & library 
information, which were identical for every command.  Please accept my 
apologies for not repeating the same information every time - I was just 
trying to shorten an already lengthy message by putting the version 
information once and eliminating redundant information throughout the 
rest of the message.


Thank you so much for your response Carl.  The information you provided 
means that my script to reprocess video files on Linux is complete!  
(Assuming I don't run into anything weird when processing different 
video formats in the future of course. ;) )  I'm happy, happy, happy 
about that! :) :) :)


Jim

___
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] Encoding Warnings

2020-06-27 Thread PaulYurt

> On Jun 26, 2020, at 3:56 PM, Ruler2112  wrote:
> 

Guessed Channel Layout for Input Stream #1.0 : stereo

Try:  -guess_layout_max 0 
___
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] Encoding Warnings

2020-06-27 Thread Carl Eugen Hoyos
Am Fr., 26. Juni 2020 um 21:56 Uhr schrieb Ruler2112 :

> Step 3: Standardize Volume
> Not performed by ffmpeg

I am curious: Why?

[...]

> The two lines that are concerning to me are:
>
>  'Guessed Channel Layout for Input Stream #1.0 : stereo'
>
> Of course it's stereo - I jump dumped it to a 2-channel wave in the step 2!
> :)

>  I'm guessing that I can safely ignore this one

Obviously.
(The wav standard does not require writing the channel layout for some
mono and stereo files and we don't do it to maintain compatibility with
ancient software that fails if the information is present.)

> 'Timestamps are unset in a packet for stream 0. This is deprecated and
> will stop working in the future. Fix your code to set the timestamps
> properly'

This warning is not meant for you and you cannot fix it.

For future questions: Please understand that posting excerpts of the
console output is not acceptable, always post the command line(s)
together with the complete, uncut console output.

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".