MXF write permission error (but not really)
Posted: Wed Jun 28, 2023 5:57 pmUsing DaVinci Resolve Studio 18.1.4 on Debian Linux I've been experiencing inability to export to MXF format that was seemingly caused by write permissions. The message I was getting was this:
"DaVinci Resolve is unable to render to the selected path
"/home/lyon/DaVinci" as it does not have write
permission. Please ensure that DaVinci Resolve has write
permission for the path selected and the first drive you list
in Preferences."
Looked like an easy fix however there was no actual problem with permissions. Exporting to i.e. MOV format worked just fine to the same directory and the same filename (apart from suffix). I have been using non-ASCII characters in the filename so changing that to the default "Untitled" was the next thing I tried, but failed again. After further testing I finally figured out that having a non-ASCII character in the project name itself was a problem!
Not sure why this only affects formats like MXF and not others but if anyone else hits the same issue in the future, make sure you only use ASCII in both project name and render file name if using MXF as output format.
Hope this helps.
Edit for the sake of completeness, these records were repeated in the log file:
"DaVinci Resolve is unable to render to the selected path
"/home/lyon/DaVinci" as it does not have write
permission. Please ensure that DaVinci Resolve has write
permission for the path selected and the first drive you list
in Preferences."
Looked like an easy fix however there was no actual problem with permissions. Exporting to i.e. MOV format worked just fine to the same directory and the same filename (apart from suffix). I have been using non-ASCII characters in the filename so changing that to the default "Untitled" was the next thing I tried, but failed again. After further testing I finally figured out that having a non-ASCII character in the project name itself was a problem!
Not sure why this only affects formats like MXF and not others but if anyone else hits the same issue in the future, make sure you only use ASCII in both project name and render file name if using MXF as output format.
Hope this helps.
Edit for the sake of completeness, these records were repeated in the log file:
- Code: Select all
ERROR: 'mbstowcs(newOutput, input, len + 1) != (size_t)(-1)' failed, in /media/datastore1/build/bmd-eng-ub_P277/project/src/libmxf/examples/writeavidmxf/write_op1a_mxf.c:305
ERROR: 'convert_string(newClipWriter, projectName)' failed, in /media/datastore1/build/bmd-eng-ub_P277/project/src/libmxf/examples/writeavidmxf/write_op1a_mxf.c:1478
ERROR: 'create_op1a_clip_writer(projectName, companyName, productName, productVer, projectFormat, projectEditRate, dropFrameFlag, useLegacy, packageDefinitions, srcMetadata, (OP1AClipWriter**)&newWrapper->clipWriter)' failed, in /media/datastore1/build/bmd-eng-ub_P277/project/src/libmxf/examples/writeavidmxf/write_mxf_wrapper.c:149
0x7fce658b9700 | Task | ERROR | 2023-06-28 19:40:38,365 | Error occured during recording of /home/lyon/DaVinci/Untitled.mxf : Can't open file for writing.
0x7fce668bb700 | Task | ERROR | 2023-06-28 19:40:38,367 | Error occured during recording of /home/lyon/DaVinci/Untitled.mxf : Unknown error.
Huge Thank you for sharing! This saved me a lot of time in tests to figure it out. 