Re: mrViewer v3.8.4
Sean Cooper <se...@...>
Wonderful, yes I will. Thank you.
On Sat, Oct 7, 2017 at 2:21 PM, <ggar...@...> wrote:
|
|
mrViewer v3.8.4
ggar...@...
https://sourceforge.net/projects/mrviewer/files/v3.8.4 Thank you.
|
|
Re: OCIO 1.0.10
Sean Cooper <se...@...>
Hi all, Patrick Hodoul has just pushed a number of Windows build related fixes as PR #464 . If any of you have free time to look at his commits and perhaps more importantly to test the build process in your Windows environment it would be much appreciated. Thanks!
On Wednesday, 26 April 2017 10:31:50 UTC-7, Sean Cooper wrote:
|
|
Re: After Effects OCIO Plugin code age
Brendan Bolles <bre...@...>
On Monday, August 14, 2017 at 5:31:29 PM UTC-7, Sean Cooper wrote:
What do you want to know? As Deke pointed out, I have a blog post where you can download it. Code is on GitHub. It was made for use in a studio, so it's been tested. It's designed similarly to the After Effects plug-in. This plug-in is a filter, so it can be applied to a layer to perform color space transformations. The big bummer about Photoshop is that a plug-in can't use used to modify the view continuously. It can export LUTs which can be used as a view LUT to the degree that Photoshop can do that.
|
|
Re: After Effects OCIO Plugin code age
Sean Cooper <se...@...>
I'll happily look at anything pushed our way. Curious, would you be able to give a quick rundown of the PS plugin functionality / implementation?
On Mon, Aug 14, 2017 at 2:07 PM, Deke Kincaid <dekek...@...> wrote:
|
|
Re: After Effects OCIO Plugin code age
Deke Kincaid <dekek...@...>
Yea, that's what I figured. You have a pull request never fulfilled from 2016 so why bother with future ones. Now that we have Sean actively accepting changes you can probably update with your newer pull requests for AE and Photoshop.
On Mon, Aug 14, 2017 at 12:36 PM, Brendan Bolles <bre...@...> wrote:
|
|
Re: After Effects OCIO Plugin code age
Brendan Bolles <bre...@...>
On Monday, August 14, 2017 at 11:34:50 AM UTC-7, Sean Cooper wrote:
Au contraire! I've actually updated it as recently as January. See my ae_plugin_update branch: https://github.com/fnordware/OpenColorIO/tree/ae_plugin_update I also have a Photoshop plug-in now in my "photoshop" branch. I haven't done any pull requests lately because OCIO has been in hibernation until recently.
|
|
Re: After Effects OCIO Plugin code age
Deke Kincaid <dekek...@...>
He also has a nice one for Photoshop http://fnordware.blogspot.com/2017/02/opencolorio-for-photoshop.html He hasn't made a pull request yet but you can see the source for it below https://github.com/fnordware/OpenColorIO/tree/photoshop/src/photoshop
On Mon, Aug 14, 2017 at 12:16 PM, Sean Cooper <se...@...> wrote:
|
|
Re: After Effects OCIO Plugin code age
Sean Cooper <se...@...>
Ah great, that's good to know. I'd never get my hand on AE anytime soon so I think its fair to trust your opinion on the situation. @cam Maybe you could be an additional tester on #405 and we can pull it in if all is in the clear
On Mon, Aug 14, 2017 at 12:12 PM, Deke Kincaid <dekek...@...> wrote:
|
|
Re: After Effects OCIO Plugin code age
Deke Kincaid <dekek...@...>
I've used the plugin a few times. Minus a few minor issues it works fairly well. There is an updated pull request from 2016 though which we should probably accept. I've used this version and not the current 5 year old version in the repo. https://github.com/imageworks/OpenColorIO/pull/405
On Mon, Aug 14, 2017 at 11:34 AM, Sean Cooper <se...@...> wrote:
|
|
Re: After Effects OCIO Plugin code age
Sean Cooper <se...@...>
The latter mostly, most VFX studios that maintain the project don't actively use After Effects so it's not usually on our minds. So its also a question of, if its broken who cares enough to do something about it? With OCIO going through a dry spell most effort has been focused on the core library, but it would be nice to see how the plugins hold up to modern inspection.
On Sun, Aug 13, 2017 at 6:42 PM, Cam Wright <cwr...@...> wrote: Hi there,
|
|
After Effects OCIO Plugin code age
Cam Wright <cwr...@...>
Hi there,
I'm taking a passing glance at colour management in After Effects and I found the OCIO plugin maintained as part of the OCIO Github project. https://github.com/imageworks/OpenColorIO/tree/master/src/aftereffects Appears like the code is a number of years old now though. Before even considering implementing in our pipeline, I'd like to find out whether the code age is a matter of "it's out of date because it doesn't see use in the real world" or a "don't fix what isn't broken" kind of deal. I suspect the latter is true, but figure a quick recce not a bad idea! Thanks. -C Cam Wright - Systems and Technical Resource Administrator CUTTINGEDGE / 90 Victoria St, West End, Brisbane, QLD, 4101 T + 61 7 3013 6200 M 0420 827 007 E cwr...@... | W www.cuttingedge.com.au /SYD /BNE /TYO -- This email is confidential and solely for the use of the intended recipient. If you have received this email in error please notify the author and delete it immediately. This email is not to be distributed without the author's written consent. Unauthorised forwarding, printing, copying or use is strictly prohibited and may be a breach of copyright. Any views expressed in this email are those of the individual sender unless specifically stated to be the views of Cutting Edge Post Pty Ltd (Cutting Edge). Although this email has been sent in the belief that it is virus-free, it is the responsibility of the recipient to ensure that it is virus free. No responsibility is accepted by Cutting Edge for any loss or damage arising in any way from receipt or use of this email. This email may contain legally privileged information and privilege is not waived if you have received this email in error.
|
|
Re: SIGGRAPH 2017 - OpenColorIO Birds of a Feather
Patrick Hodoul <patric...@...>
That's a great news. A better support of ACES (with new ops) and a better support of OpenGL capabilities (such as any types of texture & uniforms) will impose changes to the OCIO public API related to the GPU processor as well as lot of changes to the current implementation. So it seems to me that it would be better to wait the OCIO v2 API discussion in order to improve the current API using the SynColor OpenGL API and your OpenCL API proposals. The goal is to have a much more flexible OCIO v2 public API for the GPU support (i.e. full support of any kind of color transformations without any baking and support of several GPU languages). At that time it should be easier to understand how to proceed with the design & implementation. Patrick.
|
|
Re: SIGGRAPH 2017 - OpenColorIO Birds of a Feather
Dithermaster <dither...@...>
Regarding the "No quality loss through GPU" bullet and the "Do studios maintain their own fork? / If so what features have been added" query, I have permission to contribute back our OpenCL kernel generator changes, which have no quality loss on the GPU path (unlike the OpenGL path which collapse all LUTs into one 3D LUT). If it makes sense prior to this v2.0 work, I can do that soon. However, if it makes more sense to just collaborate on the GPU support in v2.0 I can do that instead. ///d@ Dennis Adams
On Thu, Aug 3, 2017 at 10:20 AM, Sean Cooper <se...@...> wrote:
|
|
Re: SIGGRAPH 2017 - OpenColorIO Birds of a Feather
Sean Cooper <se...@...>
Hello all, We've recently concluded the OpenColorIO Birds of a Feather here at SIGGRAPH 2017, so its time to mirror the discussion back to the greater community. Central to the discussion this year was an exciting proposal put forth by the Autodesk SynColor team headed by Doug Walker. Autodesk and the OCIO leadership will be evaluating the technical feasibility of merging the SynColor codebase into OCIO as a v2.0 release. This merger would add the technical precision and flexibility of the SynColor system within the OCIO paradigm while maintaining the current open source license. A truncated list of features on the table are as follows:
I have attached the Birds of a Feather slides along with this email so everyone is on the same page. While the in-person discussions clearly cannot be replicated, feel free to post questions you may have on this thread. We will maintain open communication on this forum and the Slack channel as both Autodesk and the OCIO task group work towards mutually acceptable functionality and API. So stay tuned for future updates. Thanks!
On Tuesday, 18 July 2017 15:24:32 UTC-7, Sean Cooper wrote:
|
|
Re: OCIO 1.0.10
Sean Cooper <se...@...>
Correction, this would be the example (unorganized) changelog
1.0.9 was tagged back in October 2013, so these are the lump changes since then, there is a good amount of progress that would be useful to push forward.
On Wednesday, 26 April 2017 10:31:50 UTC-7, Sean Cooper wrote:
|
|
Re: OCIO 1.0.10
Sean Cooper <se...@...>
For those that haven't been following, there have been some steps towards 1.0.10
On Wednesday, 26 April 2017 10:31:50 UTC-7, Sean Cooper wrote:
|
|
SIGGRAPH 2017 - OpenColorIO Birds of a Feather
Sean Cooper <se...@...>
For
those of you attending SIGGRAPH 2017 (conference pass required) in Los Angeles, we will be hosting
a "Birds of a Feather" event for users and developers of OpenColorIO to
get together and discuss anything and everything related to working
with OpenColorIO. Session Title: OpenColorIO MeetupDate: Tuesday, 1 August Location: LA Convention Center - Room 507 Time: 1-2pm ~Sean
|
|
Re: OCIO 1.0.10
Sean Cooper <se...@...>
Hi Jep, I've recently added you, let me know if you don't get the email.
On Fri, Jun 23, 2017 at 1:49 PM, <jep...@...> wrote:
|
|
Re: OCIO 1.0.10
jep...@...
Hi Sean, I'd love an invite to the Slack conversation, please. Cheers, Jep
On Wednesday, April 26, 2017 at 10:31:50 AM UTC-7, Sean Cooper wrote:
|
|