This is a question for any mac user who has v15j+ and v16 RC and possibly any version before v15 on their intel mac

Could you do the Teapot benchmark in all three and post the times?

I'm working on my flyer and I'd like to mention that Mac render times are improved.

it´s on my to-do-list for the next year

no seriously, i will post my rendertimes next week...

Report:
Version 15.H
render time min:sec 42:34
CPU Brand and model 2006 Intel Zeon Woodcrest 3GHZ Processor
Actual CPU speed in GHz
how many cores A:M is using: single core I think unless 15.H is capable of harnessing the power of multiple cores for render to file.
RAM 12GB 666MHZ
OS Snow Leopard OSX 10.6

mine was:
V15.H
42:34
late 2006 Apple Mac Pro Tower intel
Intel Zeon Woodcrest 3GHZ Processor
1 core
RAM 12GB 666MHZ
OS Snow Leopard OSX 10.6

V16RC
7minutes
Click to view attachment

V16 for mac has an 83% increase in speed or only takes 16% of the time it used to take to render the same scene scene.

It just dawned on me that AM for mac renders faster on Mac than on PC. I know because I have a dual boot system.

thanks! I knew it was better but didn't know it was that dramatic!

It has been dramatic!

I ran the teapot test a couple of weeks ago w/v16 and my time was 6:47.
(Mac Pro: 2 x 2.8 GHz Quad-Core Intel Xeon w/ 10GB 800 MHz DDR2 RAM)

Click to view attachment

It was definitely a big help when I had to do that commercial in such a short time. Running 7 instances of v16, rendering scenes was very fast.

How in the world did you get 7 instances of A:M running at the same time?

I think you get diminishing returns when you have instances of AM rendering beyond the number of cores in your computer. I also recommend a minimun of 2 gigs of ram per core and or instance.

By option-dragging six copies of the A:M application folder to my desktop (I add letters after each one, so they don't overwrite.) When rendering, you can change the settings so that each one of them starts on a different frame and renders every 7th frame. Once you've got all of them rendering, a scene renders very quickly.

I have 8 cores on my machine, so that still left one core free.

largento -

Yoda64 does not recommend making multiple copies of the A:M folder. Instead he wrote this short applescript to accomplish the same thing. Well, it is only for 2 instances, but the script can be modified. If you could modify it to take an input (number of instances you wanted to run) from the keyboard that would be great.

http://www.hash.com/forums/index.php?act=a...st&id=53660

Do you render FROM the same file with all 7 instances? Do you render TO the same file?

As far as I know (Iam not an hash employee):
Offical beta tester can test more than 2 cores at a time to write better bugreports.
Hash is currently deciding how this is handled in future for the user... Possible option is a new licence-type which is a little bit more expensive but offers more renderinstances. No point in discussing this so since it is not devided yet.

*Fuchur*

You would typically load the same file in all instances.

You can't render to Quicktime or AVI this way; images only, that you reassemble later into a movie.

If you give the instances all the same filename to render to (imagename000.tga) they handle the numbering automatically.

I did see that post, but haven't tried it yet.

I do render FROM the same file. In fact, it's the only time I use Project files. That way I can save all of the render settings and not have to set them again and again (also the project file allows you to change the fps.)

Then, like Robert points out, I render to image files rather than video files.

It works very nicely.

I don't think I understand what you mean by "it's the only time I use Project files."

There are two other options for saving render settings

-set them all in the camera in the chor

or, better

-save a "preset" from the render dialog

I don't save project files. I save all of my assets and choreographies as individual files and bring them in when I need them.

Opening a choreography file automatically imports the models and actions used in the choreography.

Just my personal preference.

Has advantages and disadvantages... It will always be a bit of a danger to change something because your other projects may not be compatible to the changes.... If you keep versionising or keep it always compatible it is a very good idea because you wont loose any models etc when the project gets corrupt. Using a embedded project means being able to rerender and reopen and get the exactly same result as before... I like it that way better but I make many backupfiles/versionise the projectfiles and sometimes save my models etc externally. Anyway i reembeed them again after that.

See you
*Fuchur*