[FFmpeg-trac] #1776(FFprobe:closed): ffprobe shows PAR as SAR

[FFmpeg]

#1776: ffprobe shows PAR as SAR
-------------------------------------+-------------------------------------
             Reporter:  henry        |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:  FFprobe
              Version:  unspecified  |               Resolution:  invalid
             Keywords:               |               Blocked By:
  ffprobe,PAR,SAR                    |  Reproduced by developer:  0
             Blocking:               |
Analyzed by developer:  1            |
-------------------------------------+-------------------------------------

Comment (by saste):

 Replying to [comment:5 henry]:
 > got it , also if that means  [[BR]]
 > 1. for ffprobe , PAR == SAR ? [[BR]]
 > 2. in ffproble, always only show [SAR XX:xx , DAR X:xx] , nerver show
 [PAR xx:xx  DAR XX:XX] ? [[BR]]
 > 3. in ffmpeg, always only show [PAR XX:xx , DAR X:xx] , nerver show [SAR
 xx:xx  DAR XX:XX] ? [[BR]]

 No. Previuosly, FFmpeg was using "PAR" in place of "SAR" all over the
 place, at some point we decided to switch to SAR, see commit:

 {{{
 commit fdd130a2131912133c72b5ff532726784aaa70a2
 Author: Stefano Sabatini <stefano.sabatini-lala at poste.it>
 Date:   Wed Jul 27 10:35:08 2011 +0200

     prefer "SAR" over "PAR" in av_dump_format()

     "SAR" (Sample Aspect Ratio) is globally preferred over "PAR" (Pixel
     Aspect Ratio), although the two terms share the same semantics.

     For example the corresponding AVStream field is called
     sample_aspect_ratio, and libavfilter has a filter named setsar.

     Therefore prefer the term "SAR" over "PAR" in the
     libavformat/utils.c:dump_stream_format() and avcodec_string() output
     for avoiding confusion.
 }}}

 The ffprobe/ffmpeg inconsistency you observed is due to the use of
 different releases.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1776#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker