Skip to content

F
ffmpeg.wasm-core
Switch branch/tag
  1. 01 Aug, 2018 2 commits
  3. 26 Jul, 2018 1 commit
  5. 13 Jul, 2018 1 commit
  7. 06 Jul, 2018 1 commit
  9. 29 Jun, 2018 1 commit
    • John Cox's avatar
      configure: fix inline asm checks · 52fd2afc
      John Cox authored 
      Commit 8c893aa3 removed quotes that were required to detect
inline asm:

check_insn armv5te qadd r0, r0, r0
.../test.c:1:34: error: expected string literal in 'asm'
void foo(void){ __asm__ volatile(qadd r0, r0, r0); }

The correct code is:

void foo(void){ __asm__ volatile("qadd r0, r0, r0"); }

Commit message written by Frank Liberato <liberato@chromium.org>
Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      52fd2afc
  11. 11 Jun, 2018 2 commits
  13. 04 Jun, 2018 1 commit
  15. 03 Jun, 2018 1 commit
  17. 24 May, 2018 1 commit
  19. 26 Apr, 2018 1 commit
  21. 25 Apr, 2018 2 commits
  23. 20 Apr, 2018 5 commits
  25. 19 Apr, 2018 2 commits
  27. 15 Apr, 2018 1 commit
  29. 09 Apr, 2018 5 commits
  31. 08 Apr, 2018 4 commits
    • Zhong Li's avatar
      lavc/qsvdec: set complete_frame flags for progressive picture · 54307b35
      Zhong Li authored 
      Set the flag MFX_BITSTREAM_COMPLETE_FRAME when it is a progressive picture.
This can fix vc1 decoding segment fault issues because can't set the start
code correctly.

See: ./avconv -hwaccel qsv -c:v vc1_qsv -i /fate-suite/vc1/SA00040.vc1
-vf "hwdownload, format=nv12" -f rawvideo /dev/null

v2: fix some h264 interlaced clips regression
a. field_order of some h264 interlaced video (e.g: cama3_vtc_b.avc) is marked as AV_FIELD_UNKNOWN
   in h264_parser.c. This is not a completed frames.
   So only set the MFX_BITSTREAM_COMPLETE_FRAME when it is progressive.
b. some clips have both progressive and interlaced frames (e.g.CAPAMA3_Sand_F.264),
   the parsed field_order maybe changed druing the decoding progress.

This patch has been verified for other codecs(mpeg2/hevc/vp8).
Signed-off-by: 's avatarZhong Li <zhong.li@intel.com>
Signed-off-by: 's avatarMaxym Dmytrychenko <maxim.d33@gmail.com>
      54307b35
    • Maxym Dmytrychenko's avatar
      qsv: adding Multi Frame Encode support · cca5e4f0
      Maxym Dmytrychenko authored 
      Starting from API 1.25 helps to improve performance of the simultaneous
encode, 1:N scenario, like:

./avconv  -y -hwaccel qsv -c:v h264_qsv -r 30000/1001 -i
~/bbb_sunflower_1080p_60fps_normal.mp4  -vframes 600 -an \
    -filter_complex "split=2[s1][s2]; [s1]scale_qsv=1280:720[o1];
[s2]scale_qsv=960:540[o2]" \
    -map [o1] -c:v h264_qsv -b:v 3200k -minrate 3200k -maxrate 3200k -f
rawvideo /tmp/3200a.264 \
    -map [o2] -c:v h264_qsv -b:v 1750k -minrate 1750k -maxrate 1750k -f
rawvideo /tmp/1750a.264
Signed-off-by: 's avatarMaxym Dmytrychenko <maxim.d33@gmail.com>
      cca5e4f0
    • Zhong Li's avatar
      lavf/qsvvpp: bypass vpp if not needed. · 29a8ed76
      Zhong Li authored 
      Currently vpp pipeline is always created, even for the unnecessary
cases such as setting the option "vpp_qsv=w=1280:h=720" for an input
with native resolution 1280x720. Thus introduces unnecessary performance
dropping, so bypass vpp if not needed.
Signed-off-by: 's avatarZhong Li <zhong.li@intel.com>
Signed-off-by: 's avatarMaxym Dmytrychenko <maxim.d33@gmail.com>
      29a8ed76
    • Zhong Li's avatar
      lavc/qsvdec: expose frame pic_type and key_frame · 52ed83fa
      Zhong Li authored 
      Currently pict_type and key_frame are unset.
Add an extra param to fetch the picture type from qsv decoder

The judgement “key frame is equal to IDR frame” only suitable for H264.
For HEVC, all IRAP frames are key frames, and other codecs have no IDR
frame.
Signed-off-by: 's avatarChaoX A Liu <chaox.a.liu@intel.com>
Signed-off-by: 's avatarZhong Li <zhong.li@intel.com>
Signed-off-by: 's avatarMaxym Dmytrychenko <maxim.d33@gmail.com>
      52ed83fa
  33. 04 Apr, 2018 1 commit
  35. 02 Apr, 2018 1 commit
  37. 30 Mar, 2018 3 commits
  39. 29 Mar, 2018 2 commits
  41. 28 Mar, 2018 1 commit
  43. 27 Mar, 2018 1 commit