[Peter Butler]

Now it’s perfect 🙂

Again many thanks.

Peter

[Peter Butler]

Actually just realised there’s still a decimal in there, it’s just moved inwards a bit.

Any ideas?

Peter

[Peter Butler]

Works perfectly, thank you so much. You’ve saved me a lot of time.

[Peter Butler]

Hi Declan,

Thank you so much for this, I’ll try it out in a bit and let you know how I got on.

Many thanks,

Peter

[Peter Butler]

Thanks for the reply Todd,

Yes I think it’s great that you are addressing the fact that it is now easy to do basic 3D text in AE. Sorry if I came across to harsh on this. I really do think Adobe are going to great lengths to listen to their customers.

I just think it’s a shame that if you have an ATI card it’s so much slower. To be honest I don’t know how much slower it is than if I had an Nvidia card. ButHfrom what I’ve read, there are real advantages to going with Nvidia. having a Mac doesn’t leave me many options.

Paul, I haven’t used the render in BG feature, that sounds quite useful.
It would just be nice to be able to make decisions on timing, composition and the look, faster then what I currently can with raytrace switched on. Even if I turn everything down to draft the render of each frame is really, really slow.

Thanks for the feedback, much appreciated.

Peter

[Peter Butler]

Yeah Element uses Open Gl 2.

I thought it would be easier to use 3D text in After Effects rather than having to keep rendering in Maya.

Unfortunately it looks like I may as well stick with rendering everything in Maya.

To be honest I don’t see the point of the ray-trace engine as it is. Even with a top of the range 6gb Cuda card the rendering is so much slower then if you were to do the same thing in something like Mental Ray. Even Maxwell would render faster and with far more realistic results than the times I’ve seen quoted for AE.

[Peter Butler]

I see, thanks for the info Paul. It’s a shame it on;y works with Nvidia cards. As far as I can tell you can only use the 4800 with the Macpro unless you start hacking things to work.

[Peter Butler]

Wow, I’ve got to say if there’s one thing better than great new features in any app, it’s direct feedback from the developer.

The saying “people buy people” sums this up. The fact that Todd has taken the time to reply is something I rarely see in large companies these days and very comforting to know that Adobe are listening.

Thanks Todd, I look forward to what the team have up their sleeves.

Peter

[Peter Butler]

Great points,

Funny enough I’d just emailed Adobe about improvements and one of them was the graph editor.

I’m an CG animator and so most of my work is in Maya. I use the graph editor a lot in Maya and I find it really nice to use.

I’ve used AE for quite a few years but really never had to do much in terms of animation in it. Yesterday I spent about 2 hours trying to figure out the graph editor. I came to the conclusion that it’s really, really clunky.
Why has it got two different graph modes? One for speed and one for position. You can achieve both of these using one graph.

Having pixels per second on the vertical line and frames per second on the horizontal is really confusing and as far as I know not necessary.

Surely you just need the frames per second on the horizontal and the pixel position on the vertical? Thus allowing you to dictate how fast your object goes and at what point it reach it’s destination.

It seems like the graph editor in AE has been this confusing way for years so I doubt they’ll change it but you never know.