Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?

Lars Hammarstrand writes: > > Not all iOS devices are born equal in terms of > > their ARM core. Which device crashed for you with > > bad instruction at > > >    vmov.i8 q0,  #128 This function has been unchanged for three years. If this really is a regression, please consider u

Re: [Libav-user] makefile problem on win32 MinGW

Thomas Sharpless writes: > ./configure: line 4652: git: command not found > > The very last part of the configure script fails but > it looks to me like all it is trying to do is make > sure the source code is totally current. It looks if the repository you are using is current, you don't ha

Re: [Libav-user] Video and audio timing / syncing

On 30 Mar 2013 07:56, "Kalileo" wrote: > Another thing you can do is to take a stream which plays correctly, and analyze the dts values of audio and video used there. This might show you right away where you're different. This is rarely practical: there are multiple ways to construct an FLV movie

Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?

2013/3/30 Alex Cohn > On 30 Mar 2013 02:32, "Lars Hammarstrand" > wrote: > > 1. XBMC is stopping at: > > ff_pred8x8_128_dc_neon: (libavcodec/arm/h264pred_neon.S) > > 0x5bc84: cdpeq p15, #5, c15, c0, c0, #4 <-- Thread 3: > EXC_BAD_INSTRUCTION (code=EXC_ARM_UNDEFINED, subcode=0xe50ff80) > > 0x5b

Re: [Libav-user] Video and audio timing / syncing

On Mar 30, 2013, at 04:49 , Brad O'Hearne wrote: > On Mar 29, 2013, at 2:12 PM, Kalileo wrote: > > All of the below really helps my understanding...I think a few more things I > need to know to fill in the gaps: >>> To the best of what I've been able to determine from mailing list >>> respons

Re: [Libav-user] Video and audio timing / syncing

On 30 Mar 2013 07:11, "Kalileo" wrote: > > On Mar 30, 2013, at 04:25 , Alex Cohn wrote: >> >> I beg to differ from Kalileo in one aspect: the codec may care about pts, but on the other hand it may not. > > We do not differ here. ;-) > Codec as in decoder for video or audio, i don't see that, (ex

Re: [Libav-user] Video and audio timing / syncing

On Mar 30, 2013, at 04:25 , Alex Cohn wrote: > I am sorry I cannot write a detailed answer right now from my phone. > Basically, the pts you set before encoding should be the right one, because > you have little control over the delay introduced by the encoder. But this > depends on the codec

Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?

On 30 Mar 2013 02:32, "Lars Hammarstrand" wrote: > 1. XBMC is stopping at: > ff_pred8x8_128_dc_neon: (libavcodec/arm/h264pred_neon.S) > 0x5bc84: cdpeq p15, #5, c15, c0, c0, #4 <-- Thread 3: EXC_BAD_INSTRUCTION (code=EXC_ARM_UNDEFINED, subcode=0xe50ff80) > 0x5bc88: svclt #57436 Not all iOS dev

[Libav-user] makefile problem on win32 MinGW

I have built older versions of ffmpeg on my Windows system using MinGW, but the latest snapshot refuses to build. After a bit of fuss I got a configure command to (almost) run to completion: $ ./configure --prefix=.. --enable-gpl --enable-version3 --disable-programs > --d > isable-doc --enable-li

[Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?

Hi! We (at xbmc) are having problems with the new ffmpeg n1.2 libs on IOS (ref: XBMC work in Progress FFmpeg v1.1 ... ). I did a test drive with https://github.com/kolyvan/kxmovie but it seems to suffer from the same problem.

Re: [Libav-user] Double free/corruption problem.

I am having the same problem where I can not free my buffer after I allocate my custom AVIOContext. Did anyone find a solution to this? Any help would be very thankful. , Diego ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman

Re: [Libav-user] Video and audio timing / syncing

On Mar 29, 2013, at 2:12 PM, Kalileo wrote: All of the below really helps my understanding...I think a few more things I need to know to fill in the gaps: >> To the best of what I've been able to determine from mailing list responses, >> doc, and my testing, it would appear that these settings

Re: [Libav-user] Video and audio timing / syncing

I am sorry I cannot write a detailed answer right now from my phone. Basically, the pts you set before encoding should be the right one, because you have little control over the delay introduced by the encoder. But this depends on the codec and on the container. I beg to differ from Kalileo in one

Re: [Libav-user] Video and audio timing / syncing

On Mar 30, 2013, at 03:28 , Brad O'Hearne wrote: > On Mar 28, 2013, at 11:53 PM, Kalileo wrote: >> Hi Brad, >> >> when you start writing the packets (muxing them), you give each audio and >> video packet a DTS (and PTS) value. You can start at zero. >> >> At the start you give the first audi

Re: [Libav-user] Video and audio timing / syncing

On Mar 29, 2013, at 1:43 PM, Alex Cohn wrote: > Note that the time base may be set separately for the container and for the > video stream (depends on the format and on the codec). Greetings Alex! Geesh...so many folks taking the time to answer, posting to the Libav-user mailing list appears t

Re: [Libav-user] Video and audio timing / syncing

> If I completely turn off the writing of all audio frames, there is absolutely no change in video rendering -- it still renders video frames at twice the speed. This may sound oversimplified, but maybe it will be OK to set the PTS to 2× the value you tried today. Note that the time base may be s

Re: [Libav-user] Video and audio timing / syncing

On Mar 28, 2013, at 11:53 PM, Kalileo wrote: > Hi Brad, > > when you start writing the packets (muxing them), you give each audio and > video packet a DTS (and PTS) value. You can start at zero. > > At the start you give the first audio and the first video packet the same > value. For every

[Libav-user] How can I free data buffers missed by avcodec_free_frame?

In the description for avcodec_free_frame, it states: "Warning: this function does NOT free the data buffers themselves" I have allocated my buffers as such: int curAVFramesize = avpicture_get_size(PIX_FMT_YUV420P, ccontext->width, ccontext->height); uint8_t* curAVFramePicBuffer = (uint8_t*)(av_m