I   would export png format via the queue manager. This format is uncompressed and will leave a transparent background as an alpha channel if you desire.
Its been awhile since I have used After Effects, but every video application can import an image sequence.
I tend to assemble my image sequences in Photoshop CS4 Extended, but only because it is quick and easy  to import the sequence, change edit the background drop a logo layer in front and export as a .mov ( I am on a mac and prefer quicktime as my delivery platform) At this point the movie is still uncompressed which is important. I wouldn't add any compression until the last stage , which will be saving file for web delivery. So if you plan on exporting to flash. make sure the video going into the flash video conversion is uncompressed. if it is already compressed you end up with double compression and a lesser quality end result.
This is another reason to export image sequence over a quicktime movie. I tend to only render to a quicktime movie when I a doing proof and don't mind tying up poser for a little bit. most of the time I still send those lesser quality firefly renders to the render queue so I can keep working and quickly assemble them in Quicktime Pro  to check the proof.

anyway, hope that helps some.
JC-

 Very cool demo reel! were most or all rendered in Cinema 4d? The lighting and textures are great. I saw "python physics" listed in the credits, was that Poser Physics?

 or just set the number of extended downloads to "0" and hit update.

  have you tried wardrobe wizard to convert the clothing?

 Agreed. it is cool.

 TrekkieGrrrl,
 Did you have a wind generator in that scene? Seems like the hair is waving and blowing even when he is just sitting. Could be from some of the dynamics settings, but looks like an external force.

I haven't spent a lot of time in the hair room for awhile, but got some decent results for stills. a couple things you need to keep in mind. The individual hairs keep the same thickness and thus say you have 2,000 strands on scalp. when your camera is far away it may look perfect, but then you decide to do a close-up and now the hair is sparse. I had to add more strands, but even then it wasn't looking right.  I will have to look around for some renders, but I think the mistake the many people make is that grow all the hair at once and try to style it. You need to grow it in groups , like 2 for bangs, 2 for right side and 2 for left side and 2 for top and 2 for back. You may think why 2? it adds a lot of work. but you need to have 2 to add more realism. The 2nd  set of hair in a group should be slightly shorter and offset or I like to take the style tool and just twist it a slight bit., then I slightly change the color of the 2nd set as well, just ever so slightly.
This is not something you can whip out in a few minutes , it will takes hours so be prepared, but the results will be much better. Take notes of your settings as well as you work. So you can flip the numbers for the right and lefts sides or slightly vary the length quickly without going back and forth too much.

Quote - > Quote - You should report bugs to Smith Micro. Posting them on the forums may get them noticed, or may not, but if thinkcooper misses this thread for some reason, your bug may be around long past SR1.

How do you know I haven't?

 I have super mind sourcing built into my helmethead that allows me read the minds of local populations. currently at GMT-5 it is 18:45. Through sophisticated deduction algorithms  I am assuming you are not in Columbia and have placed you on the east coast and have scanned the minds of Greensboro, North Carolina with no positive response on a recent Smith Micro bug submission.
Since my conclusion is based on science, it must be correct :)

ofcourse if by some obscure fault in my math you could be located elsewhere and actually have submitted a bug to Smith Micro. in that case. I may self destruct.

You should report bugs to Smith Micro. Posting them on the forums may get them noticed, or may not, but if thinkcooper misses this thread for some reason, your bug may be around long past SR1.

 Try dialing it in the negative value instead of positive.

nice job! and thanks for the  tips on zbrush. cool stuff!

 ok, So I am not 100% on this, but it is roughly how my friend Darrell explained it to me.
inside of 3d studio max I would add this new mesh as a morph target to the original head mesh, add a subdivision layer to it then bring the high res mesh and use the skin wrap modifier to wrap the high res to the low res mesh.

does that make sense? 

 smallspace: check out the Poser8 Blog there is some info how to make the adjustments to arm length using dependent parameters.
http://poser8.smithmicro.com/

 vilters: the problem with that solution is that the low res figure has a different poly count and can't be used for morph targets for the high res version. I suspect the workflow 3Dream had mentioned involves a 3rd party app and some retargeting of morph from low to high in that app before exporting there  and importing as a morph target. sounds too much for me. 
Why not just morph the high res figure? if that is your target.

Deecey: Thanks!

 no problem, glad you figured it out! :) we'll be awaiting the link to the final youtube animation :)

To create the emotional face files:
First  save the emotional "looks" to the  face library. Dial in a surprise, anger, etc... and save. now you have the face files. the fcz are just compressed versions. no need to compress yours.
Now take those face files and place them in an appropriate folder in the lipsync folder of the applications folder.  if you figure is betty, just make a "betty" folder and copy the emotional face files you made here. Now copy one of the viseme map. XML files and edit it  by pointing to the proper expressions that you just moved into the "betty" folder.

those will get your emotional expressions for the talk designer out of the way, but if you want your figure to work in the face room they need to have the proper Phoneme channels on the head actor. And make sure the names match the XML file. this is why it is handy to copy another figures XML file and then use the naming for your Phonemes.

I hope that helps a bit.