Re: [FFmpeg-user] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Jim DeLaHunt 

On 2020-10-01 15:37, Mark Filipak (ffmpeg) wrote:


On 2020-10-01 15:30, Jim DeLaHunt wrote:


It is an improvement that you are now stating the context, "MPEG-PS 
binary metadata values". You omitted that context before. But you 
continue to put #2 in the glossary entry, and I continue to be of the 
opinion that the glossary is the wrong place for the content.   The 
details of the table formatting of #2 is a side issue in this 
discussion.


What is #2?



"#1" and "#2" is your notation, in a message I quoted in my reply. You 
elided that quote in your reply. Here it is:


On 2020-10-01 14:13, Mark Filipak (ffmpeg) wrote:


On 10/01/2020 03:21 PM, Jim DeLaHunt wrote:
-snip-
OK, then I think what you have — what you put in your text attachment 
"d-NTSC & d-PAL .txt" in your previous message — is two single-line 
glossary entries, conjoined with entries from a table mapping H.262 
Metadata Values to video types d-NTSC and d-PAL.


Well, that deserves an answer. There are two parts to each glossary 
entry: 1, A simple statement of what a thing is, and 2, a 
"distinguished by" identification so that readers can identify the thing. 


So:

"#1" is "A simple statement of what a thing is", and
"#2" is "a 'distinguished by' identification so that readers can 
identify the thing".


  —Jim DeLaHunt

___
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] Glossary: Nyquist

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 07:43 PM, Anatoly wrote:

On Wed, 30 Sep 2020 19:21:59 -0400
"Mark Filipak (ffmpeg)"  wrote:


Nyquist [adjective]: 1, Reference to the Nyquist-Shannon sampling
theorem. 2, The principle [1] that, to most faithfully reproduce an
image at a given digital display's resolution, the samples must be
made at or above twice the display's resolution, both horizontally
& vertically [2].

Sorry, but this is wrong.
from
https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem
"If a function x(t) contains no frequencies higher than B hertz, it is
completely determined by giving its ordinates at a series of points
spaced 1/(2B) seconds apart.
A sufficient sample-rate is therefore anything larger 2B samples per
second."
Let's say we have 640 horisontal dots (pixels) per line in NTSC system.

-snip-
Yes, yes, of course. You are correct, but this is different.

The source is not an NTSC analog signal. The source is analog streams of photons striking a CCD 
imager array, frame by frame, and applies to the image regardless whether the image is moving or 
stationary, and regardless of exposure time (which affects brightness, not resolution). The source 
is a 2-dimensional, lighted field of view in a camera or film scanner transferring light energy to 
produce charge in photo transistors over a spacial area. It's not temporal as is the case when 
sampling a changing analog voltage.


When sampling an analog voltage, resolution is the ability to resolve voltage value within a certain 
period of time (i.e. within a given channel bandwidth). When sampling a visual field of view 
however, resolution is the ability to resolve stationary edges that vary spacially, going from light 
to dark or dark to light. It's the same gaussian energy transfer issue (i.e. that transferring 
energy requires time) with the same signal-to-noise issues and the same handy half-power shorthand, 
but it applies to ... wait for it ... human eyes! Human eyes resolve edges only so good, even 
totally black abutting totally white. There is nothing you can do about that, and staring at the 
edge doesn't bring it into higher resolution. However, if the image source itself has fuzzy edges 
because it was sampled at lower than Nyquist, then the result in our brains is a double gaussian, 
the first from the CCD and the second from our eyes. It's that double gaussian that is avoided by 
spacially sampling at higher than 2x the display resolution.


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] Glossary: Nyquist

2020-10-01 Thread Anatoly 
On Wed, 30 Sep 2020 19:21:59 -0400
"Mark Filipak (ffmpeg)"  wrote:

> Nyquist [adjective]: 1, Reference to the Nyquist-Shannon sampling
>theorem. 2, The principle [1] that, to most faithfully reproduce an
>image at a given digital display's resolution, the samples must be
>made at or above twice the display's resolution, both horizontally
> & vertically [2].
Sorry, but this is wrong.
from
https://en.wikipedia.org/wiki/Nyquist%E2%80%93Shannon_sampling_theorem
"If a function x(t) contains no frequencies higher than B hertz, it is
completely determined by giving its ordinates at a series of points
spaced 1/(2B) seconds apart.
A sufficient sample-rate is therefore anything larger 2B samples per
second."
Let's say we have 640 horisontal dots (pixels) per line in NTSC system.
So imagine NTSC analogue (CRT) camera that shots image of thin
alternating black and white vertical stripes. Let say there is 320
white and 320 black stripes, 640 stripes total. This picture produces
maximum possible frequency in analogue video signal.
One TV line is 64uS. Blanking interval is 12uS. Visible line is
64-12=52uS. This interval in our case is filled with square (ideally)
wave. So what is period of this wave? It is of two of those vertical
stripes. Onle line is black (negative half-wave) and one white (positive
half-wave). So what is frequency of that signal?
1/(52*10^-6)*640/2=6153846Hz or 6.15Mhz and this is our B
(Real analogue B/G TV system has slightly lower bandwidth)
According to Nyquist-Shannon we must sample at 2B or 12.3Mhz.
But what is 2B? It is one sample per one vertical stripe (black or
white), or one image dot (pixel).
640 dots per line we want to reproduce = 640 samples per line we must
take
So it is one sample per pixel.

___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 2020-10-01 14:49, Mark Filipak (ffmpeg) wrote:

On 10/01/2020 05:13 PM, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 03:21 PM, Jim DeLaHunt wrote >> OK, then I think what you have — what you put in 
your text attachment "d-NTSC & d-PAL .txt" in
your previous message — is two single-line glossary entries, conjoined with entries from a table 
mapping H.262 Metadata Values to video types d-NTSC and d-PAL.

-snip-

I'll try again.


How's this look, Jim? Clear? Or muddled?

d-NTSC [noun]: The digital equivalent of NTSC. d-NTSC is distinguished
  by a frame having all 8, MPEG-PS binary metadata values below.
   'aspect_ratio_information' = 0010  [1]
    'frame_rate_code' = 0100  [1]
[… snip …]



It is an improvement that you are now stating the context, "MPEG-PS binary metadata values". You 
omitted that context before. But you continue to put #2 in the glossary entry, and I continue to be 
of the opinion that the glossary is the wrong place for the content.   The details of the table 
formatting of #2 is a side issue in this discussion.


What is #2?


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] Is it possible to extract DVD angles from VOB files with ffmpeg?

2020-10-01 Thread Adam Kessel 

Is it possible to select/extract individual angles from a VOB file?

I found an 8-year-old thread suggesting at least at that time it wasn't 
possible 
https://lists.ffmpeg.org/pipermail/ffmpeg-user/2012-November/011665.html


There appears to be an "-angle" option but as best I can tell that only 
applies to BluRay playlists.


If ffmpeg can't extract angles, can anyone suggest a currently 
maintained tool that does?


The closest I've found is tccat from the transcode package which does 
exactly this, but transcode is no longer maintained and doesn't build in 
recent Linux distribution releases. Getting it to compile or run on a 
modern distro would require some patching for updated libraries. When 
running under an old version, it's as simple as "tccat -i file.vob -T 
1,-1,1 > file_angle_1.vob" to extract angle 1 from file.vob.


If this isn't supported in ffmpeg, might it be possible to implement 
based on the transcode/tccat source code?


___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Jim DeLaHunt 

On 2020-10-01 14:13, Mark Filipak (ffmpeg) wrote:


On 10/01/2020 03:21 PM, Jim DeLaHunt wrote:
-snip-
OK, then I think what you have — what you put in your text attachment 
"d-NTSC & d-PAL .txt" in your previous message — is two single-line 
glossary entries, conjoined with entries from a table mapping H.262 
Metadata Values to video types d-NTSC and d-PAL.


Well, that deserves an answer. There are two parts to each glossary 
entry: 1, A simple statement of what a thing is, and 2, a 
"distinguished by" identification so that readers can identify the thing. 


You are making an author's choice to put #2 in the glossary. I maintain 
that #2 is something different, and does not belong in a glossary. In my 
opinion only #1 belongs in the glossary.  #2 belongs in, for example, a 
description of the structures found in MPEG-PS streams according to 
H.262 (or something like that).


You seem to want to combine them. I disagree with this editorial choice, 
but you hold the pen and I don't care to pick it up.



On 2020-10-01 14:49, Mark Filipak (ffmpeg) wrote:

On 10/01/2020 05:13 PM, Mark Filipak (ffmpeg) wrote:
On 10/01/2020 03:21 PM, Jim DeLaHunt wrote >> OK, then I think what 
you have — what you put in your text attachment "d-NTSC & d-PAL .txt" in
your previous message — is two single-line glossary entries, 
conjoined with entries from a table mapping H.262 Metadata Values to 
video types d-NTSC and d-PAL.

-snip-

I'll try again.


How's this look, Jim? Clear? Or muddled?

d-NTSC [noun]: The digital equivalent of NTSC. d-NTSC is distinguished
  by a frame having all 8, MPEG-PS binary metadata values below.
   'aspect_ratio_information' = 0010  [1]
    'frame_rate_code' = 0100  [1]
[… snip …]



It is an improvement that you are now stating the context, "MPEG-PS 
binary metadata values". You omitted that context before. But you 
continue to put #2 in the glossary entry, and I continue to be of the 
opinion that the glossary is the wrong place for the content.   The 
details of the table formatting of #2 is a side issue in this discussion.


  —Jim DeLaHunt


___
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] Correct conversion of yuvj420p?

2020-10-01 Thread Christian Ebert 

* Peter B. on Thursday, October 01, 2020 at 14:16:02 +0200:

On 29.09.20 09:56, Christian Ebert wrote:

How about doing quick diagnosis with ffprobe before you start,
something like:

ffprobe -v error \
-print_format default=noprint_wrappers=1:nokey=1 \
-select_streams V -show_entries stream=pix_fmt

and make the command depend on the result?


Thanks for the suggestion, but that actually is what I'm doing right
now - yet it means to treat parts of the batches with different
conditions/recipes.


I would be very surprised if you could use the same command on
thousands of videos.


Additionally, in that concrete situation, the source videos (several
thousand...) are stored on an S3-type object based storage (non-Amazon
dialect). So used Mediainfo to avoid having to pull several hundred
Terabyte of videos just to get their tech-MD.


What's wrong with that? But then again I don't understand: You
want to process _all_ the thousands of files, so you need them
anyway?


And Mediainfo cannot tell me what FFmpeg considers yuvj420p, because...


If you can run Mediainfo on them (remotely?), I'd be surprised if
you couldn't run ffprobe on them - and if you haven't
built/installed ffprobe, even parsing `ffprobe -i input` lets you
detect the pix_fmt.


Even if it wasn't for the "S3-extra-fun", I'm running into this issue
every now and then in different video collections - and every "if -
then - else" adds extra points of failure (and work).


I would think if - then - else is the way to _avoid_ points of
failure, but most likely I don't understand you setup and/or
intent, sorry.

Good luck.

--
LAST SHIP HOME  --->> https://lastshiphome.de
Official Selection  DOK.fest München 2018
German Ocean Film AwardCineMare Kiel 2019
Best Documentary Feature   Wales International Film Festival 2020
___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 05:13 PM, Mark Filipak (ffmpeg) wrote:

On 10/01/2020 03:21 PM, Jim DeLaHunt wrote >> OK, then I think what you have — what you put 
in your text attachment "d-NTSC & d-PAL .txt" in
your previous message — is two single-line glossary entries, conjoined with entries from a table 
mapping H.262 Metadata Values to video types d-NTSC and d-PAL.

-snip-

I'll try again.


How's this look, Jim? Clear? Or muddled?

d-NTSC [noun]: The digital equivalent of NTSC. d-NTSC is distinguished
  by a frame having all 8, MPEG-PS binary metadata values below.
   'aspect_ratio_information' = 0010  [1]
'frame_rate_code' = 0100  [1]
  'horizontal_size_value' = 0010 1101 [1]
'vertical_size_value' = 0001 1110 [1]
  'horizontal_size_extension' = 00[2]
'vertical_size_extension' = 00[2]
   'progressive_sequence' = 0 [2]
  'progressive_frame' = 0 [3]
  [1] From sequence_header
  [2] From sequence_extension
  [3] From picture_coding_extension

--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] V360 stabilization

2020-10-01 Thread Michael Koch 

Am 01.10.2020 um 22:11 schrieb Paul B Mahol:

On Tue, Sep 29, 2020 at 10:54:54PM +0200, Michael Koch wrote:

Hello all,

I've programmed a C# workaround for stabilization of 360° videos. The
procedure is as follows:

1. FFmpeg: From each frame of the equirectangular input video, extract two
small images which are 90° apart in the input video. I call them A and B
images.

2. C# code: Analyze the x and y image shift from subsequent A and B images.
Calculate how the equirectangular frames must be rotated (yaw, pitch, roll)
to compensate the image shifts. This part wasn't easy. Two rotation matrices
and one matrix multiplication are required. Write the results to a *.cmd
file.

3. FFmpeg: Read the *.cmd file and apply the rotations with the v360 filter.
The output video is stabilized.

For details and source code please have a look at chapter 2.78 in my book:
http://www.astro-electronic.de/FFmpeg_Book.pdf

If anyone wants to implement this in FFmpeg, please feel free to do it.

Better upload DNG files that do not decode with FFmpeg.


In this message
http://ffmpeg.org/pipermail/ffmpeg-user/2020-August/049681.html
you find a link to many DNG images which FFmpeg can't decode correctly. 
There is no error message, but the result is much too dark with low 
saturation.


I did convert a RAW image from a Canon 6D to DNG with Adobe DNG 
Converter V12.4. FFmpeg is unable to decode this DNG image. See this 
message for details:

http://ffmpeg.org/pipermail/ffmpeg-user/2020-August/049738.html
You can download the DNG image here (I will delete it from my webspace 
in a few days):

www.astro-electronic.de/IMG_3459.dng

I did also try a RAW image from a Canon 5D-MK4 with the same negative 
result.


A friend gave me a DNG image that was written by his Pentax K5 camera. 
Same negative result.


Summary: I did try DNG images from 4 different sources and in 4 of 4 
cases FFmpeg failed.


Michael


___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 03:21 PM, Jim DeLaHunt wrote:
-snip-
OK, then I think what you have — what you put in your text attachment "d-NTSC & d-PAL .txt" in your 
previous message — is two single-line glossary entries, conjoined with entries from a table mapping 
H.262 Metadata Values to video types d-NTSC and d-PAL.


Well, that deserves an answer. There are two parts to each glossary entry: 1, A simple statement of 
what a thing is, and 2, a "distinguished by" identification so that readers can identify the thing. 
The table is the "distinguished by" part. I formatted it as a table to make it easy, or at least so 
I thought! :-)


For example, d-NTSC is distinguished via MPEG-PS binary metadata:
'progressive_sequence' == 0 & 'progressive_frame' == 0 & 'aspect_ratio_information' == 0010 & 
'frame_rate_code' == 0100 & 'horizontal_size_value' == 0010 1101  & 'horizontal_size_extension' 
== 00 & 'vertical_size_value' == 0001 1110  & 'vertical_size_extension' == 00.


That's the logic. Putting the table into a different glossary entry wouldn't work, but obviously, 
the way I'm doing it now is a FAIL.


I'll try again.

--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] V360 stabilization

2020-10-01 Thread Paul B Mahol 
On Tue, Sep 29, 2020 at 10:54:54PM +0200, Michael Koch wrote:
> Hello all,
> 
> I've programmed a C# workaround for stabilization of 360° videos. The
> procedure is as follows:
> 
> 1. FFmpeg: From each frame of the equirectangular input video, extract two
> small images which are 90° apart in the input video. I call them A and B
> images.
> 
> 2. C# code: Analyze the x and y image shift from subsequent A and B images.
> Calculate how the equirectangular frames must be rotated (yaw, pitch, roll)
> to compensate the image shifts. This part wasn't easy. Two rotation matrices
> and one matrix multiplication are required. Write the results to a *.cmd
> file.
> 
> 3. FFmpeg: Read the *.cmd file and apply the rotations with the v360 filter.
> The output video is stabilized.
> 
> For details and source code please have a look at chapter 2.78 in my book:
> http://www.astro-electronic.de/FFmpeg_Book.pdf
> 
> If anyone wants to implement this in FFmpeg, please feel free to do it.

Better upload DNG files that do not decode with FFmpeg.
___
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] Encrypted SRT Does Not Work

2020-10-01 Thread andrei ka 
>
> > I may be wrong, but try to put double quote on server url in your script
> file.
>

+  i may be wrong aslo, but it may be easier to manage line drops (which
may always happen) if
you encode w/ ffmpeg to multicast and next read that multicast and srt send
it with srt-live-transmit (and do the opposite on receiver side),
these srt scripts do automatic reconnects, afaik ffmpeg just exits...


___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Jim DeLaHunt 

On 2020-10-01 10:50, Mark Filipak (ffmpeg) wrote:


On 10/01/2020 01:03 PM, Jim DeLaHunt wrote:

On 2020-10-01 06:27, Mark Filipak (ffmpeg) wrote:


On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:

On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:


Continuing with relatively non controversial entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
  binary metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  480 rows: 'vertical_size_value' = 0001 1110 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  30/1.001 FPS: 'frame_rate_code' = 0100
  'progressive_sequence' = 0 & 'progressive_frame' = 0

d-PAL [noun]: 1, The digital equivalent of PAL distinguished by 
binary

  metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  576 rows: 'vertical_size_value' = 0010 0100 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  25 FPS: 'frame_rate_code' = 0011
  'progressive_sequence' = 0 & 'progressive_frame' = 0 



It seems to me that these are no longer glossary entries — or, only 
the first line of each is a glossary entry. ...


…The sentence is a statement followed by a list of metadata that 
distinguishes the subject...

Do you have any suggestions? Should I just forget this glossary idea?



What makes sense to me is a glossary which includes the entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC

d-PAL [noun]: 1, The digital equivalent of PAL

Then a table of XYZ metadata entries which have been found in the wild:


Actually, not in the wild. They are from H.262.



OK, then I think what you have — what you put in your text attachment 
"d-NTSC & d-PAL .txt" in your previous message — is two single-line 
glossary entries, conjoined with entries from a table mapping H.262 
Metadata Values to video types d-NTSC and d-PAL.


I think it is clearer to have the mapping from H.262 Metadata Values in 
a separate structure from the glossary. You seem to want to combine 
them. I disagree with this editorial choice, but you hold the pen and I 
don't care to pick it up.



[Display the following table with fixed-width font]


Actually, Jim, what you sent is not in fixed-width font. :-)



I won't try to explain the vagaries of how my client formats messages, 
how the list reformats them, and how your client displays them. I think 
it's more accurate to say that what I sent was plain text, which looks 
better displayed in a fixed-width font, but maybe your client chose to 
display it using a variable-width font.


Plain-text emails are only good for certain kinds of content. They can 
represent some table layouts, but not others. This thread appears to be 
taking tables beyond what plain-text emails can handle.


   —Jim DeLaHunt



___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 02:01 PM, Phil Rhodes via ffmpeg-user wrote:

  I don't know who's in charge of this glossary project, but can I please 
propose something on the difference between colourspace, subsampling and 
luminance encoding. And all the other things people constantly confuse.


No one's in charge. I've taken the initiative to begin (and conduct and finish and whatever it 
takes) the effort [1]. Based on the evidence, I'm not alone, but no one's in charge.


Regarding your concerns, Phil, I believe I have a lock on subsampling & luminance encoding (or, at 
least, the structures, but not the processes) and I would post glossary entries if I could, but 
they're very large and have large texie pix diagrams and are formatted to 148 columns of text and 
therefore don't fit into email format, and I would probably incur the ire of the list maintainers if 
I were to attach such large files. Sorry,


Regarding colorspace, such documentation exists, at least in name -- literally, names only to the 
best of my knowledge -- but the details of the data structures are, at best: buried in code 
algorithms without explicit structural documentation, or, at worst: completely lacking and subject 
to trial-and-error hacking, even by the developers.


[1] There are 3 ways to take leadership: #1, be appointed by some authority, or #2, be elected by 
some constituency, or #3, start leading. I have tried #1 and #2 and have not been successful due to 
wrangling, so I am pursuing route #3. If that rankles some folks, the fault is entirely mine.


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Phil Rhodes via ffmpeg-user 
 I don't know who's in charge of this glossary project, but can I please 
propose something on the difference between colourspace, subsampling and 
luminance encoding. And all the other things people constantly confuse.
P  
___
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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 01:03 PM, Jim DeLaHunt wrote:

On 2020-10-01 06:27, Mark Filipak (ffmpeg) wrote:


On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:

On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:


Continuing with relatively non controversial entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
  binary metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  480 rows: 'vertical_size_value' = 0001 1110 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  30/1.001 FPS: 'frame_rate_code' = 0100
  'progressive_sequence' = 0 & 'progressive_frame' = 0

d-PAL [noun]: 1, The digital equivalent of PAL distinguished by binary
  metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  576 rows: 'vertical_size_value' = 0010 0100 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  25 FPS: 'frame_rate_code' = 0011
  'progressive_sequence' = 0 & 'progressive_frame' = 0 



It seems to me that these are no longer glossary entries — or, only the first line of each is a 
glossary entry. ...


…The sentence is a statement followed by a list of metadata that distinguishes 
the subject...
Do you have any suggestions? Should I just forget this glossary idea?



What makes sense to me is a glossary which includes the entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC

d-PAL [noun]: 1, The digital equivalent of PAL

Then a table of XYZ metadata entries which have been found in the wild:


Actually, not in the wild. They are from H.262.


[Display the following table with fixed-width font]


Actually, Jim, what you sent is not in fixed-width font. :-)
So, you favor a formal table? I don't, but I guess that could go without 
saying, eh?
I format in plain text at 148 columns. I've found 70 columns to be too restricting and promotes 
crypticism (...is there such a word?). Personally, I don't think formal tables are needed, but if 
you do, then I'll make a formal table. But first, take a look at the current version, attached.


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
d-NTSC [noun]: The digital equivalent of NTSC. d-NTSC is distinguished via 
MPEG-PS binary metadata:
  'progressive_sequence' = 0  + 'progressive_frame' = 0 
 ...is a scan frame
  'aspect_ratio_information' = 0010   +   'frame_rate_code' = 
0100   ...4:3 DAR + 30/1.001 FPS
 'horizontal_size_value' = 0010 1101  + 'horizontal_size_extension' = 
00 ...720 samples/row
   'vertical_size_value' = 0001 1110  +   'vertical_size_extension' = 
00 ...480 rows

d-PAL [noun]: The digital equivalent of PAL. d-PAL is distinguished via MPEG-PS 
binary metadata:
  'progressive_sequence' = 0  + 'progressive_frame' = 0 
 ...is a scan frame
  'aspect_ratio_information' = 0010   +   'frame_rate_code' = 
0011   ...4:3 DAR + 25 FPS
 'horizontal_size_value' = 0010 1101  + 'horizontal_size_extension' = 
00 ...720 samples/row
   'vertical_size_value' = 0010 0100  +   'vertical_size_extension' = 
00 ...576 rows
___
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] Glossary: Nyquist

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 12:16 PM, Greg Oliver wrote:

On Wed, Sep 30, 2020 at 6:25 PM Mark Filipak (ffmpeg) 
wrote:

-snip-

Mark,

Normally I would absolutely defend your queries as they are technical and
lower level, but I would almost have to side with Bouke from post
(
bwdif filter question
)

You are trying to get free editing for your book now.


I have no book. I intend to have no book. I'm a retired engineer and don't need book proceeds. I 
intend to give everything to the ffmpeg project (and anyone else who finds it useful) for free and 
unconditionally. It is all public domain. By simply posting it, I'm making it all public domain.



 I do not agree with
that..  There are many good contributors and inquisitors (you included),
but (IMHO) you cannot solicit things like this that are grammatical rather
than technical.   I think a lot of the developers are also in the same boat
as you (sometimes) try to re-define things that are common language (even
if not accurate technically).


I'm working on a glossary, not a dictionary. I have no desire to re-define 
common language.


eg - your definition if interlaced versus interweaved..  No matter if you
are right or wrong, the concept and understanding of a majority will
prevail - no exceptions.


We shall see, eh? If there's power in (better?) terms, then they will prevail. If not, then they 
will die. For what it's worth, I've never written the word "interweaved".


Certainly, to cite just one realm, the current nomenclature is quite confused regarding pre-decoding 
streams v. post-decoding processing. The H.xxx folks leave interpretation to "context". But relying 
on context relies on understanding, and it is understanding that is lacking. Which would you shoot 
first? The chicken or the egg? -- Buy this concept or I shoot the dog.



Please (for me at least) keep your posts here related to ffmpeg and not
trying to change the nomenclature of what exists.  We are all using the
same software, so whatever the software uses for terminology (as this list
is exactly related to), please do not interfere with that.


My experience is that the entire video field, not just ffmpeg, is grossly underspecified. That hurts 
users and developers -- a lot of time is wasted and a lot of feelings are hurt. Based on my 47 years 
of engineering experience, the first things that need to be fixed is to unequivocally and 
unambiguously define all the terms & structures. To me, that's the low hanging fruit. Then comes the 
processes, but once the terms & structures are nailed down, I think we'll all discover that 
documenting the processes will be a snap.



Take that up directly with developers and let them sort it out.


I would/could never stop them from contributing. But it should be acknowledged that the developers 
have a developer's perspective. The developer view is like looking out at the world through a pinhole.



On a side note - I have yet seen one of your definitions of a technology
been held up when a developer chimes in - no hard feelings, just that
industry terminology is hard to trump :)


Oh, believe me, you've seen nothing yet. I ponder terminology and anguish over every word choice for 
a long, long time. I doggedly seek to manufacture terms that are intuitive and acceptable to all.


The developers have their opinions and have not been shy sharing it. To be honest, I don't see how 
this (my glossary) can even be an issue. I'm an ffmpeg user and so long as I'm courteous and focus 
on video issues, the developers should welcome me. If not, then I should be removed from the 
ffmpeg-user list.


Give this journey the time that it deserves. We all have the same destination in sight, just 
differing paths to get there. Perhaps there exists no single path, eh?


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Marco Mircoli 
Hello, this is the final script line, and it works perfectly.
 $shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 0:a:0 -af
highpass=50,loudnorm=I=-16 -map_metadata -1 -metadata Artist='Agency -
VISIT HTTPS://WWW.agency.EU' -metadata Title='Title' -metadata
Publisher='agency' -metadata Language=italian -b:a ".$convert_speed."k
$audio_output_mp3 2>&1");

Now, I would like to insert an album artwork in the mp3.
Is it possible?
Thanks.
S.


Il giorno gio 1 ott 2020 alle ore 17:45 Marco Mircoli 
ha scritto:

> Hello, tried but doesn't work correctly:-(
> $shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 0:a:0 -af
> highpass=700,loudnorm=I=-24 -map_metadata -1 -metadata Artist=Someone
> -metadata Title=Title -metadata author_url=http://example.com/ -b:a
> ".$convert_speed."k $audio_output_mp3 2>&1");
>
> Tried with 700 hz
> the result is very low in volume
> it seems that it normalize to -24 and after apply the highpass
>
> another point I can't fix is the metadata, they works except for the
> author:url.
> Maybe am I wrong with syntax?
>
> Thanks in advance.
>
>
>
> Il giorno gio 1 ott 2020 alle ore 15:40 Marco Mircoli <
> nuvolab...@gmail.com> ha scritto:
>
>> Thanks a lot!
>>
>> Il giorno gio 1 ott 2020 alle ore 14:17 Michael Koch <
>> astroelectro...@t-online.de> ha scritto:
>>
>>> Am 01.10.2020 um 14:06 schrieb Michael Koch:
>>> > Am 01.10.2020 um 13:25 schrieb Marco Mircoli:
>>> >> Hello',
>>> >>  I'm a newbie.
>>> >> Just bought a php script that use ffmpeg.
>>> >> it converts to mp3/96Kbps all media uploaded in a unique format.
>>> >> this is the line, and now it normalizes to R128 (thanks Moritz)
>>> >>
>>> >> $shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map
>>> >> 0:a:0 -af
>>> >> loudnorm -b:a 96k $audio_output_mp3 2>&1");
>>> >>
>>> >> I'm wondering if it is possible to include a simple hi-pass filter
>>> >> (highest
>>> >> db per octave @ 70Hz)
>>> >
>>> > add  highpass=70,before  loudnorm
>>> >
>>> > This filter attenuated 6dB per octave. If you need higher attenuation,
>>> > you can use several highpass filters, for example
>>> > highpass=70,highpass=70,highpass=70,loudnorm
>>>
>>> Correction: The filter has 12dB per octave.
>>>
>>> Michael
>>>
>>> ___
>>> 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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Jim DeLaHunt 

On 2020-10-01 06:27, Mark Filipak (ffmpeg) wrote:


On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:

On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:


Continuing with relatively non controversial entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
  binary metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  480 rows: 'vertical_size_value' = 0001 1110 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  30/1.001 FPS: 'frame_rate_code' = 0100
  'progressive_sequence' = 0 & 'progressive_frame' = 0

d-PAL [noun]: 1, The digital equivalent of PAL distinguished by binary
  metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  576 rows: 'vertical_size_value' = 0010 0100 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  25 FPS: 'frame_rate_code' = 0011
  'progressive_sequence' = 0 & 'progressive_frame' = 0 



It seems to me that these are no longer glossary entries — or, only 
the first line of each is a glossary entry. ...


…The sentence is a statement followed by a list of metadata that 
distinguishes the subject...

Do you have any suggestions? Should I just forget this glossary idea?



What makes sense to me is a glossary which includes the entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC

d-PAL [noun]: 1, The digital equivalent of PAL

Then a table of XYZ metadata entries which have been found in the wild:

[Display the following table with fixed-width font]

Kind of data   |  Metadata field entries
   |  Metadata key   | Metadata value | Meaning
---+-++
d-NTSC | 'horizontal_size_value' | 0010 1101  | 720 samples/row
   | 'horizontal_size_extension' | 00   |
               | 'vertical_size_value' | 0001 1110  | 480 rows
       | 'vertical_size_extension'   | 00         |
   | 'aspect_ratio_information'  | 0010   | 4:3 DAR
               | 'frame_rate_code' | 0100           | 30/1.001 FPS
               | 'progressive_sequence' | 0              |
   | 'progressive_frame' | 0             |
---+-++
d-PAL      | 'horizontal_size_value' | 0010 1101  | 720 samples/row
   | 'horizontal_size_extension' | 00         |
               | 'vertical_size_value' | 0010 0100  | 576rows
[… etc …]

And, you need to fill in "XYZ", which stands for the context: metadata 
of which format or specification?  Of an MPEG-2 video? Of the ISO file 
corresponding to a DVD? Of something else?


  —Jim DeLaHunt


___
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] Glossary: Nyquist

2020-10-01 Thread Greg Oliver 
On Wed, Sep 30, 2020 at 6:25 PM Mark Filipak (ffmpeg) 
wrote:

> Nyquist [adjective]: 1, Reference to the Nyquist–Shannon sampling
>theorem. 2, The principle [1] that, to most faithfully reproduce an
>image at a given digital display's resolution, the samples must be
>made at or above twice the display's resolution, both horizontally &
>vertically [2].
>[1] The Nyquist principle applies to film sampling and to digital
>cameras, but, provided that resolution is unchanged, not to
>transcoding (because the transcoder inputs are already digital).
>As proved by the improved appearance of SD media made from 2K
>samples, SD mastering prior to the advent of 2K sampling (e.g.
>DVDs mastered before the advent of HD) generally ignored the
>Nyquist principle and were undersampled. HDs sampled at 2K and
>UHDs sampled at 4K are likewise undersampled.
>[2] As a convenience, the Nyquist threshold is currently (in 2020)
>specified solely by horizontal sample count rounded up to whole
>kilo-samples (2K, 4K, 8K).
>  displayNyquist threshold
>UHD 16:9-2160:  3840 x 2160 8K
> 4:3-2160:  2880 x 2160 8K
> HD 16:9-1080:  1920 x 1080 4K
> 4:3-1080:  1440 x 1080 4K
> SD  16:9-576:  1024 x 576  4K
>  4:3-576:   768 x 576  2K
> 16:9-480:   853 x 480  2K
>  4:3-480:   640 x 480  2K



Mark,

Normally I would absolutely defend your queries as they are technical and
lower level, but I would almost have to side with Bouke from post
(
bwdif filter question
)

You are trying to get free editing for your book now.  I do not agree with
that..  There are many good contributors and inquisitors (you included),
but (IMHO) you cannot solicit things like this that are grammatical rather
than technical.   I think a lot of the developers are also in the same boat
as you (sometimes) try to re-define things that are common language (even
if not accurate technically).

eg - your definition if interlaced versus interweaved..  No matter if you
are right or wrong, the concept and understanding of a majority will
prevail - no exceptions.

Please (for me at least) keep your posts here related to ffmpeg and not
trying to change the nomenclature of what exists.  We are all using the
same software, so whatever the software uses for terminology (as this list
is exactly related to), please do not interfere with that.

Take that up directly with developers and let them sort it out.

On a side note - I have yet seen one of your definitions of a technology
been held up when a developer chimes in - no hard feelings, just that
industry terminology is hard to trump :)

-Greg
___
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] Glossary: Nyquist

2020-10-01 Thread Eduardo Alarcón 
El jue., 1 oct. 2020 a las 12:55, Mark Filipak (ffmpeg) ()
escribió:

> On 10/01/2020 11:20 AM, Eduardo Alarcón wrote:
> > El jue., 1 oct. 2020 a las 12:09, Mark Filipak (ffmpeg) (<
> markfili...@bog.us>)
> > escribió:
> >
> >> On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:
> -snip-
> >> Can you suggest better wording? I'd like to see it.
> >
> > Me too, this is not my native language so i can not suggest a better
> wording.
>
> Oh, you are doing fine. Trust me on this, being a native English speaker
> isn't all that it's cracked
> up to be -- note the "cracked up" euphemism. :-)
> I assume you're a native Spanish speaker. I think that Spanish is a very
> sensible and logical
> language. English started out that way but got wrecked by the principle
> that anyone should be
> allowed to do whatever they want.
>
> Yes, spanish speaker, well my name gives it away.

> -snip-
> > I think it should say that undersampling makes it look bad or blurry, ...
>
> Do you think the following -- changed "appearance" to "sharpness" & added
> "from film" in 2 places --
> is improved and satisfies your desires?
>
Yes, that makes more clear what is the importance of using it right.

>
> [1] The Nyquist principle applies to film sampling and to digital cameras,
> but, provided that
>  resolution is unchanged, not to transcoding (because the transcoder
> inputs are already
>  digital). As proved by the improved sharpness of SD media made from
> 2K flim samples, SD
>  mastering prior to the advent of 2K sampling (e.g. DVDs mastered from
> film before the advent
>  of HD) generally ignored the Nyquist principle and were undersampled.
> HDs sampled from film
>  at 2K and UHDs sampled from film at 4K are likewise undersampled.
>
> > Off topic, i find your questions helpful or interesting at least on this
> > list, there are concepts i know and things i don't that i had to look up
>
> Is that "Off topic" in a user list dedicated to video processing? Really?
> Well, whatever the
> opinion, I thank you for your kind words.
>

I meant off topic to this mail.

>
> --
> What if you woke up and found yourself in a police state?
> African-Americans wake up in a police state every day.
> ___
> 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] Glossary: Nyquist

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 11:20 AM, Eduardo Alarcón wrote:

El jue., 1 oct. 2020 a las 12:09, Mark Filipak (ffmpeg) ()
escribió:


On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:

-snip-

Can you suggest better wording? I'd like to see it.


Me too, this is not my native language so i can not suggest a better wording.


Oh, you are doing fine. Trust me on this, being a native English speaker isn't all that it's cracked 
up to be -- note the "cracked up" euphemism. :-)
I assume you're a native Spanish speaker. I think that Spanish is a very sensible and logical 
language. English started out that way but got wrecked by the principle that anyone should be 
allowed to do whatever they want.


-snip-

I think it should say that undersampling makes it look bad or blurry, ...


Do you think the following -- changed "appearance" to "sharpness" & added "from film" in 2 places -- 
is improved and satisfies your desires?


[1] The Nyquist principle applies to film sampling and to digital cameras, but, 
provided that
resolution is unchanged, not to transcoding (because the transcoder inputs 
are already
digital). As proved by the improved sharpness of SD media made from 2K flim 
samples, SD
mastering prior to the advent of 2K sampling (e.g. DVDs mastered from film 
before the advent
of HD) generally ignored the Nyquist principle and were undersampled. HDs 
sampled from film
at 2K and UHDs sampled from film at 4K are likewise undersampled.


Off topic, i find your questions helpful or interesting at least on this
list, there are concepts i know and things i don't that i had to look up


Is that "Off topic" in a user list dedicated to video processing? Really? Well, whatever the 
opinion, I thank you for your kind words.


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Marco Mircoli 
Hello, tried but doesn't work correctly:-(
$shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 0:a:0 -af
highpass=700,loudnorm=I=-24 -map_metadata -1 -metadata Artist=Someone
-metadata Title=Title -metadata author_url=http://example.com/ -b:a
".$convert_speed."k $audio_output_mp3 2>&1");

Tried with 700 hz
the result is very low in volume
it seems that it normalize to -24 and after apply the highpass

another point I can't fix is the metadata, they works except for the
author:url.
Maybe am I wrong with syntax?

Thanks in advance.



Il giorno gio 1 ott 2020 alle ore 15:40 Marco Mircoli 
ha scritto:

> Thanks a lot!
>
> Il giorno gio 1 ott 2020 alle ore 14:17 Michael Koch <
> astroelectro...@t-online.de> ha scritto:
>
>> Am 01.10.2020 um 14:06 schrieb Michael Koch:
>> > Am 01.10.2020 um 13:25 schrieb Marco Mircoli:
>> >> Hello',
>> >>  I'm a newbie.
>> >> Just bought a php script that use ffmpeg.
>> >> it converts to mp3/96Kbps all media uploaded in a unique format.
>> >> this is the line, and now it normalizes to R128 (thanks Moritz)
>> >>
>> >> $shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map
>> >> 0:a:0 -af
>> >> loudnorm -b:a 96k $audio_output_mp3 2>&1");
>> >>
>> >> I'm wondering if it is possible to include a simple hi-pass filter
>> >> (highest
>> >> db per octave @ 70Hz)
>> >
>> > add  highpass=70,before  loudnorm
>> >
>> > This filter attenuated 6dB per octave. If you need higher attenuation,
>> > you can use several highpass filters, for example
>> > highpass=70,highpass=70,highpass=70,loudnorm
>>
>> Correction: The filter has 12dB per octave.
>>
>> Michael
>>
>> ___
>> 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] Glossary: Nyquist

2020-10-01 Thread Eduardo Alarcón 
El jue., 1 oct. 2020 a las 12:09, Mark Filipak (ffmpeg) ()
escribió:

> On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:
> > Mostly the noun/adjective part, the part [1] about SD media and
> mastering,
> > seems to be anecdotal information more than a definition of what is the
> > Nyquist principle, you say that the images are undersampled, but what
> does
> > it mean? what is the impact, the images look blurry?, may be you defined
> > "undersampling" in other part
>
> Thanks for your thoughts. They're important. Yes, I could write more. And,
> Yes, the note is
> anecdotal. I felt that the note introduces the idea that something can be
> undersampled and with a
> concrete example of something that is undersampled so that the concept
> becomes 'real'. Can you
> suggest better wording? I'd like to see it.
>
> Me too, this is not my native language so i can not suggest a better
wording.


> Regarding what undersampling means, it's a common term that can be looked
> up in a general dictionary
> rather than a dedicated glossary. That's just my opinion of course. Where
> do you think the line
> should be drawn?
>
I think it should say that undersampling makes it look bad or blurry, so
that the concept is clear why it has to be that way.
Anyway it all depends on your target audience, if they have to know
concepts before or expect them to know nothing when reading your "manual".
That should define where the line is draw.

Off topic, i find your questions helpful or interesting at least on this
list, there are concepts i know and things i don't that i had to look up

> --
> What if you woke up and found yourself in a police state?
> African-Americans wake up in a police state every day.
> ___
> 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] Glossary: Nyquist

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 10:38 AM, Eduardo Alarcón wrote:

Mostly the noun/adjective part, the part [1] about SD media and mastering,
seems to be anecdotal information more than a definition of what is the
Nyquist principle, you say that the images are undersampled, but what does
it mean? what is the impact, the images look blurry?, may be you defined
"undersampling" in other part


Thanks for your thoughts. They're important. Yes, I could write more. And, Yes, the note is 
anecdotal. I felt that the note introduces the idea that something can be undersampled and with a 
concrete example of something that is undersampled so that the concept becomes 'real'. Can you 
suggest better wording? I'd like to see it.


Regarding what undersampling means, it's a common term that can be looked up in a general dictionary 
rather than a dedicated glossary. That's just my opinion of course. Where do you think the line 
should be drawn?


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] slow motion by changing frame rate from 60 to 30

2020-10-01 Thread Michael Koch 

Am 01.10.2020 um 16:57 schrieb Cristian Secară:

I want to make a short .mp4 clip filmed in 1080p/60 format, then change somehow 
the playing fame rate to 30Hz so that the playing speed becomes twice slower. 
Audio is not important (may be dropped completely).

As far as I know (?), a "simple" frame rate change will try to preserve the 
playing speed, so when changing from 60Hz to 30Hz, it will drop half of the movie.
At the same time, a "simple" slow motion processing will try to keep the 
original frame rate, so in this case it will interpolate the transitions or something, 
while keeping the frame rate still at 60Hz.

What options are available for preserving all frames "as is" and just slowing 
down the playing speed ?


It's described here:
https://trac.ffmpeg.org/wiki/How%20to%20speed%20up%20/%20slow%20down%20a%20video

Michael

___
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] slow motion by changing frame rate from 60 to 30

2020-10-01 Thread Cristian Secară 
I want to make a short .mp4 clip filmed in 1080p/60 format, then change somehow 
the playing fame rate to 30Hz so that the playing speed becomes twice slower. 
Audio is not important (may be dropped completely).

As far as I know (?), a "simple" frame rate change will try to preserve the 
playing speed, so when changing from 60Hz to 30Hz, it will drop half of the 
movie.
At the same time, a "simple" slow motion processing will try to keep the 
original frame rate, so in this case it will interpolate the transitions or 
something, while keeping the frame rate still at 60Hz.

What options are available for preserving all frames "as is" and just slowing 
down the playing speed ?

Cristi

-- 
Cristian Secară
https://www.secarica.ro
___
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] Glossary: Nyquist

2020-10-01 Thread Eduardo Alarcón 
Mostly the noun/adjective part, the part [1] about SD media and mastering,
seems to be anecdotal information more than a definition of what is the
Nyquist principle, you say that the images are undersampled, but what does
it mean? what is the impact, the images look blurry?, may be you defined
"undersampling" in other part


El jue., 1 oct. 2020 a las 11:18, Mark Filipak (ffmpeg) ()
escribió:

> On 10/01/2020 01:20 AM, Eduardo Alarcón wrote:
> > Nyquist is a noun, not an adjective, for Harry Nyquist. ...
>
> Hi Eduardo, Thanks.
>
> Well, technically, a noun used as an adjective: "Nyquist sampling", makes
> it an adjective, but no
> matter.
>
> What if I narrow the scope to solely the sampling theory? thusly:
>
> Nyquist sampling: The principle [1] that, to most faithfully reproduce
>an image at a given digital display's resolution, samples must be
>made at or above twice the display's resolution, both horizontally &
>vertically [2].
>[1] The Nyquist principle applies to film sampling and to digital
>cameras, but, provided that resolution is unchanged, not to
>transcoding (because the transcoder inputs are already digital).
>As proved by the improved appearance of SD media made from 2K
>samples, SD mastering prior to the advent of 2K sampling (e.g.
>DVDs mastered before the advent of HD) generally ignored the
>Nyquist principle and were undersampled. HDs sampled at 2K and
>UHDs sampled at 4K are likewise undersampled.
>[2] As a convenience, the Nyquist threshold is currently (in 2020)
>specified solely by horizontal sample count rounded up to whole
>kilo-samples (2K, 4K, 8K).
>  displayNyquist threshold
>UHD 16:9-2160:  3840 x 2160 8K
> 4:3-2160:  2880 x 2160 8K
> HD 16:9-1080:  1920 x 1080 4K
> 4:3-1080:  1440 x 1080 4K
> SD  16:9-576:  1024 x 576  4K
>  4:3-576:   768 x 576  2K
> 16:9-480:   853 x 480  2K
>  4:3-480:   640 x 480  2K
>
> >... The Nyquist–Shannon
> > sampling theorem is applicable to analog to digital conversion of signals
> > (continuous to discrete), images are a type of signal.
>
> Well, I thought that was what I wrote. What doesn't work for you?
>
> The reason I wrote "both horizontally & vertically" was to resolve that,
> unlike sampling a
> 1-dimensional (serial) signal, 2-dimensional sampling (e.g. from film) or
> within a camera, requires
> the Nyquist principle be applied in both dimensions. But perhaps that's
> not what you find lacking.
> Could you suggest different wording maybe?
>
> --
> What if you woke up and found yourself in a police state?
> African-Americans wake up in a police state every day.
> ___
> 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] Glossary: Nyquist

2020-10-01 Thread Mick Finn 
Most relevant to input sampling and not so relevant for displays unless higher 
spatial frequencies are actually present in data
Not to mention most cameras have optical low pass filters
In other words just beachside a 4k camera was used does not mean it can display 
alias free in 4k display
So please keep bad info off the list

Sent from my iPhone

> On Oct 1, 2020, at 9:18 PM, Mark Filipak (ffmpeg)  wrote:
> 
> On 10/01/2020 01:20 AM, Eduardo Alarcón wrote:
>> Nyquist is a noun, not an adjective, for Harry Nyquist. ...
> 
> Hi Eduardo, Thanks.
> 
> Well, technically, a noun used as an adjective: "Nyquist sampling", makes it 
> an adjective, but no matter.
> 
> What if I narrow the scope to solely the sampling theory? thusly:
> 
> Nyquist sampling: The principle [1] that, to most faithfully reproduce
>  an image at a given digital display's resolution, samples must be
>  made at or above twice the display's resolution, both horizontally &
>  vertically [2].
>  [1] The Nyquist principle applies to film sampling and to digital
>  cameras, but, provided that resolution is unchanged, not to
>  transcoding (because the transcoder inputs are already digital).
>  As proved by the improved appearance of SD media made from 2K
>  samples, SD mastering prior to the advent of 2K sampling (e.g.
>  DVDs mastered before the advent of HD) generally ignored the
>  Nyquist principle and were undersampled. HDs sampled at 2K and
>  UHDs sampled at 4K are likewise undersampled.
>  [2] As a convenience, the Nyquist threshold is currently (in 2020)
>  specified solely by horizontal sample count rounded up to whole
>  kilo-samples (2K, 4K, 8K).
>displayNyquist threshold
>  UHD 16:9-2160:  3840 x 2160 8K
>   4:3-2160:  2880 x 2160 8K
>   HD 16:9-1080:  1920 x 1080 4K
>   4:3-1080:  1440 x 1080 4K
>   SD  16:9-576:  1024 x 576  4K
>4:3-576:   768 x 576  2K
>   16:9-480:   853 x 480  2K
>4:3-480:   640 x 480  2K
> 
>> ... The Nyquist–Shannon
>> sampling theorem is applicable to analog to digital conversion of signals
>> (continuous to discrete), images are a type of signal.
> 
> Well, I thought that was what I wrote. What doesn't work for you?
> 
> The reason I wrote "both horizontally & vertically" was to resolve that, 
> unlike sampling a 1-dimensional (serial) signal, 2-dimensional sampling (e.g. 
> from film) or within a camera, requires the Nyquist principle be applied in 
> both dimensions. But perhaps that's not what you find lacking. Could you 
> suggest different wording maybe?
> 
> -- 
> What if you woke up and found yourself in a police state?
> African-Americans wake up in a police state every day.
> ___
> 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] Encrypted SRT Does Not Work

2020-10-01 Thread Karim SLIMANI 
Le jeu. 1 oct. 2020 à 16:10, Tim McClure  a écrit :

> When I stream ffmpeg SRT to Wowza without encryption it works however when
> I
> stream SRT encrypted I get the error listed below.  I can use other
> software
> to stream encrypted SRT to Wowza and it works so I think the issue is on
> the
> ffmpeg side.  Here is the script I am using:
>
> ffmpeg -v verbose -re -i
> IndagoLE.ts -map 0:0 -pix_fmt yuv420p -vsync 1 -vf scale=1024:576 -vcodec
> libx264 -r 25 -g 100 -sc_threshold 0 -threads 0 -b:v: 2048k -bufsize 2244k
> -maxrate 2560k -preset veryfast -profile:v baseline -tune film -f mpegts
> srt://
> 192.168.1.118:5090?pbkeylen=16=1234567890123456_size=1316
>
> The error returned is:
> processAsyncConnectRequest FAILED. Setting TTL as EXPIRED.
>
[srt @ 0x55f6073be680] Connection to srt://192.168.1.118:5090?pbkeylen=16
> failed: Input/output error
> srt://192.168.1.118:5090?pbkeylen=16: Input/output error
> [AVIOContext @ 0x55f60737a640] Statistics: 3002512 bytes read, 3 seeks
>
>
Hello Tim,

In the error message
*" [srt @ 0x55f6073be680] Connection to
srt://192.168.1.118:5090?pbkeylen=16
 failed: Input/output error"* the
server url seems troncated.

I may be wrong, but try to put double quote on server url in your script
file.
___
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] Glossary: Nyquist

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 10/01/2020 01:20 AM, Eduardo Alarcón wrote:

Nyquist is a noun, not an adjective, for Harry Nyquist. ...


Hi Eduardo, Thanks.

Well, technically, a noun used as an adjective: "Nyquist sampling", makes it an adjective, but no 
matter.


What if I narrow the scope to solely the sampling theory? thusly:

Nyquist sampling: The principle [1] that, to most faithfully reproduce
  an image at a given digital display's resolution, samples must be
  made at or above twice the display's resolution, both horizontally &
  vertically [2].
  [1] The Nyquist principle applies to film sampling and to digital
  cameras, but, provided that resolution is unchanged, not to
  transcoding (because the transcoder inputs are already digital).
  As proved by the improved appearance of SD media made from 2K
  samples, SD mastering prior to the advent of 2K sampling (e.g.
  DVDs mastered before the advent of HD) generally ignored the
  Nyquist principle and were undersampled. HDs sampled at 2K and
  UHDs sampled at 4K are likewise undersampled.
  [2] As a convenience, the Nyquist threshold is currently (in 2020)
  specified solely by horizontal sample count rounded up to whole
  kilo-samples (2K, 4K, 8K).
displayNyquist threshold
  UHD 16:9-2160:  3840 x 2160 8K
   4:3-2160:  2880 x 2160 8K
   HD 16:9-1080:  1920 x 1080 4K
   4:3-1080:  1440 x 1080 4K
   SD  16:9-576:  1024 x 576  4K
4:3-576:   768 x 576  2K
   16:9-480:   853 x 480  2K
4:3-480:   640 x 480  2K


... The Nyquist–Shannon
sampling theorem is applicable to analog to digital conversion of signals
(continuous to discrete), images are a type of signal.


Well, I thought that was what I wrote. What doesn't work for you?

The reason I wrote "both horizontally & vertically" was to resolve that, unlike sampling a 
1-dimensional (serial) signal, 2-dimensional sampling (e.g. from film) or within a camera, requires 
the Nyquist principle be applied in both dimensions. But perhaps that's not what you find lacking. 
Could you suggest different wording maybe?


--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] Encrypted SRT Does Not Work

2020-10-01 Thread Tim McClure 
When I stream ffmpeg SRT to Wowza without encryption it works however when I
stream SRT encrypted I get the error listed below.  I can use other software
to stream encrypted SRT to Wowza and it works so I think the issue is on the
ffmpeg side.  Here is the script I am using:

ffmpeg -v verbose -re -i
IndagoLE.ts -map 0:0 -pix_fmt yuv420p -vsync 1 -vf scale=1024:576 -vcodec
libx264 -r 25 -g 100 -sc_threshold 0 -threads 0 -b:v: 2048k -bufsize 2244k
-maxrate 2560k -preset veryfast -profile:v baseline -tune film -f mpegts
srt://192.168.1.118:5090?pbkeylen=16=1234567890123456_size=1316

The error returned is:

ubuntu@5df3bfb7d42b5:~$ ./srt1.sh
ubuntu@5df3bfb7d42b5:~$ ffmpeg version N-99339-ge71d73b Copyright (c)
2000-2020 the FFmpeg developers
built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
configuration: --enable-protocol=libsrt --enable-libsrt
--prefix=/home/ubuntu/ffmpeg_build --pkg-config-flags=--static
--extra-cflags=-I/home/ubuntu/ffmpeg_build/include
--extra-ldflags=-L/home/ubuntu/ffmpeg_build/lib --extra-libs='-lpthread -lm'
--bindir=/home/ubuntu/bin --enable-gpl --enable-gnutls --enable-libaom
--enable-libass --enable-libfdk-aac --enable-libfreetype --enable-libmp3lame
--enable-libopus --enable-libsvtav1 --enable-libvorbis --enable-libvpx
--enable-libx264 --enable-libx265 --enable-nonfree
libavutil 56. 59.100 / 56. 59.100
libavcodec 58.106.100 / 58.106.100
libavformat 58. 58.100 / 58. 58.100
libavdevice 58. 11.102 / 58. 11.102
libavfilter 7. 87.100 / 7. 87.100
libswscale 5. 8.100 / 5. 8.100
libswresample 3. 8.100 / 3. 8.100
libpostproc 55. 8.100 / 55. 8.100
[mpegts @ 0x55f6073717c0] parser not found for codec klv, packets or times
may be invalid.
[mpegts @ 0x55f6073717c0] parser not found for codec none, packets or times
may be invalid.
[mpegts @ 0x55f6073717c0] parser not found for codec klv, packets or times
may be invalid.
[mpegts @ 0x55f6073717c0] probed stream 2 failed
[mpegts @ 0x55f6073717c0] parser not found for codec none, packets or times
may be invalid.
[h264 @ 0x55f607376ac0] non-existing PPS 0 referenced
Last message repeated 1 times
[h264 @ 0x55f607376ac0] decode_slice_header error
[h264 @ 0x55f607376ac0] no frame!
[h264 @ 0x55f607376ac0] Reinit context to 640x480, pix_fmt: yuv420p
[mpegts @ 0x55f6073717c0] max_analyze_duration 700 reached at 7024322
microseconds st:1
[mpegts @ 0x55f6073717c0] PES packet size mismatch
[mpegts @ 0x55f6073717c0] Packet corrupt (stream = 0, dts = 157047322).
[mpegts @ 0x55f6073717c0] Could not find codec parameters for stream 2
(Unknown: none (SLAp / 0x70414C53)): unknown codec
Consider increasing the value for the 'analyzeduration' (0) and 'probesize'
(500) options
Input #0, mpegts, from 'IndagoLE.ts':
Duration: 00:14:52.26, start: 852.746311, bitrate: 2366 kb/s
Program 1
Stream #0:0[0x11]: Video: h264 (Baseline), 1 reference frame ([27][0][0][0]
/ 0x001B), yuv420p(tv, progressive, left), 640x480 [SAR 1:1 DAR 4:3], 30
fps, 30 tbr, 90k tbn, 60 tbc
Stream #0:1[0x21]: Data: klv (KLVA / 0x41564C4B)
Stream #0:2[0x22]: Unknown: none (SLAp / 0x70414C53)
10:26:56.146728/SRT:RcvQ:w1!W:SRT.cn: processAsyncConnectRequest: REJECT
reported from HS processing, not processing further.
10:26:56.146844/SRT:RcvQ:w1*E:SRT.cn: RendezvousQueue:
processAsyncConnectRequest FAILED. Setting TTL as EXPIRED.
[srt @ 0x55f6073be680] Connection to srt://192.168.1.118:5090?pbkeylen=16
failed: Input/output error
srt://192.168.1.118:5090?pbkeylen=16: Input/output error
[AVIOContext @ 0x55f60737a640] Statistics: 3002512 bytes read, 3 seeks





--
Sent from: http://www.ffmpeg-archive.org/
___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Marco Mircoli 
Thanks a lot!

Il giorno gio 1 ott 2020 alle ore 14:17 Michael Koch <
astroelectro...@t-online.de> ha scritto:

> Am 01.10.2020 um 14:06 schrieb Michael Koch:
> > Am 01.10.2020 um 13:25 schrieb Marco Mircoli:
> >> Hello',
> >>  I'm a newbie.
> >> Just bought a php script that use ffmpeg.
> >> it converts to mp3/96Kbps all media uploaded in a unique format.
> >> this is the line, and now it normalizes to R128 (thanks Moritz)
> >>
> >> $shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map
> >> 0:a:0 -af
> >> loudnorm -b:a 96k $audio_output_mp3 2>&1");
> >>
> >> I'm wondering if it is possible to include a simple hi-pass filter
> >> (highest
> >> db per octave @ 70Hz)
> >
> > add  highpass=70,before  loudnorm
> >
> > This filter attenuated 6dB per octave. If you need higher attenuation,
> > you can use several highpass filters, for example
> > highpass=70,highpass=70,highpass=70,loudnorm
>
> Correction: The filter has 12dB per octave.
>
> Michael
>
> ___
> 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] Glossary: d-NTSC & d-PAL

2020-10-01 Thread Mark Filipak (ffmpeg) 

On 09/30/2020 11:56 PM, Jim DeLaHunt wrote:

On 2020-09-30 20:36, Mark Filipak (ffmpeg) wrote:


Continuing with relatively non controversial entries:

d-NTSC [noun]: 1, The digital equivalent of NTSC distinguished by
  binary metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  480 rows: 'vertical_size_value' = 0001 1110 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  30/1.001 FPS: 'frame_rate_code' = 0100
  'progressive_sequence' = 0 & 'progressive_frame' = 0

d-PAL [noun]: 1, The digital equivalent of PAL distinguished by binary
  metadata:
  720 samples/row: 'horizontal_size_value' = 0010 1101 
   'horizontal_size_extension' = 00
  576 rows: 'vertical_size_value' = 0010 0100 
    'vertical_size_extension' = 00
  4:3 DAR: 'aspect_ratio_information' = 0010
  25 FPS: 'frame_rate_code' = 0011
  'progressive_sequence' = 0 & 'progressive_frame' = 0 



It seems to me that these are no longer glossary entries — or, only the first line of each is a 
glossary entry. ...


Each entry is just one sentence, so I guess you don't like the sentence 
spanning multiple lines (?)

The sentence is a statement followed by a list of metadata that distinguishes the subject... so that 
people can determine whether a particular video is a d-NTSC video or not a d-NTSC video for example. 
The main distinguishing feature is 'progressive_sequence' = 0 & 'progressive_frame' = 0 of course. 
The others narrow the scope to just a single species of video.


If a glossary entry requires explanation, then it's a fail. What fails? I guess I didn't anticipate 
such a total-failure mode.


Do you have any suggestions? Should I just forget this glossary idea?

... The rest seems to be a description of a data structure or representation. The entry 
doesn't say to what format or specification the representation applies. To an MPEG-2 video? To a the 
ISO file corresponding to a DVD?



--
What if you woke up and found yourself in a police state?
African-Americans wake up in a police state every day.
___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Michael Koch 

Am 01.10.2020 um 14:06 schrieb Michael Koch:

Am 01.10.2020 um 13:25 schrieb Marco Mircoli:

Hello',
 I'm a newbie.
Just bought a php script that use ffmpeg.
it converts to mp3/96Kbps all media uploaded in a unique format.
this is the line, and now it normalizes to R128 (thanks Moritz)

$shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 
0:a:0 -af

loudnorm -b:a 96k $audio_output_mp3 2>&1");

I'm wondering if it is possible to include a simple hi-pass filter 
(highest

db per octave @ 70Hz)


add  highpass=70,    before  loudnorm

This filter attenuated 6dB per octave. If you need higher attenuation, 
you can use several highpass filters, for example 
highpass=70,highpass=70,highpass=70,loudnorm


Correction: The filter has 12dB per octave.

Michael

___
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] Correct conversion of yuvj420p?

2020-10-01 Thread Peter B. 

On 29.09.20 09:56, Christian Ebert wrote:

How about doing quick diagnosis with ffprobe before you start,
something like:

ffprobe -v error \
-print_format default=noprint_wrappers=1:nokey=1 \
-select_streams V -show_entries stream=pix_fmt

and make the command depend on the result?


Thanks for the suggestion, but that actually is what I'm doing right now 
- yet it means to treat parts of the batches with different 
conditions/recipes.


Additionally, in that concrete situation, the source videos (several 
thousand...) are stored on an S3-type object based storage (non-Amazon 
dialect). So used Mediainfo to avoid having to pull several hundred 
Terabyte of videos just to get their tech-MD.



And Mediainfo cannot tell me what FFmpeg considers yuvj420p, because...
Even if it wasn't for the "S3-extra-fun", I'm running into this issue 
every now and then in different video collections - and every "if - then 
- else" adds extra points of failure (and work).



You see my challenge? :)


Kind regards,
Peter

___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Michael Koch 

Am 01.10.2020 um 13:25 schrieb Marco Mircoli:

Hello',
 I'm a newbie.
Just bought a php script that use ffmpeg.
it converts to mp3/96Kbps all media uploaded in a unique format.
this is the line, and now it normalizes to R128 (thanks Moritz)

$shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 0:a:0 -af
loudnorm -b:a 96k $audio_output_mp3 2>&1");

I'm wondering if it is possible to include a simple hi-pass filter (highest
db per octave @ 70Hz)


add  highpass=70,    before  loudnorm

This filter attenuated 6dB per octave. If you need higher attenuation, 
you can use several highpass filters, for example 
highpass=70,highpass=70,highpass=70,loudnorm


Michael

___
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] HIGHPASS FILTER AND ID£ METADATA

2020-10-01 Thread Marco Mircoli 
Hello',
I'm a newbie.
Just bought a php script that use ffmpeg.
it converts to mp3/96Kbps all media uploaded in a unique format.
this is the line, and now it normalizes to R128 (thanks Moritz)

$shell = shell_exec("$ffmpeg_b -i $audio_file_full_path -map 0:a:0 -af
loudnorm -b:a 96k $audio_output_mp3 2>&1");

I'm wondering if it is possible to include a simple hi-pass filter (highest
db per octave @ 70Hz)
AND
if I could add some id3 info and track gif to the mp3 metadata.

I think it is possible, but I don't know how to do it :-(
Consider is a web script with server call, so it would be nice to have just
one call (or command)

Thanks in advance.
S.
___
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] Win32 binaries = RIP?

2020-10-01 Thread Gilles 
Tom Sparks-2 wrote
>> If so, how hard is it to compile, and is there a tutorial?
> 
> see https://trac.ffmpeg.org/wiki/CompilationGuide

I'll give it a shot. Thank you.




--
Sent from: http://www.ffmpeg-archive.org/
___
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] Glossary: DAR, PAR, and SAR

2020-10-01 Thread Nicolas George 
Mark Filipak (ffmpeg) (12020-09-30):
> Revision: Shorter sentences, better consistency, no extra 'lesson' about how 
> to minimize ratios.\
> Formatted for email, plain text.

What is you purpose in writing this?

If you intend to make a generic erudite glossary for all video terms,
then the mailing-list for using FFmpeg is not the place to do it.

If you intend to make a glossary useful for FFmpeg users, then get rid
of all the useless lint about obsolescent standards (H.262? seriously?)
and irrelevant terms. In particular:

> PAR (picture aspect ratio [1]) [noun]: 1, The horizontal-to-vertical
>   size [3] ratio (H:V, e.g. 5:4, 3:2) for pictures. PAR is

get rid of this one altogether, because nothing in FFmpeg use it, and
rightly, because nobody should use it.

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