Quickime/OSX: render output path with diacritic signs produces no video file #45165

New Issue

Kris Slazinski · 2015-06-23T23:40:35+02:00

Kris Slazinski commented

2015-06-23 23:40:35 +02:00

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

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

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

**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 [anim.blend](https://archive.blender.org/developer/F196998/anim.blend) 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?

Kris Slazinski commented

2015-06-23 23:40:35 +02:00

Changed status to: 'Open'

Kris Slazinski commented

2015-06-23 23:40:35 +02:00

Added subscriber: @mallow

Bastien Montagne commented

2015-06-27 16:03:28 +02:00

Added subscribers: @Sergey, @mont29

jens verwiebe was assigned by Bastien Montagne

2015-06-27 16:03:28 +02:00

Bastien Montagne commented

2015-06-27 16:03:28 +02:00

Works here on Linux…

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

Works here on Linux… Jens, not sure if you still handle issues on that platform? Else please reassign to @sergey.

Bastien Montagne commented

2015-06-27 16:17:48 +02:00

Added subscriber: @MartijnBerger

Bastien Montagne commented

2015-06-27 16:17:48 +02:00

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

jens verwiebe removed their assignment 2015-09-08 20:25:41 +02:00

Martijn Berger was assigned by jens verwiebe

2015-09-08 20:30:07 +02:00

Campbell Barton commented

2015-09-11 12:50:12 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-09-11 12:50:12 +02:00

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.

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 changed title from ~~render output path with diacritic signs produces no video file~~ to Quickime/OSX: render output path with diacritic signs produces no video file

2015-09-11 13:03:46 +02:00

blender-admin commented

2015-09-11 13:32:05 +02:00

This issue was referenced by 21826af5f7

This issue was referenced by 21826af5f730e7dff441d206b25d5ccd0992dea4

Howard Trickey commented

2015-09-11 13:34:13 +02:00

Changed status from 'Open' to: 'Resolved'

Howard Trickey closed this issue

2015-09-11 13:34:13 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Quickime/OSX: render output path with diacritic signs produces no video file #45165