Skip to content

F
ffmpeg.wasm-core
Switch branch/tag
  1. 13 Apr, 2018 20 commits
  3. 12 Apr, 2018 14 commits
  5. 11 Apr, 2018 6 commits
    • Aman Gupta's avatar
      avcodec/mpegpicture: fix "stride changed" failures in gray mode · 19128408
      Aman Gupta authored 
      Before adding uvlinesize check, I was seeing failures decoding
some video with ffmpeg compiled with --enable-gray and using AV_CODEC_FLAG_GRAY.

[mpeg2video @ 0x7fa193818c00] get_buffer() failed (stride changed: linesize=1280/1280 uvlinesize=0/640)
[mpeg2video @ 0x7fa193818c00] get_buffer() failed (stride changed: linesize=1280/1280 uvlinesize=0/640)
Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      19128408
    • Timo Rothenpieler's avatar
      avcodec/nvenc: update required driver versions for nvenc · 2108a673
      Timo Rothenpieler authored
      2108a673
    • Timo Rothenpieler's avatar
      avcodec/nvenc: add support for B frames as ref · 86e9dba8
      Timo Rothenpieler authored
      86e9dba8
    • Hendrik Leppkes's avatar
      spdifenc: support ac3 core+eac3 dependent streams · 3e9d6761
      Hendrik Leppkes authored 
      Such streams are found on Blu-ray, and identified as EAC3 type in
avformat, while the bitstream of the core stream is actually a pure AC3
frame.

Adjust the parsing accordingly, since AC3 frames always hold 6 blocks
and the numblkscod syntax element is not present.
      3e9d6761
    • Bela Bodecs's avatar
      avformat/hlsenc: fix handling of delete_segments when %v is present · 9825f77a
      Bela Bodecs authored 
      When var_stream_map option is used, %v must appear either in segment
name template or in the directory path. This latter case currently is
not handled and delete_segments flag of hls_flags is broken now. This
patch fix this. The root cause of the bug was that HLSSegment struct
only stores the final filename part, but not the final directory path.
Most of the cases, final path info is unneded, It only necessary when
you want to delete old segments (e.g in case of live streaming).
Without variant streams it was unnecessary to store the final directory
path, because all segment were stored into the same directory. But
introducing %v in directory names either require to store the final
directory path into HLSSegment or associate segments with their variant
streams to be able deleting them later. I have choosen the second
solution and introduced a variant index data member into the segment
struct.
Signed-off-by: 's avatarBela Bodecs <bodecsb@vivanet.hu>
Signed-off-by: 's avatarSteven Liu <lq@onvideo.cn>
      9825f77a
    • Timo Teräs's avatar
      avformat/movenc: use correct iTunes copyright atom · 62c1cfcc
      Timo Teräs authored 
      Support for writing copyright metadata was added in commit bed4fc54
for 3GP, MOV and iTunes metadata. 3GP and MOV cases are formally
specified. However, iTunes format does not have specification, and
it seems to have been assumed that it would use the same atom as
MOV (both being Apple formats).

However, Apple uses 'cprt' atom for iTunes metadata (do note that
the iTunes 'cprt' encoding is generic iTunes ItemList atom, not
the 3GP 'cprt' encoding. These are also inside different parent
atoms).

Most references trying to document iTunes atoms mention only
the 'cprt' tag. See:
 - http://atomicparsley.sourceforge.net/mpeg-4files.html
 - http://mutagen.readthedocs.io/en/latest/api/mp4.html

Same applies to other software supporting this tag. Most of them
encode and decode only the 'cprt' atom.

ffmpeg mov demuxer supports both atoms in this context. There are
few pieces of other software that support similarly both 'cprt' and
the incorrect '\251cpy' atom in this context. I believe they do it in
order to read the ffmpeg encoded incorrect copyright atom.

In light of the above this changes the copyright atom to 'cprt' as
it seems to be supported univerally and is the correct atom to use.
Signed-off-by: 's avatarTimo Teräs <timo.teras@iki.fi>
Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      62c1cfcc