On 2015-01-23 01:54, Timo Rothenpieler wrote:
+ctx-encode_config.encodeCodecConfig.h264Config.maxNumRefFrames =
avctx-refs;
avctx-refs should propably be checked for = 0.
I'm not sure if maxNumRefFrames means the exact same thing as
avctx-refs, but the comment in the nvenc header isn't
Patch attached for consideration.
On 1/23/15 8:03 AM, jon morley wrote:
Currently check_fps has the following logic:
static int check_fps(int fps)
{
int i;
static const int supported_fps[] = {24, 25, 30, 48, 50, 60};
for (i = 0; i FF_ARRAY_ELEMS(supported_fps); i++)
if the openjpeg parameter tcp_rates is not 0 ( using the ffmpeg
compression_level option )
every 2nd image per thread is badly encoded. By moving the opj_setup_encoder
function from
libopenjpeg_encode_init to libopenjpeg_encode_frame this can be prevented.
This fixes ticket #3754.
On Fri, Jan 23, 2015 at 11:34:35PM +0100, Michael Niedermayer wrote:
On Fri, Jan 23, 2015 at 09:58:41PM +0100, Jean First wrote:
if the openjpeg parameter tcp_rates is not 0 ( using the ffmpeg
compression_level option )
every 2nd image per thread is badly encoded. By moving the
On Fri, Jan 23, 2015 at 07:06:39AM -0700, Roger Pack wrote:
OK I have made modifications to the dshow source so that it adds the
ability to specify capture device by more unique name, capture pin
by name, crossbar device support [this is basically any capture source
with multiple
On Fri, Jan 23, 2015 at 09:58:41PM +0100, Jean First wrote:
if the openjpeg parameter tcp_rates is not 0 ( using the ffmpeg
compression_level option )
every 2nd image per thread is badly encoded. By moving the opj_setup_encoder
function from
libopenjpeg_encode_init to
On Fri, Jan 23, 2015 at 11:57:26PM +0100, Jean First wrote:
On Fri Jan 23 2015 23:39:21 GMT+0100 (CET), Michael Niedermayer wrote:
On Fri, Jan 23, 2015 at 11:34:35PM +0100, Michael Niedermayer wrote:
On Fri, Jan 23, 2015 at 09:58:41PM +0100, Jean First wrote:
if the openjpeg parameter
On date Wednesday 2015-01-21 20:38:20 +0530, Arwa Arif encoded:
I still expect that eq and eq2 should have the same performances,
since the adjust callback is set depending on the parameter values. So
we should have a single eq filter.
Please investigate about why you get different
On 1/23/15, Michael Niedermayer michae...@gmx.at wrote:
The url did just end at a 403 - Snapshots not allowed
We also could point to ffmpeg.org, but the snapshots there are upto 24h old
with the current cronjob
---
src/download |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Signed-off-by: Philip Langdale phil...@overt.org
---
libavcodec/nvenc.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
index c52beb7..e68bbe9 100644
--- a/libavcodec/nvenc.c
+++ b/libavcodec/nvenc.c
@@ -614,6 +614,11 @@ static av_cold int
+ctx-encode_config.encodeCodecConfig.h264Config.maxNumRefFrames =
avctx-refs;
avctx-refs should propably be checked for = 0.
I'm not sure if maxNumRefFrames means the exact same thing as
avctx-refs, but the comment in the nvenc header isn't exactly clear
about that.
This would also
Hi,
2015-01-23 10:54 GMT+01:00 Timo Rothenpieler t...@rothenpieler.org:
This would also forward the ffmpeg default, 1, to nvenc, instead of the
nvenc default, 0, which lets the driver decide what is best. I'm not sure if
this is desireable and how much it affects the quality.
In that case,
On Fri, 23 Jan 2015 04:42:22 +0100
Michael Niedermayer michae...@gmx.at wrote:
diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
index 99467bb..6a0fb5b 100644
--- a/libavcodec/avcodec.h
+++ b/libavcodec/avcodec.h
@@ -503,11 +503,13 @@ enum AVCodecID {
AV_CODEC_ID_SSA,
On Fri, Jan 23, 2015 at 03:31:28AM +0100, Michael Niedermayer wrote:
The url did just end at a 403 - Snapshots not allowed
We also could point to ffmpeg.org, but the snapshots there are upto 24h old
with the current cronjob
---
src/download |2 +-
1 file changed, 1 insertion(+), 1
14 matches
Mail list logo
