[FFmpeg-devel] Intel QSV encoder

Sorry, sent with wrong subject. Are there any patches supporting Intel QSV encoding that will work with recent versions of ffmpeg on Windows? Thanks. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 04/12] libavcodec: Implementation of AAC_fixed_decoder (LC-module) [4/4]

Are there any patches supporting Intel QSV encoding that will work with recent versions of ffmpeg on Windows? Thanks. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [Patch] no_delay option for librtmp

changes I made to rtmpdump. My sincere apologies for wasting your time. On Thu, Feb 26, 2015 at 9:29 PM, Michael Niedermayer wrote: > On Thu, Feb 26, 2015 at 08:00:49PM -0600, Cary Tetrick wrote: > > No, i just extended what Brian already had. Just an option to to control > > the no d

Re: [FFmpeg-devel] [Patch] no_delay option for librtmp

No, i just extended what Brian already had. Just an option to to control the no delay. I put the changes inside you #if for networking config. On Feb 26, 2015 7:42 PM, "Michael Niedermayer" wrote: > On Thu, Feb 26, 2015 at 03:23:40PM -0600, Cary Tetrick wrote: > > Use t

Re: [FFmpeg-devel] [Patch] no_delay option for librtmp

Use this instead. (sorry, corrected grammatical errors.) On Thu, Feb 26, 2015 at 1:22 PM, Cary Tetrick wrote: > This adds another option to a change authored by Brian Brice < > bbr...@gmail.com> 2015-01-19 > "librtmp: Allow changing the socket send buffer size" &

[FFmpeg-devel] [Patch] no_delay option for librtmp

This adds another option to a change authored by Brian Brice < bbr...@gmail.com> 2015-01-19 "librtmp: Allow changing the socket send buffer size" (Brian is aware of this change). Unlike a previous patch, this has no dependency on rtmpdump. Options to the ffmpeg commandline in support of now a

Re: [FFmpeg-devel] [PATCH] Socket options for librtmp

> > please ping this thread when this happens > > about the patch itself > > IIUC a user using old rtmpdump with new ffmpeg would loose the > rtmp_buffer_size option. > Would it make sense to support the old setsockopt() code for this > case ? > > [...] > > > That's a really good point. So the only

[FFmpeg-devel] [PATCH] Socket options for librtmp

This reimplements a change authored by Brian Brice 2015-01-19 "librtmp: Allow changing the socket send buffer size" (Brian is aware of this change). also negates change by Michael Niedermayer 2015-01-23 10:45:35 "avformat/librtmp: Fix build with --disable-network --enable-librtmp" because it is

[FFmpeg-devel] rtmp patch

Hello, I have a patch I'd like to submit. One part is in the *git://git.ffmpeg.org/rtmpdump repository, and the other in the regular ffmpeg repository (librtmp.c).* *what is the correct way to coordinate this?* *Thanks,* *Cary* _