Export Crash by HD Resolution

Dear NodeBox-Team,

I just start to Render some simple Animations in high Resolutions like::

1920 x 900 by 30Frames/s - 500 total frames.

But NodeBox start to crash after the first 190 Frames.

Seems to be a TIF overflow because you keep the rendered pictures in a buffer before they get written into a QuickTime Movie?

I am using a Mac Pro, 4Gig of memory, enought disc space.
The Report start like that::

Date/Time: 2008-08-01 20:37:52.071 +0200
OS Version: 10.4.11 (Build 8S2167)
Report Version: 4

Command: NodeBox
Path: /Applications/NodeBox/NodeBox.app/Contents/MacOS/NodeBox
Parent: WindowServer [139]

Version: 1.9.4 ()

PID: 835
Thread: 0

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000002
Code[1]: 0x00000000


Thread 0 Crashed:
0 com.apple.CoreFoundation 0x908273b8 __CFDataGrow + 214
1 com.apple.CoreFoundation 0x908270f9 CFDataReplaceBytes + 217
2 com.apple.CoreFoundation 0x908272d7 CFDataAppendBytes + 157
3 com.apple.ImageIO.framework 0x91903f8f CGImageWriteSessionPutBytes + 109
4 libTIFF.dylib 0x91b8ae31 TIFFAppendToStrip + 474
5 libTIFF.dylib 0x91b89633 TIFFFlushData1 + 100
6 libTIFF.dylib 0x91b89716 DumpModeEncode + 190
7 libTIFF.dylib 0x91b8925c _cg_TIFFWriteScanline + 656
8 com.apple.ImageIO.framework 0x91903d1e _CGImagePluginWriteTIFF + 3749
9 com.apple.ImageIO.framework 0x91902e54 CGImageDestinationFinalize + 113
10 com.apple.AppKit 0x933ddf05 +[NSBitmapImageRep(NSBitmapImageFileTypeExtensions) representationOfImageRepsInArray:usingType:properties:] + 2345
11 com.apple.AppKit 0x933dd5cc +[NSBitmapImageRep TIFFRepresentationOfImageRepsInArray:] + 561
12 com.apple.AppKit 0x933dd2f6 -[NSImage TIFFRepresentationUsingCompression:factor:] + 1062
13 com.apple.AppKit 0x933dceca -[NSImage TIFFRepresentation] + 49
14 _objc.so 0x005430ed ffi_call_SYSV + 29
15 _objc.so 0x00543092 ffi_call + 98
16 _objc.so 0x005501e1 PyObjCFFI_Caller + 2582
17 _objc.so 0x005622de PyObjCAPI_Register + 929
18 org.python.python 0x0040e278 PyObject_Call + 45
19 org.python.python 0x00495851 PyEval_EvalFrameEx + 9242
20 org.python.python 0x004994d8 PyEval_EvalFrameEx + 24737
21 org.python.python 0x00499cdc PyEval_EvalCodeEx + 1819
22 org.python.python 0x004975b1 PyEval_EvalFrameEx + 16762
23 org.python.python 0x004994d8 PyEval_EvalFrameEx + 24737
24 org.python.python 0x00499cdc PyEval_EvalCodeEx + 1819
25 org.python.python 0x0042f537 PyFunction_SetClosure + 2019
26 org.python.python 0x0040e278 PyObject_Call + 45
27 _objc.so 0x005634ea PyObjCSelector_FindNative + 1302
28 org.python.python 0x0040e278 PyObject_Call + 45
29 org.python.python 0x00495851 PyEval_EvalFrameEx + 9242
30 org.python.python 0x00499cdc PyEval_EvalCodeEx + 1819
31 org.python.python 0x0042f537 PyFunction_SetClosure + 2019
32 org.python.python 0x0040e278 PyObject_Call + 45
33 _objc.so 0x005635ad PyObjCSelector_FindNative + 1497
34 org.python.python 0x0040e278 PyObject_Call + 45
35 _objc.so 0x0054cc12 PyObjCFFI_CountArguments + 1091
36 _objc.so 0x00542dbc ffi_prep_cif_machdep + 336

My recommendation is to save individual images rather than one QT movie, then use QT pro, some Python magic, or some other program like iMovie to stitch them together.

Thanks !!!

Thats it.

Much better solution to export frame Sequences.
I just open QuickTime Player and import an Image Sequence.

This is much better then the Movie Export.
It is also fantastic to work with PDF Movies for Resolution independent rendering & Alpha in a later step.

Also After Effects works better with Image Sequences.

Thanks a lot - this makes me happy again to continue my work in NodeBox!

cheers,

Toby