natrongithub / openfx-io Goto Github PK

This fails to compile for me. Changing to OCIO::... as in other parts of the file seems to work; unless I misunderstanding something.

https://builds.garudalinux.org/repos/chaotic-aur/logs/openfx-io.log

Got several reports (private, pixls, discord) that OCIODisplay in Natron 2.4.3 has issues.

See https://discuss.pixls.us/t/ocio-display-filmic-srgb-view-transform-is-missing/29576

Adding this now so I don't forget

I'm currently compositing large images at work that will be used in an 360 viewer. The final output image is 17814 x 8907 in either TIFF or JPEG. The actual comp is simple, I add two layers from an EXR (rendered in Blender) on top of a background image.

Any image format using WriteOIIO crash (in OpenImageIO lib, I don't have debug info on that library). The only image format I can use is PNG, as it does not use WriteOIIO.

Tested RB-2.5/RB-2.6 on Windows 10 and Ubuntu 22.04.

Will update with more info (when I get the time to build OIIO with debug info etc).

OpenColorIO now proposes openfx plugins. The OCIOColorSpace plugin has two useful functions:

• an "inverse" checkbox
• a "swap colorspaces" push button

It would be nice to have these too

ref:
from https://github.com/AcademySoftwareFoundation/OpenColorIO/blob/main/vendor/openfx/OCIODisplayView.cpp

OCIO 2 with new GPU API: AcademySoftwareFoundation/OpenColorIO#539

Sample use of the new GPU API: https://github.com/imageworks/OpenColorIO/blob/master/src/apps/ociodisplay/main.cpp

Changes to ociodisplay when it was switched to the new API: https://github.com/imageworks/OpenColorIO/pull/539/files#diff-6bb1a574c942a19eb51ffb7cee789b9c

There is still no official OCIO 2 release, so this can wait

I made a new branch, named ocio2 to start the transition to OCIO2: https://github.com/NatronGitHub/openfx-io/tree/ocio2
I tried to keep OCIO1 compatibility, using OCIO_VERSION_HEX.

The code does not yet compile with OCIO 2.0.0 (I haven't fully figured out how to use the new API, since the Nuke plugins in the code were not updated).

There are a few changes remaining to be made, including #1

As part of #36 I removed the Appveyor config but it appears that it is still getting run for pull requests. I believe there may be a webhook in this project's settings that needs to be removed. I don't have access to the project settings so I can't fix this myself.

openfx-io version: 2.4
libseexpr2 2.11 (aur)
openimageio 2.2.13.0

build log
https://pastebin.com/vdwG46sd

key errors

Package 'IlmBase', required by 'virtual:world', not found
Package IlmBase was not found in the pkg-config search path.
Perhaps you should add the directory containing `IlmBase.pc'

Package 'IlmBase', required by 'virtual:world', not found
../EXR/ReadEXR.cpp:42:10: fatal error: ImfPixelType.h: No such file or directory
   42 | #include <ImfPixelType.h>

Sorry if this is a duplicate issue.

CXX Linux-64-release/SequenceParsing.o
CXX Linux-64-release/SeExpr.o
../SeExpr/SeExpr.cpp:58:10: fatal error: SeExpression.h: No such file or directory
58 | #include <SeExpression.h>
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [../openfx/Support/Plugins/Makefile.master:83: Linux-64-release/SeExpr.o] Error 1

Hey. I don't use Natron regularly, but am looking for a way to more efficiently write to files on Windows.

• I read that the WriteFFMPEG node preforms better than the built-in Write, but understand that this information could be outdated.
• Additionally, I do not know if the source is already compiled into Natron.
• The link you posted on the README (3rdparty_windows_32_and_64bits_msvc2010.zip) goes to a dead Dropbox archive.

Thanks in advance for the help!

NatronGitHub/Natron#329
The next update cycle should include up to date FFMpeg otherwise Natron will fall behind in 4K intermediaries . Also HEVEC is getting it's edge with Nvidia.
Let me know please, where should I check or include the library in read/write node for compatibility check. It will help me to learn building OFX as well. Thanks
@devernay

https://docs.github.com/en/actions/learn-github-actions/migrating-from-travis-ci-to-github-actions

In https://github.com/NatronGitHub/Natron-Tests/tree/master/TestImagePSB

If I convert the PSB to EXR with OIIO, I can read the two subimages:
oiiotool input.psb -o oiio.exr

However, when reading the image directly with ReadOIIO in Natron, the two layers seem identical.

Natron v2.3.16 macOS