OpenColorIO Error with unicode path to config file under Windows #47869

New Issue

perfection cat · 2016-03-21T05:41:05+01:00

perfection cat commented

2016-03-21 05:41:05 +01:00

System Information
Windows 10 Pro 64bits
NVidia GTX960 2GB + Geforce GT730
16GB RAM

Blender Version
Broken: 2.77 release version
Worked: (optional)

Short description of error
error message:
OpenColorIO Error: Error could not read 'F:\work*oS*\blender-2.77-windows64\2.77\datafiles\colormanagement\config.ocio' OCIO profile.
Color management: using fallback mode for management

A part of the BOLD notation is multi-byte character string.

Exact steps for others to reproduce the error
An error occurs at the time of start of blender in OpenColorIO when I install a 2.77 official release version in a file pass including the multi-byte character string.

**System Information** Windows 10 Pro 64bits NVidia GTX960 2GB + Geforce GT730 16GB RAM **Blender Version** Broken: 2.77 release version Worked: (optional) **Short description of error** error message: OpenColorIO Error: Error could not read 'F:\work\**oS**\blender-2.77-windows64\2.77\datafiles\colormanagement\config.ocio' OCIO profile. Color management: using fallback mode for management A part of the BOLD notation is multi-byte character string. **Exact steps for others to reproduce the error** An error occurs at the time of start of blender in OpenColorIO when I install a 2.77 official release version in a file pass including the multi-byte character string. ![OpenColorIO Error.png](https://archive.blender.org/developer/F297506/OpenColorIO_Error.png)

perfection cat commented

2016-03-21 05:41:05 +01:00

Changed status to: 'Open'

perfection cat commented

2016-03-21 05:41:05 +01:00

Added subscriber: @sindra1961

Bastien Montagne changed title from ~~OpenColorIO Error: Error could not read ...........~~ to OpenColorIO Error with unicode path to config file under Windows

2016-03-21 16:03:50 +01:00

Bastien Montagne commented

2016-03-21 16:04:36 +01:00

Added subscribers: @MartijnBerger, @Sergey, @mont29

Sergey Sharybin was assigned by Bastien Montagne

2016-03-21 16:04:36 +01:00

Bastien Montagne commented

2016-03-21 16:04:36 +01:00

@Sergey think you are our OCIO guy? unless @MartijnBerger wants to handle that windows mess… ;)

Sergey Sharybin commented

2016-03-23 15:09:24 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2016-03-23 15:09:24 +01:00

blender-admin commented

2016-03-23 15:09:36 +01:00

This issue was referenced by ab4307aa08

This issue was referenced by ab4307aa0868f2d8389cc0dd500eff38909b08f1

blender-admin commented

2016-03-23 19:28:16 +01:00

This issue was referenced by c1095c7a9f

This issue was referenced by c1095c7a9f1c96a5bb249bed8e465e653a54a4dc

Sergey Sharybin commented

2016-03-23 19:29:26 +01:00

Changed status from 'Resolved' to: 'Open'

Sergey Sharybin reopened this issue

2016-03-23 19:29:26 +01:00

Sergey Sharybin commented

2016-03-23 19:29:26 +01:00

Fix wasn't really correct. Re-opening for further investigation. But it might be a limitation of OCIO API :S

perfection cat commented

2016-03-24 03:56:05 +01:00

istream can handle multi-byte character string, but is caused by the fact that multi-byte character string is included in a parameter to generate istream instance.
I think that you should preprocess the argument which is used to generate istream instance.
The basic cause thinks that type of the argument of Config::CreateFromFile is inappropriate.

istream can handle multi-byte character string, but is caused by the fact that multi-byte character string is included in a parameter to generate istream instance. I think that you should preprocess the argument which is used to generate istream instance. The basic cause thinks that type of the argument of Config::CreateFromFile is inappropriate.

Sergey Sharybin commented

2016-03-24 08:51:21 +01:00

It is nothing to do with istream. that part works just fine and config file is parsed just nicely. The issue appears when OCIO needs to access lookup table referenced in the config file. OCIO needs to know where to find those lookup tables and in normal case this is how it works:

If config is created from a given file name, then the dirname of that file name is used as a search path. So if lookup tables are referenced by a relative path in the config it all works just fine.
Additionally you can give OCIO hints about search path osing Config::setSearchPath (or something like that).

The issue here is that both points (and underlying calls) operates with char * paths (and no _w* function extensions) which Windows API expects to be ANSI encoded a\, making it impossible to operate with multi-byte paths for OCIO.

There might be some workarounds for that, that's where i am atm.

It is nothing to do with `istream`. that part works just fine and config file is parsed just nicely. The issue appears when OCIO needs to access lookup table referenced in the config file. OCIO needs to know where to find those lookup tables and in normal case this is how it works: - If config is created from a given file name, then the `dirname` of that file name is used as a search path. So if lookup tables are referenced by a relative path in the config it all works just fine. - Additionally you can give OCIO hints about search path osing `Config::setSearchPath` (or something like that). The issue here is that both points (and underlying calls) operates with `char *` paths (and no _w* function extensions) which Windows API expects to be ANSI encoded a\\, making it impossible to operate with multi-byte paths for OCIO. There might be some workarounds for that, that's where i am atm.

Sergey Sharybin commented

2016-04-26 14:07:06 +02:00

Changed status from 'Open' to: 'Archived'

Sergey Sharybin closed this issue

2016-04-26 14:07:06 +02:00

Sergey Sharybin commented

2016-04-26 14:07:06 +02:00

This is a limitation of 3rd party library API. I've reported it to the upstream: https://github.com/imageworks/OpenColorIO/issues/406

Will probably have time to look into solving it from OCIO side, but that's not a task of the bug tracker. So thanks for thee report, but closing it now.

This is a limitation of 3rd party library API. I've reported it to the upstream: https://github.com/imageworks/OpenColorIO/issues/406 Will probably have time to look into solving it from OCIO side, but that's not a task of the bug tracker. So thanks for thee report, but closing it now.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

OpenColorIO Error with unicode path to config file under Windows #47869