Return-Path: Received: from nk11p04mm-asmtpout004.mac.com ([17.158.236.239] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 4781102 for AE-List@media-motion.tv; Fri, 20 Jul 2012 19:47:29 +0200 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_kfPDwqHWwkdmufSyfoFffQ)" Received: from 66.49.40.101.nw.nuvox.net (66.49.40.101.nw.nuvox.net [66.49.40.101]) by nk11p04mm-asmtp004.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0M7H007SA09I0L80@nk11p04mm-asmtp004.mac.com> for AE-List@media-motion.tv; Fri, 20 Jul 2012 17:51:21 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-07-20_03:2012-07-19,2012-07-20,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=2 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1207200182 From: Benny Christensen Subject: Re: [AE] Photoshop CS6 Issues Date: Fri, 20 Jul 2012 12:51:17 -0500 In-reply-to: To: After Effects Mail List References: Message-id: <6D3196A5-B727-49F5-A7FB-984256B387D0@me.com> X-Mailer: Apple Mail (2.1278) --Boundary_(ID_kfPDwqHWwkdmufSyfoFffQ) Content-type: text/plain; CHARSET=US-ASCII Content-transfer-encoding: 7BIT All Photoshop video presets default to 72DPI. My reasoning is that while the program may not care about DPI per say, it affects the program under the hood in ways that made me stop using 300 DPI files. It starting acting sluggish and I would get Memory errors. Benny Christensen Producers Playhouse Oklahoma City 405-858-0700 "It's not enough that we do our best; sometimes we have to do what's required." - Sir Winston Churchill On Jul 20, 2012, at 12:42 PM, Chris Meyer wrote: > Does FCP actually take DPI into account? The very earliest versions of Premiere used to, but most apps have long since let ago of the notion of "DPI" having anything to do with video. > > - Chris > > > > On Jul 20, 2012, at 11:05 AM, Jim Curtis wrote: > >> Perhaps I should elaborate. I've been tasked to do a couple of "slide show" projects (Yikes!). Whenever I brought a bunch of JPEGs in and tried to do Motion moves, and dissolves between them, FCP crashed regularly. When I brought the same stills into Pr, I had no crashes. >> >> And on other projects, where I only had occasional stills, I'd still get crashes from the JPEGs, but not after I converted them to TIF. >> >> That's just been my experience. Maybe it's a codec thing. I think I'm the Pig Pen of finding things that crash Mac apps. >> >> >> >> On Jul 20, 2012, at 11:51 AM, James Culbertson wrote: >> >>> FCP 7.03? JPEGs and PNGs work just fine in my experience. I'm working on a feature length doc that I inherited for finishing tasks that is a smorgasbord of formats - in addition to JPEGs, and PNGs, there are also BMPs, Tiffs, and PSD. No problems whatsoever. What I would avoid are PDFs. >>> >>> If I were to choose I would stick with TIFF and JPEG, and use PSD when necessary. >>> >>> James >>> >>> >>> On Jul 20, 2012, at 7:12 AM, Jim Curtis wrote: >>> >>>> I've had bad luck with most still formats in FCP. It's pretty hostile to JPEGs and PNGs, IME. >>>> >>>> Try TIF or TGA, which also support an alpha channel. TIF is what I use (when I have to.) >>>> >>>> Pr is a LOT better at handling stills, except really large ones. >>>> >>>> >>>> On Jul 20, 2012, at 8:55 AM, Benny Christensen wrote: >>>> >>>>> That has been my workaround, but it is annoying because I don't like to use PSDs in FCP. I usually like a flattened file for titles. >>>>> >>>>> Thanks. >>>>> >>>>> Benny Christensen >>>>> Producers Playhouse >>>>> Oklahoma City >>>>> 405-858-0700 >>>>> >>>>> "To be is to do"--Socrates >>>>> "To do is to be"--Jean-Paul Sartre >>>>> "Do be do be do"--Frank Sinatra >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> On Jul 20, 2012, at 8:52 AM, Glen Tubbesing wrote: >>>>> >>>>>> You might try using Photoshop's native PSD format, instead. >>>>>> >>>>>> On Jul 20, 2012 6:38 AM, "Benny Christensen" wrote: >>>>>> I know this isn't the Photoshop list, but since it is pretty integral to our workflow here goes. >>>>>> >>>>>> I am having a couple of issues lately. >>>>>> >>>>>> 1) PNGs are not acting the same way they used to. I can't get the empty spaces to read as alpha holes in FCP. Is there a better format to use since PICT files are no longer an option. >>>>>> >>>>>> 2) Sometimes the program simply will not let me Save a file. The Save window pops up, but the buttons are not colored and won't react. In fact, at that point the program is completely locked up and I have to Force Quit. >>>>>> >>>>>> Has anyone else seen these problems? >>>>>> >>>>>> Thanks in advance. >>>>>> >>>>>> Benny Christensen >>>>>> Producers Playhouse >>>>>> Oklahoma City >>>>>> 405-858-0700 >>>>>> >>>>>> "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing ever happened." - Sir Winston Churchill >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> +---End of message---+ >>>>>> To unsubscribe send any message to >>>>> >>>> >>> >> > --Boundary_(ID_kfPDwqHWwkdmufSyfoFffQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: quoted-printable All Photoshop = video presets default to 72DPI.

My reasoning = is that while the program may not care about DPI per say, it affects the = program under the hood in ways that made me stop using 300 DPI files. =  It starting acting sluggish and I would get Memory = errors.
<= div>
=

Benny Christensen
Producers = Playhouse
Oklahoma = City
405-858-0700
=

"It's = not enough that we do our best; sometimes we have to do what's = required." - Sir Winston = Churchill

=
=



On Jul 20, 2012, at 12:42 PM, Chris Meyer wrote:

Does FCP actually take DPI into = account? The very earliest versions of Premiere used to, but most apps = have long since let ago of the notion of "DPI" having anything to do = with video.

 - = Chris



On Jul 20, = 2012, at 11:05 AM, Jim Curtis wrote:

Perhaps I should elaborate. =  I've been tasked to do a couple of "slide show" projects (Yikes!). =  Whenever I brought a bunch of JPEGs in and tried to do Motion = moves, and dissolves between them, FCP crashed regularly.  When I = brought the same stills into Pr, I had no crashes. =  

And on other projects, where I only had = occasional stills, I'd still get crashes from the JPEGs, but not after I = converted them to TIF.

That's just been my = experience.  Maybe it's a codec thing.  I think I'm the Pig = Pen of finding things that crash Mac = apps.



On Jul 20, 2012, = at 11:51 AM, James Culbertson wrote:

FCP 7.03?  JPEGs and = PNGs work just fine in my experience. I'm working on a feature length = doc that I inherited for finishing tasks that is a smorgasbord of = formats - in addition to JPEGs, and PNGs, there are also BMPs, Tiffs, =  and PSD. No problems whatsoever. What I would avoid are = PDFs.

If I were to choose I would stick with = TIFF and JPEG, and use PSD when = necessary.

James


On Jul 20, 2012, at 7:12 AM, Jim Curtis wrote:

I've had bad luck with most = still formats in FCP.  It's pretty hostile to JPEGs and PNGs, IME. =  

Try TIF or TGA, which also support an alpha = channel.  TIF is what I use (when I have to.) =  

Pr is a LOT better at handling stills, = except really large ones.


On Jul 20, 2012, at = 8:55 AM, Benny Christensen wrote:

That has been my workaround, = but it is annoying because I don't like to use PSDs in FCP. I usually = like a flattened file for titles.

Thanks.

=
Benny Christensen
Producers = Playhouse
Oklahoma = City
405-858-0700

=
"To be is to = do"--Socrates
"To do is to be"--Jean-Paul Sartre
"Do be do be = do"--Frank = Sinatra
<= /div>







On Jul 20, 2012, at 8:52 AM, Glen Tubbesing = wrote:

You might try using Photoshop's native PSD format, = instead.

On Jul 20, 2012 6:38 AM, "Benny Christensen" = <bennychristensen@me.com> = wrote:
I know this isn't the Photoshop list, but since it is pretty integral to = our workflow here goes.

I am having a couple of issues lately.

1) PNGs are not acting the same way they used to. I can't get the empty = spaces to read as alpha holes in FCP. Is there a better format to use = since PICT files are no longer an option.

2) Sometimes the program simply will not let me Save a file. The Save = window pops up, but the buttons are not colored and won't react. In = fact, at that point the program is completely locked up and I have to = Force Quit.

Has anyone else seen these problems?

Thanks in advance.

Benny Christensen
Producers Playhouse
Oklahoma City
405-858-0700

"Men occasionally stumble over the truth, but most of them pick = themselves up and hurry off as if nothing ever happened." - Sir Winston = Churchill






+---End of message---+
To unsubscribe send any message to <ae-list-off@media-motion.tv>
=






= = --Boundary_(ID_kfPDwqHWwkdmufSyfoFffQ)--