Steve Kellener
Forum Replies Created
-
Thank you Declan. I made a text layer, selected it and tried the script and get an error. I wanted to just try and automate this so it simply pulls the name from the output name file (which is based on the project name). Scripting is already a bit beyond me so if the project name is not even available then I guess it won’t work. Amazing that there’s no built-in tool that can do this by now. Thanks again for your help.
—
Steve KellenerDigital Compositor
Titmouse, Inc. -
Looking forward to Layer Tools for CS5. I know that 5.5 is out now. I’m only on CS5 though. Please don’t forget about CS5. 😉
-
Pretty awesome script Peter. I can’t seem to figure out how to have it start on frame 1 rather than frame zero though.
—
Steve KellenerDigital Compositor
Titmouse, Inc. -
Are you using two different monitors? What I have recently found is that QT gets confused as to what gamma it will display when you have two different monitors hooked up. AE seems fine no matter what, it’s QT that changes the display gamma.
Recently here at the studio we have had the gamma issue crop up. We couldn’t understand why. Everything looks fine in AE, but render out a ProRes file and view in QT and it’s completely blown out. We tried everything and nothing seemed to help. Then we tried unplugging the Cinitq that was also hooked up to the system. Guess what? The AE project and the QT with ProRes look identical!! (that’s with color management turned off.)
So I was wondering why we hadn’t noticed this before….well before I had two identical monitors hooked. Right now I have two different monitors hooked up. Unplug one…everything looks fine. Plug in the Cintiq and it goes out of whack again. I also did zap the PRAM, but that wasn’t the real problem. It’s the two different monitors that seem to be causing the headache. Also, to back up this theory, there is one comp artists who hasn’t had this issue…she has two identical monitors!! She doesn’t get the QT display shift at all.
So that is what we have found. It’s not a render issue at all. It’s a QT display issue. Files that I had rendered with the blown out display problem looked fine when I had a single monitor hooked up. I hope this suggestion works for others out there. If anyone else is having the gamma shift issue with two different types of monitors hooked up, please try unplugging one and see what happens. Please post with your results.
—
Steve KellenerDigital Compositor
Titmouse, Inc. -
Happens to me as well with most of the Adobe apps (AE, PS, FL, BR) and Firefox. Takes forever to shut down or they simply crash. When an app closes, shouldn’t it literally close? I mean, you could pull the plug and it would all shut down instantly. 😉
I have an old G4 (dual 1 Ghz PPC) at home. If I close and app on it it’s almost instant. Is this an Intel thing? Amazing how fast the Mac OS can start up these days. Shutting down seems to take forever. Using brand new a Quad 2.66, 4 GB RAM, OS X 10,.4.10