Re: [FFmpeg-trac] #5713(ffmpeg:new): Can't Recalculate the Timestamp of Fragmentary Video Streams (was: The timestamp still remaining the same within MKV when all the bytes filled with zeros are remov

2016-09-26 Thread FFmpeg 
#5713: Can't Recalculate the Timestamp of Fragmentary Video Streams
+--
 Reporter:  PureOcean   |Owner:
 Type:  defect  |   Status:  new
 Priority:  normal  |Component:  ffmpeg
  Version:  git-master  |   Resolution:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
Changes (by PureOcean):

 * component:  undetermined => ffmpeg


Comment:

 Okay. I '''finally''' found the root cause.

 FFmpeg can't recalculate only the timestamp of fragmentary video streams.
 Although it's can be resync properly to audio streams. Is it not strange?
 (A more interesting: '''MEncoder''' can recalculate/resync the timestamp
 both of fragmentary video & audio streams).

 '''Steps for Analyze & Re-produce:'''

 ''1) Download to example a fragmentary sample:''
 [https://mega.nz/#!htBQUDJD!Pr-TkZN5GmyCe99k1RfBkVh7ahp-9npjX74HE36ktfo]

 The Purpose: If the file's timestamp seems as '''00:14:48''', it is need
 resync/recalculate. Because of the file is fragmentary/brokenly.

 ''2) Run (remux only audio stream):''
 {{{
 FFmpeg -i Random_Seeking_Stream-Sintel_Sample.mkv -vn -async -1
 only_audio-timestamp_can_be_resynced_properly.mkv
 }}}

 The Result: New timestamp is '''00:03:48''' which it's properly timecode!
 Incredible, well done FFmpeg (thanks to all who contributed)!

 ''3) Run (remux only video stream):''
 {{{
 FFmpeg -i Random_Seeking_Stream-Sintel_Sample.mkv -c:v copy -an -vsync -1
 only_video-timestamp_not_resynced.mkv
 }}}

 The Result: The only video track's timestamp is still remaining the same
 input file, it can't resynced.

 ''4) Run (remux both of video + audio stream):''
 {{{
 FFmpeg -i Random_Seeking_Stream-Sintel_Sample.mkv -c:v copy -c:a copy
 -vsync -1 -async -1 not_synced.mkv
 }}}

 The Result: The output MKV's timecode not changed, still remains same (due
 to can't resynced to video stream). The video now plays with anormal
 speed, because of actually only the audio track is resynced properly.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5825(avcodec:closed): Vobsub subtitles won't overlay with some MKV

2016-09-26 Thread FFmpeg 
#5825: Vobsub subtitles won't overlay with some MKV
-+-
 Reporter:  edumj|Owner:
 Type:  defect   |   Status:  closed
 Priority:  important|Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  dvdsub   |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by edumj):

 Ok, no error with full file!

 But the 1000 fps thing...

 I used this full command:
 {{{
 "ffmpeg" -i "%~1" -lavfi
 [0:s:0][0:v]scale2ref[subs][video];[video][subs]overlay -map 0:a:1 -f avi
 -c:v libxvid -b:v 1500k -vtag XVID -c:a libmp3lame -b:a 128k
 "overlay+scale2ref -lavfi.avi"
 }}}
 And the resulting video is 1000 fps and very "pixelated" (low bitrate),
 but if I add "-r 25" as output, it's Ok. Do I have to always especify
 framerate for lavfi to work?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5671(avformat:open): FFmpeg unable to decode PCM in MXF

2016-09-26 Thread FFmpeg 
#5671: FFmpeg unable to decode PCM in MXF
-+-
 Reporter:  steved   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mxf  |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by lvml):

 * cc: lvml@… (added)


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5671(avformat:open): FFmpeg unable to decode PCM in MXF

2016-09-26 Thread FFmpeg 
#5671: FFmpeg unable to decode PCM in MXF
-+-
 Reporter:  steved   |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  mxf  |   Blocked By:
  regression |  Reproduced by developer:  1
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by lvml):

 The same bug applies to MXF files from other sources, e.g. the soundtrack
 of "Meridian", a professionally made 4k HDR video sample that Netflix
 recently published under a Creative Commons license for the purpose of
 video encoder testing.

 The Meridian MXF files are available e.g. from the xiph.org site at
 https://media.xiph.org/video/derf/

 When trying to probe https://media.xiph.org/video/derf/meridian
 /MERIDIAN_SHR_C_EN-XX_US-NR_51_LTRT_UHD_20160909_OV/MERIDIAN_SHR_C_EN-
 XX_US-NR_51_LTRT_UHD_20160909_OV_01_EN_20_B.mxf with ffprobe compiled from
 the current git master, the output looks like this:

 {{{
 [mxf @ 0x227ae20] OPAtom misinterpreted as OP1a? KLV for edit unit 0
 extending into next edit unit is not implemented. Update your FFmpeg
 version to the newest one from Git. If the problem still occurs, it means
 that your file has a feature which has not been implemented.
 [mxf @ 0x227ae20] If you want to help, upload a sample of this file to
 ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing
 list. (ffmpeg-de...@ffmpeg.org)
 Input #0, mxf, from 'MERIDIAN_SHR_C_EN-XX_US-
 NR_51_LTRT_UHD_20160909_OV_01_EN_20_B.mxf':
   Metadata:
 application_platform: Microsoft Windows 7 Professional Service Pack 1
 (Build 7601)
 uid : cdb57bb1-4f06-4c77-64e4-c0293f2c7163
 generation_uid  : 2d654592-04ae-4cf4-35ab-69707dc0de3a
 company_name: Colorfront
 product_name: Transkoder
 product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc
 product_version : 2.7.3.20150121
 modification_date: 2016-09-09 11:29:38
 material_package_umid:
 0x060A2B340101010501010F2013002C3E49A0BD1548ACD65D70EA10FAEB6B
 timecode: 00:00:17;12
   Duration: 00:11:58.92, start: 0.00, bitrate: 2304 kb/s
 Stream #0:0: Audio: pcm_s24le, 48000 Hz, 2 channels, s32 (24 bit),
 2304 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010F201300AE2179BC93E24600C47112668D9E21FB
 }}}

 When trying to transcode the PCM audio track in the same MXF file with
 "ffmpeg" from current git master, the output looks like this:

 {{{
 ./ffmpeg -i MERIDIAN_SHR_C_EN-XX_US-
 NR_51_LTRT_UHD_20160909_OV_01_EN_20_B.mxf test.wav
 ffmpeg version N-81773-g69449da Copyright (c) 2000-2016 the FFmpeg
 developers
 ...
 [mxf @ 0x20f1660] OPAtom misinterpreted as OP1a? KLV for edit unit 0
 extending into next edit unit is not implemented. Update your FFmpeg
 version to the newest one from Git. If the problem still occurs, it means
 that your file has a feature which has not been implemented.
 [mxf @ 0x20f1660] If you want to help, upload a sample of this file to
 ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing
 list. (ffmpeg-de...@ffmpeg.org)
 Guessed Channel Layout for Input Stream #0.0 : stereo
 Input #0, mxf, from 'MERIDIAN_SHR_C_EN-XX_US-
 NR_51_LTRT_UHD_20160909_OV_01_EN_20_B.mxf':
   Metadata:
 application_platform: Microsoft Windows 7 Professional Service Pack 1
 (Build 7601)
 uid : cdb57bb1-4f06-4c77-64e4-c0293f2c7163
 generation_uid  : 2d654592-04ae-4cf4-35ab-69707dc0de3a
 company_name: Colorfront
 product_name: Transkoder
 product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc
 product_version : 2.7.3.20150121
 modification_date: 2016-09-09 11:29:38
 material_package_umid:
 0x060A2B340101010501010F2013002C3E49A0BD1548ACD65D70EA10FAEB6B
 timecode: 00:00:17;12
   Duration: 00:11:58.92, start: 0.00, bitrate: 2304 kb/s
 Stream #0:0: Audio: pcm_s24le, 48000 Hz, stereo, s32 (24 bit), 2304
 kb/s
 Metadata:
   file_package_umid:
 0x060A2B340101010501010F201300AE2179BC93E24600C47112668D9E21FB
 Output #0, wav, to 'test.wav':
   Metadata:
 application_platform: Microsoft Windows 7 Professional Service Pack 1
 (Build 7601)
 uid : cdb57bb1-4f06-4c77-64e4-c0293f2c7163
 generation_uid  : 2d654592-04ae-4cf4-35ab-69707dc0de3a
 company_name: Colorfront
 product_name: Transkoder
 product_uid : 3a4fe380-0d01-11e4-869f-3cd92b5c1dfc
 product_version : 2.7.3.20150121
 modification_date: 2016-09-09 11:29:38
 material_package_umid:
 0x060A2B340101010501010F2013002C3E49A0BD1548ACD65D70EA10FAEB6B
 ISMP

Re: [FFmpeg-trac] #5677(avcodec:open): Videotoolbox encoder does not preserve A53_CC side data

2016-09-26 Thread FFmpeg 
#5677: Videotoolbox encoder does not preserve A53_CC side data
-+-
 Reporter:  tmm1 |Owner:  kernrj
 Type:  enhancement  |   Status:  open
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:   |   Blocked By:
  videotoolbox cc|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-

Comment (by tmm1):

 https://s3.amazonaws.com/tmm1/ccaptions/movie.ts
 https://s3.amazonaws.com/tmm1/ccaptions/music.ts
 https://s3.amazonaws.com/tmm1/ccaptions/sports.ts
 https://s3.amazonaws.com/tmm1/ccaptions/news.ts
 https://s3.amazonaws.com/tmm1/ccaptions/news2.ts

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #4009(undetermined:new): aiffenc qcelp remux: invalid output

2016-09-26 Thread FFmpeg 
#4009: aiffenc qcelp remux: invalid output
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:   |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by ami_stuff):

 the output file seems to play fine with qt

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5147(undetermined:new): mov: wrong output after remuxing

2016-09-26 Thread FFmpeg 
#5147: mov: wrong output after remuxing
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  avid |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-

Comment (by ami_stuff):

 attached

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5056(avcodec:closed): Empty cues when converting ASS embedded in MKV to SRT

2016-09-26 Thread FFmpeg 
#5056: Empty cues when converting ASS embedded in MKV to SRT
+---
 Reporter:  eelco   |Owner:
 Type:  defect  |   Status:  closed
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:  fixed
 Keywords:  ass |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Changes (by cehoyos):

 * keywords:  ass,srt => ass
 * priority:  important => normal
 * status:  new => closed
 * resolution:   => fixed


Comment:

 Probably fixed by Rodger Combs in 3b32e1313c6d68aa10bc7d97ad505382def833b0

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5147(undetermined:new): mov: wrong output after remuxing

2016-09-26 Thread FFmpeg 
#5147: mov: wrong output after remuxing
-+-
 Reporter:  ami_stuff|Owner:
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
  Version:  unspecified  |  undetermined
 Keywords:  avid |   Resolution:
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * keywords:   => avid


Comment:

 Please provide the samples again.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #4105(avcodec:closed): RC_Lookahead RC-Lookahead inconsistency

2016-09-26 Thread FFmpeg 
#4105: RC_Lookahead RC-Lookahead inconsistency
-+-
 Reporter:  Atarikid |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avcodec
  Version:  git-master   |   Resolution:  wontfix
 Keywords:  libvpx   |   Blocked By:
  libx264|  Reproduced by developer:  0
 Blocking:   |
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Feel free to send a patch made with {{{git format-patch}}} to the
 development mailing list.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5291(undetermined:open): Wrong parsing when start time > end time in subtitles (.ass)

2016-09-26 Thread FFmpeg 
#5291: Wrong parsing when start time > end time in subtitles (.ass)
-+-
 Reporter:  miflinak |Owner:
 Type:  defect   |   Status:  open
 Priority:  important|Component:
  Version:  git-master   |  undetermined
 Keywords:  ass  |   Resolution:
  regression |   Blocked By:
 Blocking:   |  Reproduced by developer:  1
Analyzed by developer:  0|
-+-
Changes (by cehoyos):

 * keywords:   => ass regression
 * priority:  normal => important
 * version:  unspecified => git-master
 * status:  new => open
 * reproduced:  0 => 1


Comment:

 Regression since b01891a9.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #4026(avformat:closed): AAC Number of bands exceeds limit

2016-09-26 Thread FFmpeg 
#4026: AAC Number of bands exceeds limit
-+-
 Reporter:  sssr33   |Owner:
 Type:  defect   |   Status:  closed
 Priority:  normal   |Component:  avformat
  Version:  git-master   |   Resolution:
 Keywords:  aac rtsp |  needs_more_info
 Blocking:   |   Blocked By:
Analyzed by developer:  0|  Reproduced by developer:  0
-+-
Changes (by cehoyos):

 * status:  open => closed
 * resolution:   => needs_more_info


Comment:

 Sadly, the stream is now 404.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

[FFmpeg-trac] #5865(ffplay:new): ffplay doesn't correctly center fullscreen video on rotated monitor

2016-09-26 Thread FFmpeg 
#5865: ffplay doesn't correctly center fullscreen video on rotated monitor
+--
 Reporter:  pdknsk  | Type:  defect
   Status:  new | Priority:  normal
Component:  ffplay  |  Version:
 Keywords:  |   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+--
 Open video on a rotated (pivot) monitor, example resolution: 1200x1920.
 Press F.
 The video is not centered, but shifted to the right past the screen, as if
 it were centered for a resolution of 1920x1920.

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #437(ffplay:closed): ffplay seems to "darken" certain inputs (ex: bgr24)

2016-09-26 Thread FFmpeg 
#437: ffplay seems to "darken" certain inputs (ex: bgr24)
-+-
 Reporter:  rogerdpack   |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  ffplay
  Version:  unspecified  |   Resolution:
 Keywords:  sdl yuv  |  needs_more_info
  range color|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-

Comment (by cehoyos):

 Replying to [comment:11 ubitux]:
 > Is this better with SDL2 now?
 >
 > ffplay seems to have native SDL BGRA output now (since
 9c5fab5ed421da4e55cafcbff0482e1ad926c27b).

 Are you sure that this rgb output is used for bgr24 input (the pix_fmt
 used as example in this ticket)?

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5807(avcodec:closed): Add YUV420P10 to vaapi hardware decode

2016-09-26 Thread FFmpeg 
#5807: Add YUV420P10 to vaapi hardware decode
-+---
 Reporter:  lethalwp |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:  fixed
 Keywords:  vaapi|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by cehoyos):

 * resolution:   => fixed


--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac

Re: [FFmpeg-trac] #5807(avcodec:closed): Add YUV420P10 to vaapi hardware decode

2016-09-26 Thread FFmpeg 
#5807: Add YUV420P10 to vaapi hardware decode
-+---
 Reporter:  lethalwp |Owner:
 Type:  enhancement  |   Status:  closed
 Priority:  wish |Component:  avcodec
  Version:  git-master   |   Resolution:
 Keywords:  vaapi|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+---
Changes (by cehoyos):

 * keywords:   => vaapi
 * priority:  normal => wish
 * resolution:  invalid =>


Comment:

 The patch was applied as fb37da37ac1e17f643269ea5bad5bee7e79dcb3a

--
Ticket URL: 
FFmpeg 
FFmpeg issue tracker
___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-trac