NatronGitHub / Natron

Open-source video compositing software. Node-graph based. Similar in functionalities to Adobe After Effects and Nuke by The Foundry.
http://NatronGitHub.github.io
GNU General Public License v2.0
4.54k stars 332 forks source link

(User confusing): OCIO configuration gui #841

Open Randrianasulu opened 1 year ago

Randrianasulu commented 1 year ago

Make sure to follow our issue report guidelines

Natron version

Version 2.5 (C) 2018-2022 The Natron developers

Operating system

Linux Slackware 15.0 i586

System specs

RAM: 16GB CPU: AMD FX(tm)-4300 Quad-Core Processor GPU: Radeon 3000HD but currently software 3d

Did you install Natron using the official installer?

Custom installation path

No response

What were you trying to do?

I have my .ocio file in custom location set there by custom Blender 3.3 installation.

/usr/share/blender/3.3/datafiles/colormanagement/config.ocio

when I first started self-compiled Natron it warned me about non-default OCIO file so I visied Preferences - color management and pasted this line into text field. Warnings appeared saying restart is needed. I restarted Natron - my file was not in preferencies! Only after I unchecked both warning checkboxes in preferences -> color management and manually saved preferences my choice was saved.

May be Natron should save things by default in this area, in default checkbox configuration?

What did you expect to happen? What happened instead?

pasting full file path into preferences textbox will select it for use.

Warnings demand restart without actually saving newly-added ocio file path.

Disabling warnings and manually saving preferences does the job.

Step-by-step reproduction instructions

  1. Start Natron without default OCIO file
  2. Image opening will fail.
  3. Visit preferencies and paste path/filename of ocio file into text field in preferencies/color management.
  4. hit reload near file path
  5. Natron will warn you about needed restart
  6. After restart your choice not saved

Additional details

OCIO enviroment variable works fine.

rodlie commented 1 year ago

Thanks for the report, this is a known issue but for some reason has never been fixed (I have this issue when I setup a new dev environment, but of course forget to do anything about). I think it's the warning dialog that breaks saving (don't remember).