State:Closed|icon_bug|icon_nuke|database:public|Resolution:Fixed|TargetRelease:11.3v3|BugID:198430|
Problem summary
MXF footage errors when read into Windows OS, if there are spaces in the name of the file or directory.
This issue only occurs in Windows releases and not Linux or Mac OS's
The error received will be the following:
ERROR: 'abs_uri.ParseFilename(filename)' check failedERROR: near ..\..\..\src\mxf_reader\MXFFileReader.cpp:266
Customer reported version
nuke.11.2v3
Customer reported platform
windows10
Steps to reproduce
1) Locate an MXF file
2) Rename the MXF file to add in a space in the filename. eg. 'test_clip.mxf' to 'test clip.mxf'
3) Read in the MXF file into a Windows OS Nuke release version
Result: The Read node will not be able to read the MXF file when spaces are in the filename.
Note: This also occurs if the location of the directory has spaces in it. eg. C:/Users/Mr Test/Footage/test_clip.mxf
Workaround
Ensure that when using the MXF format, that there are no spaces in either the file itself or its directory.
Reproduced by support
This bug has been reproduced in:
Nuke 11.2v3 - Windows 7
Nuke 11.2v1 - Windows 7
Nuke 11.1v6 - Windows 7
Nuke 11.1v1 - Windows 7
Nuke 11.0v4 - Windows 7
Nuke 11.0v1 - Windows 7
Nuke 10.5v7 - Windows 7
Nuke 10.5v1 - Windows 7
Nuke 10.0v6 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7 - regression
Unable to reproduce bug in:
Nuke 11.2v3 - Centos 7.5 - MacOS 10.13.6
Nuke 9.0v1 - Centos 7.5 - MacOS 10.13.6
Nuke 8.0v7 - Windows 7 - Centos 7.5 - MacOS 10.13.6
Earliest version tested
Nuke 8.0v7
- Importing MXF files was not possible till Nuke 9 releases
Expected behaviour
MXF files should be able to be read no matter if there are spaces or not in the filename or directory
Actual behaviour
MXF files are not able to be read if there are spaces in the filename or directory
We're sorry to hear that
Please tell us why