[Jimmy Brunger]

When upgrading to CS3 can you keep AE7 on your current machine and run CS3 on a new machine does anyone know?

[Jimmy Brunger]

Are there any gotchas on CS3 for Windows machines (plugins, etc)?

[Jimmy Brunger]

Don’t know the answer to that one I’m afraid, other than try it on a faster machine with more memory. AE is letting you have a comp of that size because somewhere there is a machine that can render it…it doesn’t know you’re machine can’t since the software is not tied to the hardware’s limitations in that way.

What you could try as a workaround is to enable caps lock before loading the comp in question, then load it up at quarter res or something with your quality switches down – it will be difficult to work with, especially when you need to determine how much mo blur/interlace flicker you need to apply (for a picture that size I’ll bet you’ll get some really nasty flickering on a TV screen when it’s zoomed right out) but you should still be able to render it out at full res using the secret purge menu and caps lock..Let us know how it works out.

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

With Photoshop you can do a gradient with several ‘points’, where you can alter the grad to fit each line of text (presuming you don’t alter the line spacing afterwards) and if AE CS3 supports PS layer styles fully (I haven’t got CS3 yet) then it should translate across.

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Beat me to it!

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

How much RAM do you have? Sounds like you need a load of it for resolutions like that. You could also try purging all caches before doing a preview or render – to maximise that aswell, also try skipping a frame or two on RAM preview (shift+RAM settings)

There’s the other usual workarounds like pre-rendering whatever you don’t need control of at the time of this preview, reduce res of layers if poss and their full res is not needed. Try rendering with caps lock down, so the preview window doesn’t take up memory updating. Ther’s also a secret or ‘schecret’ menu you can get to which I can’t remember (search schecret on the cow) which purges X amount of frames as you render to free up RAM. One of those should do the trick..

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Thanks for all your advice Steve..I will *HAVE* to tie the boss down to buying some blummin kit soon!!

Last, LAST thing!…Is it only Fast Preview & Fast Render that utilises all procs and speeds things up? Or do the other Spec operations use multiproc aswell?

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Hi guys,

Thanks for the responses! No, this is for another job where I personally wanted to try avoid render time by deinterlacing and rendering progressive – but a no go it seems. Can’t believe I didn’t know about AE’s ‘problem’ of taking twice as long for interlaced. Do other compositors have the same restriction? The Editbox will render either and amalgamate on the fly in the same time – I know it’s an expensive box, but I thought AE would have caught up in certain respects…I mean I know I need a much faster machine, but under the hood I’m surprised. Hey ho.

No Moldy, the ‘shooting 50i to get 25p’ guy is still a plonker and is still talking tosh. But that job didn’t come off in the end anyway unfortunately, so maybe the client thought he was full it aswell!

We might have to invest in Magic Bullet in the future then (and a faster box of course!) I just wanted to see if I could offload some work from the E/box, but obviously not for stuff like this! My keying tools are still head and shoulders above the Quantel though, so I might see some of the job, other than the very pedestrian GFX I get lumbered with!

It’s all work…

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Compounding all Dave says (you REALLY need a TV monitor of somesort, ideally at least analogue component connected for broadcast gfx wrk) red and black are notoriously hard work together – especialy if you want clean sharp lines, which it sounds like you do. Keep your black at no less than 16 in the RGB scale and try to desaturate you red until it looks good in the TV monitor, plus use your scopes in FCP.

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0

[Jimmy Brunger]

Thanks for your replies guys..I think I will be buying Nucleo Pro anyway, I just wondered if somehow CS3’s multiproc support was in ADDITION to Nucleo’s – thought that was too good to be true! Sounds like it’s either or..right? So if you are doing a spec render for instance, then your previews while that is going on can only be a standard 1-proc RAM preview, as per with AE7 withOUT Nucleo, oui?

As for this temporal thing – so does Motion Blur of layer come into this? I use mo blur on just about any layer I move, but can’t figure out if it is truly temporal or whether the render is calculated by the layer’s position differences?

Last thing (promise!) with the temporal effects will Nucleo render them, but just at normal speed, then resuming fast preview when it has passed them right? So you can do spec preview, commit to disk, background render, etc – but that part of the comp will only be rendered with 1 proc?

Thanks again. Oh – how much longer will NP2 be at that pre-order price Steve? 😉

*Production Studio Premium / *Combustion 3
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / 110GB boot/80GB media/600GB RAID-0