Lars Hammarstrand writes:
> 2013/2/17 Carl Eugen Hoyos
>
> Could one of you (who is affected by the problem,
> remember that it cannot be reproduced on same
> environments) please test mentioned patch?
> Your problem unfortunately will not be fixed as
> long as you don&#
Jérôme SALAYET writes:
> I someone can tell me if I use the better ones to decode H264 :
>
> m_lpCodecCtx->skip_frame = AVDISCARD_NONREF;
> m_lpCodecCtx->skip_loop_filter = AVDISCARD_ALL;
Do you know what these two are doing?
I consider them extremely useful but if
you don't know what
Lars Hammarstrand writes:
> > 2013/2/20 Carl Eugen Hoyos
> >
> > You reported a bug [1] that cannot easily be reproduced a
> > buggy toolchain appears to be necessary. Less than four hours
> > after your report, a patch was posted that is intended to fix
>
René J.V. Bertin writes:
> On Feb 22, 2013, at 16:35, Carl Eugen Hoyos wrote:
> >
> > Please fix your quoting, Carl Eugen
>
> Works here. Please fix your MUA :P
Should have been:
"Please set your mailer to plain
Nicolás Dato writes:
> Then, I tested it by upgrading to FFMPEG 1.0, everything looks the
> same as with 0.10.5 untill the error "channel element
> 0.2.." appears, after this happens the data is different, the
> channel 1, 2, 4, 5 and 6 are always in 0 (silence), and the channel 3
> has the infor
Brad O'Hearne writes:
> On Feb 18, 2013, at 4:43 PM, Carl Eugen Hoyos wrote:
>
> > The aconvert audio filter uses libswresample for
> > conversions, it may depend on your use case if
> > you prefer the filter or the library.
>
> In reading through FFmpeg
Brad O'Hearne writes:
> On Feb 18, 2013, at 3:50 PM, Carl Eugen Hoyos wrote:
>
> > While I have _no_ idea what the "flv audio codec" could
> > be, please use either the aconvert filter or libswresample
> > directly to convert from one audio format to
René J.V. Bertin writes:
> >In any case, using gdb should quickly show you were the
> >problem lies.
>
> Exactly, but you'd need to build the libav libs yourself,
> with debugging info.
One could argue that on this mailing list, only self-compiled
FFmpeg is supported (because you should get s
René J.V. Bertin writes:
> The SIMD version ran twice as fast as the scalar version
> until I used gcc 4.7, which has auto-vectorisation
Unfortunately, turning auto-vectorisation on triggers
bugs in gcc and is therefore no option;-(
[...]
> > One could argue that on this mailing list, only s
René J.V. Bertin writes:
> I for one assume that the gcc devs would not have provided
> default-on auto-vectorisation if the feature triggered
> (too many) bugs they know of.
You probably also assume the gcc developers do know
the difference between a undecidable and a NP-hard problem?
http:/
René J.V. Bertin writes:
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203
>
> Who cares, as long as they don't release versions
> that fail on too many kinds of code?
What about the ~50 (?) releases since this report was opened?
[...]
> BTW, is there some documentation on ffmpeg.org on
Svetlana Olonetsky writes:
> I can not find how to enable ffmpeg to work with experimental
> codec (equivalent to ffmpeg -strict -2).
See AVCodecContext:strict_std_compliance in avcodec.h
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
Julian Herrera writes:
> After few modifications to libav, it is now able to
> download and play the stream directly from the box.
Please don't forget to send any bug-fixes to ffmpeg-devel.
I can't really comment on the stream-dump question from
a FFmpeg point-of-view, but afaict, you should
Andrew Magill writes:
> Might I suggest eliminating the (max_frames>=1) condition
As in http://git.videolan.org/?p=ffmpeg.git;a=commit;h=a60530e ?
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-u
Joe Flowers writes:
> The only thing I did was change the line
> codec = avcodec_find_encoder(AV_CODEC_ID_MP2);
> to
> codec = avcodec_find_encoder(AV_CODEC_ID_PCM_S16LE);
> When I run "./decoding_encoding mp2", it ends with: "Could not
> allocate -22 bytes for samples buffer".
For PCM codecs,
Joe Flowers writes:
> Does this mean that when encoding raw s16le data to
> AV_CODEC_ID_PCM_S16LE that I should expect a pkt.size = 0 too, even
> though the pkt.data have the correctly encoded data in it?
I did not test but this sounds unlikely / impossible to me.
Carl Eugen
__
Steve Hart writes:
> Could anyone tell me if it is possible to play back and
> seek within a file that is recording at the same time.
That depends on the file format you are using.
(And maybe on the operating system.)
Carl Eugen
___
Libav-user maili
thanh nhan thanh nhan writes:
> I am developing pcm decoding using ffmpeg libraries in Linux.
> I successfully built my program. The problem is the executable
> file size is very big ( ~ 63Mb) even though i just used few
> functions on audio decoding. I wanna downsize the executable
> file as
RenE J.V. Bertin writes:
[...]
Please set your mailer to text-only when sending emails to
this mailing list, this is how your mails look like:
http://ffmpeg.org/pipermail/libav-user/2013-March/003903.html
(This gets completely unreadable after the second reply.)
Carl Eugen
___
RenE J.V. Bertin writes:
> On 4 Mar 2013, at 09:29, Carl Eugen Hoyos wrote:
>
> > (This gets completely unreadable after the second reply.)
>
> Sorry, impossible with this client ...
Then please use another mail client.
> but what happens 2 replies after one posts a me
thanh nhan thanh nhan writes:
> I configured like this:
> ./configure --enable-gpl --enable-libfdk_aac
> --enable-libmp3lame --enable-libtheora
> --enable-libvorbis --enable-libvpx --enable-libx264
This includes all default features of FFmpeg (and a few
external libraries).
If you want smalle
thanh nhan thanh nhan writes:
> >$ ./configure --disable-everything --enable-protocol=file
> >--enable-demuxer=aac,mp3 --enable-parser=aac,mpegaudio
> >--enable-decoder=aac,mp3 --enable-encoder=pcm_s16le
> >--enable-muxer=wav,pcm_s16le
[...]
> So, We cannot remove any library in link command
Danny Chami writes:
> It seems, I have to set the extra data field as the stream
> is not in ADTS format.. any idea how / what I need to set
> the extradata to?
I wonder if adts_decode_extradata() in libavformat/adtsenc.c
would help you?
Carl Eugen
__
Kai2 Li writes:
> In my project, ffmpeg's image conversion call function
> yuv2rgb_c_32 in C file
> /libffmpeg/libswscale/yuv2rgb.c
(This should not happen on x86 where optimized functions
exist.)
> With your please, I would like to ask some questions.
>
> a) Why the function writing by macr
Bjoern Drabeck writes:
> I have got that to build, however compared to builds
> from the zeranoe site (and also builds I have asked a
> friend of mine to make for me using mingw with gcc),
> I always end up with seeking problems.
This is surprising.
Are you sure that you are testing the same
Bjoern Drabeck writes:
> > > I have got that to build, however compared to builds
> > > from the zeranoe site (and also builds I have asked a
> > > friend of mine to make for me using mingw with gcc),
> > > I always end up with seeking problems.
> >
> > This is surprising.
> > Are you sure that
John Orr writes:
> The other day I noticed a commit that "lavc: Deprecate
> the deinterlace functions in libavcodec":
Deprecate != remove ;-)
There will be a better LGPL deinterlacer before the removal.
Carl Eugen
___
Libav-user mailing list
Libav-
Bjoern Drabeck writes:
> > Just guessing here, but it does not seem impossible
> > that the extra steps required to build using MSVC
> > introduce some sort of glue code,
I don't think there is any glue code.
(Remember the gcc bugs you recently found, a but
in msvc - or in the FFmpeg code -
John Orr writes:
> if (whence == AVSEEK_SIZE) {
> #ifndef _MSC_VER
> struct stat st;
>
> ret = fstat(c->fd, &st);
> #else
> struct _stat64 st;
> ret = _fstati64( c->fd, &st );
> #endif
> return ret < 0 ? AVERROR(errno) : (S_ISFIFO(st.st_mode) ? 0
Carl Eugen Hoyos writes:
> > > Just guessing here, but it does not seem impossible
> > > that the extra steps required to build using MSVC
> > > introduce some sort of glue code,
>
> I don't think there is any glue code.
> (Remember the gcc bugs you
Joe Flowers writes:
> I know I am able to see the compiler options used
> when building ffmpeg with the following command.
>
> make V=1
>
> Is there a similar command for seeing the linker options?
I wanted to answer "make V=1" but perhaps you mean
"--extra-ldflags=-Wl,-v" ?
Carl Eugen
___
Bjoern Drabeck writes:
> In most files everything seems to work fine, however
> when I have larger MKV files (for example I got one
> 15 GB movie file), the seeking can take several minutes
This should be fixed in current git head by a patch
from Hendrik.
Thank you for the report, thank you
John Orr writes:
> Parts of ffmpeg source code assume the compiler will remove
> the body of a conditional if the condition is always false
Could you test if the following fixes compilation with
--disable-optimizations with msvc?
Insert a line >> _cflags_noopt="-O1" << after
the line >> _cfla
John Orr writes:
> On 3/12/2013 7:18 PM, John Orr wrote:
> >
> >> If not: Does --enable-small work?
> >
> > I'll try in a little bit.
> >
>
> Nope. --enable-small gets the same link error.
I suspect if this is fixed, it will be easier to
understand how to map -O0 to to something that
works in
John Locke writes:
> Is there a way I can encode just one frame to display?
> I would like to Encode a single H264 from and then be
> able to decode it.
This works fine here with
$ ffmpeg -i input -vframes 1 out.h264
Carl Eugen
___
Libav-user maili
Jorge Israel Peña writes:
> Aside from that, what are the benefits of using libavfilter
> for converting to the target format over using libswresample?
I believe the main benefit is that if you want to (also)
use another filter, you only need to open one filtergraph.
If you are not using anoth
René Calles writes:
> i would like to ask you for help about pointing me where to
> start ( except for programming language ) to understand the
> basics in programmatically using Libav in general. I would
> like to understand the general basics and hope someone could
> point me to some resour
张弘强 writes:
> Recently, I’m doing development to generate video clips’
> thumbnail pic file. But, it is hard without development
> guide, would you please show me some example code for it?
First confirm that ffmpeg (the command line application)
allows you to do what you want, then look into
张弘强 writes:
> ffmpeg -i video_clip.3gp -vframes 1 -ss 00:00:01
> -vf "transpose=1" output.jpg
> (the first frame is not good enough)
Do you mean the first frame is black / does not show the
information you would like to have in your output jpg or
is there something wrong with the transoding
Nicolas George writes:
> > Any idea, why this doesn't happen, when FFmpeg is
> > compiled with MSVC?
>
> Not at all. Possibly assembly optimization that are
> not used.
The problem comes from asm mmx optimization that
does not get compiled with msvc.
Carl Eugen
xftzg writes:
> I want to perform a 'Step Forwards/Backwards' operation in my player
This is not a trivial task.
I believe there are two main approaches:
You can cache as many frames as you believe the user will want
to step backwards or you seek backwards to the next keyframe
and decode (agai
Dolevo Jay writes:
> Do I lose a lot of decoding performance because
> of --disable-yasm option?
If you are compiling for x86 (either 32 or 64bit), you
should definitely compile with yasm for performance
reasons. Many optimisations have been ported from
inline assembly to yasm over the last
Navin writes:
> As I understand, there shouldn't be any licensing issues if one uses
> ffmpeg via the ffmpeg DLL's. As provided by Zeranoe in the
> ffmpeg-win32-shared builds http://ffmpeg.zeranoe.com/builds/Nav
Why should that be?
Ie, if a license issue applies to the FFmpeg project
(in this
Brad O'Hearne writes:
> In lieu of having no luck over several weeks getting video
> + audio samples captured from QTKit resampled and encoded
> with Libav to FLV (with video), I've kind of hit a bit of
> a brick wall. The runnable Mac app and source
> demonstrating this use case hasn't appar
René J.V. Bertin writes:
>
> On 27 March 2013 09:58, Carl Eugen Hoyos wrote:
>
> > not use QTKit? There is definitely a native decoder
> > that outputs the format that (you believe) QTKit
> > offers, and that code would not be OSX specific in
> > the end.
>
Dolevo Jay writes:
> When I don't use --disable-yasm option, I got tons
> of errors just because the yasm version that we are
> using in openembedded is quite old and ffmpeg
> requires a newer version of yasm.
That is unexpected since the configure script tests
the yasm version, you should t
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
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
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
Thomas Sharpless writes:
> I solved the problem by replacing the git clone
> with a release tarball -- I have no need to follow
> the latest snapshot.
Please understand that this is not suggested unless
you are a distributor.
(The download page also offers a tarball of the
latest snapshot.)
Lars Hammarstrand writes:
> If this really is a regression, please consider
> using git bisect to find the version introducing
> it. (This isn't trivial with FFmpeg, but I will
> support you.)
>
>
> Ok, thanks - although I believe it will be a quite
> lengthy and cumbersome process
It usually
Lars Hammarstrand writes:
>> >> If the crash is reproducible with FFmpeg, you don't need xbmc to test.
>> > Sounds very good, but how? With the ffmpeg tools (ffplay, etc) as a
>> > stand alone package directly on ios?
>>
>> Exactly. This makes search for the problematic commit much easier,
>>
Lars Hammarstrand writes:
> Tested to run ffmpeg (the tool) and it crashes every
> time exactly on the same spot as xbmc!
Thank you for testing!
> Has n1.2 ever been tested on IOS?
Did you test it before?
> Question: shall I create a ticet on ffmpeg.org or at
> libav.org (since the ARM HW o
Lars Hammarstrand writes:
> (gdb) disass $pc-32,$pc+32
Please add the register dump, some developers can
see the problem if it is present.
Thank you, Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/lib
Lars Hammarstrand writes:
> > Could you run the testsuite (make SAMPLES=path fate) on the
> > iPhone? This would allow to verify if only H264 is affected
> > or also other codecs.
>
> 4. Sorry, you have to be a bit more specific on this one
> since I'm not a ffmpeg core developer. FATE is a rat
Lars Hammarstrand writes:
> > (I will open a ticket if all information is available,
>
> Great, here are some additional configure flags.
> Please tell me if you need anything else to open a ticket!
Please test if --disable-neon and -cpuflags -neon fix
the problem.
> I've no intention to com
Lars Hammarstrand writes:
> > but please test if -cpuflags -neon
> > or --disable-neon helps.
>
> Forgot to ask. Do any of these flags replace any
> other flags or should they be used in conjunction
> with existing configure flags as below?
> --enable-neon
I suspect it is not a good idea to
Carl Eugen Hoyos writes:
> > I've no intention to compile hundreds of different
> > versions by hand you know. :) :)
>
> 14 will be sufficient, I will guide you.
To elaborate:
You tell me which version does work and
which version crashes, and I will tell
you which
Lars Hammarstrand writes:
> > You tell me which version does work and
> > which version crashes, and I will tell
> > you which versions to test.
>
> You have to supply a more detailed action-plan
> to operate git bisecting in this case since the
> last (and current) working version of ffmpeg f
Lars Hammarstrand writes:
> > Exactly 14 iterations, please trust me, I am doing
> > this quite often.
>
> Ok, I'll trust you completely
(I was actually wrong: 14 iterations == 15 compiles)
> Before starting, please test -cpuflags -neon and
> --disable-neon to make 100% sure that we know what
Lars Hammarstrand writes:
> > > Success, --disable-neon and -cpuflags -neon did the trick!
> >
> > I hoped you would first test -cpuflags -neon on
> > a build with "--enable-neon" and then "--disable-neon"
> > without any cpuflags - sorry for being unclear!
>
> Ok, I'll test that too!
Don't.
It
Lars Hammarstrand writes:
> > (I was actually wrong: 14 iterations == 15 compiles)
>
> That will take roughly 7,5 hours (give or take) in a
> worst case scenario.
(There is no worst case scenario, the amount of time is
roughly the same in all scenarios.)
Could you elaborate?
Does cross compi
Lars Hammarstrand writes:
> Initially I want to run the fully automated git
> bisect run.
It appears that you know much more about
bisecting FFmpeg than I do. If you report
the first failing commit here on this
mailing list I will forward it to the
bug tracker / the relevant developers.
If
Lars Hammarstrand writes:
> Ok, can you please confirm I'm at the correct starting point:
>
> $ git bisect good 3c5fe5b
Only you can answer if 3c5fe5b works ok, if it does,
please test a1bcc76.
(In case this is not obvious: Because of the
peculiarities of the FFmpeg project, your
script may
Lars Hammarstrand writes:
> > > That will take roughly 7,5 hours (give or take) in a
> > > worst case scenario.
> > (There is no worst case scenario, the amount of time is
> > roughly the same in all scenarios.)
>
> Worst case scenario is when you need to perform all
> iterations before you find
Lars Hammarstrand writes:
> 0. 3c5fe5b# Works OK
> 1. a1bcc76 # Works OK
> (got avconv but worked with the same runtime flags as ffmpeg)
Sorry, that was my fault.
> 2. 3860e34 # Works OK
Please test 353dbaa now.
If 353dbaa works ok, please test 6b2e650
If 353dbaa does no
Lars Hammarstrand writes:
> Run Status: ffmpeg-d0b7e83: Failed. (rc=132)
> Run Status: ffmpeg-8bee8f7: OK.
Does --disable-thumb fix the crashes?
(Or --enable-thumb?)
In any case: Please run your configure line for
both above versions and post the diff for the
following two files here:
config.
Lars Hammarstrand writes:
> --as='/Users/Shared/xbmc-depends/buildtools-native/bin/gas-preprocessor.pl
Which version of gas-preprocessor.pl is this?
A version prior to October 2012 would likely
explain the crashes you are seeing.
Carl Eugen
___
Liba
praks411 writes:
> Ok after setting pts, dts and duration of output
> packets as per do_streamcopy function in avconv.c
Please note that avconv is known to contain many bugs
(some of them security relevant) and is therefore
unsupported, please see http://ffmpeg.org/download.html
for support
praks411 writes:
> I'm debugging in vc++ 2012 with libav 9.1.
This fork of FFmpeg contains several hundred known bugs that
are not reproducible with FFmpeg, some of them security
relevant. Please understand that we therefore cannot support
it on this mailing list, please see
http://ffmpeg.or
Harald Jordan writes:
> As I am on windows and MSVC (this has reasons),
> I cannot really have a look where exactly the
> error is
Without a backtrace (and without source code),
this will be impossible to fix.
Either use msvc or gdb to get a backtrace.
Carl Eugen
___
Reuben Scratton writes:
> I maintain a video player app on Android and recently had
> occasion to upgrade it's FFmpeg from 0.8.6 to 1.1.3.
Please update to 1.2 which is binary compatible and contains
many bug fixes and features not present in 1.1.
> It seems that the 1.1 AAC decoder only outp
Lars Hammarstrand writes:
> 1) Distribute a prepackaged version of gas-processor.pl
> that works, together with ffmpeg.
Very, very definitely:
No.
> 2) At the very least, update the docs (docs/platform.texi)
[...]
Hm.
3) Write a mail to yuvi and ask him to merge the
changes.
(Done and done)
Bogdan Popa writes:
> I'm receiving raw camera frames in the RGB32 little
> endian format and converting them to YUV420P frames
> which I then encode to H264 and it's working fine
> except for one thing: the colors are all messed up
Instead of PIX_FMT_RGB32 (which depends on endianess),
try
andro writes:
> I'm looking for a way to mux mjpeg (compressed) video
> data into a video container like mp4 or avi.
$ ffmpeg -i input -vcodec mjpeg out.avi
> (I'll also need to add audio in the future) .
$ ffmpeg -i input -vcodec mjpeg -acodec ac3 out.avi
> I do not want decode the MJpeg da
Lars Hammarstrand writes:
> > 3) Write a mail to yuvi and ask him to merge the
> > changes.
>
> Mailed an update to ffmpeg-devel regarding the docs
> that David Conrad intercepted and the repo is now
> refreshed with Mans changes.
(Sorry: I had written a mail to him several days ago
and when
praks411 writes:
> 1. If I play the output (.avi) file in vlc then
> I'm just able to play video there is no audio.
How does ffmpeg -i output.avi look like?
(This sounds like a well-known bug in vlc.)
Carl Eugen
___
Libav-user mailing list
Libav-use
Lars Hammarstrand writes:
> One idea could be to add an "gas" option to configure,
> like "--gas=/abosolute/path/to/gas-preprocessor"
This does already exist afaik.
> (pls note that this does not work:
> "--as=/absolute/path/to/gas-preprocessor.pl /path/to/as..." ).
Please test "/path/to/g
praks411 writes:
> The output file is perfect. It is working in both
> windows and vlc
It appears I misunderstood, I thought the file does
not work with vlc.
Sorry for the noise, Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://f
Carel Combrink writes:
> [rawvideo01dc8c40] = Invalid pixel format.
> Last message repeated 1 times
> Input #0, matroska,webm, from 'Recording.avi':
> Metadata:
> ENCODER : Lavf55.1.100
> Duration: 00:00:00.70, start: 0.00, bitrate: N/A
> Stream #0:0: Video: ra
Reuben Scratton writes:
> If I compile with -mfpu=neon then FFmpeg blows up
> with SIGILL (ILLOPTPC) when run on a non-Neon CPU.
> If I compile with -mfpu=vfvp3 then FFmpeg runs fine,
> but presumably without the optimized code
Did you test this? (with a debugger)
I don't know but it seems v
Reuben Scratton writes:
> License: nonfree and unredistributable
But this is certainly not the configure line you
use for the version that your Android users
tested and protested performance-wise or am I
wrong?
Carl Eugen
___
Libav-user mailing li
Reuben Scratton writes:
>>> License: nonfree and unredistributable
(If you believe something is unclear about
above message and that it does not explain
that you may not legally distribute the
resulting binary, please tell us!)
>> But this is certainly not the configure line you
>> use for t
Justin writes:
> the ffmpeg's configuration has no disable-asm parameter.
This is not correct.
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
writes:
> I read many hours to understand pts in libav.
> But it seems there is no common simple way to retrieve.
> I used the method from http://dranger.com/ffmpeg/.
This is quite outdated, please have a look at the
examples in doc/examples.
[...]
> Dieses Dokument ist vertraulich zu behand
andro writes:
> But If I want to write a little program using
> libav* library to do the work .
Please look at the example code in doc/examples
in your git checkout.
Please do not top-post here, Carl Eugen
___
Libav-user mailing list
Libav-user@ffm
Steffen writes:
> I took a look at the decoding examples. There the
> AVFRame->pts field is used.
> But I have some videos where this field is always 0.
What kind of videos?
You can use -debug_ts to see if FFmpeg (the application)
sees the correct pts (and where it comes from).
Carl Eugen
__
Brad O'Hearne writes:
> Is there a way to encode an FLV file with AAC audio
> rather than the ADPCM which defaults when creating an
> output format context oriented to FLV? The output
> format context defaults to the ADPCM_SWF codec, but
> when I tried to change it to AAC (or SPEEX or MP3) I
>
Brad O'Hearne writes:
> On Apr 17, 2013, at 9:36 AM, Carl Eugen Hoyos wrote:
>
> > For mp3 and speex, you have to compile FFmpeg with
> > external libraries (lame and libspeex), to use the
> > internal aac encoder you have to pass the equivalent
> > of
Tanim Islam writes:
> Is it possible to encode from a set of SVG frames,
>rather than PNG frames,
FFmpeg does not support decoding svg.
(Patch welcome.)
> in avconv?
avconv is known to contain several hundred bugs not
present in ffmpeg, some of them security-relevant,
please understand that
Brad O'Hearne writes:
> Does anyone know what is different about processing with
> an AAC encoder vs a ADPCM encoder
One takes s16 (which you probably expect), the other takes
flt-p (which is *not* flt, at least not exactly).
You can test if mono works to find out if planar is your
issue.
Car
Mert Gedik writes:
> But when I configure with --enable-asm, the audio stream
> which using mpx(mp1,mp2,mp) codec sounds squeaky.
Did you test --disable-thumb and --disable-neon?
Please try to find the function that is
responsible for the problem.
Carl Eugen
_
Mert Gedik writes:
> The sound problem happens on device only when
> configure ffmpeg with --enable-asm optimization
> parameter, no sound problem exists on simulator
> with same configuration...
Is the sound also reproducible with --disable-neon
or --disable-thumb ?
(Honestly: As long as w
Mert Gedik writes:
> ./configure ... --enable-asm --disable-neon
> ---> distortion on sound.
>
> ./configure ... --enable-asm --disable-thumb
> ---> distortion on sound.
I believe if you test the following configuration options,
it should allow to further narrow down the search for the
respon
Mert Gedik writes:
> But when I configure with --enable-asm, the audio stream
> which using mpx(mp1,mp2,mp) codec sounds squeaky.
I suspect that this is ticket #2473 which I had to
close because no information whatsoever was provided
that allowed to analyze the problem.
Thanks to you, there i
Julian Herrera writes:
> Which gas-preprocessor.pl version are you using? I
> came accross a similar issue that affected only
> mp* audio on iOS and I found a solution by using
> this preprocessor:
Please only use the official gas-preprocessor script
from https://github.com/yuvi/gas-preproce
Lars Hammarstrand writes:
> The ffmpeg implementation seems to supports DXVA2
> hw-accl codec for H.264/MPEG-4 & MPEG-2 (i.e Hi10P)
> but I only get CPU decoded and swscale converted
> working properly.
Since this is not clear (for me, I am not a native
speaker) from your message:
You do rea
Hendrik Leppkes writes:
> There was a bug a short while back which required
> you to pass --enable-dxva2 to configure because the
> auto-detection was faulty, but this was fixed in HEAD,
> and hopefully backported to 1.2 (not sure on this part).
This would have needed some advanced technology
Hendrik Leppkes writes:
> http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=2e2ec66
This cannot be a fix for the mentioned problem, Lars
explained that he also tested git head.
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://f
Pradeep Karosiya writes:
> Bit Rate = 128000 (set by me not sure what to take)
Did you test with a higher value?
Also with a significantly higher value?
Did you test with ffmpeg (the application)?
Carl Eugen
___
Libav-user mailing list
Libav-user@ff
401 - 500 of 1560 matches
Mail list logo
