[FFmpeg-devel] [PATCH] dashenc: Add a segment_start_number option

>From b38a1396e2335e2d0ef2619b5a3890f91c31c8a8 Mon Sep 17 00:00:00 2001 From: Rodger Combs Date: Thu, 20 Nov 2014 01:47:05 -0600 Subject: [PATCH] dashenc: Add a segment_start_number option This defaults to 0 instead of 1 for consistency with the segment encoder --- libavformat/dashenc.c | 6

[FFmpeg-devel] [PATCH] configure: Prevent icl being incorrectly detected as msvc.

Intel compiler xilink will also output the information from the underlying Microsoft linker. A result is that both the Intel info header and the Microsoft info header are output. This means that currently the Intel linker will get detected as the msvc linker incorrectly as configure checks for the

[FFmpeg-devel] Fix restrict bug

*restrict has been replaced by av_restrict. I meet this bug when I compiler for ARM in VS. There should be some other places need to be replaced. Best regards,Jesse 0002-restrict-bug-should-be-replaced-by-av_restrict.patch Description: Binary data _

[FFmpeg-devel] WinRT API support patch

Add WinRT API supports 0001-Add-WindowsRT-support.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] Add WinRT API convert

Hi All, With your help, I can build ffmpeg successfully on WinRT ARM, and I create a path to make ffmpeg support WinRT-API. I have redirect some unsupported apis to WinRT supported apis. I hope you can merge to master. Also, there is a bug in float_dsp_init_vfp.c, about av_restrict -void ff_but

Re: [FFmpeg-devel] Use ffmpeg as an Android stagefright plugin

Michael Chen's good work(libstagefirght ffmepg extension) is especially useful to handle codecs which google is unwiiling to support,for the reason of license fee, such as rv,ra,wma,etc.As for those commonly used codecs h264,aac, it's better way to use original libstagefright and omx hardware cod

Re: [FFmpeg-devel] Dshow Crossbar support

On Wed, Nov 19, 2014 at 02:03:08PM -0800, Zach Swena wrote: > Hi, > > Can anyone elaborate on why direct show devices that use crossbar are not > supported by FFmpeg? Also, what is keeping someone from taking the > crossbar support found in VLC and porting it to FFmpeg, assuming the said > port c

Re: [FFmpeg-devel] [PATCH 07/11] lavu/dict: add av_dict_serialize

On Wed, Nov 19, 2014 at 11:24:06PM +0100, Lukasz Marek wrote: > On 19.11.2014 21:50, Lukasz Marek wrote: > >On 19-Nov-2014 8:59 pm, "Michael Niedermayer" >> wrote: > > > > > > On Wed, Nov 19, 2014 at 02:25:48AM +0100, Lukasz Marek wrote: > > > > On 19.11.2014 01:13, Michae

Re: [FFmpeg-devel] [PATCH 07/11] lavu/dict: add av_dict_serialize

On 19.11.2014 21:50, Lukasz Marek wrote: On 19-Nov-2014 8:59 pm, "Michael Niedermayer" mailto:michae...@gmx.at>> wrote: > > On Wed, Nov 19, 2014 at 02:25:48AM +0100, Lukasz Marek wrote: > > On 19.11.2014 01:13, Michael Niedermayer wrote: > > >On Wed, Nov 19, 2014 at 12:30:53AM +0100, Lukasz M

[FFmpeg-devel] Dshow Crossbar support

Hi, Can anyone elaborate on why direct show devices that use crossbar are not supported by FFmpeg? Also, what is keeping someone from taking the crossbar support found in VLC and porting it to FFmpeg, assuming the said port complied with the FFmpeg code conventions? The current work around seems

Re: [FFmpeg-devel] [PATCH 07/11] lavu/dict: add av_dict_serialize

On 19-Nov-2014 8:59 pm, "Michael Niedermayer" wrote: > > On Wed, Nov 19, 2014 at 02:25:48AM +0100, Lukasz Marek wrote: > > On 19.11.2014 01:13, Michael Niedermayer wrote: > > >On Wed, Nov 19, 2014 at 12:30:53AM +0100, Lukasz Marek wrote: > > >>On 18.11.2014 20:47, Michael Niedermayer wrote: > > >>

Re: [FFmpeg-devel] use openh264 in ffmpeg

On Mon, 2014-11-17 at 13:34 -0800, Timothy Gu wrote: > On Mon, Nov 17, 2014 at 1:18 AM, 王山而 wrote: > > hi > > I want to use openh264 in ffmpeg, how should I do this? > > please give me some help. > > thank you. > > Why? FFmpeg has a native H.264 decoder and I am fairly sure x264 > still > perfor

Re: [FFmpeg-devel] [PATCH 07/11] lavu/dict: add av_dict_serialize

On Wed, Nov 19, 2014 at 02:25:48AM +0100, Lukasz Marek wrote: > On 19.11.2014 01:13, Michael Niedermayer wrote: > >On Wed, Nov 19, 2014 at 12:30:53AM +0100, Lukasz Marek wrote: > >>On 18.11.2014 20:47, Michael Niedermayer wrote: > >how will that work without any way to identify the version or f

Re: [FFmpeg-devel] Patch mpegts_start_pid to allow ATSC PID ranges

Thanks, Yea quoting wikipedia made me cringe too, I did check with the engineer at our network who checked what we use for satellite broadcast which starts at 0x33. Because of the nature of the patch I didn't feel like digging up the specs. Zach On Nov 18, 2014 3:57 PM, "Michael Niedermayer" wr

Re: [FFmpeg-devel] [PATCH 1/2] ffmpeg: last frame duplication heuristic

On Wed, Nov 19, 2014 at 12:53:54PM +, Carl Eugen Hoyos wrote: [...] > > Why does this not work for the sample in ticket #3052? different issue ... fixed [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Breaking DRM is a little like attempting to break through

Re: [FFmpeg-devel] [PATCH 1/2] ffmpeg: last frame duplication heuristic

Michael Niedermayer gmx.at> writes: > This improves the last frames duration with CFR and > when the input durations are inaccurate or missing Please mention ticket #4119. Why does this not work for the sample in ticket #3052? Carl Eugen ___ ffmpeg

Re: [FFmpeg-devel] Bypass video H264 IP UDP Multicast over FLV RTMP

On Wed, Nov 19, 2014 at 01:43:38PM +0700, Dang Duc Hung wrote: > This is ouput full message when I run ffmpeg > [root@Flexi108 ~]# ffmpeg -i udp://x.x.x.x:x -vcodec copy -acodec aac -strict > -2 -b:a 32k -ac 1 -ar 32000 -f flv "rtmp://x.x.x.x/ app=x playpath=x" i suspect a complete reproduceable

[FFmpeg-devel] [PATCH 1/2] ffmpeg: last frame duplication heuristic

This improves the last frames duration with CFR and when the input durations are inaccurate or missing Signed-off-by: Michael Niedermayer --- ffmpeg.c | 29 - ffmpeg.h |1 + 2 files changed, 25 insertions(+), 5 deletions(-) diff --git a/ffmpeg.c b/ffmpeg.c inde

[FFmpeg-devel] [PATCH 2/2] ffmpeg: fix indention

--- ffmpeg.c | 106 +++--- 1 file changed, 53 insertions(+), 53 deletions(-) diff --git a/ffmpeg.c b/ffmpeg.c index ab95e13..63e7714 100644 --- a/ffmpeg.c +++ b/ffmpeg.c @@ -900,62 +900,62 @@ static void do_video_out(AVFormatContext *s,

Re: [FFmpeg-devel] [PATCH] lavf/concatdec: fix timestamp conversion

On date Wednesday 2014-11-19 11:47:53 +0100, Nicolas George encoded: > Le nonidi 29 brumaire, an CCXXIII, Stefano Sabatini a écrit : > > I'm concatenating samples with different time bases. Apparently > > concatdec is setting the first stream timebase as the overall > > timebase, and always assumin

Re: [FFmpeg-devel] [PATCH] lavf/concatdec: fix timestamp conversion

Le nonidi 29 brumaire, an CCXXIII, Stefano Sabatini a écrit : > I'm concatenating samples with different time bases. Apparently > concatdec is setting the first stream timebase as the overall > timebase, and always assuming the timebase is shared for all the input > files. Concatenating segments w

Re: [FFmpeg-devel] [PATCH] lavf/concatdec: fix timestamp conversion

On date Tuesday 2014-11-18 20:30:21 +0100, Nicolas George encoded: > L'octidi 28 brumaire, an CCXXIII, Stefano Sabatini a écrit : > > Use the correct output time base when converting. > > --- > > libavformat/concatdec.c | 21 +++-- > > 1 file changed, 11 insertions(+), 10 deletions

Re: [FFmpeg-devel] [PATCH] lavf/concatdec: add timestamp log

On date Tuesday 2014-11-18 20:26:04 +0100, Nicolas George encoded: > L'octidi 28 brumaire, an CCXXIII, Stefano Sabatini a écrit : > > Help debugging timestamp conversion issues. > > --- > > libavformat/concatdec.c | 11 +++ > > 1 file changed, 11 insertions(+) > > > > diff --git a/libavfo