You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ExtractReview plugin is not creating a reviewable representation of files that have its extension in uppercase.
You can see the following message in the ExtractReview logs: INFO: Representation has unsupported extension ".MOV".
Also, in ftrack, you can see there is no reviewable component for the published version.
Expected Behavior:
The ExtractReview plugin should be extension-agnostic, meaning it should accept both .MOV and .mov as long as the extension is supported.
If configured, a reviewable component should appear for the assetversion in ftrack.
Version
1.0.14
What platform you are running on?
Linux / Centos
Steps To Reproduce:
Using the traypublisher, try to publish a render whose representation has .MOV extension.
Check ftrack, an assetversion should appear but with no ftrack review component.
Are there any labels you wish to add?
I have added the relevant labels to the bug report.
Relevant log output:
Additional context:
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior:
The
ExtractReview
plugin is not creating a reviewable representation of files that have its extension in uppercase.You can see the following message in the
ExtractReview
logs:INFO: Representation has unsupported extension ".MOV"
.Also, in ftrack, you can see there is no reviewable component for the published version.
Expected Behavior:
The
ExtractReview
plugin should be extension-agnostic, meaning it should accept both.MOV
and.mov
as long as the extension is supported.If configured, a reviewable component should appear for the assetversion in ftrack.
Version
1.0.14
What platform you are running on?
Linux / Centos
Steps To Reproduce:
.MOV
extension.Are there any labels you wish to add?
Relevant log output:
Additional context:
No response
The text was updated successfully, but these errors were encountered: