Setting up ACES/OCIO for Houdini 19
9537 10 4- paper_krane
- Member
- 9 posts
- Joined: Sept. 2019
- Offline
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
- 7659 posts
- Joined: Sept. 2011
- Offline
- paper_krane
- Member
- 9 posts
- Joined: Sept. 2019
- Offline
- jsmack
- Member
- 7659 posts
- Joined: Sept. 2011
- Offline
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
- 5151 posts
- Joined: July 2005
- Offline
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
- sepu
- Member
- 405 posts
- Joined: Feb. 2012
- Offline
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
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
- NicTanghe
- Member
- 189 posts
- Joined: Dec. 2016
- Offline
my .bashrc looks like this on fedora but i can`t seem to get it to work.
my binds and aliases do work
My /etc/profile.d/proxy.sh is simply
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.
# .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
- 7659 posts
- Joined: Sept. 2011
- Offline
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 simplyOCIO=/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.
You didn't export it
Edited by jsmack - Sept. 22, 2022 12:42:41
- NicTanghe
- Member
- 189 posts
- Joined: Dec. 2016
- Offline
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 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
- 7659 posts
- Joined: Sept. 2011
- Offline
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