Jump to content

destro

Members
  • Content Count

    988
  • Joined

  • Last visited

Posts posted by destro


  1. Nuke already uses OpenCL here and there as does Premiere Pro and you can bet your sweet as that Maxon will pimp the Physical Render and TeamRender with OpenCL in R16.

     

    Mylenium

     

    I sure hope you're right about OpenCL and the Physical Render engine.

     

    All my CPU cores run at 100%. Embree works like magic. Add my GPU cores to that and I'll be a very happy puppy.


  2. I think that one of the reasons that this works so well as parody is that it is a well-executed example of the thing being parodied.

     

    Agreed. Someone with such brilliant skills doing what looks like tutorial projects. You could pick that irony up with a magnet.


  3. My thumb is wavering between horizontal and down.

     

    Not having to pay a large sum upfront and always having the latest version is great. Renting rather than owning core assets is the balance to that.

     

    But for fucks sake, CC has to work 99.9% of the time or I would rather avoid it like the plague. I can't make a decision if CC is a good thing for me until is works like a professional solution. It's been deployed for many months now and it still feels half-assed.


  4. Norilsk Nickel revenue for 2012 = US$12 billion.

     

    Mograph and other modules will help you out but there really is no short cut to that level of detail. If you were doing this as a paying job you would need to make sure the client understands it's going to be very expensive.

     

    If you're looking for commercial animations to imitate for practice, look for something more manageable.


  5. Team Render just clocked in at 3 hours and 40 minutes. Single picture viewer clocked in at 3 hours 56 minutes. The scene is 1.08gb and has baked dynamics. The sim has not yet been baked to keyframes, but the baked interactions worked fine.

     

    Only 16 whopping minutes saved. Not the kind of gains I expected. Wondering why it's not cutting the time in a third or half. Are there any tips to optimize Team Render. Like allocating more or less RAM to the picture viewer, etc?

     

    Try baking all the dynamics before using team render. If one team render machine starts rendering at say frame 100, it is probably doing dynamics calcs for the previous 99 frames so it knows where the objects should be.


  6. Dumb R14-user question: do you have to use Team Render? Does R15 not come with Net Render at all?

     

    R

     

    Net Render is gone in R15. If you rely on Net Render in R14 to meet your deadlines, be very careful about upgrading. Team Render is great for quick test renders, but for critical final renders it's not ready for prime time.


  7.  

     

    The intention/vision is to put more 3D functionality into After Effects as well as to have better integration with an existing established 3D application. What we released in After Effects CC (12.0) was a first step. There were some small improvements in 12.1. There will be more improvements this year. And so on.

     

    Basically, we %$*&ed up with the ray-traced 3D renderer, and we learned a lot of lessons. During that time, a _lot_ of people said that we should "just do 3D like Cinema 4D". We took that to heart, and now we are doing 3D "like Cinema 4D" by doing 3D _with_ Cinema 4D.

     

    The first step is useful for some people, and it will get more useful as we and Maxon have more time to make the integration tighter and more seamless (and faster).

     

    I'm really happy to hear this. Cineware for me is a frustration more than anything. Not because it doesn't work, but because it's not yet developed to the point where it's very useful to me. It's so close to being amazing, yet not close enough for me to use. I'm primarily a 3D guy doing finishing work in AE, so I'm working in the full C4D app then moving to AE. With more time to develop I can see the C4D -> Cineware -> AE connection being a killer workflow for 3D motion graphics.

     

    And thanks again Todd for talking directly to us end users. For me to pay my CC sub it's great to know AE is going to keep developing in a way that will be genuinely useful to the way I work.


  8. The CC components are still a bit dodgy for me too. Nothing that doesn't stop me from working in my case, but it doesn't fill me with confidence that the system won't just fall over at any moment.

     

    Just taking about AE itself...If the AE team did nothing but fine-tune the software for the next year I would be happy. Snappy, responsive software is one of the biggest factors in keeping motion graphics a fun job, instead of tedious drag.


  9. If it's going onto the GPU I'd want it to be with OPENCL and not some manufacturer specific nonsense.

     

    I suspect it's heading that way. People with the new MacPros won't be keen on buying software that leaves their dual GPUs sitting idle.

×
×
  • Create New...