|
custom ocio creation for nuke
Ravindra Korde
Hi All,
I'm trying to create custom ocio file for nuke, with reference of http://opencolorio.org/. im new at this so any help or suggestion will be appreciated. Thanks!!! |
|
|
|
Academy Software Foundation Announces New Projects & New Members
Emily Olin
ASWF Community:
In case you haven't seen the news, we are excited to share that the TAC has approved OpenEXR and OpenCue as Academy Software Foundation projects. We are also welcoming three new members - NVIDIA at the Premier level, and ftrack and Red Hat at the General level. You can find more information here:
Thanks! |
|
|
|
Re: DreamWorks Animation Releases USD Manager to the Open Source Community
Daniel Heckenberg
Hi Andrew, This is a great contribution and has been received enthusiastically by the USD community and the developers and TDs at Animal Logic. Thanks! Daniel |
|
|
|
Re: DreamWorks Animation Releases USD Manager to the Open Source Community
Rob Bredow
Congratulations on this release! Rob On Fri, Mar 29, 2019 at 4:41 PM Andrew Pearce <andrew.pearce@...> wrote:
|
|
|
|
DreamWorks Animation Releases USD Manager to the Open Source Community
Andrew Pearce
Please see attached. VP Global Technology, DreamWorks, 818-695-9213 |
|
|
|
Open Source North America CFP
Emily Olin
Hi all,
If you are interested in speaking at Open Source Summit North America, August 21-23 in San Diego, the deadline to submit your abstract is April 2. The conference is hosted by the Linux Foundation and attracts several thousand developers, software engineers, technologists and other open source community and industry leaders. If there are enough talks submitted relating to the motion picture and media industries, they will consider creating a specific motion picture track for the event. Here is the link to learn more and submit: https://events.linuxfoundation.org/events/open-source-summit-north-america-2019/program/cfp/. Please feel free to email me directly with any questions at eolin@.... Thanks! Emily Olin Director of PR, Academy Software Foundation The Linux Foundation |
|
|
|
New ASWF LinkedIn Page
Emily Olin
We have just launched the Academy Software Foundation page on LinkedIn. We'd appreciate if you could please take a moment to follow our page: https://www.linkedin.com/company/academysoftwarefoundation/
Thank you! |
|
|
|
Re: OpenColorIO link is broken in main page
This should be fixed now - let us know if you still see any issues. Thank you, John Mertic Director of Program Management - Linux Foundation ASWF, ODPi, R Consortium, and Open Mainframe Project On Sun, Feb 17, 2019 at 9:28 AM Dylan Socolobsky <dsocolobsky@...> wrote: Greetings. |
|
|
|
OpenColorIO link is broken in main page
dsocolobsky@...
Greetings.
I's a rather minor annoyance but I just wanted to let you know that currently the link for the new OpenColorIO project in your landing page is broken because it's missing a semicolon in the link, and thus it can't be accessed via click. Keep up the good work. -------------------------------- Dylan |
|
|
|
OpenColorIO Joins Academy Software Foundation
Emily Olin
ASWF Community: We are very excited to share that OpenColorIO has been approved as the second Academy Software Foundation project. The press release is available here: https://www.aswf.io/ocio-joins-aswf/. Thank you! |
|
|
|
Re: ASWF CI Infrastructure: Meeting Minutes
Jean-Francois Panisset
There's a "tac" GitHub project at:
toggle quoted message
Show quoted text
https://github.com/AcademySoftwareFoundation/tac More specifically you'll find minutes for the CI working group at: https://github.com/AcademySoftwareFoundation/tac/tree/master/meetings/CI-workinggroup There's been a couple of meetings where the shared Google Doc used to take notes hasn't been converted to Markdown yet, those should be coming soon. JF Panisset On Thu, Jan 10, 2019 at 7:03 AM Patrick Hodoul <patrickhodoul@...> wrote:
|
|
|
|
ASWF CI Infrastructure: Meeting Minutes
Hi,
Where can I find all the meeting minutes of the 'ASWF CI Infrastructure' Group? Thanks, Patrick |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
Larry Gritz
As an aside, VFX Platform is, as they have repeated many times, not a list of endorsed or fundamental packages, but rather an agreement of versions for particular packages that have been historically problematic and plagued by "versionitis" (particularly in how they were used by Foundry, Autodesk, and Side Effects). VFX Platform is great at that mission, I'm not knocking what they're doing. But there is a separate, currently nonexistent, but badly needed list of core packages and versions that more accurately forms the basis of a modern VFX software stack, and that is the list that our CI is going to need to cater to. It overlaps VFX Platform somewhat, but is mostly a super-set. Whoever is scoping the work for these things must remember that VFX Platform not the complete list of the packages that need to be available as core dependencies and that need to be included in the matrix of interoperability that we are trying to test with CI. And also that we will need a "version next" entry in the test matrix that intentionally defies both lists by building all the TOT checkouts against each other, so that we can catch upcoming incompatibilities early as part of the review/CI process for PRs. On Wed, Oct 31, 2018 at 5:38 AM Aloys Baillet <aloys.baillet@...> wrote: Hi Thanh, --
Larry Gritz lg@... |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
Aloys Baillet
Hi Thanh,
I've been reading a bit more about Packer and indeed it should be a fairly easy thing to setup a docker image that matches the VFX platform. One reason I've been angling towards Docker is that NVidia (which most VFX studio have lots of hardware from) provides a very rich set of base images that allow us to build against GL and CUDA libraries, which some VFX packages have optional dependencies to (especially OpenSubdiv). Having pre-built GL-enabled variants of these packages might be desirable, especially Qt which is quite tricky to build properly and all the vendors provide in slightly different variations... That said, to get started on the official VFX platform 2018 you would just need a vanilla CentOS-7 VM/docker image and run this: yum install -y centos-release-scl-rh yum install -y devtoolset-7-toolchain make
source /opt/rh/devtoolset-7/enable
Then install cmake using this: cmake-3.12.3-Linux-x86_64.sh --skip-license (the cmake in centos7 is way too old...) Cheers, Aloys |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
On Tue, Oct 30, 2018 at 9:34 AM Trevor Thomson <tgt@...> wrote: Hi, I'm not sure how these dependencies are used within a build, but It's fairly easy to switch builders in our CI cloud. If single builds are going to run on a very specific configuration of the platform, I'd recommend creating separate clean images with exact library stacks for the tests such as an image per platform year. This ensures that when running a build that only the dependencies we are expecting for that build is being pulled in and it's not pulling in unexpected / undocumented dependencies. Then the tests can pick the specific platforms it wants to run against at runtime. Regards, Thanh |
|
|
|
Re: ASWF CI Infrastructure: VFX Reference Platform Dependencies
Phil Parsonage
All, I'd love Foundry to be involved in this - we've spend some time on this sort of problem across all three operating systems this year, and have had some good results we'd be happy to share (though our infrastructure is slightly different to what's current in the foundation it's not a million miles off). I'm afraid I'll be in transmit tomorrow evening but happy a) react to any notes, or b) write up some notes of what we're currently doing to continue the discussion is helpful? Phil On Mon, Oct 29, 2018 at 11:59 AM Daniel Heckenberg <daniel.heckenberg@...> wrote:
|
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
Trevor Thomson
Hi,
We're not using docker, but we're doing something conceptually similar to Aloys to set up our platforms. We build the compiler, the VFX Platform libraries, and all their dependencies into unique directories per VFX Platform Year per DCC. It's a little heavy-handed, but then the entire platform is available for use in one location. - Trevor |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
On Tue, Oct 30, 2018 at 6:52 AM Aloys Baillet <aloys.baillet@...> wrote:
Packer is very similar in purpose to a Dockerfile. It's purpose is to create a reusable VM image, similar to how Dockerfile's purpose is to create a reusable container image. The reason we use Packer in CI is because our CI spins up VMs. If folks find Docker to be more handy we could have a minimal Packer image that spins up a VM with Docker installed and then pulls down the Docker image to then run the build to achieve a docker based build. We have a few projects that do this today. Regards, Thanh |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
Aloys Baillet
Hi, I've been setting up CentOS-7-based VFX Platform docker images there: https://github.com/AnimalLogic/docker-usd/blob/master/linux/centos7/vfx-lite-2018/Dockerfile It's actually quite a nice way to go, I don't know how packer works exactly but these docker files can be reused to setup everything the right way for a centos-7 based build. Cheers, Aloys Aloys Baillet Lead Software Developer @ Animal Logic |
|
|
|
Re: OpenVDB Jenkins builds broken due to Boost Python not found
Daniel Heckenberg
Hi Dan, I don't think it's overly ambitious to address a number of these points, as most will be common to ASWF projects and CI. Specifically: 1) The VFX Reference Platform build environment and dependencies is a general goal for the ASWF CI and we'll have a working group on that this week. Please join us (although, I know the time is a little inconvenient for the UK) 2) Larry's proposal for robust dependency discovery modules for CMake projects would address this specific problem nicely. Although the Ubuntu provided boost version is old, it seems to be more a case of the ambiguity / variety of boost library decoration choices that has caused the build regression. 3) We should now have the requisite knowledge and support to incorporate the OpenVDB Houdini builds and tests into the ASWF CI. I think that we were waiting for the project adoption and repo transfer to be completed so we should be good to start moving on that. I'll follow up with an email. That really just leaves us with the broken build as an open problem. I defer to the OpenVDB project and others but my 2c: pybind11 is definitely a worthwhile step, but I expect that is a non-trivial effort and that it would create changes in the OpenVDB python bindings such that we couldn't really build a VFX Platform 2018 or 2019 artifact. Cheers, Daniel |
|
|