Victor DiMichina wrote:
>> You should report it to Adobe I think.
>
> I will report it to Adobe. Not sure how confident I am that they'll
> care, but it's worth a try.
> We're OS X server with AFP share. it's been doing this before 10.6,
> but I recently started batch framing, so I don't know if previous
> versions of OS X server/client/AE had this problem.
The log should raise some eyebrows.
With a successful run you get:
Executing: aerender -project " /foo/bar/path/to/r01_sn1200/projects/ae/r01_sn1200_DISP_001.aep" -comp "r01_sn1200_DISP_001" -s 211 -e 220 -mp
[..]
PROGRESS: 00211 (1): 29 Seconds
PROGRESS: 00212 (2): 30 Seconds
PROGRESS: 00213 (3): 29 Seconds
PROGRESS: 00214 (4): 26 Seconds
PROGRESS: 00215 (5): 25 Seconds
PROGRESS: 00216 (6): 24 Seconds
PROGRESS: 00217 (7): 25 Seconds
PROGRESS: 00218 (8): 22 Seconds
PROGRESS: 00219 (9): 22 Seconds
PROGRESS: 00220 (10): 21 Seconds
PROGRESS: 3/14/11 12:27:00 PM PDT: Finished composition 'r01_sn1200_DISP_001'.
..and with a bad run you get:
Executing: aerender -project " /foo/bar/path/to/r01_sn1200/projects/ae/r01_sn1200_DISP_001.aep" -comp "r01_sn1200_DISP_001" -s 191 -e 200 -mp
[..]
PROGRESS: 00191 (1): 3 Min, 25 Sec
PROGRESS: 3/14/11 12:23:58 PM PDT: Finished composition 'r01_sn1200_DISP_001'
In the latter case, from the developer's point of view, the /lack/ of information
between the first frame rendered (191) and the 'Finished composition'
should be disturbing to them; it should at least show errors if errors occurred
one way or the other about 191 thru 200; it should not just say 'nothing'.
In the above error case, the exit code of 0 is bad too; if all frames didn't
render, it should not return a zero (success) exit code.
There should be more careful attention towards error conditions in AE;
that's always been a problem. It seems like some image formats are better
advertised than others.
Also, it's important they log actual OS errors instead of just programmer's
interpretations of what went wrong. In the times I see AE throw permission errors,
it prints non-OS errors suggesting a problem with write permissions, but it should
really include the actual OS errors (using strerror() and errno) so that we can see
'Permission denied' or 'No such file or directory', and under windows it should use
the equivalent [FormatMessage() & GetLastError()] so we can see things like
'Logon failure: unknown user name or bad password.' or 'The network path was not found.'
Feel free to include my observations and email address
>> I've seen other customers run into this, and it's mostly been recently
>> (last few months). Not sure if it's something to do with a recent upgrade
>> of OSX, or AE, or some magic combo.
>
> It's been pre-10.6 for me, At least since 10.3
10.3, wow, that'd be 'forever' then.
--
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|