ID 157675 - Transcoding errors are too vague when exporting from Nuke Studio/Hiero.

Follow

Problem summary
Transcoding errors are too vague when exporting from Nuke Studio/Hiero.

Customer reported version
hiero.n/a

Customer reported platform

Steps to reproduce
1) In Nuke Studio/Hiero, import footage into the Project bin.
2) Open the Project Settings (Project > Color Management) and set the colorspace for OCIO.
3) Adjust any colorspace knobs, then close the dialog to confirm the settings.
   3a) Open the ocio.config in a text editor, and remove lines for one of the colorspaces in use.
   3b) Then save and reload the config in the Project settings. This should create an errored colorspace in the prompt.
3) Add the imported footage to the timeline, and save the project.
4) Export the Sequence observing any errors.

Expected behavior
The error should have a clear and concise message for the issue.

Actual behavior
A vague error message appears that does not depict the actual problem. Other errors can include but are not limited to: 

"Invalid data found when processing input" - this occurs when exporting a .mov, reimporting the .mov, and adding it to the timeline to be exported again (it seems to be a same file name error)

"No valid project setting for Thumbnail"

"No valid project setting for Monitor Out"


Workaround
There is no available workaround at this time.

Reproduced by Support in:
Nuke Studio/Hiero 13.1v1 - Windows 10, macOS 10.15
Nuke Studio/Hiero 13.0v1 - Windows 10
Nuke Studio/Hiero 12.0v1 - Windows 10, macOS 10.15
Nuke Studio/Hiero 11.0v1 - Windows 10
Nuke Studio/Hiero 10.0v1 - Windows 10
Nuke Studio/Hiero 9.0v1 - Windows 10


Earliest version tested
Nuke Studio/Hiero 9.0v1 - This issue appears to be in all versions of the product

    We're sorry to hear that

    Please tell us why