On Mar 29, 2013, at 03:03 , Brad O'Hearne wrote:
> On Mar 27, 2013, at 11:48 PM, Kalileo wrote:
>
>> When you encode audio and video, you'll feed each packet with the dts and
>> pts value. The encoding function for video and the encoding function for
>> audio do not know each other, they do n
Thank you for your help. I feel like I am very close. I did as you said, and
it did actually build the libav libraries as I compiled and ran my project
within Xcode. I had to put the location of the libraries in my header search
path to to be able to include the .h files. However, when I tr
On Mar 27, 2013, at 11:48 PM, Kalileo wrote:
> When you encode audio and video, you'll feed each packet with the dts and pts
> value. The encoding function for video and the encoding function for audio do
> not know each other, they do not communicate. You have to set these values
> for them,
Hi, I am trying to write a mpeg player for iOS, for some reason, same code
that calls "av_read_frame" has different result on Windows and iOS. after
calling "av_read_frame", "stream_index" field inside "
AVPacket" has non-zero value in iOS whereas on Windows it is always 0, when
trying to play same
Short answer - there is no easy way for this.
But you can do following:
1. Integrate ffmpeg into xcode project with
"XCode->New->Target->Other->External build system". You can find(google) lot of
examples on how to use it with configure & make. This will give you ability to
"Build", "Clean" an
On Thu, Mar 28, 2013 at 6:03 AM, Brad O'Hearne
wrote:
> On Mar 27, 2013, at 9:25 PM, Clément Bœsch wrote:
>
>> You realize FFmpeg 0.6 is 3 years old right?
>
> I know it very well -- but with FFmpeg documentation / examples, new doesn't
> necessarily mean more helpful. I've spent more hours than
Richard Schilling writes:
> I'm a bit confused, because it seems that FFMPEG should
> allow me to write a new filter and add it to the library.
It definitely does.
Either send your patch (that implements the new filter)
to ffmpeg-devel or set up a git clone and ask for a
merge on ffmpeg-devel
In xcode 3, I simply add a new external build target to which I add the ffmpeg
source tree. Add that target as a dependency to your own target, and you should
be set. If you want to be extra sure, build ffmpeg with the same compiler you
use in your project.
BTW, I have a git project up over on g
