From ariza.federico at gmail.com Wed Aug 3 14:56:17 2016 From: ariza.federico at gmail.com (Federico Ariza) Date: Wed, 3 Aug 2016 14:56:17 -0400 Subject: [Matplotlib-devel] New "data cursors for matplotlib" package: https://github.com/anntzer/mplcursors In-Reply-To: References: Message-ID: Hi Super cool! One idea. Why not add a simple tool (new ToolManager) to activate/deactivate the mplcursors at will from the toolbar? If you need help don't hesitate to contact me If it does adapt well as a Tool we can talk about a PR to add it as a standard tool. Good job Federico On Jul 28, 2016 2:09 PM, "Antony Lee" wrote: 2016-07-28 9:51 GMT-07:00 Benjamin Root : > Hey, that is pretty slick! I especially like the decorator option to > connecting events to the cursor objects. > This is a pretty common pattern nowadays, probably could be added to matplotlib's event handling code itself. > > Kudos! > > Ben Root > > On Sun, Jul 24, 2016 at 8:41 PM, Antony Lee > wrote: > >> Hi all, >> >> I have written a new "data cursors for matplotlib" package, inspired from >> @joferkington's mpldatacursor but rewritten from scratch, with a much >> simpler API. Please have a look at https://github.com/anntzer/mplcursors >> . >> >> I hope you'll like it. >> >> Antony >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From antony.lee at berkeley.edu Wed Aug 3 17:47:56 2016 From: antony.lee at berkeley.edu (Antony Lee) Date: Wed, 3 Aug 2016 14:47:56 -0700 Subject: [Matplotlib-devel] New "data cursors for matplotlib" package: https://github.com/anntzer/mplcursors In-Reply-To: References: Message-ID: I'd be happy to give it a try once the new toolbar becomes usable from Qt (which is the backend I use all the time) :-) Note that you can currently already activate mplcursors for any of your scripts just by setting the MPLCURSORS environment variable to a JSON-encoded kwargs that will get passed to `mplcursors.cursor()` -- the simplest being `MPLCURSORS={} python foo.py`. Antony 2016-08-03 11:56 GMT-07:00 Federico Ariza : > Hi > > Super cool! > > One idea. Why not add a simple tool (new ToolManager) to > activate/deactivate the mplcursors at will from the toolbar? > If you need help don't hesitate to contact me > > If it does adapt well as a Tool we can talk about a PR to add it as a > standard tool. > > Good job > Federico > > On Jul 28, 2016 2:09 PM, "Antony Lee" wrote: > > > 2016-07-28 9:51 GMT-07:00 Benjamin Root : > >> Hey, that is pretty slick! I especially like the decorator option to >> connecting events to the cursor objects. >> > This is a pretty common pattern nowadays, probably could be added to > matplotlib's event handling code itself. > > >> >> Kudos! >> >> Ben Root >> >> On Sun, Jul 24, 2016 at 8:41 PM, Antony Lee >> wrote: >> >>> Hi all, >>> >>> I have written a new "data cursors for matplotlib" package, inspired >>> from @joferkington's mpldatacursor but rewritten from scratch, with a much >>> simpler API. Please have a look at >>> https://github.com/anntzer/mplcursors . >>> >>> I hope you'll like it. >>> >>> Antony >>> >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Matplotlib-devel at python.org >>> https://mail.python.org/mailman/listinfo/matplotlib-devel >>> >>> >> > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayryuusei at gmail.com Thu Aug 4 12:54:41 2016 From: jayryuusei at gmail.com (jayryuusei at gmail.com) Date: Thu, 4 Aug 2016 11:54:41 -0500 Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release Message-ID: Hi everyone, I apologize if this is a stupid question: Is there a page online somewhere I can look to see the current status of the the 2.0 release? (in terms of bugs and/or features that still need fixing/implementing) I see this page in the docs that shows the latest is beta 3 from today: http://matplotlib.org/devdocs/contents.html# I ask for 2 reasons: 1. I'd be willing to help put in some hours programming if you all could use the help 2. I'm curious if for new code I am writing now I should just stick with 1.5 or if it is worth already transitioning to 2.0 and using the betas. Thanks! Jayson -------------- next part -------------- An HTML attachment was scrubbed... URL: From story645 at gmail.com Thu Aug 4 13:14:21 2016 From: story645 at gmail.com (Hannah) Date: Thu, 4 Aug 2016 13:14:21 -0400 Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release In-Reply-To: References: Message-ID: Most things tagged with the 2.0 milestone on github is probably a good place to start: https://github.com/matplotlib/matplotlib/issues?q=is%3Aopen+is%3Aissue+milestone%3A%222.0+%28style+change+major+release%29%22 https://github.com/matplotlib/matplotlib/pulls?q=is%3Aopen+is%3Apr+milestone%3A%222.0+%28style+change+major+release%29%22 On Thu, Aug 4, 2016 at 12:54 PM, jayryuusei at gmail.com wrote: > Hi everyone, > > I apologize if this is a stupid question: > Is there a page online somewhere I can look to see the current status of > the the 2.0 release? (in terms of bugs and/or features that still need > fixing/implementing) > > I see this page in the docs that shows the latest is beta 3 from today: > http://matplotlib.org/devdocs/contents.html# > > I ask for 2 reasons: > 1. I'd be willing to help put in some hours programming if you all could > use the help > 2. I'm curious if for new code I am writing now I should just stick with > 1.5 or if it is worth already transitioning to 2.0 and using the betas. > > Thanks! > Jayson > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Thu Aug 4 14:19:14 2016 From: pmhobson at gmail.com (Paul Hobson) Date: Thu, 4 Aug 2016 11:19:14 -0700 Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release In-Reply-To: References: Message-ID: Jay, My understanding is that the 2.0 release is only backwards incompatible in the sense that the default aesthetics are changing. APIs will be consistent between 1.5.X and 2.0.X -paul On Thu, Aug 4, 2016 at 9:54 AM, jayryuusei at gmail.com wrote: > Hi everyone, > > I apologize if this is a stupid question: > Is there a page online somewhere I can look to see the current status of > the the 2.0 release? (in terms of bugs and/or features that still need > fixing/implementing) > > I see this page in the docs that shows the latest is beta 3 from today: > http://matplotlib.org/devdocs/contents.html# > > I ask for 2 reasons: > 1. I'd be willing to help put in some hours programming if you all could > use the help > 2. I'm curious if for new code I am writing now I should just stick with > 1.5 or if it is worth already transitioning to 2.0 and using the betas. > > Thanks! > Jayson > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jayryuusei at gmail.com Thu Aug 4 14:49:32 2016 From: jayryuusei at gmail.com (jayryuusei at gmail.com) Date: Thu, 04 Aug 2016 18:49:32 +0000 Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release In-Reply-To: References: Message-ID: Hi Paul, Thanks for the info. I thought it was more than that, so that is a good point to help me decide. I think I'll just stick to 1.5 then. Thanks! Jay On Thu, Aug 4, 2016, 1:19 PM Paul Hobson wrote: > Jay, > > My understanding is that the 2.0 release is only backwards incompatible in > the sense that the default aesthetics are changing. APIs will be consistent > between 1.5.X and 2.0.X > -paul > On Thu, Aug 4, 2016 at 9:54 AM, jayryuusei at gmail.com > wrote: > >> Hi everyone, >> >> I apologize if this is a stupid question: >> Is there a page online somewhere I can look to see the current status of >> the the 2.0 release? (in terms of bugs and/or features that still need >> fixing/implementing) >> >> I see this page in the docs that shows the latest is beta 3 from today: >> http://matplotlib.org/devdocs/contents.html# >> >> I ask for 2 reasons: >> 1. I'd be willing to help put in some hours programming if you all could >> use the help >> 2. I'm curious if for new code I am writing now I should just stick with >> 1.5 or if it is worth already transitioning to 2.0 and using the betas. >> >> Thanks! >> Jayson >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ariza.federico at gmail.com Thu Aug 4 14:52:11 2016 From: ariza.federico at gmail.com (Federico Ariza) Date: Thu, 4 Aug 2016 14:52:11 -0400 Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release In-Reply-To: References: Message-ID: Big changes are coming for 2.1 (Mep27, Mep22, Mep23, ....) Help is always welcome Federico On Aug 4, 2016 2:49 PM, "jayryuusei at gmail.com" wrote: > Hi Paul, > > Thanks for the info. I thought it was more than that, so that is a good > point to help me decide. I think I'll just stick to 1.5 then. > > Thanks! > > Jay > > On Thu, Aug 4, 2016, 1:19 PM Paul Hobson wrote: > >> Jay, >> >> My understanding is that the 2.0 release is only backwards incompatible >> in the sense that the default aesthetics are changing. APIs will be >> consistent between 1.5.X and 2.0.X >> -paul >> On Thu, Aug 4, 2016 at 9:54 AM, jayryuusei at gmail.com < >> jayryuusei at gmail.com> wrote: >> >>> Hi everyone, >>> >>> I apologize if this is a stupid question: >>> Is there a page online somewhere I can look to see the current status of >>> the the 2.0 release? (in terms of bugs and/or features that still need >>> fixing/implementing) >>> >>> I see this page in the docs that shows the latest is beta 3 from today: >>> http://matplotlib.org/devdocs/contents.html# >>> >>> I ask for 2 reasons: >>> 1. I'd be willing to help put in some hours programming if you all could >>> use the help >>> 2. I'm curious if for new code I am writing now I should just stick with >>> 1.5 or if it is worth already transitioning to 2.0 and using the betas. >>> >>> Thanks! >>> Jayson >>> >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Matplotlib-devel at python.org >>> https://mail.python.org/mailman/listinfo/matplotlib-devel >>> >>> > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From juichenieder-nabb at yahoo.co.uk Mon Aug 8 16:56:17 2016 From: juichenieder-nabb at yahoo.co.uk (OceanWolf) Date: Mon, 8 Aug 2016 20:56:17 +0000 (UTC) Subject: [Matplotlib-devel] Where to look for current status / info about 2.0 release In-Reply-To: References: Message-ID: <2074422840.19558902.1470689777447.JavaMail.yahoo@mail.yahoo.com> But no API breaks with those big changes for now as we shall release them in 2.1 as opt-in, before changing them to opt-out, before finally deprecating the old API.? The changes that Federico talks about only relates to the user-interface API though. Best,OceanWolf From: Federico Ariza To: jayryuusei at gmail.com Cc: matplotlib development list Sent: Thursday, 4 August 2016, 20:52 Subject: Re: [Matplotlib-devel] Where to look for current status / info about 2.0 release Big changes are coming for 2.1 (Mep27, Mep22, Mep23, ....)Help is always welcomeFederico On Aug 4, 2016 2:49 PM, "jayryuusei at gmail.com" wrote: Hi Paul,Thanks for the info. I thought it was more than that, so that is a good point to help me decide. I think I'll just stick to 1.5 then. Thanks!Jay On Thu, Aug 4, 2016, 1:19 PM Paul Hobson wrote: Jay, My understanding is that the 2.0 release is only backwards incompatible in the sense that the default aesthetics are changing. APIs will be consistent between 1.5.X and 2.0.X-paulOn Thu, Aug 4, 2016 at 9:54 AM, jayryuusei at gmail.com wrote: Hi everyone, I apologize if this is a stupid question:Is there a page online somewhere I can look to see the current status of the the 2.0 release? (in terms of bugs and/or features that still need fixing/implementing) I see this page in the docs that shows the latest is beta 3 from today:http://matplotlib.org/devdocs/ contents.html# I ask for 2 reasons:1. I'd be willing to help put in some hours programming if you all could use the help2. I'm curious if for new code I am writing now I should just stick with 1.5 or if it is worth already transitioning to 2.0 and using the betas. Thanks!Jayson ______________________________ _________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/ mailman/listinfo/matplotlib- devel ______________________________ _________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/ mailman/listinfo/matplotlib- devel _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org https://mail.python.org/mailman/listinfo/matplotlib-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From efiring at hawaii.edu Fri Aug 12 17:06:07 2016 From: efiring at hawaii.edu (Eric Firing) Date: Fri, 12 Aug 2016 11:06:07 -1000 Subject: [Matplotlib-devel] switch default to h264 Message-ID: Ryan, Is there any reason not to switch the animation.codec default to 'h264'? I can make a PR to do this for 2.0 if you approve. (This is motivated by my thrashing around yesterday trying to get an animation to work on Linux and Mac. There were a variety of problems, but my impression is that using h264 was one of the keys to success.) Eric From chris.barker at noaa.gov Fri Aug 12 18:01:02 2016 From: chris.barker at noaa.gov (Chris Barker) Date: Fri, 12 Aug 2016 15:01:02 -0700 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: Animation codecs are a nightmare. There is STILL no one codec / container that will "just work" everywhere. but H.264 is as close as it gets, so I say go for it. -CHB PS: I really wish there were a standard well supported codec well suited to computer-drawn animations -- ideally lossless. i.e. like PNG, rather than like JPEG. But what can you do? On Fri, Aug 12, 2016 at 2:06 PM, Eric Firing wrote: > Ryan, > > Is there any reason not to switch the animation.codec default to 'h264'? > I can make a PR to do this for 2.0 if you approve. (This is motivated by > my thrashing around yesterday trying to get an animation to work on Linux > and Mac. There were a variety of problems, but my impression is that using > h264 was one of the keys to success.) > > Eric > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmay31 at gmail.com Fri Aug 12 18:23:52 2016 From: rmay31 at gmail.com (Ryan May) Date: Fri, 12 Aug 2016 16:23:52 -0600 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: Eric, I'm happy to sign off on a PR to set better animation defaults. I'd be happy to test here on OSX. Can anyone validate our choice on windows? Ryan On Fri, Aug 12, 2016 at 3:06 PM, Eric Firing wrote: > Ryan, > > Is there any reason not to switch the animation.codec default to 'h264'? > I can make a PR to do this for 2.0 if you approve. (This is motivated by > my thrashing around yesterday trying to get an animation to work on Linux > and Mac. There were a variety of problems, but my impression is that using > h264 was one of the keys to success.) > > Eric > -- Ryan May -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Sun Aug 14 14:36:21 2016 From: pmhobson at gmail.com (Paul Hobson) Date: Sun, 14 Aug 2016 11:36:21 -0700 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: Ping me on Github (phobson) or here with some sample code when it's ready and I'll be happy to try it out. On Fri, Aug 12, 2016 at 3:23 PM, Ryan May wrote: > Eric, > > I'm happy to sign off on a PR to set better animation defaults. I'd be > happy to test here on OSX. Can anyone validate our choice on windows? > > Ryan > > On Fri, Aug 12, 2016 at 3:06 PM, Eric Firing wrote: > >> Ryan, >> >> Is there any reason not to switch the animation.codec default to 'h264'? >> I can make a PR to do this for 2.0 if you approve. (This is motivated by >> my thrashing around yesterday trying to get an animation to work on Linux >> and Mac. There were a variety of problems, but my impression is that using >> h264 was one of the keys to success.) >> >> Eric >> > > > > -- > Ryan May > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Mon Aug 15 09:21:13 2016 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 15 Aug 2016 09:21:13 -0400 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: In my research for the animation chapter of my book, I also came to the conclusion that the `mpeg4` codec in a .mp4 container was the best bet for out-of-the-box compatibility across platforms. The one place where that format didn't work was MS PowerPoint on Windows (but, oddly enough, it worked on PowerPoint on MacOSX). Note, I did that test a couple of years ago on a Windows 7 machine, so I don't know if that limitation is still valid. Cheers! Ben Root On Sun, Aug 14, 2016 at 2:36 PM, Paul Hobson wrote: > Ping me on Github (phobson) or here with some sample code when it's ready > and I'll be happy to try it out. > > On Fri, Aug 12, 2016 at 3:23 PM, Ryan May wrote: > >> Eric, >> >> I'm happy to sign off on a PR to set better animation defaults. I'd be >> happy to test here on OSX. Can anyone validate our choice on windows? >> >> Ryan >> >> On Fri, Aug 12, 2016 at 3:06 PM, Eric Firing wrote: >> >>> Ryan, >>> >>> Is there any reason not to switch the animation.codec default to >>> 'h264'? I can make a PR to do this for 2.0 if you approve. (This is >>> motivated by my thrashing around yesterday trying to get an animation to >>> work on Linux and Mac. There were a variety of problems, but my impression >>> is that using h264 was one of the keys to success.) >>> >>> Eric >>> >> >> >> >> -- >> Ryan May >> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.barker at noaa.gov Mon Aug 15 13:23:05 2016 From: chris.barker at noaa.gov (Chris Barker) Date: Mon, 15 Aug 2016 10:23:05 -0700 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: On Mon, Aug 15, 2016 at 6:21 AM, Benjamin Root wrote: > In my research for the animation chapter of my book, I also came to the > conclusion that the `mpeg4` codec in a .mp4 container was the best bet for > out-of-the-box compatibility across platforms. > Ben -- is that H.264? It seem "mpeg 4" is not well defined. from Wikipedia: > "MPEG-4 is still an evolving standard and is divided into a number of parts. Companies promoting MPEG-4 compatibility do not always clearly state which "part" level compatibility they are referring to." Sigh. > The one place where that format didn't work was MS PowerPoint on Windows > (but, oddly enough, it worked on PowerPoint on MacOSX). > That's because PPT punts to the "system" for decoding -- it has little if any built-in support. A freakin' nightmare. > Note, I did that test a couple of years ago on a Windows 7 machine, so I > don't know if that limitation is still valid. > I think H.264 is getting better and better supported. Question: how is MPL planning to support it? Is there a not-too-hard-to-install cross platform lib??? -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From ben.v.root at gmail.com Mon Aug 15 13:38:16 2016 From: ben.v.root at gmail.com (Benjamin Root) Date: Mon, 15 Aug 2016 13:38:16 -0400 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: As I stated in my book: "While I will not claim to possess anything more than a passing familiarity with movie formats, I recognize that neither do many other people. For those who have had experience editing and creating movies and understand these concepts far more extensively, you can skip this section; be assured that I could not possibly add any new knowledge. For those reading on, there are likely to be some over-simplifications. As such, this section is only intended to provide enough information to successfully render animations and avoid pitfalls and should not be considered authoritative." My quick research at the time found that while mpeg4 and h.264 weren't strictly equivalent, for all intents and purposes they could be considered as such. And it is my understanding that avconv and such were treating it as the same (unless explicitly told not to). If I am wrong in this regard, please refer to the previous paragraph and kindly file an errata for my book. Cheers! Ben Root On Mon, Aug 15, 2016 at 1:23 PM, Chris Barker wrote: > > > On Mon, Aug 15, 2016 at 6:21 AM, Benjamin Root > wrote: > >> In my research for the animation chapter of my book, I also came to the >> conclusion that the `mpeg4` codec in a .mp4 container was the best bet for >> out-of-the-box compatibility across platforms. >> > > Ben -- is that H.264? It seem "mpeg 4" is not well defined. from Wikipedia: >> > > > "MPEG-4 is still an evolving standard and is divided into a number of > parts. Companies promoting MPEG-4 compatibility do not always clearly state > which "part" level compatibility they are referring to." > > Sigh. > > > >> The one place where that format didn't work was MS PowerPoint on Windows >> (but, oddly enough, it worked on PowerPoint on MacOSX). >> > > That's because PPT punts to the "system" for decoding -- it has little if > any built-in support. A freakin' nightmare. > > >> Note, I did that test a couple of years ago on a Windows 7 machine, so I >> don't know if that limitation is still valid. >> > > I think H.264 is getting better and better supported. > > Question: how is MPL planning to support it? Is there a > not-too-hard-to-install cross platform lib??? > > -CHB > > > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > Chris.Barker at noaa.gov > -------------- next part -------------- An HTML attachment was scrubbed... URL: From efiring at hawaii.edu Mon Aug 15 14:27:05 2016 From: efiring at hawaii.edu (Eric Firing) Date: Mon, 15 Aug 2016 08:27:05 -1000 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: References: Message-ID: <5901d692-6350-42f6-3de6-de6d2f06093c@hawaii.edu> It's all incredibly confusing, as the wikipedia article shows. The first problem is the distinction between the container format and the codec; both have to be recognized and handled properly by an application. The file extension generally is more indicative of the container than the codec. MPEG-4 seems to be an umbrella that can cover a wide variety actual codecs, one of which is h264, and that at least implies a file format ("version 2"). Specifying the mpeg4 codec in animation, with avconv or ffmpeg, seems to result in the use of a codec "mpeg4 (Simple Profile)"--but I suspect this might depend on how avconv or ffmpeg was built. Specifying h264 results in use of the newer and more efficient h264 encoder, which is what I am proposing to make the default. One problem: h264 (at least as implemented in ffmpeg and avconv) can't handle frame dimensions that include an odd number of pixels, but mpeg4 can. Regardless of whether h264 is the default, we should trap this error at an early stage; otherwise it leads to a non-obvious failure mode. I need to do a little more testing before submitting any PR. I want to identify the conditions that were leading to video files that were completely corrupted. When I was trying to get things working I was not keeping track of what I was doing, so I need to backtrack and make a set of examples. Eric On 2016/08/15 7:38 AM, Benjamin Root wrote: > As I stated in my book: > > "While I will not claim to possess anything more than a passing > familiarity with movie formats, I recognize that neither do many other > people. For those who have had experience editing and creating movies > and understand these concepts far more extensively, you can skip this > section; be assured that I could not possibly add any new knowledge. For > those reading on, there are likely to be some over-simplifications. As > such, this section is only intended to provide enough information to > successfully render animations and avoid pitfalls and should not be > considered authoritative." > > My quick research at the time found that while mpeg4 and h.264 weren't > strictly equivalent, for all intents and purposes they could be > considered as such. And it is my understanding that avconv and such were > treating it as the same (unless explicitly told not to). If I am wrong > in this regard, please refer to the previous paragraph and kindly file > an errata for my book. > > Cheers! > Ben Root > > > On Mon, Aug 15, 2016 at 1:23 PM, Chris Barker > wrote: > > > > On Mon, Aug 15, 2016 at 6:21 AM, Benjamin Root > wrote: > > In my research for the animation chapter of my book, I also came > to the conclusion that the `mpeg4` codec in a .mp4 container was > the best bet for out-of-the-box compatibility across platforms. > > > Ben -- is that H.264? It seem "mpeg 4" is not well defined. from > Wikipedia: > > > > "MPEG-4 is still an evolving standard and is divided into a number > of parts. Companies promoting MPEG-4 compatibility do not always > clearly state which "part" level compatibility they are referring to." > > Sigh. > > > > The one place where that format didn't work was MS PowerPoint > on Windows (but, oddly enough, it worked on PowerPoint on MacOSX). > > > That's because PPT punts to the "system" for decoding -- it has > little if any built-in support. A freakin' nightmare. > > > Note, I did that test a couple of years ago on a Windows 7 > machine, so I don't know if that limitation is still valid. > > > I think H.264 is getting better and better supported. > > Question: how is MPL planning to support it? Is there a > not-too-hard-to-install cross platform lib??? > > -CHB > > > > -- > > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 > voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 > main reception > > Chris.Barker at noaa.gov > > > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > From chris.barker at noaa.gov Wed Aug 17 18:21:26 2016 From: chris.barker at noaa.gov (Chris Barker) Date: Wed, 17 Aug 2016 15:21:26 -0700 Subject: [Matplotlib-devel] switch default to h264 In-Reply-To: <5901d692-6350-42f6-3de6-de6d2f06093c@hawaii.edu> References: <5901d692-6350-42f6-3de6-de6d2f06093c@hawaii.edu> Message-ID: This is all a huge pain! So thanks so much Eric! Sounds like you have a good plan. -CHB On Mon, Aug 15, 2016 at 11:27 AM, Eric Firing wrote: > It's all incredibly confusing, as the wikipedia article shows. The first > problem is the distinction between the container format and the codec; both > have to be recognized and handled properly by an application. The file > extension generally is more indicative of the container than the codec. > > MPEG-4 seems to be an umbrella that can cover a wide variety actual > codecs, one of which is h264, and that at least implies a file format > ("version 2"). > > Specifying the mpeg4 codec in animation, with avconv or ffmpeg, seems to > result in the use of a codec "mpeg4 (Simple Profile)"--but I suspect this > might depend on how avconv or ffmpeg was built. Specifying h264 results in > use of the newer and more efficient h264 encoder, which is what I am > proposing to make the default. > > One problem: h264 (at least as implemented in ffmpeg and avconv) can't > handle frame dimensions that include an odd number of pixels, but mpeg4 > can. Regardless of whether h264 is the default, we should trap this error > at an early stage; otherwise it leads to a non-obvious failure mode. > > I need to do a little more testing before submitting any PR. I want to > identify the conditions that were leading to video files that were > completely corrupted. When I was trying to get things working I was not > keeping track of what I was doing, so I need to backtrack and make a set of > examples. > > Eric > > On 2016/08/15 7:38 AM, Benjamin Root wrote: > >> As I stated in my book: >> >> "While I will not claim to possess anything more than a passing >> familiarity with movie formats, I recognize that neither do many other >> people. For those who have had experience editing and creating movies >> and understand these concepts far more extensively, you can skip this >> section; be assured that I could not possibly add any new knowledge. For >> those reading on, there are likely to be some over-simplifications. As >> such, this section is only intended to provide enough information to >> successfully render animations and avoid pitfalls and should not be >> considered authoritative." >> >> My quick research at the time found that while mpeg4 and h.264 weren't >> strictly equivalent, for all intents and purposes they could be >> considered as such. And it is my understanding that avconv and such were >> treating it as the same (unless explicitly told not to). If I am wrong >> in this regard, please refer to the previous paragraph and kindly file >> an errata for my book. >> >> Cheers! >> Ben Root >> >> >> On Mon, Aug 15, 2016 at 1:23 PM, Chris Barker > > wrote: >> >> >> >> On Mon, Aug 15, 2016 at 6:21 AM, Benjamin Root > > wrote: >> >> In my research for the animation chapter of my book, I also came >> to the conclusion that the `mpeg4` codec in a .mp4 container was >> the best bet for out-of-the-box compatibility across platforms. >> >> >> Ben -- is that H.264? It seem "mpeg 4" is not well defined. from >> Wikipedia: >> >> >> >> "MPEG-4 is still an evolving standard and is divided into a number >> of parts. Companies promoting MPEG-4 compatibility do not always >> clearly state which "part" level compatibility they are referring to." >> >> Sigh. >> >> >> >> The one place where that format didn't work was MS PowerPoint >> on Windows (but, oddly enough, it worked on PowerPoint on MacOSX). >> >> >> That's because PPT punts to the "system" for decoding -- it has >> little if any built-in support. A freakin' nightmare. >> >> >> Note, I did that test a couple of years ago on a Windows 7 >> machine, so I don't know if that limitation is still valid. >> >> >> I think H.264 is getting better and better supported. >> >> Question: how is MPL planning to support it? Is there a >> not-too-hard-to-install cross platform lib??? >> >> -CHB >> >> >> >> -- >> >> Christopher Barker, Ph.D. >> Oceanographer >> >> Emergency Response Division >> NOAA/NOS/OR&R (206) 526-6959 >> voice >> 7600 Sand Point Way NE (206) 526-6329 >> fax >> Seattle, WA 98115 (206) 526-6317 >> main reception >> >> Chris.Barker at noaa.gov >> >> >> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel >> >> > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker at noaa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcaswell at gmail.com Sat Aug 27 14:09:42 2016 From: tcaswell at gmail.com (Thomas Caswell) Date: Sat, 27 Aug 2016 18:09:42 +0000 Subject: [Matplotlib-devel] mpl governance In-Reply-To: References: Message-ID: Folks, Following up on last month's email, are there any comments, for or against, adopting the Jupyter governance model and the mechanism of ratifying the adoption? Tom On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell wrote: > Folks, > > During the sprints at SciPy Mike Droettboom and I started to adapt the > Jupyter governance documents for matplotlib. > > We are doing this in the open, and a pull request of the changes is at: > > https://github.com/matplotlib/governance/pull/1 > > To be clear, this is a work in progress and is not final or in force. > > We propose the mechanism for ratifying the these documents is to, after > input from the community, have the current "matplotlib Executive Committee" > (the signers of the FSA with NUMFocus) vote. > > Tom > > ps A very similar email was sent to the matplotlib-devel list on July 17 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pmhobson at gmail.com Mon Aug 29 11:39:53 2016 From: pmhobson at gmail.com (Paul Hobson) Date: Mon, 29 Aug 2016 08:39:53 -0700 Subject: [Matplotlib-devel] [Matplotlib-users] mpl governance In-Reply-To: References: Message-ID: I think this is a good idea. On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell wrote: > Folks, > > Following up on last month's email, are there any comments, for or > against, adopting the Jupyter governance model and the mechanism of > ratifying the adoption? > > Tom > > > On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell wrote: > >> Folks, >> >> During the sprints at SciPy Mike Droettboom and I started to adapt the >> Jupyter governance documents for matplotlib. >> >> We are doing this in the open, and a pull request of the changes is at: >> >> https://github.com/matplotlib/governance/pull/1 >> >> To be clear, this is a work in progress and is not final or in force. >> >> We propose the mechanism for ratifying the these documents is to, after >> input from the community, have the current "matplotlib Executive Committee" >> (the signers of the FSA with NUMFocus) vote. >> >> Tom >> >> ps A very similar email was sent to the matplotlib-devel list on July 17 >> > > _______________________________________________ > Matplotlib-users mailing list > Matplotlib-users at python.org > https://mail.python.org/mailman/listinfo/matplotlib-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jason at jasongrout.org Mon Aug 29 21:00:26 2016 From: jason at jasongrout.org (Jason Grout) Date: Tue, 30 Aug 2016 01:00:26 +0000 Subject: [Matplotlib-devel] [Matplotlib-users] mpl governance In-Reply-To: References: Message-ID: We're about to have some discussions in Jupyter about our governance model, and probably tweak it now that we have more experience with it. While that experience may not transfer to matplotlib's situation, it still might be good to see that discussion before making huge changes. Thanks, Jason On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson wrote: > I think this is a good idea. > > On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell > wrote: > >> Folks, >> >> Following up on last month's email, are there any comments, for or >> against, adopting the Jupyter governance model and the mechanism of >> ratifying the adoption? >> >> Tom >> >> >> On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell >> wrote: >> >>> Folks, >>> >>> During the sprints at SciPy Mike Droettboom and I started to adapt the >>> Jupyter governance documents for matplotlib. >>> >>> We are doing this in the open, and a pull request of the changes is at: >>> >>> https://github.com/matplotlib/governance/pull/1 >>> >>> To be clear, this is a work in progress and is not final or in force. >>> >>> We propose the mechanism for ratifying the these documents is to, after >>> input from the community, have the current "matplotlib Executive Committee" >>> (the signers of the FSA with NUMFocus) vote. >>> >>> Tom >>> >>> ps A very similar email was sent to the matplotlib-devel list on July 17 >>> >> >> _______________________________________________ >> Matplotlib-users mailing list >> Matplotlib-users at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-users >> >> > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bussonniermatthias at gmail.com Mon Aug 29 21:23:24 2016 From: bussonniermatthias at gmail.com (Matthias Bussonnier) Date: Mon, 29 Aug 2016 18:23:24 -0700 Subject: [Matplotlib-devel] [Matplotlib-users] mpl governance In-Reply-To: References: Message-ID: Hi all, To extend on what Jason said, the discussion have started privately on the Jupyter Steering council mailing list, we'll move it to a public space but we want to shorten what have been posted and make sure it's suitable for public consumption. -- M On Mon, Aug 29, 2016 at 6:00 PM, Jason Grout wrote: > We're about to have some discussions in Jupyter about our governance model, > and probably tweak it now that we have more experience with it. While that > experience may not transfer to matplotlib's situation, it still might be > good to see that discussion before making huge changes. > > Thanks, > > Jason > > > On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson wrote: >> >> I think this is a good idea. >> >> On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell >> wrote: >>> >>> Folks, >>> >>> Following up on last month's email, are there any comments, for or >>> against, adopting the Jupyter governance model and the mechanism of >>> ratifying the adoption? >>> >>> Tom >>> >>> >>> On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell >>> wrote: >>>> >>>> Folks, >>>> >>>> During the sprints at SciPy Mike Droettboom and I started to adapt the >>>> Jupyter governance documents for matplotlib. >>>> >>>> We are doing this in the open, and a pull request of the changes is at: >>>> >>>> https://github.com/matplotlib/governance/pull/1 >>>> >>>> To be clear, this is a work in progress and is not final or in force. >>>> >>>> We propose the mechanism for ratifying the these documents is to, after >>>> input from the community, have the current "matplotlib Executive Committee" >>>> (the signers of the FSA with NUMFocus) vote. >>>> >>>> Tom >>>> >>>> ps A very similar email was sent to the matplotlib-devel list on July 17 >>> >>> >>> _______________________________________________ >>> Matplotlib-users mailing list >>> Matplotlib-users at python.org >>> https://mail.python.org/mailman/listinfo/matplotlib-users >>> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> https://mail.python.org/mailman/listinfo/matplotlib-devel > > > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel at python.org > https://mail.python.org/mailman/listinfo/matplotlib-devel > From jason at jasongrout.org Wed Aug 31 12:20:49 2016 From: jason at jasongrout.org (Jason Grout) Date: Wed, 31 Aug 2016 16:20:49 +0000 Subject: [Matplotlib-devel] [Matplotlib-users] mpl governance In-Reply-To: References: Message-ID: FYI, here is the (beginning of the) public discussion of the Jupyter governance model we were talking about: https://github.com/jupyter/governance/issues/19 Jason On Mon, Aug 29, 2016 at 9:23 PM Matthias Bussonnier < bussonniermatthias at gmail.com> wrote: > Hi all, > > To extend on what Jason said, the discussion have started privately on > the Jupyter Steering council mailing list, we'll move it to a public > space but we want to shorten what have been posted and make sure it's > suitable for public consumption. > > -- > M > > On Mon, Aug 29, 2016 at 6:00 PM, Jason Grout wrote: > > We're about to have some discussions in Jupyter about our governance > model, > > and probably tweak it now that we have more experience with it. While > that > > experience may not transfer to matplotlib's situation, it still might be > > good to see that discussion before making huge changes. > > > > Thanks, > > > > Jason > > > > > > On Mon, Aug 29, 2016 at 11:40 AM Paul Hobson wrote: > >> > >> I think this is a good idea. > >> > >> On Sat, Aug 27, 2016 at 11:09 AM, Thomas Caswell > >> wrote: > >>> > >>> Folks, > >>> > >>> Following up on last month's email, are there any comments, for or > >>> against, adopting the Jupyter governance model and the mechanism of > >>> ratifying the adoption? > >>> > >>> Tom > >>> > >>> > >>> On Sun, Jul 31, 2016 at 6:32 PM Thomas Caswell > >>> wrote: > >>>> > >>>> Folks, > >>>> > >>>> During the sprints at SciPy Mike Droettboom and I started to adapt the > >>>> Jupyter governance documents for matplotlib. > >>>> > >>>> We are doing this in the open, and a pull request of the changes is > at: > >>>> > >>>> https://github.com/matplotlib/governance/pull/1 > >>>> > >>>> To be clear, this is a work in progress and is not final or in force. > >>>> > >>>> We propose the mechanism for ratifying the these documents is to, > after > >>>> input from the community, have the current "matplotlib Executive > Committee" > >>>> (the signers of the FSA with NUMFocus) vote. > >>>> > >>>> Tom > >>>> > >>>> ps A very similar email was sent to the matplotlib-devel list on July > 17 > >>> > >>> > >>> _______________________________________________ > >>> Matplotlib-users mailing list > >>> Matplotlib-users at python.org > >>> https://mail.python.org/mailman/listinfo/matplotlib-users > >>> > >> > >> _______________________________________________ > >> Matplotlib-devel mailing list > >> Matplotlib-devel at python.org > >> https://mail.python.org/mailman/listinfo/matplotlib-devel > > > > > > _______________________________________________ > > Matplotlib-devel mailing list > > Matplotlib-devel at python.org > > https://mail.python.org/mailman/listinfo/matplotlib-devel > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: