- Tue May 08, 2007 10:04 am
#223910
can we please get the rendering paths sorted out for the next release of cinemaxwell on os X.
currently cinemaxwell writes random nonsense into the path depending on the file format you have chosen.
i.e.
if i have a scene called 'blah' and render it as a jpeg file then everything is fine and maxwell renders blah.jpg.
if i try to render the same scene as a tiff file cinemaxwell tries get mxcl to write a file called blahPNG (it hasn't added a '.' and the file extension is wrong and in all caps).
if i wish to render this as a png file cinemaxwell once again calls the file blahPNG which is almost there apart from the fact that once again it has lost the '.' and capitalised the extension. i can get this to render but only if i call my scene blah. and accept that maxwell is going to add a capitalised PNG on the end.
cheers, simon w.
currently cinemaxwell writes random nonsense into the path depending on the file format you have chosen.
i.e.
if i have a scene called 'blah' and render it as a jpeg file then everything is fine and maxwell renders blah.jpg.
if i try to render the same scene as a tiff file cinemaxwell tries get mxcl to write a file called blahPNG (it hasn't added a '.' and the file extension is wrong and in all caps).
if i wish to render this as a png file cinemaxwell once again calls the file blahPNG which is almost there apart from the fact that once again it has lost the '.' and capitalised the extension. i can get this to render but only if i call my scene blah. and accept that maxwell is going to add a capitalised PNG on the end.
cheers, simon w.
- By choo-chee
- By Mark Bell