-
Weird render problems??
I’ve got a fairly heavy 45 second sequence I’m trying to render and AE is behaving very strangely…
I’m using Nucleo Fast Render to do a full res QT and two things are happening – when I come back in the morning to view my render AE is saying would you like to overwrite the output module, even though there is nothing in the destination folder with even a remotely similar filename. However when I look directly into my dest folder the render had already been done – it’s almost as if AE wants to render it twice. In the render queue my original render is still queued and there is no record of the one that has finished as being done!?!
AND….when I view the full res render that has actually been done it is cut short at the same point everytime I try this. It seems to coincide with the start of a new layer. Now this layer will render fine if I just render that portion around it and it will preview fine, but when rendered with the rest of the comp it seems to fall over at this point.
On face value you’d think it was a memory issue, but there have been no memory warnings that I have seen.
My comp is the following: 6720 x 784 pixels, about 70 layers – half or so are footage of various rez/PSDs/AIs and the rest are text layers.
My system specs are in my sig, but memory settings are as follows:-
max mem 120% / max ram cache 60% / secret menu: purge every 15 frames
It is annoying A) because I can’t get a full-res render out of AE and B) because I can’t render anything else later in the queue because after my first job is rendered (which will only happen at QTR res or so) I get this overwrite dialogue box which I obviously don’t see til the next morning!!!
Any ideas guys?
AE7 Pro – Nucleo – Mocha v1.2.0 – PS CS3 – FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30″ ACD / Wacom Intuos 3 A4 / XServe RAID
———————————
Production Studio CS2 – Combustion 3 – Mocha v1.0.1
Win XP Pro 32 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4 / 110GB/80GB/600GB RAID-0 -
6 Replies
-
No, I’m on Mac aswell Dave. 10.4.11.
This is becoming a real problem – if it’s a Nucleo thing then this problem cancels out it’s purpose if we can’t render more than one thing in a queue. Switching it off to render means we might aswell not have it! My collegue is having the same problem on his 8core leopard machine aswell…
I’m doing a render test tonight *without* Nucleo to see if it’s that. I thought it might be a QT thing initially, but my workmate is rendering TGA seqs and having same problem so it’s not that.
As for high-res renders not finishing AT ALL, I will try a full res TGA sequence to a local drive and see if that will finish…will report back tomorrow!
AE7 Pro – Nucleo – Mocha v1.2.0 – PS CS3 – FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30″ ACD / Wacom Intuos 3 A4 / XServe RAID
———————————
Production Studio CS2 – Combustion 3 – Mocha v1.0.1
Win XP Pro 32 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4 / 110GB/80GB/600GB RAID-0 -
actually, no nuceo here, but i generally hear good things about it, and would like to have the features they advertise.
rendering without nucleo is a good way to start troubleshooting this. atleast you can rule out one potential problem.
i assume you are not using quicktime 7.4.0, correct?
it’s interesting that that one render failed at the point same point as a layer began… i’ve run into this occationally with old projects in new ae versions, usually due to an effect (recently it was with light factory 2 plugins specifically on 3d layers). anything special about that layer?
Kevin Camp
Senior Designer
KCPQ, KMYQ & KRCW -
Hi all – thanks for replies…
I didn’t test without Nucleo last night in the end – thought I’d try rendering a local TGA seq, then a QT in the queue first – to try eliminate one thing at a time. Thought it might be that I’m rendering full-res over the network, from the network if that makes sense (all media and project files are stored/read from our XServe and renders are generally done back to it aswell) but that didn’t work!…
My full-res TGA seq got about halfway through (not at the same point as before – I checked and nothing of any real note comes in at that point, so I doubt it’s an effect or particular layer) In AE I got the ‘overwrite…’ dialogue box again and in the render queue both things I set to go last night are still ‘queued’ despite the first one rendering to halfway.
I have tried all manner of reboots, reinstalls, etc to no avail. I am on Quicktime 7.4.1 and my colleague is on 7.4.5, so I can’t see how it can be a QT issue.
I will try the non-Nucleo render tonight to see if it’s that, but my problem is that with one core it might not even get finished doing the render in one night! It’s eating into my working day, but can’t be helped I guess.
If anyone from Gridiron or any long-standing Nucleo users has any ideas that’d be awesome. I’ll post this in Gridiron forum aswell, but I figured AE forum gets the most traffic..
Jim.
AE7 Pro – Nucleo – Mocha v1.2.0 – PS CS3 – FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30″ ACD / Wacom Intuos 3 A4 / XServe RAID
———————————
Production Studio CS2 – Combustion 3 – Mocha v1.0.1
Win XP Pro 32 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4 / 110GB/80GB/600GB RAID-0 -
See https://forums.creativecow.net/readpost/235/91 for suggestions (in the Creative Cow: Gridiron Software forum)
Chris
GridIron Software – Verification and Customer Support
Check our Frequently Asked Questions (https://www.gridironsoftware.com/pg/Nucleo_FAQ) -
I’m just wondering if you’ve had trouble rendering before with the 6720 x 784 frame size. Kinda big. Just curious.
Joey -
This is a new job for me, but our company has been doing these big 5 screen wide HD comps for a few years now, initially on dual-core machines. We now have 4 quads and 1 octocore mac and only recently have I and one other collegue been having this problem…a week or so after we bought Nucleo actually! Weird thing is, I’m getting errors with Nucleo switched off now aswell.
AE7 Pro – Nucleo – Mocha v1.2.0 – PS CS3 – FCP 5.1.4
MacPro Quad 3GHz / ATI 1900XT / 8GB RAM / OSX 10.4.11
30″ ACD / Wacom Intuos 3 A4 / XServe RAID
———————————
Production Studio CS2 – Combustion 3 – Mocha v1.0.1
Win XP Pro 32 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5s / Sony BVM-20G1E / 2 x Dell 2007FP / Wacom Intuos 3 A4 / 110GB/80GB/600GB RAID-0
Reply to this Discussion! Login or Sign Up