Brad Bussé
Forum Replies Created
-
Thanks for posting the solution.
-
I don’t remember the outcome, but it very well could be due to the 55mm/Tiffen DFX filters– I use those extensively.
-
Doh! Brain no worky today.
-
Glad I’m not the only one. I normally stabilize with send to Motion, but recently thought I might save some time on a project that needed lots of smoothing by using SmoothCam….
-
I hadn’t hear of this, but if there is a preferred order, I’d love to know.
However, if you’re running Shake, you absolutely have to install Shake before FCS.
-
Thanks Walter,
My concern is that this monitor will primarily be displaying game footage, which has HUD elements that are static and constant. Have you ever experienced image retention on a plasma when working with footage that has a station ID (not a jelly bug, but the full opacity type), or when leaving color bars up for a few hours?
I know that LCD is supposed to be pretty much impervious to image retention, but after 3 years my aluminum 24″ ACD displays developed a bad case. Normally it’s not very noticeable in FCP or AE, but as soon as I open up Shake, the darker shade of grey of the UI makes it really obvious – it almost looks like Shake is being displayed at 80% opacity – I can see all of the windows that were displayed previous to opening Shake for a couple of minutes.
-
No, I didn’t. I’ve had some projects that needed to be addressed, so I’m still running off my Leopard build and haven’t had time to install software on my Snow Leopard install.
For the project that I needed it for last week, I knew that the client was presenting using a PS3, so I was able to instead burn out a slightly higher than blu-ray quality h.264 encoded .mp4 and deliver that on a thumbdrive.
-
I’m currently running FCP 7 on Leopard – it’s upgraded from FCS2, not a fresh install, and I have Shake installed. Perhaps I had installed Shake after FCS2 and that’s the problem? But Compressor works okay. QMaster usually doesn’t, but I’m not alone there.
-
Shane, I agree with this except for AE; as Dave L. mentions in the post below. You’re not pushing AE very hard if 8 GB of RAM isn’t maxed out with AE, FCP, and others all running. I downgraded from 20 GB to 16 GB, and my AE project this summer was really hurting. I’d often be running 2 separate instances of AE for rendering via a script, in addition to a third instance for working (with multi-core enabled). That’s on an octacore. For heavy AE projects, 2 GB per core is really the minimum for stable performance – and that’s running a single instance of AE only – no FCP, Shake, VMWare Fusion, etc.
-
Thanks, I actually got it to work; you have to go to “Video Options” and uncheck Main in the restricted profiles.