When using clang-cl it expects parameters passed in MSVC-style, so appropriate
toolchain should be selected.
As soon as both clang and clang-cl report themselfs as "clang" with -v option
the only chance to detect
clang-cl is passing -? option to both which is valid for clang-cl.exe and not
for c
hows me some small load on MFX - I THINK that GPU
is responsible for copying and converting. But this are just my thoughts,
that's all as no info is provided in documentation.
Many thanks for reviewing the code,
- Alex
2017-08-14 14:26 GMT+02:00 Mark Thompson :
> On 11/08/17 10:10, Alexande
c b/libavcodec/qsvdec_screen.c
new file mode 100644
index 00..aeea851333
--- /dev/null
+++ b/libavcodec/qsvdec_screen.c
@@ -0,0 +1,250 @@
+/*
+ * Intel QSV screen capture decoder
+ *
+ * This file is part of FFmpeg.
+ *
+ * Copyright (C) 2017 Alexander Bilyak
+ *
+ * FFmpeg is free software;
44
index 00..475a9a4c50
--- /dev/null
+++ b/libavdevice/qsvscreen.c
@@ -0,0 +1,216 @@
+/*
+ * Intel QSV screen capture interface
+ *
+ * This file is part of FFmpeg.
+ *
+ * Copyright (C) 2017 Alexander Bilyak
+ *
+ * FFmpeg is free software; you can redistribute it and/or
+ * modify it unde
Added more options for OpenH264 encoder
---
libavcodec/libopenh264enc.c | 60 +
1 file changed, 34 insertions(+), 26 deletions(-)
diff --git a/libavcodec/libopenh264enc.c b/libavcodec/libopenh264enc.c
index 24bc228..532cb5d 100644
--- a/libavcodec/libop
