[FFmpeg-devel] [PATCH 1/2] opus_pvq: add resynth support and band encoding cost function
On Fri, 14 Apr 2017 14:30:28 +0200 Carl Eugen Hoyos wrote: i understand you want to fix the copyright header of the file, that is a good idea. >We know that the avconv developers are violating the >copyright of many people, we fix that in the FFmpeg code as >soon as we are aware of it, there are many examples in gitlog. >I don't see how this case would be different. please refrain from making accusations and starting fights in ffmpeg mailing lists. this mailing list is for development, not fights. if you have a specific problem, feel free to blog about it on your personal website, like many other developers do. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [RFC] Reviewing merges
i apologize in advance for replying to this email and not carls, but be assured i am replying to both carl and wm4 here. On Mon, 24 Apr 2017 19:13:32 +0200, wm4 wrote: > On Mon, 24 Apr 2017 16:00:41 +0200 > Carl Eugen Hoyos wrote: > > 2017-04-24 15:38 GMT+02:00 wm4 : > > > On Mon, 24 Apr 2017 15:23:20 +0200 > > > Carl Eugen Hoyos wrote: > > >> 2017-04-24 13:39 GMT+02:00 Ronald S. Bultje : > > >> > On Mon, Apr 24, 2017 at 5:57 AM, wm4 wrote: > > >> >> On Mon, 24 Apr 2017 10:46:38 +0200 > > >> >> Carl Eugen Hoyos wrote: > > >> >> > 2017-04-24 5:50 GMT+02:00 Aaron Levinson : > > >> >> > > On 4/23/2017 7:07 PM, Michael Niedermayer wrote: > > >> >> > >> > > >> >> > >> Should changes ported from libav (what we call merges) be > > >> >> > >> reviewed before being pushed? > > >> >> > > > > But if the regressions remain unfixed, it is a little surprising > > to speak about "no major issues", don't you agree? > > Which regressions? You claim they exist, yet you never mention any of > those by name. Maybe you're lying, joking, having problems due to > English not being your native language like you often mention, etc.? guys... maybe just ... less words and post more trac urls. > Now most/all distros have switched from Libav to FFmpeg. Do you see > Libav being forced to merge FFmpeg API? No? then why was FFmpeg > "forced" to do it? > > I'd really like to know your thoughts about this (we all know they are > free of lies and jokes, no worries). wm4 and carl, can you maybe take this conversation and write libav/ffmpeg history up somewhere else? no one here cares to read 6 year old history again on ffmpeg-devel. seriously, please. not here. not again. NO ONE WANTS TO READ THIS. no one cares who is right carl or wm4. fight elsewhere. not here. > Well, and I find your personal issues with the Libav project odd, to > say the least. personal issues arent ffmpeg-devel technical discussions, please take this private off list. please oh please. both carl and wm4 please. > > > Frankly you're on the level of an aggressive troll, and always have > > > been when it came to things related to Libav. calling people names like troll probably not good idea in professional environment. also maybe CoC violation. > Let me make this clear: we WILL be friendly with the Libav project. We > WILL work towards reunification with it. We WILL work towards reducing > conflict with it. We WILL make an effort to reach these goals. The past > does not matter, there was shit on both sides. Please remove the shit > still remaining on one of the sides. mostly positive. although i wonder what is being called shit here though. but i will wonder off-list. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [rfc] coc violation tribunal
as a few developers have wondered... how is our project to judge, report and punish coc violations? since we had a vote to approve of the COC, we will probably need another vote to approve of the COC rules. do you want group consensus? how big of a group? whos in the group? who wants to do a bunch of crapwork telling devs to be nice in the sandbox and stop throwing sand at each other or they'll get a timeout? do you want irc/ml admins to handle it? e.g. lou and me set moderation flags on developers and delete mails that are not development related? who judges the judges? what if we scare off devs who get frustrated that the COC was not fully fairly applied to everyone? e.g. one dev gets moderated while another skates ? thats where the strife gains momentum. thoughts? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] New to the list... thinking about a feature
On Thu, 18 May 2017 12:20:55 +0200, Pedro Andres Aranda Gutierrez wrote: > I'm completely new to the list but have a couple of years experience as a > user. I happen to work a lot with things I record from satellite. My > recorder will include a lot of empty streams in the transport stream and > that is annoying. I have tweaked ffmpeg here and there to show only > non-empty streams at the 'normal' verbosity level and include empty streams > at heightened verbosity. depending on the complexity of the patch. and if it does not break other files. and assuming it passes fate... just submit patch here , we'll review it. even if ffmpeg does not accept it, its possible that other people will use your patch for their setup. thanks! welcome to ffmpeg. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Policy on ffmpeg-devel list and contributions [was: Re: [PATCH] Refactor Developer Docs, update dev list section (v2)]
attempt. :) hope this clears things up. feel free to ask me questions off list, or we can be found on irc.freenode.net #ffmpeg-devel as well for real time chat. tl;dr my suggestions: 1. split docs patch 2. less words, rephrase for brevity 3. welcome to open source team collaboration :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] AMD external header
On Wed, 29 Nov 2017 15:58:29 +0100, wm4 wrote: > On Tue, 28 Nov 2017 16:09:57 + > "Mironov, Mikhail" wrote: > > > > I wanted to stay out of license issues and this forum is oriented more > > towards > > technical discussion but I can't resist putting my two cents: Yes, HW > > manufactures > > live out of HW sell. And yes, integration with products like ffmpeg should > > benefit them (us). > > But they(us) do not sell software. The enablement of HW acceleration adds > > features to ffmpeg project. > > And we do it ourselves. We also intend to contribute more. So it is > > mutually beneficial. Isn't it? > > Well, don't worry too much. as an mplayer user who had to go looking to find a bunch of sdk headers and hope that the instructions written 2 years ago still point to a working URL, i feel a lot of pain in this thread. svn has svn externals, where a svn checkout would pull from other svn repositories. i am assuming git has the same thing? if so these headers could go in an external repo, but a ffmpeg git pull would pull them down? are there any objections to that ? that would cut down on our objections and maintainership and git history concerns... i think? so long as its easy for non amd users to flip a config switch to disable pulling those amd headers down. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] AMD external header
On Wed, 29 Nov 2017 16:16:12 +0100, Paul B Mahol wrote: > On 11/29/17, Carl Eugen Hoyos wrote: > > 2017-11-29 15:58 GMT+01:00 wm4 : > > > >> Well, don't worry too much. People like him are, as some would say, > >> toxic members of the community. Frequent drama and flame wars happen. > >> (And here's where I wished ffmpeg were a properly managed project.) > > > > Look who's talking! > > > > Given that you started a fork of FFmpeg repeating ancient lies > > and stating you don't support FFmpeg anymore: > > Why do you post here? > > Because he like to argue with toxic people like you. carl, wm4 and paul please ignore flames. please? no reason to continue these flames and not on the mailing list for sure. nicolas is entitled to his opinion and licensing choices. no single dev speaks for the entire project. wm4 is entitled to fork whatever open source project he wants, and hes welcome to post here and review patches and be a developer. carl you dont have to respond to every aggressive post. nor do you have to attack people. paul and wm4 please stop insulting developers and calling them names. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] AMD external header
On Wed, 29 Nov 2017 15:45:28 +, "Mironov, Mikhail" wrote: > May I suggest to go down to business of enabling HW encoders by default? > Yesterday Mark submitted the initial implementation and I really want > to thank him for his mentoring and participation - it was very useful. > Question is: how to move forward on practical terms? I really don’t know how > this team makes such decisions. > Or maybe it is impasse case and all want to keep things the way they are > today? probably wait a few days until the maintainer of hwaccels can chime in, possibly with some more reviews. please be patient. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] AMD external header
On Wed, 29 Nov 2017 18:06:46 +, "Mironov, Mikhail" wrote: > This was a suggestion in one of the posts, not my idea. I personally would > prefer to include headers. i also prefer including headers into ffmpeg. only for the big 3 intel amd and nvidia... unless something else comes along i have no problem with this. but its also not my call, just my personal opinion. to make it easier on users who dont have to go around looking for sdk and extracting headers and all that baloney. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] AMD external header
On Fri, 15 Dec 2017 00:31:27 +, "Mironov, Mikhail" wrote: > Do you think that two and half weeks is long enough to wait? > So far except creating a repo for NVidia there is no activity. did you resend your patchset without the header included? sorry i am too busy to even read the list right now. maybe the patchset without the included header could get reviewed some more and possibly applied while we wait for the external repo changes. remember we are mostly volunteers working on ffmpeg. which means we all have regular non-ffmpeg jobs. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] CoC enforcement activated
http://ffmpeg.org/developer.html#Code-of-conduct 5 Code of conduct Be friendly and respectful towards others and third parties. Treat others the way you yourself want to be treated. Be considerate. Not everyone shares the same viewpoint and priorities as you do. Different opinions and interpretations help the project. Looking at issues from a different perspective assists development. Do not assume malice for things that can be attributed to incompetence. Even if it is malice, it’s rarely good to start with that as initial assumption. Stay friendly even if someone acts contrarily. Everyone has a bad day once in a while. If you yourself have a bad day or are angry then try to take a break and reply once you are calm and without anger if you have to. Try to help other team members and cooperate if you can. The goal of software development is to create technical excellence, not for any individual to be better and "win" against the others. Large software projects are only possible and successful through teamwork. If someone struggles do not put them down. Give them a helping hand instead and point them in the right direction. Finally, keep in mind the immortal words of Bill and Ted, "Be excellent to each other." - enough fighting on the mailing list. emergency moderation has now been enabled. why do i have to enforce the COC? the ffmpeg-devel mailing list is for technical discussions of developing ffmpeg. personal insults will not be tolerated. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] CoC enforcement activated
On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock wrote: > On Sun, 17 Dec 2017 15:36:53 -0500 > Compn wrote: > > > [...] > > > > emergency moderation has now been enabled. > > > > why do i have to enforce the COC? > > > > the ffmpeg-devel mailing list is for technical discussions of > > developing ffmpeg. personal insults will not be tolerated. > > > > Note that there is nothing on how the CoC should be 'enforced'. Also consider > that the CoC in our case is more of guidelines than strict rules to be > followed. There has also been no consensus on moderation being enabled under > what circumstances. right, i brought this up in april. http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/210519.html -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] CoC enforcement activated
On Sun, 17 Dec 2017 22:16:50 +, Josh de Kock wrote: > On Sun, 17 Dec 2017 17:12:24 -0500 > Compn wrote: > > > On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock > > wrote: > > > > > On Sun, 17 Dec 2017 15:36:53 -0500 > > > Compn wrote: > > > > > > > [...] > > > > > > > > emergency moderation has now been enabled. > > > > > > > > why do i have to enforce the COC? > > > > > > > > the ffmpeg-devel mailing list is for technical discussions of > > > > developing ffmpeg. personal insults will not be tolerated. > > > > > > > > > > Note that there is nothing on how the CoC should be 'enforced'. Also > > > consider that the CoC in our case is more of guidelines than strict rules > > > to be followed. There has also been no consensus on moderation being > > > enabled under what circumstances. > > > > right, i brought this up in april. > > > > http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/210519.html > > > > My point is: You should turn off this 'emergency moderation' as there's > nothing in the *non-existent* guidelines which say you are allowed to do so. as said on irc, emergency moderation is the standard and expected tool for ml admins to use to stomp out flame wars. When this option is enabled, all list traffic is emergency moderated, i.e. held for moderation. Turn this option on when your list is experiencing a flamewar and you want a cooling off period. emergency moderation is part of an ml admins job. it is not something i thought up, invented, or wrote guidelines for. it is not something i enjoy either. having mails delayed ~2 minutes never hurt anyone. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] order T-shirts
On Mon, 18 Dec 2017 14:29:51 +0100, Timo Rothenpieler wrote: > Forgot to mention it here, but I got my shirt a while ago and it fits > perfectly. > Thank you very much! > ditto, much thanks. although Deutsche Post decided it did not like your envelope so they put it in a protective plastic bag. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [FFmpeg-cvslog] [ffmpeg-web] branch master updated. 979b3a6 web/contact: note that no discussions occur on cvslog and trac mailing lists
On Thu, 21 Dec 2017 10:32:50 -0900, Lou Logan wrote: > On Thu, Dec 21, 2017, at 4:07 AM, Carl Eugen Hoyos wrote: > > Where was this agreed upon? > > > > Carl Eugen > > I did not assume further discussion was required for this subject, but I am > confident that the vast majority of developers will support this, in my > opinion minor, decision. i think the argument that historically -cvslog was a place to discuss commits was true. presently no one discusses commits on -cvslog. this change seems to be common sense. i understand carls' argument but i also understand -cvslog mailing lists have evolved to make things easier and simpler for developers to not have to follow two lists for discussion. also possibly git log has replaced -cvslog for many developers. carl if you have a suggestion for better wording, please send patch ? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [FFmpeg-cvslog] [ffmpeg-web] branch master updated. 979b3a6 web/contact: note that no discussions occur on cvslog and trac mailing lists
On Fri, 22 Dec 2017 14:39:40 -0500, Compn wrote: > carl if you have a suggestion for better wording, please send patch ? also as the other ml admin, i agree with lou's commit and community agreed upon policy change. what discussions do you want to have on -cvslog that would not be better heard on -devel? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 2/7] decode: add a method for attaching lavc-internal data to frames
On Tue, 17 Oct 2017 20:37:32 +0200, Thilo Borgmann wrote: > I do care because I am delaying my work on some other cuvid related thing > because of this. > > I would prefer not to dive into this topic any further because it seems > rather "not so important" to my task. And just another cook in the kitchen > would also more likely avoid conensus here. thilo, can we bribe you to massage this patch a little? it seems like wm4 and michael both are not budging... a third party might be able to settle the stalemate. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 2/7] decode: add a method for attaching lavc-internal data to frames
On Wed, 4 Oct 2017 11:34:18 +0200, wm4 wrote: > > more so, opaque_ref is used in only 5 lines in the whole codebase, > > so there is not much code to consider when using a different solution > > We shouldn't add such special fields, we have enough hacks already. Is > that your only suggestion how to do this? Because it's a bad one. michael, do you have other suggestions how to solve this problem? are you going to fix the errors in the doxygen that you noticed due to merges? wm4, would you object to adding another special field? if someone else edited this and made a patch? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] order T-shirts
On Sun, 22 Oct 2017 21:29:52 +0200, Thilo Borgmann wrote: > >> So what do others think about colors? Shall I make a 3-color-sample first? > >> We might do more than one version. > >> They open again Tuesday... > >> > > > > I personally don't think it's a big deal either way, but green logo would > > be nice, I believe the original logo (and current favicon) was green. > > Okay then I'll try to have the logo in green and white printing. I'd order all > green printings for the case that green/white printings would be too much > extra > cost (>15/shirt I'd say). i am fine with green or white. i hope that the green (light green?) is visible on a black shirt of course. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] d3d11va: use the proper slice index
On Mon, 10 Oct 2016 17:07:06 +0200 Hendrik Leppkes wrote: > On Mon, Oct 10, 2016 at 4:01 PM, Michael Niedermayer > > > > maybe our dxva2 maintainer wants a co maintainer? > > if so would someone be interrested to help ? > > > > Unfortunately I have no way of testing the D3D11 stuff in there (and I do you want a windows box with a d3d11 card? there are many companies now using ffmpeg and they want to get boxes into developer hands for testing. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer
On Thu, 27 Oct 2016 15:42:22 -0300 James Almer wrote: > On 10/27/2016 3:36 PM, Reynaldo H. Verdejo Pinochet wrote: > > On 10/27/2016 11:25 AM, James Almer wrote: > >> This is not how things were agreed. > > I haven't agreed to this. > You could have shown your displeasure in the relevant discussion and > patch threads, and on IRC. Why didn't you? > > A quick search on the archive shows > https://ffmpeg.org/pipermail/ffmpeg-devel/2016-April/192808.html > https://ffmpeg.org/pipermail/ffmpeg-devel/2016-July/196500.html but then there was this in september, after the news entry was posted http://ffmpeg.org/pipermail/ffmpeg-devel/2016-September/199686.html i'd suggest talking to that person before applying said patch. we can talk before applying a patch still, right? :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Add support for 24 bit RTSP audio playback
On Sat, 5 Nov 2016 01:15:44 +0300 Timur Aydin wrote: > ff_register_rtp_dynamic_payload_handlers(void) > ff_register_dynamic_payload_handler(&ff_vorbis_dynamic_handler); > ff_register_dynamic_payload_handler(&ff_vp8_dynamic_handler); > ff_register_dynamic_payload_handler(&ff_vp9_dynamic_handler); > +ff_register_dynamic_payload_handler(&l24_dynamic_handler); > ff_register_dynamic_payload_handler(&gsm_dynamic_handler); > ff_register_dynamic_payload_handler(&opus_dynamic_handler); > ff_register_dynamic_payload_handler(&realmedia_mp3_dynamic_handler); should probably l24 be under gsm as this list looks like alphabetical order. i've only seen l16 rtsp samples, have not seen l24 yet. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] vp9: add avx2 iadst16 implementations.
On Tue, 8 Nov 2016 14:44:32 -0500 "Ronald S. Bultje" wrote: > >> x86-32 linux gets stomach ache from this: > >> > >> YASMlibavcodec/x86/vp9itxfm.o > >> src/libavcodec/x86/vp9itxfm.asm:2150: error: instruction expected > >> after label > >> src/libavcodec/x86/vp9itxfm.asm:2151: error: instruction expected > >> after label > >> src/libavcodec/x86/vp9itxfm.asm:2152: error: instruction expected > >> after label > > > > > > Ah right, yes this is meant to be for 64bit only. I'll add some > > #if/%if around it... > > > > They were already there but one %endif was misplaced. Fixed locally. is nice to resend patch just so "we" (by we i mean michael) can keep checking for problems like this ;) unless you already tested on x86... -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] TR-03 implementation
On Thu, 10 Nov 2016 14:44:44 -0500 (EST) Éloi Bail wrote: > We would like to contribute to FFmpeg by adding the support of those > pixel formats and thus make FFmpeg usable for the next generation of > broadcasting products. > > Could you tell us if our contribution would make sense and eventually > advise us on the best way to address that ? sure, ffmpeg has support for many pixel formats and adding more pixfmts is not a problem. my best answer would be to look at commits which add other pixel formats and just follow how they were added to libswscale. make some fate tests, and it should be done. hopefully you have test samples made of these pixfmts you want to add. that makes testing for us easier, as we can test on multiple cpu arch's to make sure the code is safe and works. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [RFC]MAINTAINERS: Add developers who have git write access but are otherwise not listed
On Fri, 25 Nov 2016 11:11:23 +0100 (CET) Marton Balint wrote: > > On Mon, 21 Nov 2016, Michael Niedermayer wrote: > > > I omitted developers who do not use their account and i felt would > > prefer not to be listed. > > I think everyone with access should be listed. If somebody does not > use his account for a year or so, his/her access should be revoked. any scientific reason why? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [RFC]MAINTAINERS: Add developers who have git write access but are otherwise not listed
On Sat, 26 Nov 2016 17:15:36 +0100 (CET) Marton Balint wrote: > > On Sat, 26 Nov 2016, compn wrote: > > > On Fri, 25 Nov 2016 11:11:23 +0100 (CET) > > Marton Balint wrote: > > > >> > >> On Mon, 21 Nov 2016, Michael Niedermayer wrote: > >> > >> > I omitted developers who do not use their account and i felt > >> > would prefer not to be listed. > >> > >> I think everyone with access should be listed. If somebody does not > >> use his account for a year or so, his/her access should be revoked. > > > > any scientific reason why? > > > > In an open source project, the list of people with commit rights > should be public. > no problem > Revoking unused accounts is a simple security measure against > lost/compromised private keys. so unlikely that i cannot even imagine the odds. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [RFC]MAINTAINERS: Add developers who have git write access but are otherwise not listed
On Sat, 26 Nov 2016 18:05:52 +0100 Nicolas George wrote: > Le sextidi 6 frimaire, an CCXXV, compn a écrit : > > so unlikely that i cannot even imagine the odds. > > Any scientific reason why? if one wants to be worried about security issues, there are bigger fish to fry. for one example, how about any and all patches applied to ffmpeg by various distros ? https://lists.debian.org/debian-security-announce/2008/msg00152.html because this is a real threat to our users' security. not some lost commit key. we should be analyzing all distro patches and making sure all CVE fixes get applied by distros as well. our other developer policies help to mitigate any lost/stolen commit keys anyway. public patch posting and mailing list review, static code analyzing etc. has any developer come back from the proverbial "dead" , like say fabrice, to make a new commit? no. would we take notice if he did? yes of course. have developers had write access, been hired by large multinational corporations, stopped developing ffmpeg as a hobby, and then come back years later to work on ffmpeg as part of their employment? yes! multiple times. just my personal opinion. theres really not much difference between keeping old author accounts or deleting old author accounts from a real world perspective. one plan just takes some precious time away from the busy developer. because he has to make a list, and check it twice, just to find out who is naughty and who is nice. he sees when you are active... he sees when you are inactive... -compn (help, i've had far too much eggnog.) ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer
maybe when there is a conflict of opinion on a patch, we should agree to disagree on said patch and ignore it? instead of arguing endlessly about it? not specifically targeting you, james, but a lot of people in this thread. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer
On Mon, 28 Nov 2016 02:22:48 +0100 Michael Niedermayer wrote: > I dont know if people want me and reynaldo to spend less time on > FFmpeg, but time is a finite resource. If ffserver is maintained > externally it would mean a noticable hit in maintaince man hours of > FFmpeg. Now it might be that ffserver being pushed out would kill it. > But really as dumb as i am, i dont belive theres a majority who wants > to kill FFserver when there are people who actively work on it and > care about it. it seems like there are at least a few developers who would feel better if ffserver was removed from master / moved somewhere else to die etc. these developers feel very strongly about removing ffserver. it might be wise to follow the opinions of these developers in order to have a higher morale and continue the working environment here in the project. otherwise some developers may feel betrayed, harmed, ignored, etc and foster hatred because their opinions were not chosen. so michael, my advice to you is to just OK the patch and deal with ffserver later... if enough users come back to complain about its demise. i feel that this discussion is going no where if both sides are unable to come to a compromise. sometimes you have to cut off the toe to save the patient. :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/mov: Accept multiple fourcc for AVID 1:1
On Tue, 29 Nov 2016 22:10:47 +0100
Carl Eugen Hoyos wrote:
> From add7f5d51491152af6d0431331543212c2c21ca4 Mon Sep 17 00:00:00 2001
> From: Carl Eugen Hoyos
> Date: Tue, 29 Nov 2016 22:09:21 +0100
> Subject: [PATCH] lavf/mov: Accept multiple fourcc for AVID 1:1.
>
> Fixes ticket #5982.
> ---
> libavformat/mov.c |1 +
> 1 file changed, 1 insertion(+)
if (codec_tag &&
(codec_tag != format &&
+ (codec_tag != AV_RL32("AV1x") || format != AV_RL32("AVup")) &&
// prores is allowed to have differing data format and codec tag
codec_tag != AV_RL32("apcn") && codec_tag != AV_RL32("apch") &&
// so is dv (sigh)
what about adding a comment like the prores/dv comments?
(or in a separate patch, make a nicer comment for prores,avid and dv?)
there are more than just these two AVID isoms.
a quick search reveals...
'AV1X': 'Avid 1:1x (Quick Time)',
'AVD1': 'Avid DV (Quick Time)',
'AVDN': 'Avid DNxHD (Quick Time)',
'AVMP': 'Avid IMX (Quick Time)',
'AVUP': 'Avid 10bit Packed (Quick Time)',
possibly AVin
sample here : http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket524/AVCI50.mov
do any of these isoms need to be added to the list in mov.c ?
otherwise, looks ok if tested with our av1x/avup samples.
thanks,
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/mov: Accept multiple fourcc for AVID 1:1
On Fri, 2 Dec 2016 00:40:02 +0100
Carl Eugen Hoyos wrote:
> 2016-12-01 19:58 GMT+01:00 compn :
>
> > if (codec_tag &&
> > (codec_tag != format &&
> > + (codec_tag != AV_RL32("AV1x") || format !=
> > AV_RL32("AVup")) && // prores is allowed to have differing data
> > format and codec tag codec_tag != AV_RL32("apcn") && codec_tag !=
> > AV_RL32("apch") && // so is dv (sigh)
> >
> > what about adding a comment like the prores/dv comments?
>
> How should the comment look like?
// Avid codecs create different format and codec tags
no idea.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] remove news entry about ffserver
yeah. -compndiff --git a/src/index b/src/index index c203676..f6c925f 100644 --- a/src/index +++ b/src/index @@ -86,15 +86,6 @@ We recommend users, distributors, and system integrators, to upgrade unless they use current git master. - July 10th, 2016, ffserver program being dropped - -After thorough deliberation, we're announcing that we're about to drop the ffserver program from the project starting with the next release. -ffserver has been a problematic program to maintain due to its use of internal APIs, which complicated the recent cleanups to the libavformat -library, and block further cleanups and improvements which are desired by API users and will be easier to maintain. Furthermore the program has -been hard for users to deploy and run due to reliability issues, lack of knowledgable people to help and confusing configuration file syntax. -Current users and members of the community are invited to write a replacement program to fill the same niche that ffserver did using the new APIs -and to contact us so we may point users to test and contribute to its development. - July 1st, 2016, FFmpeg 3.1.1 "Laplace" FFmpeg 3.1.1, a new point release from the 3.1 release branch, is now available! ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 1/3] Revert "avcodec: Add max_pixels options"
On Sun, 11 Dec 2016 17:39:58 +0100 Nicolas George wrote: > This reverts commit 2f07830e69bd14eaba348eb739b9503e7eb7cd4b. would you rather the people doing the fuzzing use this feature as a separate patch so it does not contaminate master? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] ffmpeg: add ffmpeg_d3d11va
On Wed, 14 Dec 2016 11:44:13 +0100 wm4 wrote: > On Wed, 14 Dec 2016 09:30:35 + > Stève Lhomme wrote: > > > On Tue, Dec 13, 2016 at 2:35 PM, wm4 wrote: > > > On Tue, 13 Dec 2016 14:19:35 +0100 > > > Steve Lhomme wrote: > > > > > > > I'm pretty much against this, since it duplicates the profile > > > selection code all over again, even if it could be shared. (And > > > this code should be in libavcodec in the first place.) Someone > > > adding such code would have to refactor ffmpeg_d3d11va too. > > > > I'm not sure how this relates to the line above. d3d11va and dxva2 > > are definitely not the same thing. On mobile you do not have DXVA2 > > at all but D3D11(VA) is present. There must be a way to have one > > without the other. > > Yeah, but selection of the decoder GUIDs is very similar between both > APIs. It can definitely be shared (we do this in mpv). There's > absolutely no reason to copy-paste that stuff from ffmpeg_dxva2.c into > ffmpeg_d3d11va.c. > is having this duplication a blocker to this patch would you say? > As for how libavcodec can do provide this part, see the Libav/avconv > vaapi support (none of that is in ffmpeg yet). same question here. i am not arguing one way or the other, just asking. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Trying to ftp upload sample video
On Wed, 21 Dec 2016 14:31:43 +0100 wm4 wrote: > On Tue, 20 Dec 2016 20:34:28 +0100 > Paul B Mahol wrote: > > > Upload it somewhere else. > > Maybe we should stop recommending the FTP for sample uploading? I > never had much luck on it (on both sides: uploading, or looking at > something someone else uploaded). we need to talk to vlc about getting better ftp/http etc with our incoming dir. > Also remove the recommendation for this datafilehost site. It's a > terrible POS site which deserves to die. agree dfh sucks, but it would also be nice to have a replacement. one that accepts large files. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 1/3] lavf: identify MP2 as a distinct container from MP3
On Wed, 21 Dec 2016 12:51:18 -0600 Rodger Combs wrote: > > > On Dec 21, 2016, at 02:27, Carl Eugen Hoyos > > wrote: > > > > 2016-12-21 5:48 GMT+01:00 Rodger Combs : > >> This allows us to report the correct codec ID here > > > > Just curious: What does this fix? > > Reporting in ffprobe, or when using lavf as a library. Some devices > and decoders either refuse to decode MP2, or need to be told that the > input is MP2 as opposed to MP3 ahead of time. This also means we'll > write the correct ID when remuxing. if mp2 is a problem, i would rather make it more difficult for the user to encode mp2. by defaulting to mp3 and / or printing a warning message about mp2. honestly i cant remember any good coming from someone using mp2. mp2 is dead, long live mp3. also please share your mp2 sample, if you have not already done so, if possible. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [FFmpeg-cvslog] mov: Support prores with multiple stsd
On Wed, 13 Jul 2016 17:06:43 +0200 (CEST)
g...@videolan.org (Vittorio Giovara) wrote:
> ffmpeg | branch: master | Vittorio Giovara
> | Thu Jun 9 18:55:19 2016 -0400|
> [846a3e78a535f05ee61bb23a160f3378f041f751] | committer: Vittorio
> Giovara
>
> mov: Support prores with multiple stsd
>
> This function needs to return false, or data in the additional tables
> will be skipped, and the decoder will not be able to decode frames
> associated with them.
>
> > http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=846a3e78a535f05ee61bb23a160f3378f041f751
> ---
>
> libavformat/mov.c |2 ++
> + // prores is allowed to have differing data format and
> codec tag
> + codec_tag != AV_RL32("apcn") && codec_tag !=
> AV_RL32("apch") && (c->fc->video_codec_id ? video_codec_id !=
arent there more than just apch / apcn isom tags?
libavformat/isom.c lists a few:
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c', 'h') }, /* Apple ProRes 422 High
Quality */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c', 'n') }, /* Apple ProRes 422 Standard
Definition */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c', 's') }, /* Apple ProRes 422 LT */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c', 'o') }, /* Apple ProRes 422
Proxy */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', '4', 'h') }, /* Apple ProRes */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', '4', 'x') }, /* Apple ProRes XQ
*/
shouldnt these other 4 tags also be added?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [FFmpeg-cvslog] mov: Support prores with multiple stsd
On Thu, 14 Jul 2016 16:26:09 -0400 compn wrote: > shouldnt these other 4 tags also be added? also i think adding a comment in isom.c about adding any new prores tags to this hack in mov.c would be useful. i am assuming prores will have more tags in the future. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Regarding License Purchase
On Mon, 18 Jul 2016 18:55:13 +0530 Umesh Nepali wrote: > Hello Everybody > > > There is an android application in which i have to compress video to > upload on server.By using FFmpeg library i have implement > successfully but this was only for 15 days trial version. So i just our ffmpeg software is free and available at ffmpeg.org. we dont know what software you are using, you have contacted the wrong people. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 1/2] Add an OpenH264 decoder wrapper
On Tue, 26 Jul 2016 14:06:57 + (UTC) Carl Eugen Hoyos wrote: > > one could potentially want to use it to take advantage > > of the cisco patent license offer. > > I am not sure I understand this, could you elaborate? > In any case, this should imo not be part of the commit > message. http://www.openh264.org/faq.html https://github.com/cisco/openh264 -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [REMINDER] VideoLAN Dev Days 2016
On Fri, 12 Aug 2016 12:01:58 +0200 Thilo Borgmann wrote: > Hi! > > Am 09.08.16 um 23:01 schrieb Jean-Baptiste Kempf: > > My fellow members of the ffmpeg development community, > > > > As it is now customary, I'd like to invite you to VideoLAN Dev Days > > 2016, on the 1st week-end of September: 2-4 September 2016, in > > Berlin. > > I'm just aware of Thomas Volkert and myself who are attending for > sure. > > Who else is planning to come? i'm planning to go. it will be interesting for me to see this qtcon as well :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Outreachy 2016 december
On Wed, 17 Aug 2016 18:24:09 +0200 Michael Niedermayer wrote: > On Wed, Aug 17, 2016 at 09:16:16PM +0530, Umair Khan wrote: > > I'd love to mentor some *easy* project in the Outreachy program > > definitely. May be I can even get some students to apply to the > > program. > > that would be great, do you have any specific ideas for a easy > project ? reviewing all (or maybe 500) bugs in trac, testing with latest git version and updating or closing old bugs? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] IOS-IPv6-only-network-use-hardcode-IPv4-fix
On Wed, 24 Aug 2016 01:03:00 +
liu jc wrote:
>
> there is a bug when useing getaddrinfo in IOS when use
if this is an IOS hack, it should be ifdef'd?
also i thought we had a policy against putting os bugfixes in our
codebase? although i dislike this policy...
> -snprintf(portstr, sizeof(portstr), "%d", port);
> +
> + switch (port) {
> +case 80:
> +snprintf(portstr, sizeof(portstr), "%s", "http");
> +break;
> +case 1935:
> +snprintf(portstr, sizeof(portstr), "%s",
> "macromedia-fcs"); //know as rtmp
> +break;
> +default:
> +snprintf(portstr, sizeof(portstr), "%d", port);
> +break;
so only 80, 1935 ? rtmp uses some other ports too. 443 etc.
i am not against patch, i hope there is a way to fix this.
do we have any apple contacts to report this bug?
is it possible to use a different getaddrinfo on ios?
thanks for patch.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Nvidia NVENC 10-bit HEVC encoding and rate control lookahead support
On Sat, 27 Aug 2016 13:49:25 +0200 Timo Rothenpieler wrote: >I'll push for another attempt of including the header in ffmpeg including nvidia header in linux kernel was a no-go ? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: Include nvEncodeAPI v7 SDK header
On Sat, 27 Aug 2016 14:58:53 +0200 Timo Rothenpieler wrote: > As Nvidia has put the most recent Video Codec SDK behind a double > registration wall, of which one needs manual approval of a lenghty > application, bundling this header saves everyone trying to use NVENC > from that headache. > > The header is still MIT licensed and thus fine to bundle with ffmpeg. is ok with me. but i am not maintainer. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] MKV Header: Writing duration early
On Tue, 12 Jul 2016 10:15:08 + Soft Works wrote: > anyway, while I haven't looked into that yet. I also haven't > performed research > > about other ffmpeg output formats, to see if there is an existing case > > where duration is written early... > > > Before coding anything I'd like to get a feeling for what kind of > solution > > could be acceptable for the project. there is qt fast start feature in ffmpeg. which is similar , but for mp4 files. i am not sure if the devs want this feature to be copied into mkv, you better ask the best way to do it before starting. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Searchable archives for ffmpeg-devel and ffmpeg-cvslog
On Fri, 23 Sep 2016 09:57:02 +0200 Robert Krüger wrote: > Hi, > > I am looking for searchable archives of ffmpeg-devel and > ffmpeg-cvslog. I used to use gmane but that seems to no longer work. > > Would be great if someone has a hint. I can't imagine that people out > there search ml archives by going through them month by month. possible with google using: searchterm site:ffmpeg.org inurl:ffmpeg-cvslog searchterm site:ffmpeg.org inurl:ffmpeg-devel i dont know if mailman has a search feature. https://wiki.list.org/DOC/How%20do%20I%20make%20the%20archives%20searchable -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH/RFC]lavf/aacdec: Do not auto-detect a single frame
On Sat, 24 Sep 2016 00:00:35 +0200 Carl Eugen Hoyos wrote: > Hi! > > I use this patch locally for some time. It fixes > many misdetections, a similar patch was applied to > loas detection three years ago. > An alternative would be to return "1" for two frames. this prevents all of those files from trying to be decoded as aac ? if so, good. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] lurking bugs in the mmx-related assembler code (?)
On Sun, 2 Oct 2016 23:16:02 +0200 u-h...@aetey.se wrote: > > looking at the code? Seriously?) > > Yes, I am serious. vp3 is a decoder written 10+ years ago by a dev who is no longer active in ffmpeg. we have many decoders and encoders (and other code) in ffmpeg that have not been audited (to my knowledge). i know this isnt an excuse for not looking at the code. just letting you know the history. > Frankly, your tone looks unpleasant. > It is a friendly information to make you aware. I guess you were not. please dont think carl's tone is unpleasant, maybe he is just incredulous. carl has tested and verified thousands of bugs for ffmpeg. carl also fixes some of them. carl i think was confused by your comment, because carl would like to reproduce the bug. reproducing the bug with an easy command line, on a dev computer usually makes the bug finding and fixing quicker. > To give you an example of successful code auditing, the corresponding > UB-problem in libtheora was properly fixed without anybody at Xiph > having to install musl. > That's why I still believe that auditing the code is more useful than > hunting once again the hard-to-pinpoint symptoms of the already known > cause. do you have any suggestions for how the ffmpeg project could do successful code audits? we have static code analyzers like coverity running on ffmpeg. there has also been a lot of fuzz testing done. i'm sure some of the more popular decoders like h264 have had code audits done in private. i really dont see much enthusiasm for line by line code auditing within ffmpeg. in fact, i'd say people would rather re-write an entirely new piece of code than try to clean up the old code. this isnt a knock on anyone or any piece of code, just my observation. feel free to tell me that i am wrong. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] lurking bugs in the mmx-related assembler code (?)
On Sun, 2 Oct 2016 08:29:22 -0400 "Ronald S. Bultje" wrote: > I also think we could contact musl developers and see what's going on > there. We certainly shouldn't blindly fix this bug by adding an emms > in a random place, to me that's like opening pandora's box. on irc i pointed dalias to this thread. or you can just ask on #musl in freenode. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] lurking bugs in the mmx-related assembler code (?)
On Mon, 3 Oct 2016 12:45:13 +0200 u-9...@aetey.se wrote: > > > http://git.musl-libc.org/cgit/musl/tree/src/malloc/malloc.c#n114 > > > > Urgh. This is even worse than I imagined. FFmpeg is using undefined > > behaviours by calling it without resetting the state, but this is > > also completely undefined behaviour on their side. > > I feel a duty to remind, in the most positive and friendly tone: > > The author of the referred code acts in his actual area of competence > (C libraries and standards). > > The comments here on the C library code and standard compliance come > from developers having a different competence area (multimedia > programming). > > As bright as the people here are, they land in a foreign area, which > accidentally leads to statements like the above. ehe, well.. do your homework before assuming things. ;) rich felker , who wrote musl, was an mplayer and ffmpeg? developer actually. he wrote musl because everyone hated glibc. i contacted both him and even mike melanson (vp3 decoder author) mikes reply: >* I didn't write any VP3 MMX (or other SIMD), so I can't be of much > immediate help, even if I did have perfect recall of the code. > However, I invite you to run 'git blame' on the vp3 code and see how > many of my non-comment lines still persist. rich felker musl reply: > [23:46] yes they're violating the x86 abi > [23:46] at function call time the x87 floating point stack > has to be empty (and thus in x87 mode, not mmx mode) > [23:47] you can't call external functions while in mmx state i dont doubt its a bug in vp3 that needs to be rewritten. but we also go to extreme lengths to blame others... ;D musl could handle it better sure, but should they really write a full c-checker into their lib? would make it as bloated as glibc! -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] lurking bugs in the mmx-related assembler code (?)
On Mon, 3 Oct 2016 23:57:32 +0200 u-9...@aetey.se wrote: please refrain from off topic posts on this mailing list. bug reports go to trac or ffmpeg-user list. see http://ffmpeg.org/bugreports.html "Please do not report your problem on the developer mailing list:" > You are welcome to learn why the things are done in a certain way. > A good place to start might be the musl mailing list. after reading this thread, the thing i realize now is that our developers would rather do a line by line audit of another libc software project than an audit of ffmpeg code :D -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] mov: Evaluate the movie display matrix
On Thu, 6 Oct 2016 16:40:12 -0400 Vittorio Giovara wrote: > > what is the intended / correct SAR / DAR for this sample ? > > without the patch Stream #0:0(und): Video: h264 (High) (avc1 / > 0x31637661), yuv420p, 540x576 [SAR 1:1 DAR 15:16], 102 kb/s, 25 fps, > 25 tbr, 12800 tbn, 50 tbc (default) > > with the patch Stream #0:0(und): Video: h264 (High) (avc1 / > 0x31637661), yuv420p, 540x576 [SAR 1:1 DAR 15:16], 102 kb/s, SAR > 93207:65536 DAR 1016804:762601, 25 fps, 25 tbr, 12800 tbn, 50 tbc > (default) > > This last one is the intended and correct one. why are SAR and DAR in the output twice now? it might be confusing to users? or just me... -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [SPI] Outreachy funding
On Wed, 3 Feb 2016 10:08:43 +0100 Stefano Sabatini wrote: > > I'd also suggest to pay the mentor with the fund, for a total of 500 > USD, to incentivate him/her. sounds good to me. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Libavcodec consulting
On Thu, 3 Mar 2016 12:11:25 + Jonathan Girven wrote: > Hi all, Hi , i'm not a consultant , but i maybe can help clarify a thing. > The requirements are: > > - The file is hosted on a remote http server. > > - The original file is in mp4 format. > > - The code cannot read in the entire remote video file to get a > segment at the end of the file. the mp4 format can either have an index at the start of the file or at the end of the file. you cannot read (easily) an mp4 file without its index. http://wiki.multimedia.cx/index.php?title=MP4 http servers can be made to support "request range" and thus allow seeking to the start or end of the mp4 file. existing mp4 files can be edited to have the index at the start or end. otherwise, mp4 cannot be streamed. by anyone, in any situation (well, without serious hacks). the current way mp4 is "streamed" is to split up mp4 files into a thousand smaller mp4 files and sent to a player using a playlist. mp4 cannot be streamed. it sucks. changing the http server would be easier than changing mp4 indexing. or using an intermediate format would be easier (mkv perhaps). hope this helps -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] version.sh: Always use latest tag for generated version number
On Fri, 4 Mar 2016 14:44:28 -0800 Timothy Gu wrote: > So after all the email exchanges, I think there are certain things > that our version SHOULD contain: > > - The hash > - The next release (i.e. n3.1) > - A way to compare two versions > > The date is considered to be "good" but perhaps not as necessary. the problem i've seen when helping users when the date is inside the version string (in mplayer) is that the idiot distros build an old mplayer 1.1-2016-01-01 right? except mplayer 1.1 was released 3 years ago. in 2013. they just built a 3 year old tarball two months ago and users install it like it was new! which is why ffmpeg and mplayer have the copyright year in the version string to help. slightly. assuming distros dont mess with it. > > Any objections? > should put it up to a vote what devs and users want to see. otherwise its just a few vocal devs on the list dictating it for everyone :P -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Motion interpolation in libavfilter
On Tue, 8 Mar 2016 09:26:22 +0100 Paul B Mahol wrote: > On 3/8/16, Subhashish Pradhan wrote: > > Hello, > > > > I am Subhashish Pradhan, a CS undergrad from India. I want to take > > up the project "Motion interpolation in libavfilter" for GSoC 2016 > > and I'd like to understand the goals for this project. > > Goals are already written on wiki, if you have more specific > questions ask them. the goals on the wiki for motion interpolation in libavfilter are here: https://trac.ffmpeg.org/wiki/SponsoringPrograms/GSoC/2016#Motioninterpolationinlibavfilter some students have been having trouble finding the wiki page. maybe we could put a news entry about it ? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] How to handled gzip'd files?
On Sun, 3 Apr 2016 09:02:27 -0400 "Ronald S. Bultje" wrote: > Hi, > > On Sat, Apr 2, 2016 at 12:29 PM, Reimar Döffinger > wrote: > > > Do we have a way to transparently decompress? > > > Why would we? It's not like this is commonplace across all formats, > it's only present in a handful, and we can deal with it on a > case-by-case basis, just as we handle compressed mov. Right? if we have gzip demuxer and probe gzip compression... then pass it onto probe after decompressing? its not like compressed mov because the compressed mov header is inside of the regular mov container (iirc). there are a lot of video files that are zipped or rared. also zip compressed image files , example cbz/cbr. can we get zip/rar demuxer? some video players are able to play multipart rar video files. i understand that its still a low priority. https://trac.ffmpeg.org/ticket/4374 -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Line endings in Makefiles
On Fri, 22 Apr 2016 07:52:56 +0200 Andreas Weis wrote: > here) there are no drawbacks arising from the change. if we have mismatched line endings in makefiles it might screw up anyone wishing to make patches if their git has changed the line endings. i cant remember if this is a problem however, probably not. generally its ffmpeg rule to not apply hacks for broken build systems (of which, msys/mingw's outdated libs count as this). i am for your patch, but i am not maintainer. ;) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] avformat/riff: assign g721 and g723 codec tags to g726 decoder
On Wed, 27 Apr 2016 20:39:34 +0200
Piotr Bandurski wrote:
> Subject: [PATCH] avformat/riff: assign g721 and g723 codec tags to
> g726 decoder
> +{ AV_CODEC_ID_ADPCM_G726, 0x0014 },
> +{ AV_CODEC_ID_ADPCM_G726, 0x0040 },
i wonder if we should make a comment that these are different codecs,
in the unlikely eventuality that we split 721 723 and 726 decoders from
one another?
> +{ AV_CODEC_ID_ADPCM_G726, 0x0014 }, /* g723 Antex */
> +{ AV_CODEC_ID_ADPCM_G726, 0x0040 }, /* g721 Antex */
?
"Antex" taken from twocc list:
http://wiki.multimedia.cx/index.php?title=TwoCC
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 57/57] support for matrox m703 mpeg-2
On Tue, 26 Apr 2016 17:11:26 +0300
Александр Слободенюк wrote:
> { AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '1') },
> +{ AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '3') },
> { AV_CODEC_ID_MPEG2VIDEO, MKTAG('M', '7', '0', '5') },
i wonder if we can add m702 + m704 as well? i do not have samples but
it looks like mpeg2 from the information i have.
VIDC.M701=mvcVfwSwitcher.dll Matrox MPEG-2 I-frame HD
VIDC.m702=digivcap.dll Matrox Offline HD
VIDC.M703=mvcVfwMpeg2HDV.dll
VIDC.M704=mvcVfwMpeg2Alpha.dll
VIDC.M705=mvcVfwMpeg2AlphaHD.dll
http://wiki.multimedia.cx/index.php?title=Category_talk:Video_FourCCs
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 57/57] support for matrox m703 mpeg-2
On Mon, 02 May 2016 18:50:18 +0200 Piotr Bandurski wrote: > > > > > VIDC.m702=digivcap.dll Matrox Offline HD > > > > It looks like I managed to create samples for this: > > > > > > but the problem is that there are some errors while decoding > > "m702_2.avi". > > > > https://www.datafilehost.com/d/524f41e4 > > and it may be similar thing like in ticket #2615 as long as we are throwing out questions. the m70x stuff is similar to m10x . and uses same binary codec: VIDC.M101=mvcVfw.dll VFW M101 Matrox Uncompressed SD VIDC.m102=mvcVfwHD.dll Matrox Uncompressed HD VIDC.m103=mvcVfwYUVA.dll Matrox Uncompressed SD + Alpha VIDC.m104=mvcVfwYUVAHD.dll Matrox Uncompressed HD + Alpha VIDC.M301=mvcVfwRefAVI.dll any chance for more samples ? you rock at samples! only took 6 years... https://ffmpeg.org/pipermail/ffmpeg-devel/2010-June/091180.html -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] avformat/riff: assign g721 and g723codec tags to g726 decoder
On Sun, 01 May 2016 00:09:46 +0200
Piotr Bandurski wrote:
> > > On Wed, 27 Apr 2016 20:39:34 +0200
> > Piotr Bandurski wrote:
> >
> > > Subject: [PATCH] avformat/riff: assign g721 and g723 codec tags to
> > > g726 decoder
> >
> > > + { AV_CODEC_ID_ADPCM_G726, 0x0014 },
> > > + { AV_CODEC_ID_ADPCM_G726, 0x0040 },
> >
> > i wonder if we should make a comment that these are different
> > codecs, in the unlikely eventuality that we split 721 723 and 726
> > decoders from one another?
> >
> > > + { AV_CODEC_ID_ADPCM_G726, 0x0014 }, /* g723 Antex */
> > > + { AV_CODEC_ID_ADPCM_G726, 0x0040 }, /* g721 Antex */
> >
> > ?
>
> I'm ok with this change.
merged,
thanks
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] why ffmpeg reports error when decoding rm or rmvb files
On Mon, 16 May 2016 17:35:03 +0800 (CST) qw wrote: > Hi, > > I'm using the following command to decode some rm and rmvb files, and > ffmpeg reports error as shown below: > > [root@PT-18376 test-clips]# ffmpeg -i hanma.rm -xerror -f > null /dev/null ffmpeg version 2.8.3 Copyright (c) 2000-2015 the > FFmpeg developers built with icc (ICC) 14.0.2 20140120 hi, does error still occur with latest 2016 ffmpeg? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 14:41:46 +0100 Derek Buitenhuis wrote: > On 5/18/2016 2:30 PM, Carl Eugen Hoyos wrote: > > Since you indicated lately that you are so terribly interested > > in the tone here: > > Please stop making such comments! > > It's a legitimate criticism. You refuse to follow the FFmpeg > developer rules of using git format-patch. carl is grandfathered in :P -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 14:10:57 +0200 Paul B Mahol wrote: > On 5/18/16, Carl Eugen Hoyos wrote: > > Hi! > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > demuxer. > > > > Please comment, Carl Eugen > > > > Please attach actual patch with commit log message. commit message is in the subj of the email i thought. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 16:12:40 +0200 Paul B Mahol wrote: > Dana 18. 5. 2016. 16:05 osoba "compn" napisala je: > > > > On Wed, 18 May 2016 14:10:57 +0200 > > Paul B Mahol wrote: > > > > > On 5/18/16, Carl Eugen Hoyos wrote: > > > > Hi! > > > > > > > > Attached patch allows to mux raw G.729 as supported by our G.729 > > > > demuxer. > > > > > > > > Please comment, Carl Eugen > > > > > > > > > > Please attach actual patch with commit log message. > > > > commit message is in the subj of the email i thought. > > Even if that's true It's not enough. the commit message itself "lavf/rawenc: Add a G.729 muxer" is deficient in some way? if you could, please expand your answer? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH]lavf/rawenc: Add a G.729 muxer
On Wed, 18 May 2016 16:24:53 +0200 wm4 wrote: > That's why it's important. But he keeps ignoring our requests to > change this, mostly because he disrespects us for working with his > sworn arch-enemy, Libav. comments like this are not helpful. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Remove Derek Buitenhuis from MAINTAINERS
On Fri, 20 May 2016 01:55:15 +0200 Lukasz Marek wrote: > On 19 May 2016 at 15:18, Derek Buitenhuis > wrote: > > > On 5/19/2016 2:12 PM, Michael Niedermayer wrote: > > > if derek still wants to leave in 2 weeks then so be it, its his > > > choice but i really hope things can be resolved in a way that > > > everyone stays and works together and is happy > > > > I will wait 2 weeks. > > > > Is Derek revoked to commit or what? Couldn't he just commit this > patch and leave? :P I was a problem for some people, but I see they derek and all other devs still have commit access. no one has been banned, removed, sanctioned or anything. derek said he unsubscribed from the mailing lists, himself. nothing stopping him from committing this himself. i would hope developers could work, if not together, at least tolerate each other. i understand some devels have had disagreements for years now. i'd hate to see anyone leave, but i also am not a fan of arguments in every thread either. i ignore comments most times and stick to the code. imo i wouldnt call any discussions in the past years "toxic". a few gripes, snarks or passive agressive comments from a few developers, sure. show me one software project that doesnt have conflicts between developers. if any of my mail has offended anyone, please read it with the most gracious and open tone, i am not trying to be insulting. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Prores encoding optmizations
On Mon, 23 May 2016 14:30:54 +0200 Håvard Espeland wrote: > Currently, we are also developing a version of the same encoder for > Nvidia TX1 with Cuda/Neon SIMD for supporting multiple high quality > streams in real time using ffmpeg. I guess there is little interest > in merging this as well, but please let us know otherwise. we always welcome patches, even if we dont merge them immediately. please share with us the cuda simd when you get it working. theres always the chance that we will convert it to yasm. prores is a highly used codec, so there is lots of interest in making it faster. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] IRC meeting
On Fri, 3 Jun 2016 20:32:51 +0200 Christophe Gisquet wrote: > SIX) > > May 28 19:32:58since cehoyos is here, we could > > maybe talk about his behavior and why the CoC and repercussions for > > violating it was introduced to begin with May 28 21:51:31 > > is there anything concrete we’re going to do w.r.t. derek and carl? > > May 28 21:59:52So Derek and carl? May 28 22:26:54 > > its too late now, and we need to handle the > > situation at hand May 28 22:28:24nevcairiel, do > > you want a vote here and now, to what effect? May 28 22:31:09 > >I agree that a vote on the ML would be better to give > > people that fell asleep here the chance to participate also May 28 > > 22:34:59It's late here. I'm ok for a vote also, > > just not sure what kind of offense it would be > > And the big, flashy pink, elephant in the room: > Action: draft a vote on the repercussions to Carl Eugen Hoyos > behaviours (patch submission, general interaction with others) > Note, I don't have a strong idea on what it may contain (option of > temp/week/perma ban, warning, removal of some rights, etc). i am against voting on rules and then retroactively applying them to anyone. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] IRC meeting
On Fri, 3 Jun 2016 21:13:09 +0200 Michael Niedermayer wrote: > On Fri, Jun 03, 2016 at 08:32:51PM +0200, Christophe Gisquet wrote: > i want some assistent to help with dayly server admin duties > most root admins we have help and contribute but are often busy > raz recently set up a full backup system for us, someone seems > helping with security updates as iam not always the first doing them > (i think its lou but didnt check) and all kinds of other things ... > > what would be really nice would be someone who has some time and for > whom server admining is a fun thing to do, > someone who would do it "because it needs to be done" would be 2nd > choice IMHO > i am against using github, but am for using vlc admins if we vote that way. i think i may take back my offer to admin. i was more offering to help michael with $random admin tasks. but i dont think i can dedicate much time to it, sorry :( > > [...] > > SIX) > > > May 28 19:32:58since cehoyos is here, we could > > > maybe talk about his behavior and why the CoC and repercussions > > > for violating it was introduced to begin with May 28 21:51:31 > > >is there anything concrete we’re going to do w.r.t. derek > > > and carl? May 28 21:59:52So Derek and carl? May > > > 28 22:26:54 its too late now, and we need to > > > handle the situation at hand May 28 22:28:24 > > > nevcairiel, do you want a vote here and now, to what effect? May > > > 28 22:31:09I agree that a vote on the ML would be better > > > to give people that fell asleep here the chance to participate > > > also May 28 22:34:59It's late here. I'm ok for a > > > vote also, just not sure what kind of offense it would be > > > > And the big, flashy pink, elephant in the room: > > Action: draft a vote on the repercussions to Carl Eugen Hoyos > > behaviours (patch submission, general interaction with others) > > Note, I don't have a strong idea on what it may contain (option of > > temp/week/perma ban, warning, removal of some rights, etc). > > iam not suggesting anything specific but there is one thing that i > think i have not seen talked about and that is moderation. Mailman > supports moderating individual subscribers. > > It might be along the lines of > If one repeatly and conciously violates the CoC and no real solution > can be found, he can be given the choice by the mailman admins to > either promise to attempt not to repeat the violation > or to be moderated until an event occurs that changes the situation > or some timeout. > The insulted person should have the option to veto this at any time so > if one feels that it wasnt enough to justify the inconvenience the > "hurt" party should be able to stop this. > This would have to be combined with something effective for IRC and > possibly git, in case issues shift there too i like the idea of moderating certain members, when they start in with insults. assuming we vote in the CoC... i personally enjoy free speech to insult everyone but , democracy :P -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] IRC meeting
On Sat, 4 Jun 2016 13:03:47 +0200 Michael Niedermayer wrote: > On Fri, Jun 03, 2016 at 10:19:29PM -0400, compn wrote: > > On Fri, 3 Jun 2016 21:13:09 +0200 > > Michael Niedermayer wrote: > > > > > On Fri, Jun 03, 2016 at 08:32:51PM +0200, Christophe Gisquet > > > wrote: i want some assistent to help with dayly server admin > > > duties most root admins we have help and contribute but are often > > > busy raz recently set up a full backup system for us, someone > > > seems helping with security updates as iam not always the first > > > doing them (i think its lou but didnt check) and all kinds of > > > other things ... > > > > > > what would be really nice would be someone who has some time and > > > for whom server admining is a fun thing to do, > > > someone who would do it "because it needs to be done" would be 2nd > > > choice IMHO > > > > > > > i am against using github, but am for using vlc admins if we vote > > that way. > > > What exactly are all these suggestions about ? > "Delegate admin tasks to VLC", "using vlc admins", "move to github", > ... > ? > I think this needs to be understood first ... someone thought you did not want to be admin. if you are happy to be admin, i am happy :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 1/2] Remove Benjamin Larsson from MAINTAINERS
On Fri, 10 Jun 2016 04:09:26 +0200 Michael Niedermayer wrote: > On Thu, Jun 09, 2016 at 10:01:27PM +0200, Michael Niedermayer wrote: > > On Thu, Jun 09, 2016 at 09:21:22PM +0200, Benjamin Larsson wrote: > > > --- > > > MAINTAINERS | 9 ++--- > > > 1 file changed, 2 insertions(+), 7 deletions(-) > > > > may i ask why you leave ? > > i understand you where leaning more toward the fork and where > > inactive for a long time but still, it almost feels inpolite of me > > to just apply this without asking > > i received a private reply from ben about this > just saying so it doesnt look like he ignored the question Benjamin also removed himself from libav consulting as well. http://lists.libav.org/pipermail/libav-devel/2016-June/077471.html the usual reason for not being a consultant anymore is that the dev got a full time job. or realized that they do not have enough free time to work on small consulting jobs. working on ffmpeg, libav or any other multimedia oss project is an interesting way to get hired. or to start their own video related business. :) devs come and go, the number one reason is lack of free time. thats whats nice about open source, you can pick it up and drop it whenever. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] bans
On Wed, 15 Jun 2016 21:21:28 -0300 James Almer wrote: ... you are aware that we have voted in a code of conduct.[1] you may want to review it, again. https://ffmpeg.org/developer.html#Code-of-conduct calling developers names will not be tolerated. -compn [1] http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2016-May/194529.html ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] MAINTAINERS: Add myself for videotoolbox.c, remove vda* maintainer
On Thu, 16 Jun 2016 09:12:39 -0400 Rick Kern wrote: > Person in MAINTAINERS hasn't responded to a patch on the ML or private > email, and doesn't maintain the files according to git. LGTM -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] bans
On Thu, 16 Jun 2016 00:56:28 -0300 James Almer wrote: > I don't think i called him names but if you think i did and violated >>You'll get inside a spiral of bullshit with no >>end until you decide to stop feeding the troll disguised as worried >>contributor. you did call him a troll. :D > the CoC then you're welcome to call a vote for whatever action you nah, i actually dont give a shit. i'm for free speech, not nonsense censorship. :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] bans
On Thu, 16 Jun 2016 15:21:47 +0200 Michael Niedermayer wrote: > I agree but if i do nothing people are unhappy that i did nothing, > if i talk with people trying to resolve a conflict well, it did not > work this time. and if i do something else people complain too. you tried. thanks for trying. why is no one happy? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] FFmpeg 3.1 name
On Thu, 23 Jun 2016 23:00:48 +0200 Michael Niedermayer wrote: > what shall FFmpeg 3.1 be called ? > Are there other suggestions? has fibonacci been used? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [RFC] beginner difficulty bug trac tag for new open source developers
hello about once a month (also, around OPW/GSOC time) we get people in #ffmpeg-devel or the ml asking about contributing to ffmpeg. i think we need to try to organize something for new contributors. usually there is only one or two devs alive (including me) to guide newbies. most times these want-to-be devs already have knowledge of git, make, etc and have c or c++ programming skills. what they ask for is an easy way to start or easy bugs to look at. so my proposed idea is to make a tag or priority on the bug tracker for "easy" bugs. that way new contributors can look at a list of bugs that are easy to fix. what i need from you, fellow reader: 1. do you think this is a good idea? or do you have other ideas to help? maybe write a newbie developer guide for developer documentation? is there any knowledge from the OPW/gsoc mentors that we should put in the developer docs? 2. what the name of this bug tag should be? "easy bugs" ? "beginner difficulty" ? 3. are there other oss projects out there that already help new contributors? can we steal something from them? i'm not sure what criteria would make for an easy bug vs a hard bug. but i'd rather leave that open to whoever adds/reviews the bug. i think we all agree adding a codec tag or documentation is easier than adding 3d mvc h264 support. i'm also not suggesting tagging every bug with a difficulty rating , as that would take a while and i'm not sure of the benefit. i just want to have a solid number (100-300+) of bugs that are somewhat easy to understand, implement, review and finish. have a great summer (for those in the northern hemisphere), -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [RFC] beginner difficulty bug trac tag for new open source developers
On Mon, 4 Jul 2016 12:43:03 +0300 Sami Hult wrote: > My five cents would be to advice every aspiring contributor to focus > on bugs or lacking features that are an issue for themselves. That > ensures motivation to really fix it :) that is good advice, thank you. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Added Quadrox format
On Tue, 5 Jul 2016 09:57:28 +0200 Michael Niedermayer wrote: > On Mon, Jul 04, 2016 at 06:13:50AM +0530, smitbose wrote: > > --- > > libavformat/riff.c | 1 + > > 1 file changed, 1 insertion(+) > > applied > > thanks congratulations on your first contribution to ffmpeg, smitbose. welcome to the world of open source. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] ffmpeg: Remove deadcode
On Mon, 26 Dec 2016 21:35:12 +0100 Michael Niedermayer wrote: > -int stop_encoding = 0; it would be nice if the commit message was "ffmpeg: remove stop_encoding function , it is dead / unused code" or so, with the function name in the message? easier to grep? i have not tested patch... -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Implement optimal huffman encoding for (M)JPEG.
On Tue, 27 Dec 2016 07:37:09 + Jerry Jiang wrote: > Hey everyone, > > This is my first patch submitted to FFmpeg, so I'm sure that I missed > something. Please bear with me. :P This patch implements the solution > outlined here: https://guru.multimedia.cx/small-tasks-for-ffmpeg/ hi! it is impressive for a first patch! well done. your patch is missing docs (document -huffman optimal by creating mjpeg encoder section in doc/encoders.texi) and changelog entry (Optimal Huffman tables for MJPEG encoding). -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] Implement optimal huffman encoding for (M)JPEG.
On Wed, 28 Dec 2016 08:13:52 + Rostislav Pehlivanov wrote: > The only problem I have with the code is that it uses a linked list > and calls malloc during runtime. Couldn't the linked list be replaced > with an array allocated during init (it should be okay, I don't think > resolution is allowed to change during encoding)? That way it'll be did you test our samples where the resolution changes mid stream? http://samples.ffmpeg.org/V-codecs/VP6/size_change.nsv http://samples.ffmpeg.org/MPEG2/resolutionchange.mpg http://samples.ffmpeg.org/MPEG2/res_change_ffmpeg_aspect.ts someone should probably organize a small suite of res changing samples... i think someone had a bunch of them, maybe michael or stefano? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] patch for Sricam, Floureon, etc. IP cameras
On Fri, 30 Dec 2016 14:32:06 -0800 John Comeau wrote: > diff --git a/TODO.txt b/TODO.txt > new file mode 100644 > index 00..1b0c64c186 > --- /dev/null > +++ b/TODO.txt > @@ -0,0 +1 @@ > +2016-12-06: Fix assembly for NASM. See > http://stackoverflow.com/questions/36854583/compiling-ffmpeg-for-kali-linux-2 this change looks unrelated. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] ffserver: local OOB write with custom program name
On Fri, 6 Jan 2017 23:33:16 +0100 Tobias Stoeckmann wrote: > +slash = strrchr(my_program_name, '/'); > +memcpy(pathname, my_program_name, slash - my_program_name); > -strcpy(slash, "ffmpeg"); > +strcat(pathname, "ffmpeg"); this replaces a strcpy with a memcpy, is this intended (and safe?)? (possibly this is a dumb question, if so, please ignore this mail.) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] xalg xdcam isom ticket #6099
patch for #6099
https://trac.ffmpeg.org/ticket/6099
while i was looking, it seems there is also an avlg codec isom, but i see only
one result in google so i did not add it.
{ AV_CODEC_ID_H264, MKTAG('a', 'v', 'l', 'g') }, /* Panasonic P2 AVC-LongG */
i would prefer we added avlg as well, even if we don't have samples.
-compn
xalg.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Video decoding error asks me to upload video to non-existing site ftp://upload.ffmpeg.org/incoming/
On Tue, 31 Jan 2017 13:09:07 +0100 Thilo Borgmann wrote: > We mention ftp://upload.ffmpeg.org/incoming/ in several places. If it > is not the place to upload things then these messages should be > changed accordingly and the preferred way to upload samples need to > be documented. currently upload.ffmpeg.org points to streams.videolan.org , videolan is currently hosting our incoming ftp server access. videolan has been having trouble with it for a while. you can see posts on the internet complaining about the automatic vlc bug reporter also being down because of this. what we need is someone to run a small ftp drop for large files, i guess i'll post a patch for the ffmpeg.org page requesting such hosting temporarily. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [PATCH] [rfc] web/index request incoming ftp server
not sure if this is the right way to do it, maybe its easier to ask for someone on twitter? it would be nice to have a backup just in case videolan has problems. then we dont have to ask users to use datafilehost heh. i dont want to burden ffmpeg admins to maintain some ftp either. carl, what do you think? ideas welcome. -compndiff --git a/src/index b/src/index index c203676..cf45f4f 100644 --- a/src/index +++ b/src/index @@ -37,6 +37,15 @@ News + February 01, 2017, Backup ftp server needed. + +We are in need of a ftp backup for users to upload sample files to us. +Our current ftp, hosted by videolan, is still being worked on, with no ETA for a fix. + + +What we need: public ftp with anonymous upload only, and authenticated read/downloads for developers. +space a few TB, speed 1mb/s+. Nothing fancy. Please send mail to proje...@ffmpeg.org if you want to help. + October 30th, 2016, Results: Summer Of Code 2016. This has been a long time coming but we wanted to give a proper closure to our participation in this run of the program and it takes time. Sometimes it's just to get the final report for each project trimmed down, others, is finalizing whatever was still in progress when the program finished: final patches need to be merged, TODO lists stabilized, future plans agreed; you name it. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [rfc] web/index request incoming ftp server
On Wed, 1 Feb 2017 07:34:11 +0100 wm4 wrote: > On Wed, 1 Feb 2017 00:09:41 -0500 > compn wrote: > > > not sure if this is the right way to do it, maybe its easier to ask > > for someone on twitter? > > > > it would be nice to have a backup just in case videolan has > > problems. then we dont have to ask users to use datafilehost heh. > > > > i dont want to burden ffmpeg admins to maintain some ftp either. > > > > carl, what do you think? > > ideas welcome. > > > > -compn > > Who maintains this piece of infrastructure at all? videolan maintained the server, carl does most of the moving files to our samples repo and bug trac. but heres the new news from #videolan: [05:41] Compn, http://streams.videolan.org/upload/ should work more or less ^ this is currently where we should send users to upload files. an http uploader (not sure about resume support...). [05:49] Compn, there will be no ftp access to streams, ever [05:50] Compn, we're following the Great Leadership of kernel.org ^^ this is the news on the ftp that we currently have in our docs. so we should change all of our docs over to the http uploader. also i suggest we ask for a backup ftp server from another host (by applying this or similar patch), for those people who prefer to use ftp. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [rfc] web/index request incoming ftp server
On Wed, 1 Feb 2017 17:45:16 +0100, Carl Eugen Hoyos wrote: > 2017-02-01 14:10 GMT+01:00 compn : > > > [05:41] Compn, http://streams.videolan.org/upload/ > > should work more or less > > > > ^ this is currently where we should send users to upload files. > > an http uploader (not sure about resume support...). > > > > [05:49] Compn, there will be no ftp access to streams, ever > > Apart from the fact that this contradicts a promise that has been > made: yes i noticed that too. oh well. i've made the changes to mplayer DOCS, although it would be nice to also have a backup ftp server for people using old docs and the old ftp url. (todo: update urls in the homepage repo). > How are we supposed to access the samples? files uploaded with the vlc http upload http://streams.videolan.org/upload/ are immediately accessable publically here, with no login. http://streams.videolan.org/ffmpeg/incoming/ i just tested and all seems to be working. aside from having to put in a vlc version for ffmpeg and mplayer. has anyone reviewed the files in http://streams.videolan.org/ffmpeg/ ? go to http://streams.videolan.org/ and there is a dir for mplayer and mplayer/incoming as well http://streams.videolan.org/MPlayer/ http://streams.videolan.org/MPlayer/incoming/ -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Video decoding error asks me to upload video to non-existing site ftp://upload.ffmpeg.org/incoming/
On Tue, 31 Jan 2017 17:34:55 +0100 DogFilm wrote: > I am still waitinng for an upload facility. Please send me an email > so I can follow this. Also please consider removing that mis-leading > information from ffmpeg error msgs, thanks, have to move on! hi, please use this to upload your file: http://streams.videolan.org/upload/ thank you. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH] [rfc] web/index request incoming ftp server
On Thu, 2 Feb 2017 09:30:30 +0100, Carl Eugen Hoyos wrote: > 2017-02-01 19:36 GMT+01:00 Compn : > > >> How are we supposed to access the samples? > > > > files uploaded with the vlc http upload > > http://streams.videolan.org/upload/ > > > > are immediately accessable publically here, with no login. > > http://streams.videolan.org/ffmpeg/incoming/ > > Meaning our promise to our users that we can keep the > samples to ourselves is broken;-( thats what we need a private ftp for, private samples. > That's apart from the fact that from my pov the whole > idea was of course that we are able to access the vlc > samples to get more bug reports... the vlc samples are http://streams.videolan.org/ i have just now asked about getting a login for the vlc incoming. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] DVR MPEG4 variant (AS-3024)
On Fri, 3 Feb 2017 15:46:20 +0200, Ivo Andonov wrote: > I successfully used a modified Pinetron library on Windows to use my own > software for decoding the stream. While fiddling with the modification I > saw they are using the statically linked FFmpeg API. the dvr company ships ffmpeg? they must ship ffmpeg source as well, the modified ffmpeg source may contain the patch needed to play such dvr files. where can we see this pinetron library ? -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] DVR MPEG4 variant (AS-3024)
On Sat, 4 Feb 2017 12:59:13 +0100, wm4 wrote: > On Sat, 4 Feb 2017 00:02:16 +0200 > Ivo Andonov wrote: > > > 2017-02-03 23:18 GMT+02:00 Compn : > > > > > On Fri, 3 Feb 2017 15:46:20 +0200, Ivo Andonov > > > wrote: > > > > > > > I successfully used a modified Pinetron library on Windows to use my own > > > > software for decoding the stream. While fiddling with the modification I > > > > saw they are using the statically linked FFmpeg API. > > > > > > the dvr company ships ffmpeg? they must ship ffmpeg source as well, the > > > modified ffmpeg source may contain the patch needed to play such > > > dvr files. > > > > > > where can we see this pinetron library ? > > > > > > -compn > > > ___ > > > ffmpeg-devel mailing list > > > ffmpeg-devel@ffmpeg.org > > > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > > > > > > I thought the same as well but am not too much into the licencing terms... > > I tried in vain finding any sources. > > They do not ship ffmpeg directly (as a separate library). They modify the > > source and use it statically linked in their projects. > > This is a link to the IE ActiveX for playing the stream (displaying DVR > > cams): http://www.dvrstation.com/pdvratl.php?vendor=0#version=1,0,1,26 This > > is also the library I modded in order to use the decoder on Windows > > platforms before I decided to spend some time to research the differences > > in respect to the MPEG4 standard and use the stream in a Linux environment. > > > > This is a link to a 64-bit Linux app: > > http://pinetron.ru/files/software/cms-lite-linux.zip Never actually tried > > it. The libpapi-shared.so.* files are clearly based on the ffmpeg source. > > > > This is the android app: http://www.apkmonk.com/app/com.pinetron.TouchCMS/ > > One library in there for Arm, also clearly based on ffmpeg. > > Can you ask them for source? I don't think the GPL obligates them to i mean technically, if they put it on http where you can wget, you can also ask them for source, since they distributed something based on ffmpeg to you... but yeah someone should ask them. i was off looking at 3 different pinetron websites and didnt even see pinetron.ru :\ -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [rfc] tasks for new ffmpeg developers
people new to the project join #ffmpeg-devel and ask us for help on how to start contributing to ffmpeg. usually none of us have any cohesive answers. mostly suggestions are to review bugs or patches or code. nothing really concise or organized. i've reviewed a few bugs and think these may be good starting points for new developers to try. they might also be useful for qualification tasks in the future? i dont know. i'm not sure how to organize these, maybe a trac keyword? for now , i'll just post them here. if you have comments, suggestions, or just want to tell me that my idea is bad, please speak up. these have specs / open source implementations: https://trac.ffmpeg.org/ticket/5285 Missing subtitle format. ISMT (xml based) https://trac.ffmpeg.org/ticket/4728 support DICOM format (medical jpg image) https://trac.ffmpeg.org/ticket/1959 Support codec2 (os audio codec) https://trac.ffmpeg.org/ticket/2377 Support lossless mp3HD (abandoned? lossless audio codec) ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [rfc] tasks for new ffmpeg developers
On Mon, 06 Feb 2017 13:22:31 +, Kieran Kunhya wrote: > On Mon, 6 Feb 2017 at 05:54 Compn wrote: > > > people new to the project join #ffmpeg-devel and ask us for help on how > > to start contributing to ffmpeg. > > > > A simple one is work on making decoders threadsafe (pthread_once on static > inits). can you (or someone) come up with a simple starter howto and some doc or description for what exactly needs to be done? maybe is there a commit to a decoder showing what was done to make it threadsafe? the howto would detail how to test for threadsafe , what tools to use, what an unsafe thread does or looks like in valgrind or gdb etc? showing devs to use AVOnce and list other ff/av functions to fix unsafe code. grep FF_CODEC_CAP_INIT_THREADSAFE * to get the list of codecs that are thread safe. the rest need to be done, in order of useful codecs first? i'm not saying we have to hold everyones hand, but a little documentation, direction and clarity will go a LONG way in getting things worked on. :) i know the ffmpeg devs can do all of this in their sleep, backwards. but if you take the time to write down the steps you take, just once, maybe someone will read, learn and come to contribute. i found these quick posts about threadsafe code, maybe they help the curious. or maybe they arent applicable to ffmpeg at all. https://insights.sei.cmu.edu/sei_blog/2014/10/thread-safety-analysis-in-c-and-c.html http://www.thegeekstuff.com/2012/07/c-thread-safe-and-reentrant/ http://www.thinkingparallel.com/2006/10/15/a-short-guide-to-mastering-thread-safety/ thank you -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [rfc] ffmpeg security issue mailing list
On Thu, 09 Feb 2017 13:24:53 +, Kieran Kunhya wrote: > > > > I dont think we should give access to ffmpeg-security to everyone who > > wants to be on the list. This is of course something the community > > has to decide and not me, iam just err-ing on the safe side and am very > > restrictive on who is added. > > > > This is a bogus argument considering how many people have commit access and > can commit whatever. honestly with the fearmongering? are you saying the russian ffmpeg developers can just commit whatever they want whenever they want?! also there are some chinese ffmpeg developers! even the president says china cant be trusted! the russians hacked the election and now they will put backdoors in ffmpeg!?!?! (this email is satire btw... i do not believe russia affected the us election, nor brexit. and china is cool with me.) if kierank and wm4 want on the -security list, please put them on the security list. i doubt anyone will vote against their inclusion on the list. count this as my vote for any current regular developers (e.g. the ones on irc or the non-irc devs if they have more than 1 year committing) to be subscribed if they want. thanks for reading. -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] [community vote] add devs to -security alias
as stated , this is a community issue, so heres the vote thread. vote to add kieran and wm4 to ffmpeg-security email alias. any votes for or against? votes will be tallied in 2 weeks. active committers/contributors will be counted. if you have ideas for how the -security should be handled, make a new thread. if you have comments about anything else, please make a different thread or talk on irc. this is the vote thread only. please oh please, just can we have one simple vote thread with no off-topic or flames? just once? "i vote for kieran and wm4 to be added to the ffmpeg-security email" -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
