Hello.
I would like to use a different OCIO config file for mrViewer, it makes the tools to loads much faster than using the default aces 1.2.
The problem is that in the preferences I set it to use "Save OCIO Config File in Preferences", it is correctly saved in the config file, but every time I restart mrViewer it keeps using my config file from the OCIO envar rather than the config file from the mrViewer settings file.
I have attached a couple of files you wil the discrepancy between the preferences window and the settings file.
mrViewer uses the config in the preferences UI not the one specified in the config file.
Using mrViewer 5.8.9
Thanks
Hi, Pablo. That's by design. Any environment variable overrides any setting set anywhere else. The idea being that it is easier to change an env var than it is to keep saving different settings every time you fire mrViewer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey.
Well in that case the tooltip help "Save OCIO Config File in Preferences" I believe it says that what that parameter is doing used it overrides the OCIO en var.
The thing is that our generic ocio config is used pretty much eveywhere , and would be great to have a mechanism to override the OCIO envar for mrViewer.
thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right. The tooltip is wrong and misleading.
I don't understand why you need something else to override the ocio config. If you have it used pretty much everywhere, you can set the OCIO environment variable on any shot, show, user or machine as you see fit and that should take precedence over anything else you saved in the preferences file. It seems you are expecting it to behave the opposite way.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is much simpler, only has the minimum needed to review renders, and using it mrViewer loads much faster, basically aces1.2 takes around 5 sec to load, or that is roughly the difference I see when using a more simple ocio setup.
So it makes sense to have a simple OCIO setup for review and another one used in the DCC apps.
Most of us we really use 1% of OCIO to be honest.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Still, using an environment variable can still be the way to go. On Linux or Mac, create a shell script with the simple OCIO variable and call mrViewer.
On Windows, you'd create a .bat file, with something like:
set OCIO=D:/path/to/simple/ocioconfig
call "C:/path/to/mrviewer.exe"
Then fire up that .bat file instead of the .exe. And set all file associations to that .bat file instead of mrviewer.exe.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep definitely we can make a wrapper, but is not really a clean solution for this problem I think.
Many tools allows you to choose whether or not you want to use OCIO from the envar or from an explicit config file in the settings.
Actually, mrViewer has already everything there implemented, it just need to to what it says in the tooltip, because the preferences are already saving the config file correctly
Last edit: ggarra13 2021-06-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello.
I would like to use a different OCIO config file for mrViewer, it makes the tools to loads much faster than using the default aces 1.2.
The problem is that in the preferences I set it to use "Save OCIO Config File in Preferences", it is correctly saved in the config file, but every time I restart mrViewer it keeps using my config file from the OCIO envar rather than the config file from the mrViewer settings file.
I have attached a couple of files you wil the discrepancy between the preferences window and the settings file.
mrViewer uses the config in the preferences UI not the one specified in the config file.
Using mrViewer 5.8.9
Thanks
Hi, Pablo. That's by design. Any environment variable overrides any setting set anywhere else. The idea being that it is easier to change an env var than it is to keep saving different settings every time you fire mrViewer.
Hey.
Well in that case the tooltip help "Save OCIO Config File in Preferences" I believe it says that what that parameter is doing used it overrides the OCIO en var.
The thing is that our generic ocio config is used pretty much eveywhere , and would be great to have a mechanism to override the OCIO envar for mrViewer.
thanks
You are right. The tooltip is wrong and misleading.
I don't understand why you need something else to override the ocio config. If you have it used pretty much everywhere, you can set the OCIO environment variable on any shot, show, user or machine as you see fit and that should take precedence over anything else you saved in the preferences file. It seems you are expecting it to behave the opposite way.
If you remember this:
https://sourceforge.net/p/mrviewer/discussion/bugs/thread/1dcc600a14/
Problem is OCIO is becoming a monster, aces 1.2 is quite big and the new one is even bigger, when starting something like Nuke or Houdini the time to load OCIO is unnoticed, but with mrViewer, that you want to be snappy, just double click and open the files, the time to load OCIO is an issue.
So I tested a simpler OCIO setup, I literally grab this one:
https://caveacademy.com/product/cave-cg-animation-aces-ocio-config/
It is much simpler, only has the minimum needed to review renders, and using it mrViewer loads much faster, basically aces1.2 takes around 5 sec to load, or that is roughly the difference I see when using a more simple ocio setup.
So it makes sense to have a simple OCIO setup for review and another one used in the DCC apps.
Most of us we really use 1% of OCIO to be honest.
Still, using an environment variable can still be the way to go. On Linux or Mac, create a shell script with the simple OCIO variable and call mrViewer.
On Windows, you'd create a .bat file, with something like:
set OCIO=D:/path/to/simple/ocioconfig
call "C:/path/to/mrviewer.exe"
Then fire up that .bat file instead of the .exe. And set all file associations to that .bat file instead of mrviewer.exe.
Yep definitely we can make a wrapper, but is not really a clean solution for this problem I think.
Many tools allows you to choose whether or not you want to use OCIO from the envar or from an explicit config file in the settings.
Actually, mrViewer has already everything there implemented, it just need to to what it says in the tooltip, because the preferences are already saving the config file correctly
Last edit: ggarra13 2021-06-25
Okay, I fixed it to behave like you want, albeit I still think this is a bad idea.
Thanks!
Will be 5.8.10?
Following the current releases, it will be 5.9.0.
Great thanks, I appreciate it