Processing a Video Wall of 143 videos
by jason agar (jasona)
on
Apr 11, 2008 at 1:43:30 am
Hi,
I just constructed a 3D 'curved' video wall in After Effects utilizing Trapcode's Echospace, Slider expressions to controller the spacing between the 'screens,' and a camera mimicking a wide angle lens (zoomed out and moved in). I'm working in Full HD (1920x1080) on a Top of the line Mac Pro - 2 quad core Xeon processors with 16 gb of ram.
Though I'm only using solids as a placeholder, have the workspace resolution down to 1/4 and each individual layer set to draft quality, the computer is running into some processing issues while trying to create a ram preview and may even lock up (even with multi-core processing on). I'm testing with a 10s animation with camera movement and both motion blur on and off. However, I tested a render and, though expectedly slow (20mins with Motion blur on and 1 min with it off), it seems to render out ok.
Now if it's sucking back this much processing now, I can just imagine the troubles I going to run into when I attach a video file to my wall?
Do you have any recommendations on processor saving techniques and work flow which could save this project for me? Other than the obvious-hiding layers,using less videos, or proxies.
This is a doosy, but if I can pull this project together it'll prove to be quite the show piece for me and After Effects gurus alike.
Re: Processing a Video Wall of 143 videos by Wilky Black on May 1, 2008 at 3:05:15 pm
i've had the same problem before. is all of your media on your local drive? that was my problem, as soon as i moved the media from a network server to my local drive the problem went away.
Re: Processing a Video Wall of 143 videos by jason agar on May 1, 2008 at 4:20:13 pm
I found that it also had to do with multiple cores and Open GL. It might be a dumbed down way of looking at it, but there's technically 8 cores in my machine and only one video card for them all to fight over.
It also helps to work in single core mode because there's a lot of information when you hit that preview button which is loaded into the ram.
I was originally boggled because I wasn't working from a network drive and with solids as place holders, so read speed wasn't the issue.
