Re: [Libav-user] ff_log2_tab defined multiple times in the fmpeg 1.1 libraries, bug or feature ??
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't comment on the patch;-( It appears that this mail was unclear, I am sorry about it, I am not a native speaker! Let me try again: 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 this bug and a message was sent to this mailing list to ask if the patch fixes your compilation problem: [2]. Four days later, I asked again for a test: [3] Please understand that it is neither necessary to report this problem on another mailing list (it is actually not a good idea, reporting bugs here is 100% ok), nor is it necessary to explain why you have to use this toolchain (we do try to support slightly broken environments, but please understand that we need some help on these). Is it also not really a good idea to explain to the FFmpeg developers about performance issues and non-issues, it is safe to assume that there are not many projects that are more performance-driven than FFmpeg. As said, what is needed is somebody to test if the patch fixes the reported problem. Please disregard this email if you are not interested anymore in fixing this bug. Thank you for your support, Carl Eugen 1: http://article.gmane.org/gmane.comp.video.ffmpeg.libav.user/9926 2: http://thread.gmane.org/gmane.comp.video.ffmpeg.libav.user/9941 3: http://thread.gmane.org/gmane.comp.video.ffmpeg.libav.user/9964/focus=9993 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] CodecContext Optimization to Decode H264
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 they exactly do, it is very bad to set them. > m_lpCodecCtx->skip_idct = AVDISCARD_ALL; > m_lpCodecCtx->idct_algo = 1; I suspect they have no effect on H264 decoding, generally I don't think you would use them if they would work. > m_lpCodecCtx->has_b_frames = 0; > m_lpCodecCtx->refs = 1; Documentation says "decoding: Set by libavcodec", so you should definitely not set them. > av_opt_set(m_lpCodecCtx->priv_data, "preset", "ultrafast", 0); > av_opt_set(m_lpCodecCtx->priv_data, "tune", "zerolatency", 0); I may absolutely miss something, but these look like encoding parameters. > I also set the codec flags like this : > > if(m_lpCodec->capabilities&CODEC_CAP_TRUNCATED) > m_lpCodecCtx->flags|= CODEC_FLAG_TRUNCATED; I would expect that this has a performance hit, only use it if you know why. > // Enable faster H264 decode. > m_lpCodec->capabilities |= CODEC_CAP_FRAME_THREADS; I don't think you can set codec capabilities. > m_lpCodecCtx->flags |= CODEC_FLAG_LOW_DELAY; (I am not convinced you should always set this flag, but I probably don't know enough to really say this.) > m_lpCodecCtx->flags2 |= CODEC_FLAG2_FAST; This is the only dangerous flag, it means: "I know that my input is 100% error free, I don't mind if libavcodec crashes on invalid input." (Depending on your use-case this may or may not be what you want, note that the performance impact is very, very small, so you probably don't want it.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ff_log2_tab defined multiple times in the fmpeg 1.1 libraries, bug or feature ??
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 > > this bug and a message was sent to this mailing list to ask > > if the patch fixes your compilation > > Hi Carl! Sorry about that but I've totally missed the fact > there was already a fix available for test. Can you please > provide a link to where I can find it? (You did answer the mail where it was mentioned and you were asked for a test...) You have cut the relevant part of my message: ;-( http://thread.gmane.org/gmane.comp.video.ffmpeg.libav.user/9941 (You have to google the subject mentioned in this mail to find the patch.) Please fix your quoting, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ff_log2_tab defined multiple times in the fmpeg 1.1 libraries, bug or feature ??
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-text." Sorry, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Decoding an AAC-LATM 5.1 audio returns errors and only 1 channel with data
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 information (and it looks OK). This should be fixed in current git head, thank you for the report! Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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 source, it would appear > that the libswresample/swresample.h and > libavresample/avresample.h are very similar. > Are these libraries interchangeable No, I don't think so (libavresample was written to be not interchangeable with libswresample so I would at least be surprised). > -- is there any reason to use one over the other? Yes, only libswresample is supported, libavresample is not even built by default. Please read this article if you need more information: http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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 another. > > This has turned out to be much more difficult than expected. Before you start debugging (the cast to sourceData looks suspicious): Did you look at doc/examples/filtering_audio.c and doc/examples/resampling_audio.c ? I suspect using the aconvert filter has the advantage that you can do other changes to the audio without additional code (and bugs). In any case, using gdb should quickly show you were the problem lies. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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 support wherever you download your binaries). > There's another thing that's nagging me. IIUC, the goal here > is to convert a buffer of (C) floats into signed shorts. I > have some difficulty believing that doing this through a > generic workhouse function can be more efficient than > writing a simple loop and let a good optimising compiler > create the best assembly out of it ... Such a very implausible claim definitely needs some performance numbers. (Or in other words: No, current compilers are unable to optimize code the way you expect them.) Please fix your quotes, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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 self-compiled > > FFmpeg is supported > > One could, but that argument would not be supported by > the mailing list's own title: > "This list is about using libavcodec, libavformat, > libavutil, libavdevice and libavfilter. " > > The concept "using libav*" doesn't imply anything about > how you obtained the libraries We only provide sources and therefore only support self-compiled versions. And since this is a mailing list for developers, it makes absolutely no sense to argue "compilation is so difficult", especially as it is only a question of doing "./configure && make" if you are not cross- compiling. > and indeed, who built the libraries you're using > (as opposed to which and how) should be irrelevant. > It does however constitute a clear invitation to > post questions like "how do I convert an audio format". And such questions are welcome here! As said, I think a cast should not be necessary when calling swr_convert(), so this is a good start, but gdb will probably tell you more exactly. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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://gcc.gnu.org/bugzilla/show_bug.cgi?id=11203 Seriously: If auto-vectorisation works (for some gcc versions) and has a performance-gain, please send a patch. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Converting audio sample buffer format
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 how to > create patches after having hacked around in the > source tree? http://ffmpeg.org/developer.html > And a related question: what's a good way to perform > real-world benchmarks on the libraries? Apart from time there are START_TIMER and STOP_TIMER macros in libavutil. > Can ffmpeg be compiled so that it collects performance > statistics on specific operations? Definitely. > Because I presume no one will be interested in patches > that give a performance gain that's significant > (reproducible) but completely irrelevant on the overall > timescale of operations... This is simply plain wrong. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] how to allow '-strict -2' in C++
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 http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Dump unmodified MPEGTS from RTSP streaming server
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 simply start dumping everything that comes from the protocol reader to a file as soon as the user starts time-shift. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Misidentification of data stream as AAC_LATM
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-user
Re: [Libav-user] Why (c->frame_size = 0) ? -> Could not allocate -22 bytes for samples buffer
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, frame_size is 0 and calling av_samples_get_buffer_size() makes no sense. av_samples_get_buffer_size() returns AVERROR(EINVAL) which happens to be "-22". Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Why (c->frame_size = 0) ? -> Could not allocate -22 bytes for samples buffer
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Record, seek and play
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 mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libav-user list post!
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 much as possible. Please provide your current FFmpeg configure line / start with --disable-all and enable everything you need. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libav-user list post!
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libav-user list post!
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 message > is hardly my responsibility You misunderstand: I did not mean that your mail is readable and only gets unreadable if somebody replies but that your email is already unreadable (for some reason you removed the link above) and it will not get better after the next reply. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libav-user list post!
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 smaller libraries, you have to change your FFmpeg configure line (it cannot help if you change something about your linking command for your own application x2pcm, that cannot work!) - since you did not explain exactly which features you need, I can only guess but I suggest you start with a line like the following and test, you will find many missing features: $ ./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 Please understand that this is certainly not exactly what you need, it is meant to help finding the right options. You can further decrease the size of the libraries by using --disable-all instead of --disable-everything but you need to enable even more features in that case. --disable-debug should not be necessary since I expect you will strip your final executable anyway, but you can of course add it to configure as well. Please google for "top-posting" and please avoid it here, it is considered rude. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libav-user list post!
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. > What we can do is downsize the libraries. Am i right? Yes. > All of features i need is: decoding the aac, mp3, > ogg, flac, wma, m4a, 3ga, wav Then please try to add them to the configure line I posted above and start testing. The configure options --list-decoders, --list-parsers etc. will help you. If there is a feature / decoder / demuxer that you fail to add, ask again! > into pcm file and then resample pcm file into > expected sample format, number of channel and > sampling rate. Add --enable-filter=aresample to allow resampling etc. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Packing Raw AAC in MPEGTS & Extradata
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Questions about ffmpeg's image conversion
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 macro? > b) Whether the function can be optimized? > > c) Has there some updates or new version? > > d) Will ffmpeg have ARM platform specialized version or patch? > My hardware is Sumsang Pad GT-P5110 (1G dural core, > 1G RAM, 32G SD card), ffmpeg version is 0.11.1 Is this ARM hardware? If yes, nobody added arm optimizations for libswscale so far, look into the subdirectories in libswscale to see some examples (x86, ppc, sparc and bfin, consider looking at sparc if you really only need yuv2rgb32, x86 contains a myriad of optimizations more). If you plan to work on adding optimizations, please update to current git head and please read http://ffmpeg.org/developer.html (And if you plan to implement this, ffmpeg-devel is of course the right mailing list for implementation- related question, it isn't clear to me though if you want to do that.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 versions? Did you try to disable optimizations? > In most files everything seems to work fine, however > when I have larger MKV files (for example I got one > 15 GB movie file) Does mkvalidator report the following? "Unnecessary secondary SeekHead was found at " (followed by a very large number) This would indicate ticket #2263, we don't even know how to produce such a file... [...] > I used this configuration (which contains the essentails > I need: LGPL, v3, dxva2 support, shared dlls): Completely unrelated: Could you explain why you "need" v3 ? Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 versions? > > I have downloaded the zeranoe build marked as 1.1.3 and I > also got http://ffmpeg.org/releases/ffmpeg-1.1.3.tar.bz2 > and built that myself.. so I would say it's the same version. Could you also test current git head? (Or, since that is atm unstable origin/release/1.2) If it does not work, can you test if ffmpeg (the application) allows to reproduce the problem? If not, a test-case will probably be required... > > Did you try to disable optimizations? > > For some reason I get build errors as soon as I use > --disable-optimizations: > > LDlibavutil/avutil-52.dll > Creating library libavutil/avutil.lib and object libavutil/avutil.exp > cpu.o : error LNK2019: unresolved external symbol _ff_get_cpu_flags_ppc > referenced in function _av_get_cpu_flags Dead-code-elimination is always required to build FFmpeg, try --extra-cflags=-O1 (or actually the msvc equivalent). (Please set your mailer to text-only if possible.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Is there no LGPL deinterlacer left
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-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 - is not less likely.) > > and that might include seek-related code that is > > particularly non-optimal. It could of course be related to the glue code mingw uses... > > Is there any reason to build ffmpeg with MSVC, rather > > than using mingw with msys or a mingw cross-compiler > > on a simple linux VM? Apart from the fact that I still cannot understand why building with a cross-compiler in a VM can be easier than doing a native mingw build: For years, this was one of the most often requested "features", probably to allow debugging within msvc. > the main reason was basically just for convenience > (build it all from just one place; also linux environments > are new to me).. seemed to work fine at first, and was > quite quick to set up... Thank you for posting this, I wondered how difficult it is! > But right now am just thinking about setting up Ubuntu to > see if I can get it to build correctly like that.. I believe you had to install mingw to use msvc, the gcc compiler you installed should work fine, no reason to setup Ubuntu to compile for win32. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 :
> st.st_size);
> }
> #ifndef _MSC_VER
> ret = lseek(c->fd, pos, whence);
> #else
> ret = _lseeki64(c->fd, pos, whence);
> #endif
Perhaps you could (fix the whitespace and) send a patch
to ffmpeg-devel or set up a git clone to allow merging?
Thank you for the solution!
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 recently found, a but > in msvc - or in the FFmpeg code - is not less likely.) But that is not the case here. > > > and that might include seek-related code that is > > > particularly non-optimal. > > It could of course be related to the glue code mingw > uses... ;-)) See libavformat/os_support.h as explained by Hendrik I suspect a change in line 34 is sufficient. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Seeing the linker options when make-ing ffmpeg?
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 for the analysis! Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 >> _cflags_size="-O1" << which should be line 2746. If not: Does --enable-small work? Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Building with MSVC toolchain resulting in seeking problem?
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 msvc_flags() in configure. I looked here to find out what could make the difference: http://msdn.microsoft.com/en-us/library/k1ack8f1%28v=vs.100%29.aspx But did not find anything obvious, testing will be necessary. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Encode just one frame [H264] or others?
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 mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] libswresample vs libavfilter for target format conversion
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 another audio filter, there probably is no benefit (except that you may or may not prefer the filter interface over the libswresample interface). Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] How to get started with libav basics
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 resource where i can find that. Please download current FFmpeg and look into doc/examples: http://ffmpeg.org/download.html Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] How to extract a H264 video frame (container is 3GPP/MP4) into a JPG File (with libavformat and libavcode) ?
张弘强 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 doc/examples to learn how to use libavformat and libavcodec. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] 答复: How to extract a H264 video frame (container is 3GPP/MP4) into a JPG File (with libavformat and libavcode) ?
张弘强 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 like for example a non-keyframe gets encoded and the output image is broken? If that is the case, please provide your complete, uncut console output and a sample. Please do not top-post here, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Help with a couple of bitmap scaling issues
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] How to Frame Step Forwards/Backwards?
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 (again) until the requested frame (this may take considerable time). If your problem is that you cannot seek backwards to a keyframe, please post code that allows to test this. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] --disable-asm --disable-yasm options
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 years. (yasm cannot be used when compiling for other hardware.) --disable-asm is relevant for all (most) platforms, you should never use it except for debugging (as with --disable-yasm), if you have any problems when not using it, please report them either here or on trac. Please understand the project is called "FFmpeg", find the current version at http://ffmpeg.org/download.html Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Libav, licensing, h.264
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 case a license issue that applies to one of the libraries Brad wants to use, namely libx264 which is - under normal circumstances - available under the terms of the GPL, which makes FFmpeg linked to libx264 automatically GPL) not apply to the Zeranoe builds that are made from FFmpeg sources? Please do not top-post here. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] QTKit -> Libav: has it ever been done?
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 apparently shed any > light on why the audio being encoded is junk. The reason is probably that most developers do not own OSX hardware and therefore cannot test your code. Did you already try to produce a test-case that does 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. You could start with one of the examples in doc/examples and change it to your needs. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] QTKit -> Libav: has it ever been done?
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. > > Are you saying there's a decoder that outputs the > decoded content in QTSampleBuffer format, tested to be > accepted as input by QTKit? No, I am not saying that. (I don't know.) I am saying that for every (input) format that the resampler (both the library and the filter) accepts, a (at least one) native decoder exists that produces this format (and can therefore be used to test the code that you use to resample). It is of course possible that QTKit uses a completely different format, but one way to find out is to test your resampling wrapper code with a decoder for which you know the actual format. Note that an endianess issue is very unlikely because FFmpeg only supports native endian audio formats (as opposed to codecs), a signed / unsigned problem is of course possible but this should be relatively easy to verify. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] --disable-asm --disable-yasm options
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 therefore get only one error: Please provide your configure line and the first error (and the versions you are testing). > Updating yasm is fairly easy but then I got multiple > of tons of different errors due to compatibility > issues between different packages that are used in > openembedded. That also sounds unexpected: yasm is a static executable (that you can put into /usr/local/bin and) that imo simply cannot interfere with any other package. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] creating a new filter...
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. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
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 have to worry about the warnings. > But then, horrors! > $ makecommon.mak:139: *** missing separator. Stop. This indicates that your checkout is broken, use: $ git config --global core.autocrlf false and checkout again. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
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 using git bisect to find the version introducing it. (This isn't trivial with FFmpeg, but I will support you.) > --extra-cflags='-O2 [...] This is probably unrelated, but could you explain why you are adding (most) options? Some of them obviously make no sense, the paths are of course needed, for the remaining ones, I'd like to ask if they fix any problems? If yes, this should be fixed in configure, don't you agree? Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] makefile problem on win32 MinGW
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.) Please do not top-post here, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 takes me <15 minutes, but arguably I know what to do. As said, I can help you. > as xbmc currently is based on ffmpeg version 0.10.2 I may misunderstand: Is the crash only reproducible with xbmc and not with FFmpeg? If yes, the bisect will probably not help because the reason is something like a unsufficiently aligned buffer within xbmc. If the crash is reproducible with FFmpeg, you don't need xbmc to test. > What do you say about regression testing the binary > way and start somewhere in the middle. What version > do you suggest we start with? The optimal version to start is of course the one you know is working fine (if I suggested one "in the middle" it would not save you more than one compile). If you know that 0.10.2 is working, you could start with 3c5fe5b (that will save you one compile). Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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, >> and also helps to fix it. > > Cool - didn't know that ffplay was able to run on ios "bare-metal" Never use ffplay for (real) tests, it depends on an external library that is known to contain bugs (as FFmpeg). Always use ffmpeg (the application) for such tests. Please try to fix your quoting / set your mailer to text-only. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 optz orginates from Mans > Mullgards work) or both maybe? Only trac is supported (and suggested) on this mailing list. Please test current git head first to make sure the problem is still reproducible. 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. Does it work with -cpuflags -neon? Does it work with --disable-neon? Is this a regression, ie does it work with any older version? Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 rather > complex automated testing environment Yes, definitely: $ make SAMPLES=fate-suite fate-rsync $ make SAMPLES=fate-suite fate ;-) (Needs rsync installed) Most of your remaining questions are simply impossible to answer (I don't remember FFmpeg ever having a maintainer for x86, ppc or any other architecture and allow me to repeat that only trac is relevant on this mailing list), but please test if -cpuflags -neon or --disable-neon helps. (I will open a ticket if all information is available, if you open it without bisecting this will unfortunately not really help.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 compile hundreds of different > versions by hand you know. :) :) 14 will be sufficient, I will guide you. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 use --disable-neon --enable-neon (-cpuflags is a runtime option) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 versions to test. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 for > xbmc is n0.10.2 which is quite a few commits > from n2.1, probably a whole lot more than just > 14 iterations Exactly 14 iterations, please trust me, I am doing this quite often. Before starting, please test -cpuflags -neon and --disable-neon to make 100% sure that we know what we are searching for. For the bisect, please confirm first that 3c5fe5b does indeed work fine (this corresponds to 0.10 and is the first of 14 compiles). Then please test a1bcc76. If it works ok, test 3860e34, if not try 35894eb (These are compiles two and three.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 > we are searching for. > > 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! 100% unrelated to this bisect that we should really do in any case (you may already have realized that nobody else but you is able to do it): I only start to realize now what you are actually doing, please allow me state very, very clearly that it is imo *not* a good idea to update xbmc now to a version of FFmpeg that is already outdated. There will be no future release series containing new features but the old API! Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 appears that exchanging mails takes an enormous time, so just start bisecting with the versions I already sent. As an alternative, you may of course do the bisect without my help (that means less work for me). If you are lucky with the versions you choose, it may also mean a significant reduction of the amount of time you need. (But also consider that I use git bisect more often than you and that it bears some annoyances when used with the FFmpeg sources.) [...] > Well, yes - we're aware about the new api and that > 1.2 will the be the last version with the old api. That is all I wanted to make sure of. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 compilation take approximately 30 minutes? If yes, it will be easy to reduce the time... (I originally thought that reducing compilation time will take more time than it saves, but with 30 minutes per run that is of course not true.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 you decide that you want to do it my way, please follow: http://thread.gmane.org/gmane.comp.video.ffmpeg.libav.user/10324/focus=10406 Thank you, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 save you some time but will not work the way you are used to from other git repositories, I therefore suggest manual compilation.) If compilation really takes >10minutes, you can try the following configure line with current git head: $ ./configure --disable-everything --enable-protocol=file --enable-demuxer=mov --enable-parser=h264 --enable-decoder=h264 (You of course have to add the cross-compilation options.) This assumes your crashing test file is a mov file, adapt the --enable-demuxer entry in case it is not. You can also test --disable-optimizations, this speeds compilation up significantly but may hide the bug: It is probably ok in your case but who knows. (This will work even less with a script because some revisions will need additional --enable-* options to succeed compilation.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 the "bad commit". Please understand that there is no worst-case scenario when doing git bisect. (There is only one scenario +/- 1 compile.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 not work, please test 230bef0 If you tested 6b2e650 and if works ok please test 6b8f211 If you tested 6b2e650 and if does not work, test 5361f49 Only if you tested 230bef0 and it worked, test 6717d1a If you tested 230bef0 and it failed, test f2c49da > 3. 35894eb # Didn't compile: But it wasn't necessary anyway, you correctly tested 3860e34. Since the regression is so "new" (fork development has slowed down significantly), a normal bisect will likely work fine. (I was assuming an older bug when git bisect always wanted to test broken versions.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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.h config.mak Thank you, Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Audio and Video Stream copy
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 supported versions. Check the doc/examples subdirectory for some example code. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Audio and Video Stream copy
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.org/download.html for supported versions. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Filtering_video.c and yadif does not work
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Efficient AAC decoding on ARM with FFmpeg 1.1.x
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 outputs samples as > AV_SAMPLE_FMT_FLTP. I therefore need to convert these to > AV_SAMPLE_FMT_S16 before they can be played Please use either libswresample or the aconvert audio filter (which uses libswresample) for the conversion. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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). Note that I originally wanted to write that I find it an incredibly bad idea that xbmc contains its own gas-preprocessor script. I agree now that the problem was not so simple but I still find it much, much better to have a link to upstream instead of a fork. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Problems converting raw camera frames
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 the four native pix_fmts: AV_PIX_FMT_ARGB AV_PIX_FMT_ABGR AV_PIX_FMT_RGBA AV_PIX_FMT_BGRA (Sorry if you feel I should point out the right one immediately or at least mark the one that definitely does not work.) Generally, please don't use pastebin when posting here, post the complete information in your email. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] how to mux MJPEG encoded data into AVI container
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 data first ,and then > encode and mux it into AVI container . $ ffmpeg -i mjpeg -vcodec copy out.avi Generally, it is a good idea to test something before posting on this mailing list and report here if it does not work (includig failing command line and complete, uncut console output). Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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 he merged I assumed it was because of my message, I had missed yours.) [...] > > I still find it much, much better to have a link > > to upstream instead of a fork. > > Like a git submodule or what do you suggest? A link to github as on http://ffmpeg.org/platform.html#Darwin-_0028Mac-OS-X_002c-iPhone_0029 Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Seeking encoded video (.avi)
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-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Reference app with ffmpeg n1.2 libs that works on IOS ?
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/gcc" > As an addition to the above suggestion, a version > control of gas-processor.pl during the configure > process of ffmpeg would be a rather nice complement. Patch (extremely) welcome! (My idea is to grep for the right syntax in configure, contrary to you I cannot test.) Regarding your other question: Simply do not provide a copy of anything that exists already, simply add a link. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Seeking encoded video (.avi)
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://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] 16-Bit RAW Video Recording Problem
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: rawvideo, 1024x768, SAR 1:1 DAR 4:3 While this does indeed look like a regression, I wonder if it was intended behaviour at any time: Afaik, matroska does not define gray16 rawvideo, so I wonder if it was a good idea to choose mkv as output format. (And the name you chose for the file does not increase confidence that you know exactly what you are doing.) I suggest to use nut instead, it contains definitions for the format. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Runtime ARM Neon detection?
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 very unlikely to me that a
compiler option ("-mfpu=vfvp3") affects FFmpeg asm
optimizations.
[...]
> Would it be possible for FFmpeg to detect Neon at runtime?
Looking at ff_dsputil_init_arm() in
libavcodec/arm/dsputil_init_arm.c, that is exactly what it
currently does.
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Runtime ARM Neon detection?
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 list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Runtime ARM Neon detection?
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 the version that your Android users >> tested and protested performance-wise or am I >> wrong? > > You're not wrong, this is indeed the version > being protested performance-wise. Then please remove the option --enable-nonfree from your configure line. It is a copyright violation to distribute FFmpeg binaries that were built with this option. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] x264 encoding error
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
Re: [Libav-user] pts problem
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 behandeln. Please understand that this makes absolutely no sense when sending an email to a public email list that is mirrored several times on the internet. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] how to mux MJPEG encoded data into AVI container
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@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] pts problem
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] AAC with FLV
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 > received an error message -- that these codecs > couldn't be found. 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 -strict -2 to the system. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] AAC with FLV
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 -strict -2 to the system. > Is the "-strict -2" passed to extra-cflags, > extra-ldflags, or a separate option in the configure? It is a ffmpeg runtime option, the equivalent is: avctx->strict_std_compliance = FF_COMPLIANCE_EXPERIMENTAL; (avctx being AVCodecContext iirc) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] encode directly from svg rather than png in avconv?
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 we therefore cannot support it on this mailing list. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] AAC with FLV
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. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ffmpeg configure for ios - using asm options causes MPx (mp1, mp2, mp3) codecs sound problems
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 ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ffmpeg configure for ios - using asm options causes MPx (mp1, mp2, mp3) codecs sound problems
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 we don't find the offending function, this is quite unlikely to get fixed.) Please do not top-post on this mailing list and please avoid cross-posting, both is considered rude. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ffmpeg configure for ios - using asm options causes MPx (mp1, mp2, mp3) codecs sound problems
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 responsible function: --cpu=armv4 --cpu=armv5 --cpu=armv6 (They correspond to libavcodec/arm/dsputil_init*.c) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ffmpeg configure for ios - using asm options causes MPx (mp1, mp2, mp3) codecs sound problems
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 is a little more information now (arm but not neon related iiuc), but more tests will be needed to allow fixing this issue. (I unfortunately do not have acess to a suitable testing environment.) Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] ffmpeg configure for ios - using asm options causes MPx (mp1, mp2, mp3) codecs sound problems
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-preprocessor as explained on http://ffmpeg.org/platform.html and please report any problems with it! Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Anybody got DXVA2 running?
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 realize that ffmpeg (the application) does not suport dxva2 ? Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Anybody got DXVA2 running?
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 since the bug was reported after 1.2 was released. Carl Eugen ___ Libav-user mailing list Libav-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Anybody got DXVA2 running?
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://ffmpeg.org/mailman/listinfo/libav-user
Re: [Libav-user] Audio quality loss while encoding
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@ffmpeg.org http://ffmpeg.org/mailman/listinfo/libav-user
