Setting up ACES/OCIO for Houdini 19

Forums Houdini Indie and Apprentice Setting up ACES/OCIO for Houdini 19

9705 10 4


paper_krane: Member; 9 posts; Joined: Sept. 2019; Offline

Oct. 27, 2021 5:32 p.m.

Has anyone else successfully set up ACES inside of Houdini 19? I originally started with adding the OCIO = C:/path/to/config.ocio in my houdini.env file and that didn't work. Then I read that you are not supposed to put the OCIO variables in the .env file anymore (https://www.sidefx.com/docs/houdini/io/ocio.html). Am I misreading this and if now, could anyone help guide me as to how to set up ACES with Houdini 19?


jsmack: Member; 7737 posts; Joined: Sept. 2011; Offline

Oct. 27, 2021 6:31 p.m.

On Windows, add it to the System Environment Variables; on Linux, a .bashrc or other automatically sourced shell script.


paper_krane: Member; 9 posts; Joined: Sept. 2019; Offline

Oct. 27, 2021 7:53 p.m.

Oh man, now that you say it aloud, that makes complete sense. I feel like a dunce. Thank you so much for this. I see ACES in the render window. Just another question, will it not show in the viewport anymore (i.e. the darker blue gradient)?


jsmack: Member; 7737 posts; Joined: Sept. 2011; Offline

Oct. 27, 2021 8:40 p.m.

paper_krane
Just another question, will it not show in the viewport anymore (i.e. the darker blue gradient)?

It depends on your OCIO config and whether or not the output display transform is reversible. With ACES and the srgb display, it is, so the blue gradient should look approximately the same as before an OCIO config.


malexander: Staff; 5156 posts; Joined: July 2005; Offline

Oct. 29, 2021 10:15 a.m.

paper_krane
Oh man, now that you say it aloud, that makes complete sense. I feel like a dunce. Thank you so much for this. I see ACES in the render window. Just another question, will it not show in the viewport anymore (i.e. the darker blue gradient)?

Many of the elements that had color correction applied before in 18.5 (incorrectly), like the background gradient, now display properly with OCIO in 19.0.


KawaLe: Member; 1 posts; Joined: April 2021; Offline

Nov. 8, 2021 1:10 p.m.

jsmack
On Windows, add it to the System Environment Variables; on Linux, a .bashrc or other automatically sourced shell script.

Hello,

I have the same issue but i dont know how to add it to the System environment viariables ( on windows ). Thanks for your answer !


sepu: Member; 419 posts; Joined: Feb. 2012; Offline

Nov. 9, 2021 10:47 p.m.

Press the window btn on your keyboard and type "Edit the system environment variables" that will open a little window click on the environment variables... btn
Then inside create a new "system Variable"

Then Create an OCIO like the image make sure that you add the path as shown and that should do it

Attachments:
EpicPen_P4zooJE0bN.png (13.3 KB)
EpicPen_oVLJdKkJRc.png (5.2 KB)


NicTanghe: Member; 190 posts; Joined: Dec. 2016; Offline

Sept. 22, 2022 5:58 a.m.

my .bashrc looks like this on fedora but i can`t seem to get it to work.

# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
        . /etc/bashrc
fi

# User specific environment
if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]]
then
    PATH="$HOME/.local/bin:$HOME/bin:$PATH"
fi
export PATH

# Uncomment the following line if you don't like systemctl's auto-paging feature:
# export SYSTEMD_PAGER=

# User specific aliases and functions
if [ -d ~/.bashrc.d ]; then
        for rc in ~/.bashrc.d/*; do
                if [ -f "$rc" ]; then
                        . "$rc"
                fi
        done
fi

unset rc


#userconf
set -o vi
bind '"\C-l":clear-screen'

alias ls='ls --color=auto'

alias l='ls -a --color=auto'

alias ll='ls -la'

eval "$(starship init bash)"

OCIO=/home/ntanghe/CGI/color/OpenColorIO-Configs/aces_1.2/config.ocio

my binds and aliases do work

My /etc/profile.d/proxy.sh is simply

OCIO=/home/ntanghe/CGI/color/OpenColorIO-Configs/aces_1.2/config.ocio

I can echo $OCIO without annyt problems on the shell

I can do a workaround with setting up an environment variable in the env file for each version of houdini this is however not desirable.

Edited by NicTanghe - Sept. 22, 2022 06:36:07


jsmack: Member; 7737 posts; Joined: Sept. 2011; Offline

Sept. 22, 2022 12:41 p.m.

NicTanghe
my .bashrc looks like this on fedora but i can`t seem to get it to work.

# .bashrc

# Source global definitions
if [ -f /etc/bashrc ]; then
        . /etc/bashrc
fi

# User specific environment
if ! [[ "$PATH" =~ "$HOME/.local/bin:$HOME/bin:" ]]
then
    PATH="$HOME/.local/bin:$HOME/bin:$PATH"
fi
export PATH

# Uncomment the following line if you don't like systemctl's auto-paging feature:
# export SYSTEMD_PAGER=

# User specific aliases and functions
if [ -d ~/.bashrc.d ]; then
        for rc in ~/.bashrc.d/*; do
                if [ -f "$rc" ]; then
                        . "$rc"
                fi
        done
fi

unset rc


#userconf
set -o vi
bind '"\C-l":clear-screen'

alias ls='ls --color=auto'

alias l='ls -a --color=auto'

alias ll='ls -la'

eval "$(starship init bash)"

OCIO=/home/ntanghe/CGI/color/OpenColorIO-Configs/aces_1.2/config.ocio

my binds and aliases do work

My /etc/profile.d/proxy.sh is simply

OCIO=/home/ntanghe/CGI/color/OpenColorIO-Configs/aces_1.2/config.ocio

I can echo $OCIO without annyt problems on the shell

I can do a workaround with setting up an environment variable in the env file for each version of houdini this is however not desirable.

~~are you unsetting OCIO in the houdini startup script, or overriding it in the houdini.env?~~

You didn't export it

Edited by jsmack - Sept. 22, 2022 12:42:41


NicTanghe: Member; 190 posts; Joined: Dec. 2016; Offline

Sept. 30, 2022 6:37 p.m.

Hm, yes, oversight in the post here.

I later noticed it is because I use sudo to launch with nice as my user, which doesn't use the environment variables I set up.
I’ve tried changing the sudoers file to pass the OCIO environment variable, but it didn’t take, so now i just launch without nice and that works fine.


jsmack: Member; 7737 posts; Joined: Sept. 2011; Offline

Oct. 2, 2022 1:53 p.m.

NicTanghe
Hm, yes, oversight in the post here.

I later noticed it is because I use sudo to launch with nice as my user, which doesn't use the environment variables I set up.
I’ve tried changing the sudoers file to pass the OCIO environment variable, but it didn’t take, so now i just launch without nice and that works fine.

I wouldn't use sudo to launch Houdini, that's dangerous

Quick Links

                    
                        Search links
                        Show recent posts
                        Show unanswered posts