Quickime/OSX: render output path with diacritic signs produces no video file
Closed, ResolvedPublic

Description

System Information
Operating system and graphics card
OSX 10.10.3, NVIDIA GeForce 320M 256 MB

Blender Version
Broken: 2.75 RC1 bff8b5d

Short description of error
When you try to render animation and set render output path with diacritic signs, Blender is rendering the video frame by frame, notifies that it's finished work, but in the end it produces no video file.

Exact steps for others to reproduce the error

  1. Open attached blend file
  2. render output path is set to "//renderó/" (ó is an example of diacritic sign in Polish language)
  3. Render animation using Animation button or Ctrl F12
  4. In the //renderó/ folder you end up with no file in the end.
  5. Change output path from "renderó/" to "render/"
  6. Render again.
  7. Now everything works and you end up with video file.

Maybe something changed about Blender's language coding? It's not UTF-8 anymore?

Chris Slazinski (mallow) updated the task description. (Show Details)
Chris Slazinski (mallow) raised the priority of this task from to Needs Triage.
Chris Slazinski (mallow) set Type to Bug.

Works here on Linux…

Jens, not sure if you still handle issues on that platform? Else please reassign to @Sergey Sharybin (sergey).

Actually, it’s Martijn now our OSX maintainer ;)

Confirmed this on OSX 10.9.5

Note that unlike win32, OSX path/encoding is the same as Linux/BSD's (From Blender's code-side at least).


This problem us only happening with Quicktime exported movies.

Checked on the code qtkit_export.m and possible causes are:

381 ┊▒▒▒┊▒▒▒qtexport->filename = [[NSString alloc] initWithCString:name
382 ┊▒▒▒┊▒▒▒ encoding:[NSString defaultCStringEncoding]];

Looking at the docs, defaultCStringEncoding is discouraged:

https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSString_Class/index.html#//apple_ref/occ/clm/NSString/defaultCStringEncoding

You might sometimes need to use this encoding when interpreting user documents with unknown encodings, in the absence of other hints, but in general this encoding should be used rarely, if at all.


However this is tricky, In Blender all object names are utf8, but paths are an exception, where non utf8 latin1 characters are allowed too.

Even so, it may be best to use UTF8 (NSUTF8StringEncoding) here, since this is what blender uses for all input.

Campbell Barton (campbellbarton) renamed this task from render output path with diacritic signs produces no video file to Quickime/OSX: render output path with diacritic signs produces no video file.Sep 11 2015, 1:03 PM